iceonu wrote: Unsure what initially caused it to be unregistered, as I had not implemented any changes and had been working okay prior.
Issues can occur in users' routers, such as NAT corruption, without them doing anything. Consequently, users stating that nothing has changed on their end doesn't necessarily mean very much.
Refer to point D from
viewtopic.php?f=8&t=20199#p78976
Thanks to Mango, many of us now understand that in order for ATAs to remain registered and working properly with a VoIP SIP provider like Freephoneline, in particular after power failures, the following conditions must be met:
UDP Unreplied Timeout (in your router) < NAT Keep-alive Interval (in your ATA; for Obihai ATAs this is X_KeepAliveExpires; for Grandstream, the setting is SIP OPTIONS Keep Alive Interval) < UDP Assured Timeout (in your router) < SIP Registration Failure Retry Wait Time (or RegisterRetryInterval in Obihai ATAs)
“<“ means less than.
When a modem leases a new IP address, a problem can arise where prior associations using the old IP address are maintained in the router. When the ATA attempts to communicate using the old IP address, the response is unreplied, and then if the UDP Unreplied timeout is greater than the Keep Alive Interval (and UDP Unreplied timeout is often set to 30 by default in consumer routers) a problem arises where the corrupted connection persists. If UDP Unreplied timeout is, for example, 15, and the NAT Keep Alive Interval is 20, then the corrupted connection will timeout or close. A new connection will be created, and everything will work fine.
Another problem can occur when the Keep-Alive interval is greater than UDP Assured Timeout (often 180 by default in consumer routers): the NAT hole will close due to the ATA not communicating frequently enough with the SIP server. In turn, incoming calls may, intermittently, not reach the ATA. Again, X_KeepAlivesExpires (SIP OPTIONS Keep Alive Interval) is supposed to be 20 with FPL.
To help ensure this situation doesn’t reoccur. . .
1) Are you using a Telus Wi-fi Hub? If so, ensure its LAN Port that is connected to Ubiquiti router is set to “Bridge”. Contact Telus for assistance.
Otherwise please ensure whatever modem/router combo, hub, or gateway your ISP issued is in bridge mode.
2) In your Unifi Controller (or Cloud Key), navigate to ‘Routing & Firewall’ -> ‘Firewall’ -> ‘Settings’.
Disable "SIP".
3) Refer to point D from
viewtopic.php?f=8&t=20199#p78976
Thanks to Mango, many of us now understand that in order for ATAs to remain registered and working properly with a VoIP SIP provider like Freephoneline, in particular after power failures, the following conditions must be met:
UDP Unreplied Timeout (in your router) < NAT Keep-alive Interval (in your ATA; for Obihai ATAs this is X_KeepAliveExpires; for Grandstream, the setting is SIP OPTIONS Keep Alive Interval) < UDP Assured Timeout (in your router) < SIP Registration Failure Retry Wait Time (or RegisterRetryInterval in Obihai ATAs)
“<“ means less than.
In your Unifi Controller (or Cloud Key), navigate to ‘Routing & Firewall’ -> ‘Firewall’ -> ‘Settings
Change
a) udp stream 115 (assured)
b) udp other 15 (unreplied)
The defaults are 180 for Stream and 30 for Other.
(Refer to pages 35 and 36 from
https://dl.ui.com/guides/UniFi/UniFi_Co ... _V5_UG.pdf)
So, 15 seconds (UDP Unreplied or Other) < 20 seconds (SIP OPTIONS/NOTIFY Keep Alive Interval: 20) < 115 seconds (UDP Assured or Stream) < 120 seconds (SIP Registration Failure Retry Wait Time)
If you want to keep the router defaults for UDP Stream and UDP Other instead, then you could change, in your IP Phone,
SIP OPTIONS/NOTIFY Keep Alive Interval to 35 seconds
and
SIP Registration Failure Retry Wait Time to 185 seconds
However, in the event of a failed registration, the IP Phone will now take 185 seconds instead of 120 seconds before attempting to register again with FPL's proxy server.
Also, the Keep Alive packets (which is sent to help keep the NAT connection/hole alive) will be sent at 35 second intervals instead of 20. I doubt this would cause a problem for you.
c) click "Apply Changes"
You can also do steps 2 and 3 by SSHing into your router, if you prefer:
configure
set system conntrack modules sip disable
set system conntrack timeout udp stream 115
set system conntrack timeout udp other 15
commit
save
exit
4) Reboot Router. Wait for it to be fully up and running first. Then reboot or power cycle IP phone. This is always proper device reboot order (well, rebooting ISP modem is the first device step, but that shouldn't be necessary here).