Sporadic Failover Calls in the past couple of months

[GreenLantern]

I may be on to something with this issue. I want to see if anyone else can verify what I'm seeing.

It appears that sometimes the registration times out early, causing a brief period for every registration cycle, where calls will failover.

Example, if my registration timeout is 10 minutes, the voipo server seems to timeout at around 9 min 20 sec. So there's about 40 seconds where calls failover.

I can increase or decrease the timeout with the same result... just more or less frequent, but still leaving a downtime every cycle.

To verify this, I simply log into a control panel and hit refresh while watching the registration as the timeout approaches. Then sure enough, I see "no devices registered" message towards the end of the registration period.

Anyone else experiencing this?

[chpalmer]

To verify this, I simply log into a control panel and hit refresh while watching the registration as the timeout approaches. Then sure enough, I see "no devices registered" message towards the end of the registration period. Anyone else experiencing this?

I just did this and see that my devices actually update earlier than the timeout period by a minute or so.. Both my Voipo provided device and my BYOD PAP2. I have no issues with my lines.

[GreenLantern]

I just did this and see that my devices actually update earlier than the timeout period by a minute or so.. Both my Voipo provided device and my BYOD PAP2. I have no issues with my lines.

Good info.

I see that the Grandstream ATA's have a "re-register before expiration" setting.

This likely helps in situations exactly like this, where the service provider has an early timeout.

I suspect this issue has been affecting lots of BYOD users with devices that don't have a "re-register before expiration" setting.

Seems to have started in the last couple of months, perhaps after some voipo software changes/updates.

So hopefully voipo can do something on their side to set expirations correctly.

[GreenLantern]

late last night, voipo resolved a clock synchronization issue, that was causing registration to expire prematurely.

registrations are now expiring accurately.

many thanks to the voipo team for working on that and getting it fixed!

[tritch]

GreenLantern, thanks for taking a look and your help with Voipo's team to resolve this issue. We'll see how things go from here...


Update 9/7/16: 100% fixed...not a single failover issue since. Great work!

[tritch]

I'm seeing this same issue again (on my father's BYOD ATA). SIP server registrations expiring 20-30 seconds prematurely causing calls to fail.

GreenLatern, would you mind confirming this is happening again? If so, could you please contact the same support person again to get this fixed...much appreciated.!!

FYI: I had him switch over to sip7 and it is occurring on there as well.