[SR-Users] RTPProxy and bridging IPv4/IPv6 with parallel forking

Dan-Cristian Bogos danb.lists at googlemail.com
Wed Apr 13 14:10:17 CEST 2011


Hey Guys,

I was recently playing with gateway-ing IPv4-IPv6 and hit the
following scenario:
 * AOR having contacts on both ipv4 and ipv6 and I wanted to do
parallel forking.

RTPProxy bridging works without any issue on a normal setup, however
the problem shows up when needing to make calls toward rtpproxy to
return both sides of bridge or only one (ee and ie combinations). Did
any of you experiment with this scenario?

EG: Call comes from ipv4, you want to send it to both ipv4 and ipv6.
The branch route looks the right place to call rtpproxy but when
calling unforce_rtp_proxy() on CANCEL, will rtpproxy be aware about
which ports are we trying to cancel? One more issue would be with
re-invite which must go out with the same ip of rtpproxy as original
INVITE. Here we could store the bridge direction in some route
parameter but unfortunately adding route params is not possible in
branches.

So what do u think?

DanB

PS: The "normal" setup of forking calls only ipv4 or only ipv6 works
smooth, so support of ipv6 in kamailio or rtpproxy is not
questionable.



More information about the sr-users mailing list