<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
<br>
<div class="moz-cite-prefix">On 27/02/15 09:26, Sebastian Damm
wrote:<br>
</div>
<blockquote
cite="mid:CABkWSFz4LXrd_VZsXXhNbxSkVsq=5d9KU+U02=wMzJG+saZynQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hi,<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Feb 27, 2015 at 9:07 AM, Juha
Heinanen <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jh@tutpro.com" target="_blank">jh@tutpro.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">Sebastian Damm writes:<br>
<br>
> Does anyone have a hint, how to keep the IPv6
registrations alive? Thanks<br>
> in advance.<br>
<br>
</span>use tcp.<br>
</blockquote>
<div><br>
</div>
<div>Okay, should have added: UDP, please.<br>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
I would use an extra branch flag here.<br>
<br>
Keepalives are sent based on nat_bflag and sipping_bflag. You can
set both no matter it is actually a register from a natted phone or
not.<br>
<br>
The extra flag will be set to mark it is an IPv6 device.<br>
<br>
When doing NAT handling inside the config file, if IPv6 branch flag
is set, you should not engage rtp relaying (unless it is gatewaying
to IPv4) or do other nat specific fixing to headers for the callee.<br>
<br>
Cheers,<br>
Daniel<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - <a class="moz-txt-link-freetext" href="http://www.kamailioworld.com">http://www.kamailioworld.com</a></pre>
</body>
</html>