Need to reboot SIP device often

[fplLover]

Roger that. Just as a test after this initial overnight test I can disable STUN and try these additional setting...never know...could be related...As you said, one thing at a time...

Thanks

[fplLover]

So I did the over night test (i.e.: forced wan ip renegotiation on router) and 7 hours later the SPA112 was still in a failed state and I had no dial tone. A per usual rebooting it fixed the problem.

After this test I have now removed the STUN setup and put your other 3 suggested settings in its place...worked like a charm. I never knew about those 3 settings for some reason...Guess I just never came across your post at the time I set things up...That works great. I certainly like that better. I never really like that reliance on STUN. So thanks for that.

After putting the STUN changes in I repeated the manual wan ip renegotiation testing and observed something interesting. After the Wan ip renegotiation was done, and once the SPA112 had its Registration State go "Failed", I stayed logged into the SPA112's web interface and kept refreshing the Voice Information Status page. I would see over and over the "Next Registration In" field show 360 sec. As I was refreshing I would see it count down...Interestingly enough it would count down for only 20 sec to 340 sec and then the "Next Registration In" field would just go blank for a bit...Almost as if it was not counting down anymore...And then a little while later it would show 360 again, count down and get to 340 and go blank again...It just perpetually keeps doing this over and over while it is in the defunct state, never getting below 340 in the countdown...

Kind of interesting how it only counts down 20 seconds (same as the keep alive interval) before starting over at 360...

This would seem to me that it will never count down to 0 and actually retry the registration. Does this mean anything to you?

Weird

[Mango]

Well, that is certainly disappointing. Thank you for testing my theory and I'm sorry it didn't work. Perhaps another member will have a different idea.

Just to confirm, both your router and your ATA have the latest firmware?

[fplLover]

I just recently updated my router not too long ago so it is good...

The SPA112 is running -->

Model: SPA112, 2 FXS
Hardware Version: 1.0.0
Boot Version: 1.3.1 (Dec 11 2013 - 11:38:47)
Firmware Version: 1.3.3 (015) Dec 13 2013
Recovery Firmware: 1.2.0 (001)

[fplLover]

Upgraded the SPA112 to what I believe is the latest -->

Model: SPA112, 2 FXS
Hardware Version: 1.0.0
Boot Version: 1.3.1 (Dec 11 2013 - 11:38:47)
Firmware Version: 1.3.5 (004p) Oct 28 2014
Recovery Firmware: 1.2.0 (001)

Will test with this

[fplLover]

No dice. Even with the latest firmware on the SPA112 the behaviour is the same

[fplLover]

Problem solved. Static Ip. I had other reasons anyway that justified one. All good.

Thanks for your help.

[Mango]

Dang.

So you assigned a static IP to your ATA, and the problem went away?

[f_laplante]

Interresting discussion. My system also go down once in 4-6 week and it often happens when I'm out of for more than 24h...

Il arrive environ une fois par 6 semaines qui le système téléphone s'interrompe dans le 2e logement et on reset les modem, ATA et router en même temps et tout se replace. Un mince inconvénient pour les autres avantages.

ESt-ce qu'une adresse IP fixe rèeglerait ce problème?

[Bram14]

Can someone please tell me where to enter these values in the configuration menu for spa112. thanks in advance.
Registration Interval: 3600 seconds (1hour)
Failed Registration Re-Try Interval:120 seconds

[Bram14]

Is it always advisable to upgrade your ATA's firmware when their is a new release become available.
Thanks for your input

[arsh]

Hi all,

I have opened a new account about three weeks ago. I have configured my Sipura 3000 according to the guide, but still having register failed issue. The ATA will not register after its time to re-register (every 3600 seconds), this happens on different times some time after say five hours and other times it go up to 20 hours with any issue, so far the longest time it holds the registration is about 20 hours. Only way to get it to re-register is to change the sip proxy from voip.freephoneline.ca to voip2.freephoneline.ca and vice versa. I have tried the other two servers with the same results. Its very annoying because I have to monitor my ATA every hour to see if it is still registered and when ever its failed I have to switch to a different server. I have searched the forum but did not find any solution to this problem, I am looking to get some help here to resolve this issue any help will be appreciated.

arsh

[penn]

First, I have tried the recommended configuration for Grandstream HT502:
http://forum.fongo.com/download/file.php?id=1734

On my DSL modem/router, I port-forwarded ports 5004-5012, 5060-5062, 6060-6062, 13000-13001 to the fixed IP address of my Grandstream HT502. The status page of my Grandstream HT502 shows Registered, but for ATA it shows Unknown NAT. Outgoing and incoming calls are successful, but there is no incoming voice path.

Next, I tried setting NAT traversal to STUN (using STUN server stun.callwithus.com). The status page of my Grandstream HT502 shows Registered, and for ATA it shows Port Restricted Cone NAT (STUN). With this setting, both incoming and outgoing calls are successful with incoming and outgoing voice path.

But after awhile (not sure how long, but definitely overnight), the SIP status for my device on freephoneline.ca shows not connected. The status page of my Grandstream HT502 still shows Registered and I can make outgoing calls, but incoming calls go straight to voicemail. If I reboot my Grandstream HT502, the SIP connection is restored and incoming calls are successful again. But I have not found anything on the forum to help maintain my SIP connection.

Can anyone help?

[penn]

Finally found a post that pointed me in the right direction:
http://forum.fongo.com/viewtopic.php?f= ... ted#p49034

Grandstream HT Register Expiration setting is in minutes (60), not seconds (3600). My SIP status stayed connected overnight, so it looks like problem solved!