forked from kamailio/kamailio
-
Notifications
You must be signed in to change notification settings - Fork 1
/
rtpengine_admin.xml
1088 lines (1048 loc) · 40.6 KB
/
rtpengine_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 "../../../docbook/entities.xml">
%docentities;
]>
<!-- Module User's Guide -->
<chapter>
<title>&adminguide;</title>
<section>
<title>Overview</title>
<para>
This is a module that enables media streams to be proxied
via an &rtp; proxy. The only &rtp; proxy currently known to work
with this module is the Sipwise rtpengine
<ulink url="https://github.com/sipwise/rtpengine"></ulink>.
The rtpengine module is a modified version of the original
rtpproxy module using a new control protocol. The module is
designed to be a drop-in replacement for the old module from
a configuration file point of view, however due to the
incompatible control protocol, it only works with &rtp; proxies
which specifically support it.
</para>
</section>
<section>
<title>Multiple &rtp; proxy usage</title>
<para>
The rtpengine module can support multiple &rtp; proxies for
balancing/distribution and control/selection purposes.
</para>
<para>
The module allows definition of several sets of rtpproxies.
Load-balancing will be performed over a set and the admin has the
ability to choose what set should be used. The set is selected via
its id - the id being defined with the set. Refer to the
<quote>rtpengine_sock</quote> module parameter definition for syntax
description.
</para>
<para>
The balancing inside a set is done automatically by the module based on
the weight of each &rtp; proxy from the set.
</para>
<para>
The selection of the set is done from script prior using
rtpengine_delete(), rtpengine_offer() or rtpengine_answer()
functions - see the set_rtpengine_set() function.
</para>
<para>
Another way to select the set is to define setid_avp
module parameter and assign setid to the defined avp
before calling rtpengine_offer() or rtpengine_manage()
function. If forwarding of the requests fails and
there is another branch to try, remember to unset the
avp after calling rtpengine_delete() function.
</para>
<para>
For backward compatibility reasons, a set with no id take by default
the id 0. Also if no set is explicitly set before
rtpengine_delete(), rtpengine_offer() or rtpengine_answer()
the 0 id set will be used.
</para>
<para>
IMPORTANT: if you use multiple sets, take care and use the same set for
both rtpengine_offer()/rtpengine_answer() and rtpengine_delete()!!
If the set was selected using setid_avp, the avp needs to be
set only once before rtpengine_offer() or rtpengine_manage() call.
</para>
<para>
From the current implementation point of view, the sets of rtpproxy nodes
are shared memory(shm), so all processes can see a common list of nodes.
There is no locking when setting the nodes enabled/disabled (to keep the
memory access as fast as possible). Thus, problems related to node state
might appear for concurent processes that might set the nodes
enabled/disabled(e.g. by fifo command). This robustness problems are overcomed as follows.
</para>
<para>
If the current process sees the selected node as disabled, the node is
<emphasis>force tested</emphasis> before the current process actually
takes the disabled decision. If the test succeeds, the process will set
the node as enabled (but other concurrent process might still see it as disabled).
.
</para>
<para>
If the current process sees the selected node as enabled, it does no additional checks
and sends the command which will fail in case the machine is actually broken.
The process will set the node as disabled (but other concurrent process might still see it as enabled).
</para>
<para>
The 'kamctl fifo' commands (including rtpengin ones) are executed by an exclusive
process which operate on the same shared memory node list.
</para>
<para>
All the nodes are pinged in the beginning by all the processes,
even if the node list is shared memory.
</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 module</emphasis> - (optional) if you want to
have rtpengine_manage() fully functional
</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 id="rtpengine.p.rtpengine_sock">
<title><varname>rtpengine_sock</varname> (string)</title>
<para>
Definition of socket(s) used to connect to (a set) &rtp; proxy. It may
specify a UNIX socket or an IPv4/IPv6 UDP socket.
</para>
<para>
<emphasis>
Default value is <quote>NONE</quote> (disabled).
</emphasis>
</para>
<example>
<title>Set <varname>rtpengine_sock</varname> parameter</title>
<programlisting format="linespecific">
...
# single rtproxy
modparam("rtpengine", "rtpengine_sock", "udp:localhost:12221")
# multiple rtproxies for LB with weights (missing weight defaults to 1)
modparam("rtpengine", "rtpengine_sock",
"udp:localhost:12221=2 udp:localhost:12222=1")
# multiple sets of multiple rtproxies
modparam("rtpengine", "rtpengine_sock",
"1 == udp:localhost:12221 udp:localhost:12222")
modparam("rtpengine", "rtpengine_sock",
"2 == udp:localhost:12225")
...
</programlisting>
</example>
</section>
<section id="rtpengine.p.rtpengine_disable_tout">
<title><varname>rtpengine_disable_tout</varname> (integer)</title>
<para>
Once an &rtp; proxy was found unreachable and marked as disabled, the rtpengine
module will not attempt to establish communication to that &rtp; proxy for
rtpengine_disable_tout seconds.
</para>
<para>
<emphasis>
Default value is <quote>60</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>rtpengine_disable_tout</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpengine", "rtpengine_disable_tout", 20)
...
</programlisting>
</example>
</section>
<section id="rtpengine.p.rtpengine_tout_ms">
<title><varname>rtpengine_tout_ms</varname> (integer)</title>
<para>
Timeout value expressed in milliseconds in waiting for reply from &rtp; proxy.
</para>
<para>
<emphasis>
Default value is <quote>1000</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>rtpengine_tout_ms</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpengine", "rtpengine_tout_ms", 2000)
...
</programlisting>
</example>
</section>
<section id="rtpengine.p.rtpengine_allow_op">
<title><varname>rtpengine_allow_op</varname> (integer)</title>
<para>
Enable this to allow finishing the current sessions while denying new sessions for the
<emphasis>manually deactivated nodes </emphasis> via kamctl command i.e. "disabled(permanent)" nodes.
Probably the manually deactivated machine is still running(did not crash).
</para>
<para>
This is <emphasis>useful</emphasis> when deactivating a node for maintanance and reject new sessions but allow current ones to finish.
</para>
<para>
<emphasis>
Default value is <quote>0</quote> to keep the current behaviour.
</emphasis>
</para>
<example>
<title>Set <varname>rtpengine_allow_op</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpengine", "rtpengine_allow_op", 1)
...
</programlisting>
</example>
</section>
<section id="rtpengine.p.queried_nodes_limit">
<title><varname>queried_nodes_limit</varname> (integer)</title>
<para>
The total number of nodes inside a set (sets are configurable via rtpengine_sock function) to be queried
before giving up establishing a session. This brings more flexibility in case checking all rtpengines
would take too long. Max limit is 50.
</para>
<para>
<emphasis>
By default all nodes in a set are tried before giving up communicating with the rtpengines.
</emphasis>
</para>
<example>
<title>Set <varname>queried_nodes_limit</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpengine", "queried_nodes_limit", 5)
...
</programlisting>
</example>
</section>
<section id="rtpengine.p.rtpengine_retr">
<title><varname>rtpengine_retr</varname> (integer)</title>
<para>
How many times the module should retry to send and receive after
timeout was generated.
</para>
<para>
<emphasis>
Default value is <quote>5</quote>.
</emphasis>
</para>
<example>
<title>Set <varname>rtpengine_retr</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpengine", "rtpengine_retr", 2)
...
</programlisting>
</example>
</section>
<section id="rtpengine.p.extra_id_pv">
<title><varname>extra_id_pv</varname> (string)</title>
<para>
The parameter sets the PV defination to use when the <quote>b</quote>
parameter is used on rtpengine_delete(), rtpengine_offer(),
rtpengine_answer() or rtpengine_manage() command.
</para><para>
Default is empty, the <quote>b</quote> parameter may not be used then.
</para>
<example>
<title>Set <varname>extra_id_pv</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpengine", "extra_id_pv", "$avp(extra_id)")
...
</programlisting>
</example>
</section>
<section id="rtpengine.p.setid_pv">
<title><varname>setid_avp</varname> (string)</title>
<para>
The parameter defines an AVP that, if set,
determines which &rtp; proxy set
rtpengine_offer(), rtpengine_answer(),
rtpengine_delete(), and rtpengine_manage()
functions use.
</para>
<para>
There is no default value.
</para>
<example>
<title>Set <varname>setid_avp</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpengine", "setid_avp", "$avp(setid)")
...
</programlisting>
</example>
</section>
<section id="rtpengine.p.force_send_interface">
<title><varname>force_send_interface</varname> (string)</title>
<para>
Forces all control messages between the &sip; proxy and
the &rtp; proxy to be sent from the specified local
interface. Both IPv4 and IPv6 addresses are supported. If
not specified, the default interface selected by the
operating system will be used.
Note: when rtpengine_sock is a IPv6 link-local address,
one _must_ set this parameter in order to successfully connect to RTP engine.
This is necessarely because OS needs additional scope_id hint to communicate
over IPv6 link locals. The scope_id is resolved based on the given IPv6.
</para>
<para>
There is no default value.
</para>
<example>
<title>Set <varname>force_send_interface</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpengine", "force_send_interface", "10.3.7.123")
modparam("rtpengine", "force_send_interface", "2001:8d8:1ff:10c0:9a90:96ff:fea8:fd99")
...
</programlisting>
</example>
</section>
<section id="rtpengine.p.read_sdp_pv">
<title><varname>read_sdp_pv</varname> (string)</title>
<para>
If this parameter is set to a valid AVP or script var specifier, rtpengine
will take the input SDP from this pv instead of the message body.
</para>
<para>
There is no default value.
</para>
<example>
<title>Set <varname>read_sdp_pv</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpengine", "read_sdp_pv", "$var(sdp)")
...
route {
...
$var(sdp) = $rb + "a=foo:bar\r\n";
rtpproxy_manage();
}
</programlisting>
</example>
</section>
<section id="rtpengine.p.write_sdp_pv">
<title><varname>write_sdp_pv</varname> (string)</title>
<para>
If this parameter is set to a valid AVP or script var specifier, the
SDP returned by rtpengine in the offer/answer operations
is returned in the specified variable instead of the
message body.
</para>
<para>
There is no default value.
</para>
<example>
<title>Set <varname>write_sdp_pv</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpengine", "write_sdp_pv", "$avp(sdp)")
...
route {
...
rtpproxy_manage();
set_body("$avp(sdp)a=baz123\r\n", "application/sdp");
}
</programlisting>
</example>
</section>
<section id="rtpengine.p.rtp_inst_pvar">
<title><varname>rtp_inst_pvar</varname> (string)</title>
<para>
A pseudo variable to store the chosen RTP Engine IP address.
If this parameter is set, the IP address and port of the instance chosen will be stored in the given variable.
</para>
<para>
By default, this parameter is not set.
</para>
<example>
<title>Set <varname>rtp_inst_pvar</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpproxy", "rtp_inst_pvar", "$avp(RTP_INSTANCE)")
...
</programlisting>
</example>
</section>
<section id="rtpengine.p.hash_table_size">
<title><varname>hash_table_size</varname> (integer)</title>
<para>
Size of the hash table. Default value is 256.
</para>
<para>
NOTE: If configured size is <emphasis>less than</emphasis> 1, the size will be defaulted to 1.
</para>
<example>
<title>Set <varname>hash_table_size</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpproxy", "hash_table_size", "123")
...
</programlisting>
</example>
</section>
<section id="rtpengine.p.hash_table_tout">
<title><varname>hash_table_tout</varname> (integer)</title>
<para>
Number of seconds after an rtpengine hash table entry is marked for deletion.
By default, this parameter is set to 120 (seconds).
</para>
<para>
To maintain information about a selected rtp machine node, for a given call, entries are added in a hashtable of (callid, node) pairs.
When "offer" comes, insert new entry in the hastable.
When subsequent commands come, lookup callid and return chosen node.
When "delete" comes, remove old entry from hashtable.
</para>
<para>
NOTE: In the current implementation, the actual deletion happens <emphasis>on the fly</emphasis>,
while insert/remove/lookup the hastable, <emphasis>only</emphasis> for the entries in the insert/remove/lookup path.
</para>
<example>
<title>Set <varname>hash_table_tout</varname> parameter</title>
<programlisting format="linespecific">
...
modparam("rtpproxy", "hash_table_tout", "300")
...
</programlisting>
</example>
</section>
</section>
<section>
<title>Functions</title>
<section id="rtpengine.f.set_rtpengine_set">
<title>
<function moreinfo="none">set_rtpengine_set(setid[, setid])</function>
</title>
<para>
Sets the ID of the &rtp; proxy set to be used for the next
rtpengine_delete(), rtpengine_offer(), rtpengine_answer()
or rtpengine_manage() command. The parameter can be an integer or
a config variable holding an integer.
</para>
<para>
A second set ID can be specified to daisy-chain two &rtp; proxies.
The two set IDs must be distinct from each other and there must not
be any overlap in the proxies present in both sets. In this use case,
the request (offer, answer, etc) is first sent to an &rtp; proxy from
the first set, which rewrites the &sdp; body and sends it back to the
module. The rewritten &sdp; body is then used to make another request
to an &rtp; proxy from the second set, which rewrites the &sdp; body
another time and sends it back to the module to be placed back into the
&sip; message. This is useful if you have a set of &rtp; proxies that
the caller must use, and another distinct set of &rtp; proxies that the
callee must use. This is supported by all rtpengine commands except
rtpengine_manage().
</para>
<para>
This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE,
BRANCH_ROUTE.
</para>
<example>
<title><function>set_rtpengine_set</function> usage</title>
<programlisting format="linespecific">
...
set_rtpengine_set("2");
rtpengine_offer();
...
</programlisting>
</example>
</section>
<section id="rtpengine.f.rtpengine_offer">
<title>
<function moreinfo="none">rtpengine_offer([flags])</function>
</title>
<para>
Rewrites &sdp; body to ensure that media is passed through
an &rtp; proxy. To be invoked
on INVITE for the cases the &sdp; bodies are in INVITE and 200 OK and on 200 OK
when &sdp; bodies are in 200 OK and ACK.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
<listitem>
<para>
<emphasis>flags</emphasis> - flags to turn on some features.
</para>
<para>The <quote>flags</quote> string is a list of space-separated items. Each item
is either an individual token, or a token in <quote>key=value</quote> format. The
possible tokens are described below.</para>
<itemizedlist>
<listitem><para>
<emphasis>via-branch=...</emphasis> - Include the <quote>branch</quote>
value of one of the <quote>Via</quote> headers in the request to the
&rtp; proxy. Possible values are:
<quote>1</quote> - use the first <quote>Via</quote> header;
<quote>2</quote> - use the second <quote>Via</quote> header;
<quote>auto</quote> - use the first <quote>Via</quote> header if this is
a request, or the second one if this is a reply;
<quote>extra</quote> - don't take the value from a header, but instead use
the value of the <quote>extra_id_pv</quote> variable.
This can be used to create one media session per branch
on the &rtp; proxy. When sending a subsequent <quote>delete</quote> command to
the &rtp; proxy, you can then stop just the session for a specific branch when
passing the flag '1' or '2' in the <quote>rtpengine_delete</quote>, or stop
all sessions for a call when not passing one of those two flags there. This is
especially useful if you have serially forked call scenarios where the &rtp; proxy
gets an <quote>offer</quote> command for a new branch, and then a
<quote>delete</quote> command for the previous branch, which would otherwise
delete the full call, breaking the subsequent <quote>answer</quote> for the
new branch. <emphasis>This flag is only supported by the Sipwise rtpengine
&rtp; proxy at the moment!</emphasis>
</para></listitem>
<listitem><para>
<emphasis>asymmetric</emphasis> - flags that UA from which message is
received doesn't support symmetric &rtp;. Disables learning of endpoint addresses
in the Sipwise rtpengine proxy.
</para></listitem>
<listitem><para>
<emphasis>force-answer</emphasis> - force <quote>answer</quote>, that is,
only rewrite &sdp; when corresponding session already exists
in the &rtp; proxy. By default is on when the session is to be
completed.
</para></listitem>
<listitem><para>
<emphasis>direction=...</emphasis> - this option specifies a logical network
interface and should be given exactly twice. It enables &rtp; bridging between
different addresses or networks of the same family (e.g. IPv4 to IPv4). The
first instance of the option
specifies the interface that the originator of this message should be using,
while the second instance specifies the interface that the target should be
using. For example, if the &sip; message was sent by an endpoint on a private
network and will be sent to an endpoint on the public internet, you would use
<quote>direction=priv direction=pub</quote> if those two logical network
interfaces were called <quote>priv</quote> and <quote>pub</quote> in your
&rtp; proxy's configuration respectively. The direction must only be specified
in for initial &sdp; offer; answers or subsequent offers can omit this option.
</para></listitem>
<listitem><para>
<emphasis>internal, external</emphasis> - shorthand for
<quote>direction=internal</quote> and <quote>direction=external</quote>
respectively. Useful for brevity or as legacy option if the &rtp; proxy only
supports two network interfaces instead of multiple, arbitrarily named ones.
</para></listitem>
<listitem><para>
<emphasis>auto-bridge</emphasis> - this flag an alternative to the
<quote>internal</quote> and <quote>external</quote> flags
in order to do automatic bridging between IPv4 on the
"internal network" and IPv6 on the "external network". Instead of
explicitly instructing the &rtp; proxy to select a particular address
family, the distinction is done by the given IP in the &sdp; body by
the &rtp; proxy itself. Not supported by Sipwise rtpengine.
</para></listitem>
<listitem><para>
<emphasis>address-family=...</emphasis> - instructs the &rtp; proxy that the
recipient of this &sdp; body expects to see addresses of a particular family.
Possible values are <quote>IP4</quote> and <quote>IP6</quote>. For example,
if the &sdp; body contains IPv4 addresses but the recipient only speaks IPv6,
you would use <quote>address-family=IP6</quote> to bridge between the two
address families.
</para><para>
Sipwise rtpengine remembers the address family preference of each party after
it has seen an &sdp; body from them. This means that normally it is only
necessary to explicitly specify the address family in the <quote>offer</quote>,
but not in the <quote>answer</quote>.
</para><para>
Note: Please note, that this will only work properly with non-dual-stack user-agents or with
dual-stack clients according to RFC6157 (which suggest ICE for Dual-Stack implementations).
This short-cut will not work properly with RFC4091 (ANAT) compatible clients, which suggests
having different m-lines with different IP-protocols grouped together.
</para></listitem>
<listitem><para>
<emphasis>force</emphasis> - instructs the &rtp; proxy to ignore marks
inserted by another &rtp; proxy in transit to indicate that the
session is already goes through another proxy. Allows creating
a chain of proxies. Not supported and ignored by Sipwise rtpengine.
</para></listitem>
<listitem><para>
<emphasis>trust-address</emphasis> - flags that IP address in &sdp; should
be trusted. Starting with rtpengine 3.8, this is the default behaviour.
In older versions, without this flag the &rtp; proxy ignores the address in
the &sdp; and uses source address of the &sip; message as media
address which is passed to the &rtp; proxy.
</para></listitem>
<listitem><para>
<emphasis>SIP-source-address</emphasis> - the opposite of
<emphasis>trust-address</emphasis>. Restores the old default behaviour
of ignoring endpoint addresses in the &sdp; body.
</para></listitem>
<listitem><para>
<emphasis>replace-origin</emphasis> - flags that IP from the origin
description (o=) should be also changed.
</para></listitem>
<listitem><para>
<emphasis>replace-session-connection</emphasis> - flags to change the session-level
&sdp; connection (c=) IP if media description also includes
connection information.
</para></listitem>
<listitem><para>
<emphasis>symmetric</emphasis> - flags that for the UA from which
message is received, support symmetric &rtp; must be forced. Does nothing with
the Sipwise rtpengine proxy as it is the default.
</para></listitem>
<listitem><para>
<emphasis>repacketize=NN</emphasis> - requests the &rtp; proxy to perform
re-packetization of &rtp; traffic coming from the UA which
has sent the current message to increase or decrease payload
size per each &rtp; packet forwarded if possible. The NN is the
target payload size in ms, for the most codecs its value should
be in 10ms increments, however for some codecs the increment
could differ (e.g. 30ms for GSM or 20ms for G.723). The
&rtp; proxy would select the closest value supported by the codec.
This feature could be used for significantly reducing bandwith
overhead for low bitrate codecs, for example with G.729 going
from 10ms to 100ms saves two thirds of the network bandwith.
Not supported by Sipwise rtpengine.
</para></listitem>
<listitem><para>
<emphasis>ICE=...</emphasis> - controls the &rtp; proxy's behaviour
regarding ICE attributes within the &sdp; body. Possible values
are: <quote>force</quote> -
discard any ICE attributes already present in the &sdp; body
and then generate and insert new ICE data, leaving itself
as the <emphasis>only</emphasis> ICE candidates;
<quote>force-relay</quote> -
discard any <quote>relay</quote> type ICE attributes already present
in the &sdp; body and then generate and insert itself
as the <emphasis>only</emphasis> ICE <quote>relay</quote> candidates;
<quote>remove</quote> instructs the &rtp; proxy to discard
any ICE attributes and not insert any new ones into the &sdp;.
The default (if no <quote>ICE=...</quote> is given at all),
new ICE data will only be generated
if no ICE was present in the &sdp; originally; otherwise
the &rtp; proxy will only insert itself as
<emphasis>additional</emphasis> ICE candidate. Other
&sdp; substitutions (c=, m=, etc) are unaffected by this flag.
</para></listitem>
<listitem><para>
<emphasis>RTP, SRTP, AVP, AVPF</emphasis> - These flags control the &rtp;
transport protocol that should be used towards the recipient of
the &sdp;. If none of them are specified, the protocol given in
the &sdp; is left untouched. Otherwise, the <quote>SRTP</quote> flag indicates that
SRTP should be used, while <quote>RTP</quote> indicates that SRTP should not be used.
<quote>AVPF</quote> indicates that the advanced RTCP profile with feedback messages
should be used, and <quote>AVP</quote> indicates that the regular RTCP profile
should be used. See also the next set of flags below.
</para></listitem>
<listitem><para>
<emphasis>RTP/AVP, RTP/SAVP, RTP/AVPF, RTP/SAVPF</emphasis> - these serve as
an alternative, more explicit way to select between the different &rtp; protocols
and profiles supported by the &rtp; proxy. For example, giving the flag
<quote>RTP/SAVPF</quote> has the same effect as giving the two flags
<quote>SRTP AVPF</quote>.
</para></listitem>
<listitem><para>
<emphasis>to-tag</emphasis> - force inclusion of the <quote>To</quote> tag.
Normally, the <quote>To</quote> tag is always included when present, except
for <quote>delete</quote> messages. Including the <quote>To</quote> tag in
a <quote>delete</quote> messages allows you to be more selective about which
dialogues within a call are being torn down.
</para></listitem>
<listitem><para>
<emphasis>rtcp-mux-demux</emphasis> - if rtcp-mux (RFC 5761) was
offered, make the &rtp; proxy accept the offer, but not offer it to the
recipient of this message.
</para></listitem>
<listitem><para>
<emphasis>rtcp-mux-reject</emphasis> - if rtcp-mux was offered, make the
&rtp; proxy reject the offer, but still offer it to the recipient. Can be
combined with <quote>rtcp-mux-offer</quote> to always offer it.
</para></listitem>
<listitem><para>
<emphasis>rtcp-mux-offer</emphasis> - make the &rtp; proxy offer rtcp-mux
to the recipient of this message, regardless of whether it was offered
originally or not.
</para></listitem>
<listitem><para>
<emphasis>rtcp-mux-accept</emphasis> - if rtcp-mux was offered, make the
&rtp; proxy accept the offer and also offer it to the recipient of this
message. Can be combined with <quote>rtcp-mux-offer</quote> to always offer it.
</para></listitem>
<listitem><para>
<emphasis>media-address=...</emphasis> - force a particular media address to
be used in the &sdp; body. Address family is detected automatically.
</para></listitem>
<listitem><para>
<emphasis>TOS=...</emphasis> - change the IP TOS value for all outgoing &rtp;
packets within the entire call in both directions. Only honoured in an
<quote>offer</quote>, ignored for an <quote>answer</quote>. Valid values are
0 through 255, given in decimal. If this option is not specified, the TOS
value will revert to the default TOS (normally 184). A value of -1 may be used
to leave the currently used TOS unchanged.
</para></listitem>
<listitem><para>
<emphasis>delete-delay=...</emphasis> - override the default delay (in seconds)
before a call is actually deleted from memory. Can be set to zero to effectuate
immediate deletion. This option only makes sense for <emphasis>delete</emphasis>
operations.
</para></listitem>
<listitem><para>
<emphasis>strict-source</emphasis> - instructs the &rtp; proxy to check the
source addresses of all incoming &rtp; packets and drop the packets if the
address doesn't match.
</para></listitem>
<listitem><para>
<emphasis>media-handover</emphasis> - the antithesis of
<emphasis>strict-source</emphasis>. Instructs the &rtp; proxy not only to accept
mismatching &rtp; source addresses (as it normally would), but also to accept
them as the new endpoint address of the opposite media flow. Not recommended
as it allows media streams to be hijacked by an attacker.
</para></listitem>
<listitem><para>
<emphasis>DTLS=...</emphasis> - influence the behaviour of DTLS-SRTP. Possible
values are <quote>no</quote> or <quote>off</quote> to suppress offering or
accepting DTLS-SRTP, and <quote>passive</quote> to prefer participating in
DTLS-SRTP in a passive role.
</para></listitem>
<listitem><para>
<emphasis>SDES-off</emphasis> - don't offer SDES when it normally would. In an SRTP
context, this leaves DTLS-SRTP as the only other option.
</para></listitem>
<listitem><para>
<emphasis>SDES-unencrypted_srtp, SDES-unencrypted_srtcp,
SDES-unauthenticated_srtp</emphasis> - these directly reflect the SDES session
parameters from RFC 4568 and will make the &rtp; proxy offer these parameters
when offering SDES.
</para></listitem>
<listitem><para>
<emphasis>SDES-encrypted_srtp, SDES-encrypted_srtcp,
SDES-authenticated_srtp</emphasis> - the opposites of the flags above. Useful
if accepting these parameters is not desired and they should be rejected instead.
</para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<para>
This function can be used from ANY_ROUTE.
</para>
<example>
<title><function>rtpengine_offer</function> usage</title>
<programlisting format="linespecific">
route {
...
if (is_method("INVITE")) {
if (has_body("application/sdp")) {
if (rtpengine_offer())
t_on_reply("1");
} else {
t_on_reply("2");
}
}
if (is_method("ACK") && has_body("application/sdp"))
rtpengine_answer();
...
}
onreply_route[1]
{
...
if (has_body("application/sdp"))
rtpengine_answer();
...
}
onreply_route[2]
{
...
if (has_body("application/sdp"))
rtpengine_offer();
...
}
</programlisting>
</example>
</section>
<section id="rtpengine.f.rtpengine_answer">
<title>
<function moreinfo="none">rtpengine_answer([flags])</function>
</title>
<para>
Rewrites &sdp; body to ensure that media is passed through
an &rtp; proxy. To be invoked
on 200 OK for the cases the &sdp; bodies are in INVITE and 200 OK and on ACK
when &sdp; bodies are in 200 OK and ACK.
</para>
<para>
See rtpengine_offer() function description above for the meaning of the
parameters.
</para>
<para>
This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE,
FAILURE_ROUTE, BRANCH_ROUTE.
</para>
<example>
<title><function>rtpengine_answer</function> usage</title>
<para>
See rtpengine_offer() function example above for example.
</para>
</example>
</section>
<section id="rtpengine.f.rtpengine_delete">
<title>
<function moreinfo="none">rtpengine_delete([flags])</function>
</title>
<para>
Tears down the RTPProxy session for the current call.
</para>
<para>
See rtpengine_offer() function description above for the meaning of the
parameters. Note that not all flags make sense for a <quote>delete</quote>.
</para>
<para>
This function can be used from ANY_ROUTE.
</para>
<example>
<title><function>rtpengine_delete</function> usage</title>
<programlisting format="linespecific">
...
rtpengine_delete();
...
</programlisting>
</example>
</section>
<section id="rtpengine.f.rtpengine_manage">
<title>
<function moreinfo="none">rtpengine_manage([flags])</function>
</title>
<para>
Manage the RTPProxy session - it combines the functionality of
rtpengine_offer(), rtpengine_answer() and rtpengine_delete(), detecting
internally based on message type and method which one to execute.
</para>
<para>
It can take the same parameters as <function>rtpengine_offer().</function>
The flags parameter to rtpengine_manage() can be a configuration variable
containing the flags as a string.
</para>
<para>
Functionality:
</para>
<itemizedlist>
<listitem>
<para>
If INVITE with &sdp;, then do <function>rtpengine_offer()</function>
</para>
</listitem>
<listitem>
<para>
If INVITE with &sdp;, when the tm module is loaded, mark transaction with
internal flag FL_SDP_BODY to know that the 1xx and 2xx are for
<function>rtpengine_answer()</function>
</para>
</listitem>
<listitem>
<para>
If ACK with &sdp;, then do <function>rtpengine_answer()</function>
</para>
</listitem>
<listitem>
<para>
If BYE or CANCEL, or called within a FAILURE_ROUTE[], then do <function>rtpengine_delete()</function>
</para>
</listitem>
<listitem>
<para>
If reply to INVITE with code >= 300 do <function>rtpengine_delete()</function>
</para>
</listitem>
<listitem>
<para>
If reply with &sdp; to INVITE having code 1xx and 2xx, then
do <function>rtpengine_answer()</function> if the request had &sdp; or tm is not loaded,
otherwise do <function>rtpengine_offer()</function>
</para>
</listitem>
</itemizedlist>
<para>
This function can be used from ANY_ROUTE.
</para>
<example>
<title><function>rtpengine_manage</function> usage</title>
<programlisting format="linespecific">
...
rtpengine_manage();
...
</programlisting>
</example>
</section>
<section id="rtpengine.f.start_recording">
<title>
<function moreinfo="none">start_recording()</function>
</title>
<para>
This function will send a signal to the &rtp; proxy to record
the &rtp; stream on the &rtp; proxy.
<emphasis>This function is not supported by Sipwise rtpengine at the moment!</emphasis>
</para>
<para>
This function can be used from REQUEST_ROUTE and ONREPLY_ROUTE.
</para>
<example>
<title><function>start_recording</function> usage</title>
<programlisting format="linespecific">
...
start_recording();
...
</programlisting>
</example>
</section>
</section>
<section>
<title>Exported Pseudo Variables</title>
<section>
<title><function moreinfo="none">$rtpstat</function></title>
<para>
Returns the &rtp; statistics from the &rtp; proxy. The &rtp; statistics from the &rtp; proxy
are provided as a string and it does contain several packet counters. The statistics
must be retrieved before the session is deleted (before <function>rtpengine_delete()</function>).
</para>
<example>
<title>$rtpstat Usage</title>
<programlisting format="linespecific">
...
append_hf("X-RTP-Statistics: $rtpstat\r\n");
...
</programlisting>
</example>
</section>
</section>
<section>
<title><acronym>MI</acronym> Commands</title>
<section id="rtpengine.m.nh_enable_rtpp">
<title><function moreinfo="none">nh_enable_rtpp proxy_url/all 0/1</function></title>
<para>
Enables a &rtp; proxy if the second parameter value is greater than 0. Disables it if a zero value is given.
The first parameter is either a specific &rtp; proxy url (exactly as defined in
the config file) or the keyword <emphasis>all</emphasis>.
The second parameter value must be a number in decimal.
</para>
<para>
When try to enable the &rtp; proxy, an application ping command is sent to it.
If it fails, the proxy is not enabled.
Displays <emphasis>success</emphasis> or <emphasis>fail</emphasis> when try to enable/disable.
</para>
<para>
NOTE: If a &rtp; proxy is defined multiple times (in the same or diferent sets), all of its instances will be enabled/disabled.
</para>
<para>
NOTE: If a &rtp; proxy is in the disabled permanent state and one tries to enable it, even if the ping fails,
it is moved to a disabled temporary state and a recheck_ticks are given to it.
While the recheck_ticks are grater than 0, the proxy is considered disabled temporary, and it is not taken into consideration for sending data.
When the recheck_ticks are 0, the proxy is retested <emphasis>when trying to send data</emphasis>(not automatically retested), and data can be send to it on success.
</para>
<para>
NOTE: When specify the IPv6 &rtp; proxy url one must prefix it with <emphasis>::</emphasis>
to escape the :: from the IPv6 address. See the example below.
</para>
<example>
<title>
<function moreinfo="none">nh_enable_rtpp</function> usage</title>
<programlisting format="linespecific">
...