If does not work with one instance, I would use branch flags to mark the branch doing ipv4 to ipv6 translation and engage a dedicated rtpproxy for it. You can run two rtpproxy-es on the same server, in different sets: http://kamailio.org/docs/modules/stable/modules_k/rtpproxy.html#id3012059 http://kamailio.org/docs/modules/stable/modules_k/rtpproxy.html#id3009496 So the branch doing ipv4-ipv6 will have a flag set and use a particular rtpproxy. On the 200ok, you can check the branch flag and engage again the proper rtpproxy.

14 apr 2011 kl. 09.48 skrev Klaus Darilion: > > > Am 13.04.2011 15:55, schrieb Daniel-Constantin Mierla: >> If does not work with one instance, I would use branch flags to >> mark the branch doing ipv4 to ipv6 translation and engage a >> dedicated rtpproxy for it. You can run two rtpproxy-es on the >> same server, in different sets: >> http://kamailio.org/docs/modules/stable/modules_k/rtpproxy.html#id3012059 >> >>

Now you have opened a can of worms. Let me start :-) If I have a dual stack UA and registers with an IPv4 address - how do you know that I'm dual stack? I really don't need an RTP proxy.

The IETF thinks we should use SIP outbound and register twice. Kamailio doesn't support this as far as I remember and won't see that we have two locations for the very same UA. Now, if you have a URI like "sip:board@kamailio.org" and that URI's domain has two priority levels of SRV records. The first level is only IPv4 and the second level includes IPv6 to indicate a preference to receive calls in IPv4 and an ability to receive them in IPv6 if that's preferred by the caller. Would Kamailio understand this?

There is work to be done here. /O _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

14 apr 2011 kl. 09.48 skrev Klaus Darilion: Now you have opened a can of worms. Let me start :-) If I have a dual stack UA and registers with an IPv4 address - how do you know that I'm dual stack? I really don't need an RTP proxy. The IETF thinks we should use SIP outbound and register twice. Kamailio doesn't support this as far as I remember and won't see that we have two locations for the very same UA.

Now, if you have a URI like "sip:board@kamailio.org" and that URI's domain has two priority levels of SRV records. The first level is only IPv4 and the second level includes IPv6 to indicate a preference to receive calls in IPv4 and an ability to receive them in IPv6 if that's preferred by the caller. Would Kamailio understand this? There is work to be done here. /O _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Am 13.04.2011 15:55, schrieb Daniel-Constantin Mierla: That's a nice idea. Some time ago I tried the same setup and failed. Are there some easy methods to find out if a target is IPv4 or IPv6, e.g. something like if ( is_ipv6("$rd") ) { ... }

Hey there Daniel, Many thanks for so fast reply! I will test the scenario recommended in our labs and come back to you asap. The only thing which is still not clear to me is how to "store" the used rtp set, so I can re-use it with INVITEs. The thing which I have experienced is that on INVITE it is easy to spot the right configuration since I know the address family of both originator(af param) and destination(based on location), however on re-invite it will help to have the setup loaded from somewhere. My idea was route parameters, but impossible to set them in branches right now. Another option will be to decide based on origination/termination address family, but the termination one is right now available only in onsend routes where the rtpproxy functions are not in.

Ta, DanB On Wed, Apr 13, 2011 at 3:55 PM, Daniel-Constantin Mierla <miconda(a)gmail.com> wrote: > Hello, > > On 4/13/11 2:10 PM, Dan-Cristian Bogos wrote: >> 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? > interesting setup, indeed, but for sure to become very common in the near > future, personally I haven't got to this scenario yet :-) > > If does not work with one instance, I would use branch flags to mark the > branch doing ipv4 to ipv6 translation and engage a dedicated rtpproxy for > it. You can run two rtpproxy-es on the same server, in different sets: > http://kamailio.org/docs/modules/stable/modules_k/rtpproxy.html#id3012059 > http://kamailio.org/docs/modules/stable/modules_k/rtpproxy.html#id3009496 > > So the branch doing ipv4-ipv6 will have a flag set and use a particular > rtpproxy. On the 200ok, you can check the branch flag and engage again the > proper rtpproxy. > > Cheers, > Daniel > >> 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. > -- > Daniel-Constantin Mierla > http://www.asipto.com > >