Browse code

dispatcher: removed mi modules from docs example

Daniel-Constantin Mierla authored on 06/01/2017 07:50:49
Showing 2 changed files
... ...
@@ -73,7 +73,7 @@ sip_warning=no
73 73
 mpath="/usr/local/lib/kamailio/modules/"
74 74
 
75 75
 loadmodule "db_mysql.so"
76
-loadmodule "mi_fifo.so"
76
+loadmodule "jsonrpcs.so"
77 77
 loadmodule "kex.so"
78 78
 loadmodule "tm.so"
79 79
 loadmodule "tmx.so"
... ...
@@ -86,7 +86,6 @@ loadmodule "siputils.so"
86 86
 loadmodule "xlog.so"
87 87
 loadmodule "sanity.so"
88 88
 loadmodule "ctl.so"
89
-loadmodule "mi_rpc.so"
90 89
 loadmodule "acc.so"
91 90
 loadmodule "dispatcher.so"
92 91
 
... ...
@@ -94,6 +93,10 @@ loadmodule "dispatcher.so"
94 94
 # ----------------- setting module-specific parameters ---------------
95 95
 
96 96
 
97
+# ----- jsonrpcs params -----
98
+modparam("jsonrpcs", "pretty_format", 1)
99
+
100
+
97 101
 # ----- rr params -----
98 102
 # add value to ;lr param to cope with most of the UAs
99 103
 modparam("rr", "enable_full_lr", 1)
... ...
@@ -424,11 +424,13 @@ modparam("dispatcher", "force_dst", 1)
424 424
 	<section id="dispatcher.p.sock_avp">
425 425
 		<title><varname>sock_avp</varname> (str)</title>
426 426
 		<para>
427
-			The name of the avp which will hold the list with the sockets associated to the addresses stored in dst_avp avp.
427
+			The name of the avp which will hold the list with the sockets
428
+			associated to the addresses stored in dst_avp avp.
428 429
 		</para>
429 430
 		<note>
430 431
 		<para>
431
-			If you want to do load balancing fail over, you have to set this parameter to use the correct socket for each gateway.
432
+			If you want to do load balancing fail over, you have to set
433
+			this parameter to use the correct socket for each gateway.
432 434
 		</para>
433 435
 		</note>
434 436
 		<para>
... ...
@@ -462,10 +464,10 @@ modparam("dispatcher", "force_dst", 1)
462 462
  		</emphasis>
463 463
  		</para>
464 464
  		<example>
465
- 		<title>Use $avp(i:273) for hashing:</title>
465
+ 		<title>Use $avp(hash) for hashing:</title>
466 466
  <programlisting format="linespecific">
467 467
  ...
468
- modparam("dispatcher", "hash_pvar", "$avp(i:273)")
468
+ modparam("dispatcher", "hash_pvar", "$avp(hash)")
469 469
  ...
470 470
  </programlisting>
471 471
  		</example>
... ...
@@ -631,9 +633,13 @@ modparam("dispatcher", "force_dst", 1)
631 631
  	<section id="dispatcher.p.ds_ping_reply_codes">
632 632
  		<title><varname>ds_ping_reply_codes</varname> (string)</title>
633 633
  		<para>
634
-		This parameter defines the valid response codes, which are accepted as a valid reply to the PING-Method.
635
-		It is a list separated by colons, whery you may define either a single code (e.g. "code=202" would accept 202 as an additional, valid response) or a class of responses, you want to accept (e.g. "class=2" would accept everything from 200 to 299 as valid response).
636
-		This parameter can be modified via ser config framework.
634
+			This parameter defines the valid response codes, which are accepted
635
+			as a valid reply to the PING-Method. It is a list separated by
636
+			colons, whery you may define either a single code (e.g. "code=202"
637
+			would accept 202 as an additional, valid response) or a class of
638
+			responses, you want to accept (e.g. "class=2" would accept
639
+			everything from 200 to 299 as valid response). This parameter can
640
+			be modified via config framework.
637 641
  		</para>
638 642
  		<para>
639 643
 			Please note that the response codes the module accepts as valid reply to the
... ...
@@ -666,14 +672,16 @@ modparam("dispatcher", "force_dst", 1)
666 666
 		<itemizedlist>
667 667
 		<listitem>
668 668
 			<para>Value 0: If set to 0, only the gateways with state PROBING are tested.
669
-                              After a gateway is probed, the PROBING state is cleared in this mode.</para>
669
+            After a gateway is probed, the PROBING state is cleared in this mode.</para>
670 670
 		</listitem>
671 671
 		<listitem>
672
-			<para>Value 1: If set to 1, all gateways are tested.  If set to 1 and there is a failure of keepalive
673
-		    		to an active gateway, then it is set to TRYING state.</para>
672
+			<para>Value 1: If set to 1, all gateways are tested.  If set to 1 and
673
+			there is a failure of keepalive to an active gateway, then it is
674
+			set to TRYING state.</para>
674 675
 		</listitem>
675 676
 		<listitem>
676
-			<para>Value 2: if set to 2, only gateways in inactive state with probing mode set are tested.</para>
677
+			<para>Value 2: if set to 2, only gateways in inactive state with
678
+			probing mode set are tested.</para>
677 679
 		</listitem>
678 680
 		<listitem>
679 681
 			<para>Value 3: If set to 3, any gateway with state PROBING is continually probed
... ...
@@ -1369,7 +1377,7 @@ onreply_route {
1369 1369
 
1370 1370
 	<section>
1371 1371
 	<title>RPC Commands</title>
1372
-	<section id="dispatcher.rpc.set_state">
1372
+	<section id="dispatcher.r.set_state">
1373 1373
 		<title>
1374 1374
 		<function moreinfo="none">dispatcher.set_state</function>
1375 1375
 		</title>
... ...
@@ -1408,7 +1416,7 @@ onreply_route {
1408 1408
 ...
1409 1409
 </programlisting>
1410 1410
     </section>
1411
-	<section id="dispatcher.rpc.list">
1411
+	<section id="dispatcher.r.list">
1412 1412
 		<title>
1413 1413
 		<function moreinfo="none">dispatcher.list</function>
1414 1414
 		</title>
... ...
@@ -1426,7 +1434,7 @@ onreply_route {
1426 1426
 		&sercmd; dispatcher.list
1427 1427
 		</programlisting>
1428 1428
     </section>
1429
-	<section id="dispatcher.f.reload">
1429
+	<section id="dispatcher.r.reload">
1430 1430
 		<title>
1431 1431
 		<function moreinfo="none">dispatcher.reload</function>
1432 1432
 		</title>
... ...
@@ -1448,7 +1456,7 @@ onreply_route {
1448 1448
 		</programlisting>
1449 1449
     </section>
1450 1450
 
1451
-	<section id="dispatcher.rpc.ping_active">
1451
+	<section id="dispatcher.r.ping_active">
1452 1452
 		<title>
1453 1453
 		<function moreinfo="none">dispatcher.ping_active</function>
1454 1454
 		</title>