Reregistration of SIP fails - initial registration is OK

[crusader9]

After initial connection (reboot of ATA) the SIP service shows registered. However when the register-expires timer is exceeded and the device attempts to re-register the status shows failed and my phone service is unavailable. This only started happening either this morning or last night.

Why could be the problem? no changes on my end were made.

I can disable the line in the ATA and re-enable then the first SIP registration is successful again, obviously this is not a solution.

[tbrummell]

I'm seeing my re-register fail as well, but my line is at least staying registered. They may not be accepting re-register until the timer has expired, but that would leave a gap of XX seconds where you would possibly offline. Strange.

If history shows us anything, reporting it here will do no good. Call in for help.

[crusader9]

After initial connection (reboot of ATA) the SIP service shows registered. However when the register-expires timer is exceeded and the device attempts to re-register the status shows failed and my phone service is unavailable. This only started happening either this morning or last night.

Why could be the problem? no changes on my end were made.

I can disable the line in the ATA and re-enable then the first SIP registration is successful again, obviously this is not a solution.

So it looks like I may have tried to disable/re-eneable the ATA line1 too quick (before the register-expires timer)..... I had this set to 180 (3 minutes), and found that it wasn't re-registering until long after this time (seems to be somewhere between 5 and 10 minutes).

I think it was a coincidence that the first time I rebooted and/or disabled/re-enabled the line it was much longer after the initial registration so I got lucky.

In the meantime I bumped up the register expires back to the default of 3600 (1 hr). I will see if the re-registration fails again after it expires this time around.

This still begs the question, because my re-register value was always 3min and working fine before this issue occurred for the first time today, so I suspect FPL/Fongo made some change with respect to SIP re-registration and/or throttling of devices/connections -------- and if so it would help to know the new minimum value it can be set to, can Steve or Mike confirm?

[crusader9]

automatic re-registration succeeded after changing the timeout to 1h (3600), so it seems the question remains as to why it was suddenly changed, it's still advertised as

Registration Expires: 180 to 3600

on the FPL -> App Settings -> Settings -> SIP settings webpage

We will need to know what the new (minimum) value is!

[Jake]

I'm seeing this in my logs

Registration for '1613366XXXX@voip.freephoneline.ca' timed out, trying again (Attempt #11)
Got SIP response 480 "Temporarily Unavailable" back from 208.65.240.165:5060

But calls seem to come in as normal. From what I can see it looks like this all started around 4:00 am EST this morning (18th Dec).

As I said, calls seem to be coming in, so I'm not sure how much of a problem this is. Either way it's obviously not right.

[crusader9]

Hi Jake,

Just a thought here, but if they were implementing some kind of UDP connection throttling on the server end ...... your packet could be dropped outright and make it appear as though the connection timed out. At the time my register failed I was running an ICMP to sip.fongo.com (208.65.240.165) and it was replying so clearly it wasn't a "real" network issue. What has your register expire value set to? Your ATA device seems to behave different from mine under what probably are the same conditions.

[Jake]

I am using an Elastix PBX which I think has a default registration time of 120 seconds.

The logs have quite a few of these 480 errors.

I'll play around with registration times and see if anything changes.

[OverDrive]

Mine too is having problems re-registering. Mine is set for 200 seconds. Nothing changed on my end - this started today. It's not all the time either - sometimes it registers, then it fails. It just now re-registered successfully from the failed state.

[meokey]

I have not been able to register for the last 3 days. The error message read
Register Failed: No Response From Server (server=208.65.240.165:5060; retrying)

and I happened to have the similar problem with another voip provider and could not be able to register. I contacted with their tech support and they told me to use another server because the server I was using is too busy. I turned to another server without changing anything else, it works well now.

In the same VOIP box, I have 3 other VOIP providers configured and work well, only have trouble with FPL. I suspect the issue is with the capacity of the server voip.freephoneline.ca.
a quick question to the tech support: Is there any backup server in FPL we can use?

[radio]

add me to the list of registration failed messages on the ATA. Just started today.

[mebwp]

Same problem.
shows registration failed.
If I unplug ata for a minute and plug it back in, it is then registered.
Nothing has changed on my system.

[CaptainN]

I just switched registration time from 3600 to 180 the other day as a workaround to issues with a dead line which I'm attributing to rebooting of cable modem. Both of my ATAs were down this morning, power cycled them which fixed them for a few minutes, have since put one to 2400 to get it working longer. The other one is still at 180 and goes to VM directly if called. Need to figure out the shortest registration time.

[Mallox]

Mine start having register issus on the night of Dec. 16-17, but now it's coming worse. Does anyone had feedback from fongo and know what's going on?

[tbrummell]

They finally ack'd there is an issue going on....

http://forum.fongo.com/viewtopic.php?f=4&t=7286

[pete_fpl]

Changing registration from 180 to 3600 worked, for now. Having it on 180 for the longest time and it was working just fine, so not sure why yesterday it didn't wanna be nice

Where do you guys view the registration failed messages?

[crusader9]

Changing registration from 180 to 3600 worked, for now. Having it on 180 for the longest time and it was working just fine, so not sure why yesterday it didn't wanna be nice

Where do you guys view the registration failed messages?

So for me, it was under the Voice menu -> Information -> Line 1 Status ->

Registration State: Registered
Last Registration At: 12/19/2012 17:38:07
Next Registration In: 1594 s

Mine is presently working (and the issue is still intermitent), but the registration state was "Failed" prior to this.

[FONGO_mike]

Closing thread and guiding it to here.