<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I get you.<div>The good thing with TCP is that most routers have a TCP NAT KeepAlive timer around 1 hour.</div><div>The onlly issue I see with a 3600s registration timer is if the registrar looses the registration for any reason.</div><div>It seems some phones do not always try to re-register before the timeout if they loose their registration.</div><div>Have you tested the Aastra with this ?</div><div><br></div><div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" color="#1C00FF">David Ponzone </font><font class="Apple-style-span" color="#000000" size="3"><span class="Apple-style-span" style="font-size: 12px; ">Direction Technique</span></font></font></div><div><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px; ">email: <a href="mailto:david.ponzone@ipeva.fr">david.ponzone@ipeva.fr</a></span></font></font></div><div><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px; ">tel: 01 74 03 18 97</span></font></font></div><div><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px; ">gsm: 06 66 98 76 34</span></font></font></div><div><font class="Apple-style-span" face="'Helvetica Neue'"><br></font></div><div><font class="Apple-style-span" color="#1C00FF" face="'Helvetica Neue'">Service Client<span class="Apple-converted-space"> </span></font><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" color="#FF0000">IP</font></font><font class="Apple-style-span" color="#1C00FF" face="'Helvetica Neue'">eva</font></div><div><font class="Apple-style-span" color="#1C00FF" face="'Helvetica Neue'"><span class="Apple-style-span" style="color: rgb(0, 0, 0); font-family: Helvetica; "><div><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px; ">tel: 0811 46 26 26</span></font></font></div><div><font class="Apple-style-span" face="'Helvetica Neue'" size="3"><span class="Apple-style-span" style="font-size: 13px; "><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Arial; color: rgb(0, 34, 243); "><span style="text-decoration: underline; "><a href="BLOCKED::http://www.ipeva.fr/">www.ipeva.fr</a></span><span style="color: rgb(101, 104, 149); "> - <span style="color: rgb(0, 34, 243); text-decoration: underline; "><a href="BLOCKED::http://www.ipeva-studio.com/">www.ipeva-studio.com</a></span></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Arial; color: rgb(0, 34, 243); "><span class="Apple-style-span" style="text-decoration: underline; "><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 10px/normal Arial; color: rgb(0, 34, 243); "><span class="Apple-style-span"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; text-align: justify; font: normal normal normal 10px/normal Arial; color: rgb(192, 192, 192); "><i>Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. </i><b><i>IPeva</i></b><i> décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur.</i></div><div style="text-decoration: underline; text-align: justify; "><font class="Apple-style-span" color="#C0C0C0"><i><br></i></font></div></span></div></span></font></div></span></font></div></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br><div><div>Le 10/02/2011 à 17:33, Philippe Sultan a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Well, I was looking for something like what's implemented in the<br>Thomson ST2030 series, that is, have the phone initiate SIP OPTIONS,<br>and process them with SER.<br><br>I was not able to find such a mechanism, but digging in the docs, it<br>appears that I can just use SIP over TCP and keep the connection<br>maintained using TCP keepalive. That wil be just fine I guess.<br><br>On the other hand, you can of course have FS send SIP OPTIONS packets<br>to the phones, but I'd like to keep the NAT handling on the front end<br>SIP proxy as much as possible.<br><br>Philippe<br><br>On Thu, Feb 10, 2011 at 12:23 PM, David Ponzone <<a href="mailto:david.ponzone@ipeva.fr">david.ponzone@ipeva.fr</a>> wrote:<br><blockquote type="cite">Philippe,<br></blockquote><blockquote type="cite">can you confirm there is no NAT Keepalive feature in the Aastra ?<br></blockquote><blockquote type="cite">That's quite weird.<br></blockquote><blockquote type="cite">David Ponzone Direction Technique<br></blockquote><blockquote type="cite">email: <a href="mailto:david.ponzone@ipeva.fr">david.ponzone@ipeva.fr</a><br></blockquote><blockquote type="cite">tel: 01 74 03 18 97<br></blockquote><blockquote type="cite">gsm: 06 66 98 76 34<br></blockquote><blockquote type="cite">Service Client IPeva<br></blockquote><blockquote type="cite">tel: 0811 46 26 26<br></blockquote><blockquote type="cite"><a href="http://www.ipeva.fr">www.ipeva.fr</a> - <a href="http://www.ipeva-studio.com">www.ipeva-studio.com</a><br></blockquote><blockquote type="cite">Ce message et toutes les pièces jointes sont confidentiels et établis à<br></blockquote><blockquote type="cite">l'intention exclusive de ses destinataires. Toute utilisation ou diffusion<br></blockquote><blockquote type="cite">non autorisée est interdite. Tout message électronique est susceptible<br></blockquote><blockquote type="cite">d'altération. IPeva décline toute responsabilité au titre de ce message s'il<br></blockquote><blockquote type="cite">a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce<br></blockquote><blockquote type="cite">message, merci de le détruire immédiatement et d'avertir l'expéditeur.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Le 10/02/2011 à 11:39, Philippe Sultan a écrit :<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Tim,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">That helped a lot, thanks! More comments inline.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Thu, Feb 10, 2011 at 3:18 AM, Tim St. Pierre<br></blockquote><blockquote type="cite"><<a href="mailto:fs-list@communicatefreely.net">fs-list@communicatefreely.net</a>> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I'm wondering about these values:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">sip registration retry timer: 10<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">sip registration renewal timer: 15<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">sip registration timeout retry timer: 10<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">sip registration period: 60<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">sip rport: 1<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">They seem a bit short, especially on a LAN. Do you really need your<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">phones to re-register every 45 seconds?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Indeed, I don't. But need a mechanism to keep NAT sessions alive in<br></blockquote><blockquote type="cite">case phones are being deployed behind NAT boxes. It seems like<br></blockquote><blockquote type="cite">transporting SIP over TCP from the phone, plus using TCP keepalives<br></blockquote><blockquote type="cite">will solve that issue though. I also have Thomson ST2030 phones, and<br></blockquote><blockquote type="cite">they send SIP OPTIONS packets every 50 seconds for that purpose (all<br></blockquote><blockquote type="cite">handled by the SER proxy).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Try setting sip registration period to 600 That's 10 minutes.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">sip registration renewal timer can be a bit longer - 30 seconds maybe,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">or 60 if you are at all worried about reliability.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Here is what I put in the aastra.cfg file from your suggestions :<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">sip registration period: 3600<br></blockquote><blockquote type="cite">sip registration renewal timer: 3565<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">And that does the trick, that is, the phone registers every 45<br></blockquote><blockquote type="cite">seconds. I'll try to update those values to have a larger registration<br></blockquote><blockquote type="cite">period, rely on TCP keepalives in order to maintain NAT sessions, and<br></blockquote><blockquote type="cite">have all that NAT handling in SER. Here is the topology :<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Aastra ---(sip/tcp)--- SER ---(sip/udp)--- FS<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">ST2030 ---(sip/udp)--- SER ---(sip/udp)--- FS<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks again!<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Philippe<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">FreeSWITCH-users mailing list<br></blockquote><blockquote type="cite"><a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br></blockquote><blockquote type="cite"><a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br></blockquote><blockquote type="cite">UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br></blockquote><blockquote type="cite"><a href="http://www.freeswitch.org">http://www.freeswitch.org</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">FreeSWITCH-users mailing list<br></blockquote><blockquote type="cite"><a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br></blockquote><blockquote type="cite"><a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br></blockquote><blockquote type="cite">UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br></blockquote><blockquote type="cite"><a href="http://www.freeswitch.org">http://www.freeswitch.org</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><br><br><br>-- <br>Philippe Sultan<br><br>_______________________________________________<br>FreeSWITCH-users mailing list<br><a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br>http://www.freeswitch.org<br></div></blockquote></div><br></div></body></html>