No devices registered in Vpanel

[KenH]

My HT502 has registered. No reboot required.

[Xponder1]

My HT502 has registered. No reboot required.

Ya I just got a email from support saying to reboot the device but its already working. Probably because they have them set to reregister ever minute lol.

[serialportme]

Working now, but not earlier.

Failover failure is a huge problem for me...

[VOIPoTim]

http://forums.voipo.com/forumdisplay.php?f=24

[KenH]

Not sure where the failover data is stored. Is it possible that even that data was unaccessible during the outage, causing the loss of the failover feature?

[scott2020]

My 502 showed registered but nothing in vpanel. Inbound calls went to "The number you have dialed has been disconnected" instead of failover. Rebooting fixed all, but like others if failover is not working I'm in trouble.

[KenH]

Only port 2 is registered now and, of course my phone is connected to port 1. What's going on?

[VOIPoTim]

Only port 2 is registered now and, of course my phone is connected to port 1. What's going on?

If you didn't reboot after the outage, you may need to.

[voxabox]

If you didn't reboot after the outage, you may need to.

uhm, why the HT-502 did not keep on retrying (SIP registration) after failing to to do?
even if it is a bug, the ATA should try to register again at regular interval (reg. interval, specified in the ATA config.)

[VOIPoTim]

uhm, why the HT-502 did not keep on retrying (SIP registration) after failing to to do?
even if it is a bug, the ATA should try to register again at regular interval (reg. interval, specified in the ATA config.)

We've been asking Grandstream the same question for the last few weeks. They seem to be very hit and miss with re-registering on their own if there is any kind of service interruption (even a few seconds).

They are "aware of the issue" and "hope to fix it in the next firmware".

We're still pressing for a better answer than that.