-
Notifications
You must be signed in to change notification settings - Fork 909
/
ims_dialog_admin.xml
1238 lines (1160 loc) · 38 KB
/
ims_dialog_admin.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding='ISO-8859-1'?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
<!-- Include general documentation entities -->
<!ENTITY % docentities SYSTEM "../../../../doc/docbook/entities.xml">
%docentities;
]>
<!-- Module User's Guide -->
<chapter>
<title>&adminguide;</title>
<section>
<title>Overview</title>
<para>
The ims_dialog module provides dialog awareness to the &kamailio; proxy. Its
functionality is to keep track of the current dialogs, to offer information
about them (like how many dialogs are active) or to manage them. The module
exports several functions that could be used directly from scripts.
The ims_dialog module extends the original dialog module by providing support
for forked calling and early dialog termination. It is the intention that
the ims_dialog module will eventually replace the dialog module.
</para>
<para>
The module, via an internal API, also provide the foundation to build on
top of it more complex dialog-based functionalities via other &kamailio;
modules.
</para>
</section>
<section>
<title>How it works</title>
<para>
To create the dialog associated to an initial request, the flag
<quote>dlg_flag</quote> (
<xref linkend="dlg-flag-id"/>) must be set before
creating the corresponding transaction.
</para>
<para>
The dialog is automatically destroyed when a
<quote>BYE</quote> is
received. In case of no
<quote>BYE</quote>, the dialog lifetime is
controlled via the default timeout (see
<quote>default_timeout</quote>
-
<xref linkend="default-timeout-id"/>) and custom timeout (see
<quote>timeout_avp</quote> -
<xref linkend="timeout-avp-id"/>). The
dialog timeout is reset each time a sequential request passes.
</para>
</section>
<section>
<title>Dialog profiling</title>
<para>
Dialog profiling is a mechanism that helps in classifying, sorting and
keeping trace of certain types of dialogs, using whatever properties of
the dialog (like caller, destination, type of calls, etc).
Dialogs can be dynamically added in different (and several) profile
tables - logically, each profile table can have a special meaning (like
dialogs outside the domain, dialogs terminated to PSTN, etc).
</para>
<para>
There are two types of profiles:
<itemizedlist>
<listitem>
<para>
<emphasis>with no value</emphasis> - a dialog simply belongs
to a profile. (like outbound calls profile). There is no other
additional information to describe the dialog's belonging to the
profile;
</para>
</listitem>
<listitem>
<para>
<emphasis>with value</emphasis> - a dialog belongs to a profile
having a certain value (like in caller profile, where the value
is the caller ID). The belonging of the dialog to the profile is
strictly related to the value.
</para>
</listitem>
</itemizedlist>
</para>
<para>
A dialog can be added to multiple profiles in the same time.
</para>
<para>
Profiles are visible (at the moment) in the request route (for initial
and sequential requests) and in the branch, failure and reply routes of
the original request.
</para>
</section>
<section>
<title>Dependencies</title>
<section>
<title>&kamailio; Modules</title>
<para>
The following modules must be loaded before this module:
<itemizedlist>
<listitem>
<para>
<emphasis>TM</emphasis> - Transaction module
</para>
</listitem>
<listitem>
<para>
<emphasis>RR</emphasis> - Record-Route module
</para>
</listitem>
</itemizedlist>
</para>
</section>
<section>
<title>External Libraries or Applications</title>
<para>
The following libraries or applications must be installed before
running &kamailio; with this module loaded:
<itemizedlist>
<listitem>
<para>
<emphasis>None</emphasis>.
</para>
</listitem>
</itemizedlist>
</para>
</section>
</section>
<section>
<title>Parameters</title>
<section>
<title>
<varname>enable_stats</varname> (integer)
</title>
<para>
This function is currently not supported by the ims_dialog module.
To be incorporated in the future.
</para>
</section>
<section>
<title>
<varname>hash_size</varname> (integer)
</title>
<para>
The size of the hash table internally used to keep the dialogs. A
larger table is much faster but consumes more memory. The hash size
must be a power of two number.
</para>
<para>
IMPORTANT: If dialogs' information should be stored in a database,
a constant hash_size should be used, otherwise the restoring process
will not take place. If you really want to modify the hash_size you
must delete all table's rows before restarting the server.
</para>
<para>
<emphasis>
Default value is
<quote>4096</quote>.
</emphasis>
</para>
<example>
<title>Set
<varname>hash_size</varname> parameter
</title>
<programlisting format="linespecific">
...
modparam("ims_dialog", "hash_size", 1024)
...
</programlisting>
</example>
</section>
<section>
<title>
<varname>rr_param</varname> (string)
</title>
<para>
Name of the Record-Route parameter to be added with the dialog cookie.
It is used for the fast dialog matching of sequential requests.
</para>
<para>
<emphasis>
Default value is
<quote>did</quote>.
</emphasis>
</para>
<example>
<title>Set
<varname>rr_param</varname> parameter
</title>
<programlisting format="linespecific">
...
modparam("ims_dialog", "rr_param", "xyz")
...
</programlisting>
</example>
</section>
<section id="dlg-flag-id">
<title>
<varname>dlg_flag</varname> (integer)
</title>
<para>
Flag to be used for marking if a dialog should be constructed for the
current request (this makes sense only for initial requests).
</para>
<para>
<emphasis>
Default value is
<quote>none</quote>.
</emphasis>
</para>
<example>
<title>Set
<varname>dlg_flag</varname> parameter
</title>
<programlisting format="linespecific">
...
modparam("ims_dialog", "dlg_flag", 4)
...
</programlisting>
</example>
</section>
<section id="timeout-avp-id">
<title>
<varname>timeout_avp</varname> (string)
</title>
<para>
The specification of an AVP that contain a custom timeout (in seconds)
for the dialog. It may be used only in a request (initial or sequential)
context
</para>
<para>
<emphasis>
Default value is
<quote>none</quote>.
</emphasis>
</para>
<example>
<title>Set
<varname>timeout_avp</varname> parameter
</title>
<programlisting format="linespecific">
...
modparam("ims_dialog", "timeout_avp", "$avp(i:10)")
...
</programlisting>
</example>
</section>
<section id="default-timeout-id">
<title>
<varname>default_timeout</varname> (integer)
</title>
<para>
The default dialog timeout (in seconds) if no custom one is set.
</para>
<para>
<emphasis>
Default value is
<quote>43200 (12 hours)</quote>.
</emphasis>
</para>
<example>
<title>Set
<varname>default_timeout</varname> parameter
</title>
<programlisting format="linespecific">
...
modparam("ims_dialog", "default_timeout", 21600)
...
</programlisting>
</example>
</section>
<section>
<title>
<varname>dlg_extra_hdrs</varname> (string)
</title>
<para>
A string containing the extra headers (full format, with EOH)
to be added in the requests generated by the module (like BYEs).
</para>
<para>
<emphasis>
Default value is
<quote>NULL</quote>.
</emphasis>
</para>
<example>
<title>Set
<varname>dlf_extra_hdrs</varname> parameter
</title>
<programlisting format="linespecific">
...
modparam("ims_dialog", "dlg_extra_hdrs", "Hint: credit expired\r\n")
...
</programlisting>
</example>
</section>
<section>
<title>
<varname>dlg_match_mode</varname> (integer)
</title>
<para>
Deprecated - in the new dialog module we always match using DID ONLY
</para>
</section>
<section>
<title>
<varname>detect_spirals</varname> (integer)
</title>
<para>
Whether spirals (i.e., messages routed through the proxy multiple times)
should be detected or not.
</para>
<para>
If set to 0, spirals will not be detected and result in the generation of a
new, possibly dangling dialog structure per occurring spiral. If set to 1,
spirals are detected and internally mapped to existing dialog structures.
</para>
<para>
Default value is 1.
</para>
<example>
<title>Set
<varname>detect_spirals</varname> parameter
</title>
<programlisting format="linespecific">
...
modparam("ims_dialog", "detect_spirals", 1)
...
</programlisting>
</example>
</section>
<section>
<title>
<varname>db_url</varname> (string)
</title>
<para>
Db storage not yet supported by ims_dialog - this to be done in future.
</para>
</section>
<section>
<title>
<varname>db_mode</varname> (integer)
</title>
<para>
Db storage not yet supported by ims_dialog - this to be done in future.
</para>
</section>
<section>
<title>
<varname>db_update_period</varname> (integer)
</title>
<para>
Db storage not yet supported by ims_dialog - this to be done in future.
</para>
</section>
<section>
<title>
<varname>db_fetch_rows</varname> (integer)
</title>
<para>
Db storage not yet supported by ims_dialog - this to be done in future.
</para>
</section>
<section>
<title>
<varname>table_name</varname> (string)
</title>
<para>
Db storage not yet supported by ims_dialog - this to be done in future.
</para>
</section>
<section>
<title>
<varname>profiles_with_value</varname> (string)
</title>
<para>
List of names for profiles with values.
</para>
<para>
<emphasis>
Default value is
<quote>empty</quote>.
</emphasis>
</para>
<example>
<title>Set
<varname>profiles_with_value</varname> parameter
</title>
<programlisting format="linespecific">
...
modparam("dialog", "profiles_with_value", "caller ; my_profile")
...
</programlisting>
</example>
</section>
<section>
<title>
<varname>profiles_no_value</varname> (string)
</title>
<para>
List of names for profiles without values.
</para>
<para>
<emphasis>
Default value is
<quote>empty</quote>.
</emphasis>
</para>
<example>
<title>Set
<varname>profiles_no_value</varname> parameter
</title>
<programlisting format="linespecific">
...
modparam("dialog", "profiles_no_value", "inbound ; outbound")
...
</programlisting>
</example>
</section>
<section>
<title>
<varname>bridge_controller</varname> (string)
</title>
<para>
SIP address to be used in From header when initiating a call bridge.
</para>
<para>
<emphasis>
Default value is
<quote>sip:controller@kamailio.org</quote>.
</emphasis>
</para>
<example>
<title>Set
<varname>bridge_controller</varname> parameter
</title>
<programlisting format="linespecific">
...
modparam("dialog", "bridge_controller", "sip:ctd@kamailio.org")
...
</programlisting>
</example>
</section>
<section>
<title>
<varname>initial_cbs_inscript</varname> (string)
</title>
<para>
This has been deprecated since dlg_manage has been removed.
</para>
</section>
</section>
<section>
<title>Functions</title>
<section>
<title>
<function moreinfo="none">set_dlg_profile(profile[, value])</function>
</title>
<para>
Inserts the current dialog into a profile. Note that if the profile does
not supports values, this will be silently discarded. Also, there is
no check for inserting the same dialog in the same profile for multiple
times.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para>
<emphasis>profile</emphasis> - name of the profile to be
added to;
</para>
</listitem>
<listitem>
<para>
<emphasis>value</emphasis> (optional) - string value to
define the belonging of the dialog to the profile - note that the
profile must support values.
Pseudo-variables are supported.
</para>
</listitem>
</itemizedlist>
<para>
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE,
REPLY_ROUTE and FAILURE_ROUTE.
</para>
<example>
<title>
<function>set_dlg_profile</function> usage
</title>
<programlisting format="linespecific">
...
set_dlg_profile("inbound_call");
set_dlg_profile("caller","$fu");
...
</programlisting>
</example>
</section>
<section>
<title>
<function moreinfo="none">unset_dlg_profile(profile[, value])</function>
</title>
<para>
Removes the current dialog from a profile.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para>
<emphasis>profile</emphasis> - name of the profile to be
removed from;
</para>
</listitem>
<listitem>
<para>
<emphasis>value</emphasis> (optional) - string value to
define the belonging of the dialog to the profile - note that the
profile must support values.
Pseudo-variables are supported.
</para>
</listitem>
</itemizedlist>
<para>
This function can be used from BRANCH_ROUTE,
REPLY_ROUTE and FAILURE_ROUTE.
</para>
<example>
<title>
<function>unset_dlg_profile</function> usage
</title>
<programlisting format="linespecific">
...
unset_dlg_profile("inbound_call");
unset_dlg_profile("caller","$fu");
...
</programlisting>
</example>
</section>
<section>
<title>
<function moreinfo="none">is_in_profile(profile[, value])</function>
</title>
<para>
Checks if the current dialog belongs to a profile. If the profile
supports values, the check can be reinforced to take into account a
specific value - if the dialog was inserted into the profile for a
specific value. If no value is passed, only the simply belonging of
the dialog to the profile is checked. Note that if the profile does
not supports values, this will be silently discarded.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para>
<emphasis>profile</emphasis> - name of the profile to be
checked against;
</para>
</listitem>
<listitem>
<para>
<emphasis>value</emphasis> (optional) - string value to
further restrict the check. Pseudo-variables are supported.
</para>
</listitem>
</itemizedlist>
<para>
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE,
REPLY_ROUTE and FAILURE_ROUTE.
</para>
<example>
<title>
<function>is_in_profile</function> usage
</title>
<programlisting format="linespecific">
...
if (is_in_profile("inbound_call")) {
log("this request belongs to an inbound call\n");
}
...
if (is_in_profile("caller","XX")) {
log("this request belongs to a call of user XX\n");
}
...
</programlisting>
</example>
</section>
<section>
<title>
<function moreinfo="none">get_profile_size(profile[, value], size)</function>
</title>
<para>
Returns the number of dialogs belonging to a profile. If the profile
supports values, the check can be reinforced to take into account a
specific value - how many dialogs were inserted into the profile with
a specific value. If no value is passed, only simply belonging of the
dialog to the profile is checked. Note that if the profile does not
supports values, this will be silently discarded.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para>
<emphasis>profile</emphasis> - name of the profile to get
the size for;
</para>
</listitem>
<listitem>
<para>
<emphasis>value</emphasis> (optional) - string value to
further restrict the check. Pseudo-variables are supported;
</para>
</listitem>
<listitem>
<para>
<emphasis>size</emphasis> - an AVP or script variable to
return the profile size in.
</para>
</listitem>
</itemizedlist>
<para>
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE,
REPLY_ROUTE and FAILURE_ROUTE.
</para>
<example>
<title>
<function>get_profile_size</function> usage
</title>
<programlisting format="linespecific">
...
if(get_profile_size("inbound_call","$avp(size)"))
xlog("currently there are $avp(size) inbound calls\n");
...
if(get_profile_size("caller","$fu","$avp(size)"))
xlog("currently, the user $fu has $avp(size) active outgoing calls\n");
...
</programlisting>
</example>
</section>
<section>
<title>
<function moreinfo="none">dlg_isflagset(flag)</function>
</title>
<para>
Check if the dialog flag is set or not.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para>
<emphasis>flag</emphasis> - index of the flag - can be
pseudo-variable.
</para>
</listitem>
</itemizedlist>
<para>
This function can be used from BRANCH_ROUTE,
REQUEST_ROUTE, ONREPLY_ROUTE and FAILURE_ROUTE.
</para>
<example>
<title>
<function>dlg_isflagset</function> usage
</title>
<programlisting format="linespecific">
...
if(dlg_isflagset("1"))
{
...
}
...
</programlisting>
</example>
</section>
<section>
<title>
<function moreinfo="none">dlg_setflag(flag)</function>
</title>
<para>
Set the dialog flag.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para>
<emphasis>flag</emphasis> - index of the flag - can be
pseudo-variable.
</para>
</listitem>
</itemizedlist>
<para>
This function can be used from BRANCH_ROUTE,
REQUEST_ROUTE, ONREPLY_ROUTE and FAILURE_ROUTE.
</para>
<example>
<title>
<function>dlg_setflag</function> usage
</title>
<programlisting format="linespecific">
...
dlg_setflag("1");
...
</programlisting>
</example>
</section>
<section>
<title>
<function moreinfo="none">dlg_resetflag(flag)</function>
</title>
<para>
Reset the dialog flag.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para>
<emphasis>flag</emphasis> - index of the flag - can be
pseudo-variable.
</para>
</listitem>
</itemizedlist>
<para>
This function can be used from BRANCH_ROUTE,
REQUEST_ROUTE, ONREPLY_ROUTE and FAILURE_ROUTE.
</para>
<example>
<title>
<function>dlg_resetflag</function> usage
</title>
<programlisting format="linespecific">
...
redlg_setflag("1");
...
</programlisting>
</example>
</section>
<section>
<title>
<function moreinfo="none">dlg_terminate</function>
</title>
<para>
Terminates a dialog. In ims_dialog module this function now
includes support for early as well as confirmed dialogs.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para>
<emphasis>side</emphasis> - which side to terminate.
It can be: caller, callee or both of them.
</para>
</listitem>
<listitem>
<para>
<emphasis>reason</emphasis> - reason for termination.
</para>
</listitem>
</itemizedlist>
<para>
This function can be used from BRANCH_ROUTE,
REQUEST_ROUTE, ONREPLY_ROUTE and FAILURE_ROUTE.
</para>
<example>
<title>
<function>dlg_terminate</function> usage
</title>
<programlisting format="linespecific">
...
dlg_terminate("all", "Insufficient QoS");
...
</programlisting>
</example>
</section>
<section>
<title>
<function moreinfo="none">dlg_refer(side, address)</function>
</title>
<para>
This function is currently not supported by the ims_dialog module.
To be incorporated in the future.
</para>
</section>
<section>
<title>
<function moreinfo="none">dlg_manage()</function>
</title>
<para>
This has been deprecated in ims_dialog. Instead set dialog flag for
initial INVITE and Route-parameter-callback execution for
within-dialog requests.
</para>
</section>
<section>
<title>
<function moreinfo="none">dlg_bridge(from, to, op)</function>
</title>
<para>
This function is currently not supported by the ims_dialog module.
To be incorporated in the future.
</para>
</section>
<section>
<title>
<function moreinfo="none">dlg_get(callid, ftag, ttag)</function>
</title>
<para>
Search and set current dialog based on Call-ID, From-Tag and To-Tag
parameters.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para><emphasis>callid</emphasis> - SIP call-id.
</para>
</listitem>
<listitem>
<para><emphasis>ftag</emphasis> - SIP From tag.
</para>
</listitem>
<listitem>
<para><emphasis>ttag</emphasis> - SIP To tag.
</para>
</listitem>
</itemizedlist>
<para>
This function can be used from BRANCH_ROUTE,
REQUEST_ROUTE, ONREPLY_ROUTE and FAILURE_ROUTE.
</para>
<example>
<title><function>dlg_get</function> usage</title>
<programlisting format="linespecific">
...
if(dlg_get("abcdef", "123", "456"))
{
dlg_bye("all");
}
...
</programlisting>
</example>
</section>
<section>
<title>
<function moreinfo="none">is_known_dlg()</function>
</title>
<para>
This function is currently not supported by the ims_dialog module.
To be incorporated in the future.
</para>
</section>
</section>
<section>
<title>Exported statistics</title>
<section>
<title>
<varname>active_dialogs</varname>
</title>
<para>
This function is currently not supported by the ims_dialog module.
To be incorporated in the future.
</para>
</section>
<section>
<title>
<varname>early_dialogs</varname>
</title>
<para>
This function is currently not supported by the ims_dialog module.
To be incorporated in the future.
</para>
</section>
<section>
<title>
<varname>processed_dialogs</varname>
</title>
<para>
This function is currently not supported by the ims_dialog module.
To be incorporated in the future.
</para>
</section>
<section>
<title>
<varname>expired_dialogs</varname>
</title>
<para>
This function is currently not supported by the ims_dialog module.
To be incorporated in the future.
</para>
</section>
<section>
<title>
<varname>failed_dialogs</varname>
</title>
<para>
This function is currently not supported by the ims_dialog module.
To be incorporated in the future.
</para>
</section>
</section>
<section>
<title>MI Commands</title>
<section>
<title>
<varname>dlg_list</varname>
</title>
<para>
Lists the description of a dialog or of all dialogs (calls). If only
one dialogs is to be listed, the dialog identifiers are to be passed
as parameter (callid and fromtag). In ims_dialog module this also now
also lists all dlg_out entries for early dialogs.
</para>
<para>
Name:
<emphasis>dlg_list</emphasis>
</para>
<para>Parameters:</para>
<itemizedlist>
<listitem>
<para>
<emphasis>callid</emphasis> (optional) - callid if a single
dialog to be listed.
</para>
</listitem>
<listitem>
<para>
<emphasis>from_tag</emphasis> (optional, but cannot be present
without the callid parameter) - from tag (as per initial request)
of the dialog to be listed. Note that if the from_tag is not
specified, only dialogs created by a request without a from tag
are matched, which will only occur with broken clients and is
thus a very rare situation.
</para>
</listitem>
</itemizedlist>
<para>
MI FIFO Command Format:
</para>
<programlisting format="linespecific">
:dlg_list:_reply_fifo_file_
_empty_line_
</programlisting>
<programlisting format="linespecific">
:dlg_list:_reply_fifo_file_
abcdrssfrs122444@192.168.1.1
AAdfeEFF33
</programlisting>
</section>
<section>
<title>
<varname>dlg_list_ctx</varname>
</title>
<para>
This function is currently not supported by the ims_dialog module.
To be incorporated in the future.
</para>
</section>