Browse code

rtpproxy: regenerated readme for flags x and 3

Daniel-Constantin Mierla authored on 17/10/2012 19:41:40
Showing 1 changed files
... ...
@@ -24,6 +24,12 @@ Edited by
24 24
 
25 25
 Sas Ovidiu
26 26
 
27
+Edited by
28
+
29
+Carsten Bock
30
+
31
+   ng-voice GmbH
32
+
27 33
    Copyright � 2003-2008 Sippy Software, Inc.
28 34
 
29 35
    Copyright � 2005 Voice Sistem SRL
... ...
@@ -360,6 +366,8 @@ rtpproxy_offer();
360 366
             the ngcp-mediaproxy-ng rtpproxy at the moment!
361 367
           + 2 - append second Via branch to Call-ID when sending command
362 368
             to rtpproxy. See flag '1' for its meaning.
369
+          + 3 - behave like flag 1 is set for a request and like flag 2 is
370
+            set for a reply.
363 371
           + a - flags that UA from which message is received doesn't
364 372
             support symmetric RTP. (automatically sets the 'r' flag)
365 373
           + l - force "lookup", that is, only rewrite SDP when
... ...
@@ -380,6 +388,12 @@ rtpproxy_offer();
380 388
             Note: As rtpproxy is in bridge mode per default asymmetric,
381 389
             you have to specify the 'w' flag for clients behind NAT! See
382 390
             also above notes!
391
+          + x - this flag will do automatic bridging between IPv4 on the
392
+            "internal network" and IPv6 on the "external network". The
393
+            distinction is done by the given IP in the SDP, e.g. a IPv4
394
+            Address will always call "ie" to the RTPProxy (IPv4(i) to
395
+            IPv6(e)) and an IPv6Address will always call "ei" to the
396
+            RTPProxy (IPv6(e) to IPv4(i)).
383 397
           + f - instructs rtpproxy to ignore marks inserted by another
384 398
             rtpproxy in transit to indicate that the session is already
385 399
             goes through another proxy. Allows creating chain of proxies.