Yes, unfortunately registrations were still at an all-time high with no signs of dropping before this server failed.
See this thread for info: http://forums.voipo.com/showthread.p...newpost&t=1197
Printable View
Yes, unfortunately registrations were still at an all-time high with no signs of dropping before this server failed.
See this thread for info: http://forums.voipo.com/showthread.p...newpost&t=1197
We also lost device registration again with a 502. I have to say this is starting to become a nuisance with the service. While in beta, it just worked and we never had issues. I am hoping that we can get back to the level of service we had while in beta.
I just did a reboot and it is not registering. I do see the new DNS servers set in the Basic settings page.
I lost registration again today. Unfortunately, it won't re-register after reboot. Currently on hold with the helpdesk.
I'm told we need to make one more change to switch all portions of our network to failover hardware.
We're doing this now and I'll post an update when it's done (few minutes).
Down here as well....
Mine just came up..Quote:
Originally Posted by burris
Me too, w/PAP2T. May be unrelated, but I noticed that my Call History in vPanel is empty.Quote:
Originally Posted by burris
Mine is still down, goes directly to voicemail when I dial home from my cell.
Just tried rebooting my pap2 adapter, all lights are on and I get a dial tone but am not registered in vpanel.
Vinnie
ATA re-registered and is back up!
But is it working both in and out?Quote:
Originally Posted by Hawkmeister
"You do not currently have any devices registered to our servers!" :mad:
I'm down as well. Rebooting the device will cause it to re-register, but it then loses registration again within a couple of minutes again. I initially had entered the DNS entries as suggested, but removed them thinking that could be the cause of the registration issue, no change unfortunately.
My device shows up sporadically in vPanel. It's there one second, gone the next. When it does show, I'm only seeing one line, not both as I normally do with the PAP2T. Incoming calls "appear" to work sporadically as well. Sometimes I get 4 rings, other times straight to failover (VM). I'm not at home, so can't test outgoing, nor confirm that incoming is actually ringing the phone.Quote:
Originally Posted by TomP
Just saw Tim's post about one of their servers going down. I'll hold off on submitting a ticket until that server comes back up to see if it solves my problems.
Mine began working in and out...try it.Quote:
Originally Posted by CrownSeven
Looks like incoming calls are working, but outgoing are not - just getting a fast busy signal. Device is showing up as registered. I'll give it some more time.
One interesting thing, i previously posted about some 'popping' issues that i could here when picking up my handset, those are now gone.
Incoming and outgoing working now. But the phone keeps ringing on incoming even after the caller hangs up.
Tim,
Is Failover Forwarding supposed to work during this kind of a hardware failure. I understand the nature of hardware failure. But I would expect the calls to be forwarded to my failover number. But it did not happen during this outage.
It did for me, but it was going up and down so much, I am not sure what the state of the VOIPo systems (and the ATA) were at that instant.
Failover did not work for me either.Quote:
Originally Posted by sr98user
Mine started working correctly after the caller hangup..Quote:
Originally Posted by sr98user
Its working good now.Quote:
Originally Posted by burris
Just went down again on my end.
At this point, everything else should have stabilized. It looks like adapters are re-registering pretty well.
I would recommend a reboot in any case though just in case the connection is stale so it doesn't have an issue later.
Basically we are moving call history to a new system (outside of RADIUS system that we used until now) which should alleviate a lot of these issues.
Shortly you'll see the call log page being populated with new calls and a link the the "old" call logs for previous calls as well.
We expect this to be done within an hour. Calls are now logging using new method (database directly) just not displaying for you yet.
My device (likely) lost registration with the RADIUS server issue earlier today.
I have a 502 and it did not reregister.
I am thinking about putting it out in front of my router, if that will solve my issues. (I do have all the ports open from the document.)
Are there issues with getting into my home network (remote desktop, http) across the 502? Are there any issues with Xbox Live? If I try and have any of these issues, maybe I will start a new thread.
Thanks,
Dan
24 hours, and no issues. The first time in about 2 weeks :)Quote:
Originally Posted by Brian
Thanks for confirming. Hardcoding the DNS seems to fix the GS re-registering issue.Quote:
Originally Posted by Brian
If you have your router correctly configured and your HT-502 is correctly configured - it shouldn't be an issue having it behind the router. If you are BYOD and haven't set up a STUN server, I would suggest it if you decide to keep in behind the router. I think the provisioned 502's are set up with a STUN server (maybe someone could confirm this). You should not have an issue accessing your home network passed the HT-502, but without knowing your network setup I can't say whether some tweaks to your HT-502 or network may be required. I guess try it is the best way to see. I don't have a problem getting past my HT-502, but I am running a network server and there is no issue logging on to my domain, but most home networks are not setup this way.Quote:
Originally Posted by orum
If you have registration problems, you will probably need to hard code a DNS into your 502 (again BYOD not provisioned) as mentioned in this thread. I am using DHCP but the DNS it accesses is pretty fast hence a non issue. If you are setup as DHCP you are most likely accessing your ISP's DNS and may or may not be lagging. Hope this helps and doesn't muddy the waters worse.
Just lost registration after 4 days. Vpanel shows no registration. But adapter says its registered.
Contact support and they can check your ATA logs.Quote:
Originally Posted by sr98user