<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">The metaswitch way is that it will do it automatically for you if it thinks you're behind a NAT. So if you force nat, it will do the fast registration automatically. It's one line of config on the sip adjacency for the MaxUC application.<br class="">
<div><br class=""><blockquote type="cite" class=""><div class="">On Jun 10, 2021, at 5:33 PM, Matthew Crocker <<a href="mailto:matthew@corp.crocker.com" class="">matthew@corp.crocker.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">The acme/oracle way of doing Hosted NAT Traversal is to set the expire time down to 30 seconds and have the phones REGISTER every 30 seconds. The SBC eats the registration so it doesn’t overload the switch. If the CGN NAT drops the entry it gets recreated with the new registration in 30 seconds.<o:p class=""></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">We have had very good results with the acme/oracle approach<o:p class=""></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: 3pt 0in 0in;" class=""><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 11pt; font-family: Calibri, sans-serif;"><b class=""><span style="font-size: 12pt;" class="">From:<span class="Apple-converted-space"> </span></span></b><span style="font-size: 12pt;" class="">VoiceOps <<a href="mailto:voiceops-bounces@voiceops.org" style="color: blue; text-decoration: underline;" class="">voiceops-bounces@voiceops.org</a>> on behalf of Pete Mundy <<a href="mailto:pete@mac.geek.nz" style="color: blue; text-decoration: underline;" class="">pete@mac.geek.nz</a>><br class=""><b class="">Date:<span class="Apple-converted-space"> </span></b>Thursday, June 10, 2021 at 5:11 PM<br class=""><b class="">To:<span class="Apple-converted-space"> </span></b>VoiceOps <<a href="mailto:voiceops@voiceops.org" style="color: blue; text-decoration: underline;" class="">voiceops@voiceops.org</a>><br class=""><b class="">Subject:<span class="Apple-converted-space"> </span></b>Re: [VoiceOps] "Timeout" on VoIP call traversing Verizon data<o:p class=""></o:p></span></p></div><div class=""><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless you recognize the sender and know the content is safe.<br class=""><br class=""><br class="">Precisely. And those "NAT table entries" eventually time out. On CG-NAT they often time out aggressively; <60 seconds. Hence sending OPTIONS over SIP over UDP regularly keeps the NAT table entries refreshed and active and therefore the UDP 'connection' open. I've come across firewalls with 30 second timeouts, so we use 25 second keepalives (OPTIONS).<br class=""><br class="">Pete<br class=""><br class="">>> On 11/06/2021, at 8:24 AM, Alex Balashov <<a href="mailto:abalashov@evaristesys.com" style="color: blue; text-decoration: underline;" class="">abalashov@evaristesys.com</a>> wrote:<br class="">>><br class="">>> Not to muddy the waters here with needless pedantry, but:<br class="">>><br class="">>> While UDP may be "connectionless", the only way UDP, and in particular, symmetric SIP signalling, can work through NAT is if a stateful firewall + NAT gateway has some awareness (that is, state) of UDP "flows", or groups of packets flowing between ports consistently in some kind of temporary logical association--one might say, the endpoints have a "connection" of sorts...<br class="">>><br class="">>> -- Alex<br class="">>><br class="">> On 6/10/21 4:07 PM, Peter Beckman wrote:<br class="">> uhhhh.... SIP here is UDP, no?<br class="">> There's no connection to close for UDP.<br class="">> The source port for UDP doesn't matter. It's not part of the whole<br class="">> conversation, unless your switch cares that all communications continue to<br class="">> come from the source port. It's connectionless.<br class="">> TCP 5060 isn't even listening on our switches.<br class="">> So, maybe you're doing SIP over TCP?<br class="">> On Thu, 10 Jun 2021, Mark Wiles wrote:<br class="">_______________________________________________<br class="">VoiceOps mailing list<br class=""><a href="mailto:VoiceOps@voiceops.org" style="color: blue; text-decoration: underline;" class="">VoiceOps@voiceops.org</a><br class=""><a href="https://puck.nether.net/mailman/listinfo/voiceops" style="color: blue; text-decoration: underline;" class="">https://puck.nether.net/mailman/listinfo/voiceops</a><o:p class=""></o:p></div></div></div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">VoiceOps mailing list</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="mailto:VoiceOps@voiceops.org" style="color: blue; text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">VoiceOps@voiceops.org</a><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="https://puck.nether.net/mailman/listinfo/voiceops" style="color: blue; text-decoration: underline; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">https://puck.nether.net/mailman/listinfo/voiceops</a></div></blockquote></div><br class=""></body></html>