Printable View
This morning at around 6am I noticed that both lines were not registered. Rebooted ATA and everything was fine.
Again recently, one line was registered and another one was not.. But it came back soon. And I see 4 lines registered in the Devices page..
Anybody else seeing problems this morning.
Some incoming calls are going busy for me. Call logs are still unavailable from the maintenance.
In and outbound calls are all going to fast busy right now for me.
Same here. All systems are not working this morning.
Please reboot and advise if you are still experiencing any issues.
Wont the device automatically reregister after a period of time and, if so, will that fix it? I too had issues similar to what's described above this morning and the wife is headed home as I write this. I won't be home for many more hours.Quote:
Originally Posted by VOIPoBrandon
Yes, devices will automatically re-register in 99% of cases.Quote:
Originally Posted by Russell
My device has alternated between registered and not registered a couple times this morning. Callers to our number continue to receive a fast busy signal.
Why are incoming calls not going to our failover number?
Same problem here today. This seems to happen every 7-10 days. I have an open ticket
Outgoing attempts receive the message "Device not Registered". The HT502 shows "Not Registered" on the status page. VPanel shows that the device is registered and the registration renews, but still no service.
Incomming does not complete calls. Callers receive a message "call can not be completed". The incoming call is not sent to failover or email. The VOIPO system doesn't see an unregisterd device, so failover is not sent. Don't know why it is not sent to voicemail.
I'm using BYOD device with the second port on a different provider. That line continues to work properly and has never lost registeration. If the number would failover or voice mail it would be better than limbo.
Stil having problems with incoming and outgoing after reboot...