<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 3/25/2013 9:46 AM, Olle E. Johansson wrote:
<blockquote
cite="mid:527762E2-32D4-435E-9692-0B295FC321F7@edvina.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<base href="x-msg://2/"><br>
<div>
<div>25 mar 2013 kl. 09:23 skrev Miguel Baptista <<a
moz-do-not-send="true"
href="mailto:miguel.baptista@uninett.no">miguel.baptista@uninett.no</a>>:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000" style="font-family:
Helvetica; font-size: medium; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2; text-align:
-webkit-auto; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; ">Hello,<br>
<br>
I have been doing some tests with kamailio and IPv6.<span
class="Apple-converted-space"> </span><br>
<br>
My initial setup was IPv6 only and now am I extending it to
a dual-stack environment. Well, and now I am starting to
face some (interesting) challenges.<br>
<br>
So, the first step in the dual-stack environment was to
install RTP Proxy and configured kamailio to use it. With
this setup, the UAs locally registered were able to
communicate with each-other no matter with address family
(IPv4/IPv6) they were using. So far so good.<br>
<br>
But now I want to extend my tests a bit more ... I want to
communicate with the "outside world" (using ENUM and domain
based SIP URIs). Do I have a way to know if the
"destination" is IPv4 or IPv6? Because I need that
information in order to properly bridge the calls on
rtpproxy.<span class="Apple-converted-space"> </span><br>
<br>
I tried to use the onsend_route but it didn't work. I mean,
I am able to know if the "next-hop" is IPv6 or IPv4 but it
seems that it is "too late" to use rtpproxy. BTW ... I am
assuming that if the "next-hop" is IPv6 then the final user
agent will also be IPv6 (the same for IPv4)<span
class="Apple-converted-space"> </span><br>
<br>
Should I use some other approach? For example, failure route
instead?<span class="Apple-converted-space"> </span><br>
Does anyone have a similiar setup? How are you solving this
issue?<br>
</div>
</blockquote>
</div>
<br>
<div>The only way you can get an indication of the other end is to
check their SRV records, but that doesn't say anything about the
devices and their media capability. The best way moving forward
is to support ICE for exactly this case.</div>
<div><br>
</div>
<div>The RFC for SIP IPv6 migration says that it's the IPv6
supporting device's responsibility to send an offer with dual
stack support, so your callers need to make sure you have both
IPv4 and IPv6 addresses in the ICE candidates in the SDP offer.</div>
<div><br>
</div>
<div>As I'm currently hacking SNMP, can you please check if there
are any issues with IPv6 in the SNMPstats module?</div>
<div><br>
</div>
<div>/O<br>
</div>
<br>
</blockquote>
Thanks for your feedback Olle.
<blockquote
cite="mid:527762E2-32D4-435E-9692-0B295FC321F7@edvina.net"
type="cite">
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
</body>
</html>