eugenem wrote:SIP
SIP ALG should be disabled.
and Firewall on the router are disabled
Using no firewall is a security risk.
Follow the steps below, carefully, in the order they're presented:
1. Use this PDF guide to ensure your ATA is configured properly:
viewtopic.php?f=15&t=18839#p74000.
Check all settings, especially
a. Enable SIP Options Keep Alive: Yes
b. SIP OPTIONS Keep Alive Interval: 20
c. SIP REGISTER Contact Header Use: WAN Address
d. Use Random SIP Port: Yes
e. Register Expiration: 60 minutes (default)
f. SIP Registration Failure Retry Wait Time: 120 seconds
2. Proper device reboot order is always modem-->router (wait for Wi-Fi SSIDs to populate first)-->ATA (in that order). Reboot your devices now in that order and test with an incoming call from a regular (non-VoIP) cellphone or landline service.
3. If that doesn't work, you can try specifying an RTP port in the ATA and port forwarding that port to the ATA.
a. Disable "use Random RTP port" in the ATA.
b. Take note of the RTP port specified for "Local RTP Port" in the ATA.
c. Login into your router and port forward the RTP port (it's always UDP--and not TCP) to your ATA.
If you need your ATA's LAN IP address ,dial *** followed by 02. Take note of the IP address that you hear.
Refer to your router's manual, and contact your ISP if you need help with port forwarding.
Note that port forwarding is also a security risk--but not really as horrible as completely dropping your firewall or using DMZ. Port forwarding and, especially, disabling your firewall, should not be done unless all else fails. If you ever have to drop your firewall to get a SIP service working, it's time to get a new router.
4. If you still have problems, open a support ticket at
https://support.fongo.com/hc/en-us/requests/new.
When creating a ticket, for the issue type select "VoIP Unlock Key-->My account inquiry". Ask for a "forced registration."
If no responds to your support ticket, provide the ticket number in a private message to Fongo Support after registering and logging into the forums:
ucp.php?i=pm&mode=compose&u=7852#6 is less likely related to your issue if your phone actually rings on incoming calls.
By the way, modem/router combos or gateways that ISPs issue are predominately bad choices for use with SIP services. Especially refer to #D in the second post below
5. 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) < SIP OPTIONS Keep Alive Interval (in your ATA; for Obihai ATAs this is X_KeepAliveExpires) < 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, 17, and the NAT (SIP Options) 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, SIP OPTIONS Keep Alive Interval is supposed to be 20 with FPL.
Getting access to both UDP Unreplied Timeout and UDP Assured Timeout settings in consumer routers may be difficult, if not impossible.
Asuswrt-Merlin (I would avoid any model below/less powerful than an RT-AC68U), third party firmware for Asus routers, does offer easy access to these two settings, which are found under General–>Tools-->Other settings. My understanding is that third party Tomato firmware has these two settings as well. So if your router supports Tomato firmware, that may be another option. Note that I will not be held accountable any damage resulting from failed firmware updates. Apparently, Mikrotik routers also allow users to change both Assured and Unreplied UDP timeout settings as well:
https://forums.redflagdeals.com/recomme ... 2115672/2/The keep alive interval for FPL is 20. The SIP Registration Failure Retry Wait Time is 120. I use 17 for UDP Unreplied Timeout and 117 for UDP Assured Timeout
Unfortunately, the Hitron CODA modem/router combo or gateway doesn't let you adjust UDP timeouts.
6.
https://community.freepbx.org/t/trunk-s ... ca/22479/8"As May 2013, our servers will rate limit REGISTER requests to a maximum of 10 requests per 5 minutes. Each authentication round usually consumes 2 requests (digest auth), so it is a fair number given our guidelines. Also, it does not affect INVITES (which are also authenticated)…
This rate limit is applied per IP address as our service is tailored to residential Canadian users (ADSL/Cable)."
That's why the registration interval of 3600 seconds and failed retry timer of 120s in the ATA are important.
If the ATA loses registration for any reason, incoming calls won't work on it. Note that only one registration per FPL account is allowed at any time. When there are multiple devices/softphones using the same account, only the most recent registration is valid. The previous device will lose registration. This is especially important to consider if someone else is using your SIP credentials (username and password) that are found after logging in at
https://www.freephoneline.ca/showSipSettings (or if you're trying to register your FPL account with a smartphone SIP app or with another device). Registration is required for incoming calls. It is not required for outgoing calls. If you simply want to make outgoing calls using your FPL number, configure, but don't register the account, on the SIP app being used. This is also important to consider if you're using Freephoneline's desktop application (don't have it running while using your ATA with the same FPL account). Additionally, keep in mind that if someone else is also attempting to register the same SIP credentials on another device where you live, too many registration attempts can result in a temporary IP ban. Always check registration status in the IP Phone and also your SIP status after logging in at
https://www.freephoneline.ca/showSipSettings. If you see a device listed under SIP User Agent that you don't recognize, you've either been hacked or someone else is using your Freephoneline SIP username and SIP Password.
Always check registration status both in your ATA first and at
https://www.freephoneline.ca/showSipSettings if incoming calls aren't being received.