maximebeauvais wrote:
Over the last year, every 2-3 months, I have to change the proxy server name because freephoneline stop to work.
1) What happens? Do you not hear a dial tone? Does your ATA become unregistered?
2) When this issue occurs, what does SIP Status indicate after logging in at
https://www.freephoneline.ca/showSipSettings ?
Also check to ensure that SIP User agent shows a device you recognize when this problem occurs.
Registration or a "connected" status is required for incoming calls. Registration is not required for outgoing calls.
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 and incoming calls will not work on it.
3) The next time this problem happens, dial ***1, and enter the IP address you're told into your web browser.
If you used the Obitalk web portal (
http://www.obitalk.com) to configure your ATA, keep in mind that you must continue using it to configure your ATA. Otherwise whatever settings you change will eventually be overwritten by what you previously entered at obitalk.com anyway. If you wish to disable this behaviour, dial ***1. Enter that IP address into a web browser. Navigate to System Management-->OBiTalk Provisioning-->select Disabled for the method. Save. Reboot ATA. Now obitalk.com won't overwrite whatever changes you make via the device's interface (via IP address).
Pick one method (obitalk.com) or the other (IP address of device) for changing device settings. Never use both methods.
If you're using Obitalk.com, look at this picture for reference:
http://i.imgur.com/xwyqgRE.jpgThat grey cog wheel with the "E" is for the expert configuration menu.
It shows when logging in at
http://www.obitalk.com, selecting "Edit Profile" on the left, then scrolling down
under "Advanced Options" and finally selecting "Enable OBi Expert Entry from Dashboard."
If you're using Obitalk.com, you will need to enter the expert menu.
i) navigate to Voice Services-->SP(FPL) Service-->X_UserAgentPort. X_UserAgentPort should be a random port number between 30000 and 60000. Just pick a port number in that range. Change to a new port number in that range. Click the “submit” button, and reboot the ATA. (If you use Obitalk.com to change settings, you will need to use Obitalk.com).
If changing X_UserAgentPort fixes the problem, you were dealing with a corrupted NAT connection in your router.
Possibly a NAT router connection was never disconnected or never timed out properly. And, then, the
ATA keeps the corrupted connection in a persistent state over and over again. (Credit goes to Mango for
this information). Possibly, this problem is due to the router's UDP timeout being in excess of the ATA's
Failure Retry timer (RegisterRetryInterval with Obihai ATAs). With FPL, that's 120 seconds.
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) < 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 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_KeepaliveExpires 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, third party firmware for Asus routers, does offer
easy access to these two settings, which are found under Tools-->Other settings. However, my understanding is that third party Tomato firmware has these two settings as well. Mikrotik routers do as
well:
https://forums.redflagdeals.com/recomme ... #p28056619. 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. 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.
is it normal
No. The only time you should have to switch ProxyServer is if you're temporarily IP banned due to too many registration attempts within a short period.
Keep the following in mind:
https://community.freepbx.org/t/trunk-s ... ca/22479/7"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)."
So, it's important that after navigating in your ATA to ITSP Profile (FPL)-->SIP-->
a) RegistrationPeriod is set to 3600 seconds, and
b) RegisterRetryInterval is at least 120 seconds
https://support.freephoneline.ca/hc/en- ... redentialsEach time you reboot, your ATA is attempting to register again. So be careful about how many registration attempts you're trying within 5 minutes.
By the way, proper device reboot order is always modem-->router (wait for it to be fully up and running first)-->ATA.