Something stuck? No Vpanel or inbound calls

[usa2k]

I'm showing 4 lines registered for my two on the HT502.
One is port 5062 and the other three are port 5079.

[Vumes]

Mine was like that last week, actually maybe 2 weeks ago, except I had 6 lines registered.

[carlquist]

My ATA lost registration as well. Calls going to failover. Happened sometime between 10 am and 8:30 pm. ATA is attached directly to cable modem. Never had this issue prior to recent firmware upgrade. Not sure if it's related or not...

A reboot of the ATA did NOT fix the problem.

[scott2020]

I have had my 502 behind my router since day 1, before they enabled STUN and other NAT-Friendly settings. I never lost registration either until this latest firmware update.

[carlquist]

My ATA lost registration as well. Calls going to failover. Happened sometime between 10 am and 8:30 pm. ATA is attached directly to cable modem. Never had this issue prior to recent firmware upgrade. Not sure if it's related or not...

A reboot of the ATA did NOT fix the problem.

Just to follow up. After waiting a little while then again rebooting my 502, it did re-register and is now showing in Devices on the vPanel.

[VOIPoTim]

Our guys are working on this this week and we hope to have it fully nailed down by the end of the week. Unfortunately, it seems to be related to firmware.

We're working on identifying exactly what the firmware issue is to see if it's something we can address without another firmware change. We'll likely make a decision tomorrow if we want to revert.

It's not affecting everyone, but does seem to be affecting enough people to potentially justify rolling it back to the old firmware to give us some time to work it out with Grandstream.

[VOIPoTim]

Is there anyone here who is experiencing this that is on the older firmware?

[zcnkac]

I use Asterisk 1.4.21.2 - usually in the night around 9 PM PST, a few times, the server takes a very long time to respond to register requests. Once it took around 20 seconds to respond, another time, 31 seconds. I have increased the registration timeouts on my server to 60 seconds to prevent my trunk from timing out. I am using central01. I have a ticket open on this - FJJ-815835.

[buckethead]

Is there anyone here who is experiencing this that is on the older firmware?

Yes - just posted on DSLR as well before I noticed this post. Still on old firmware and lost registration yesterday, rebooted and all was well. Also lost registration this morning - can not reboot till I get home in a couple hours though.

[dlangley]

Came unregistered again twice since yesterday afternoon
Just found the last one about 5 minutes ago.