I just lost registration on my PAP2T. I am on east01.voipwelcome.com. Reboot did not fix it. Anybody else seeing the problem. I just created a ticket for it.
Printable View
I just lost registration on my PAP2T. I am on east01.voipwelcome.com. Reboot did not fix it. Anybody else seeing the problem. I just created a ticket for it.
I waited for atleast 5 minutes before I posted. Within couple of minutes it reconnected.
It may have been a function of the new routing servers they just brought online.
We've been working with the DCs to make sure all the network routing is clean, so there could have been a network hiccup there.
Now my traceroutes are 2 hops farther and 20 ms longer.
How many hops are you seeing? I am seeing 13 for east01, central02, and sip. 25ms to sip and central02, and 54ms to east01.
Support noted in their ticket that they saw some really high latency reaching my ATA, which prompted me to check. (2000-3000ms).
Its about 15 for me now for east01. I think it used be 13 for me and 40ms. Now its about 60ms.
Whereabouts in the country are you located?
Same problem here.
Wife was talking on phone, went dead. Lost registration.
Cannot restore. Repeat cannot restore.
OK - re-registered - at least one port anyway.
Mine lost all registration. I rebooted and got two registrations, and then one of them dropped out.
We just saw a huge spike in latency in the DC zeus/sip is in. We're working with the DC to make sure this is over now.Quote:
Originally Posted by digger16309
Any affected users should re-register on their own on their next re-registration interval.
I just looked over at my PAP2T and noticed my bottom two green lights were not lit. I checked my device and it was not registered. Rebooting the device resolved the problem. I logged into my mother-in-law's vPanel--who lives within a stone's throw--and her device was registered. To my knowledge this is the first time my device has lost its registration. Theoretically will the device re-register on its own?
Yeah it will on the next scheduled registration. I'm pretty confident it would have come back on its own.Quote:
Originally Posted by Bill Odom
Ok, now I have both registrations. Now, Vpanel is no longer showing new calls. I guess when it rains it pours.
The latency could cause some call logs to be missed, but as it clears up that'll resolve itself.Quote:
Originally Posted by Bobman
http://forums.voipo.com/showthread.p...newpost&t=1266
Calls seem to be showing up now...was this during the network issue?
Tim....I just made another call and it didn't show up in vpanel.
Was it a completed call (answered)?Quote:
Originally Posted by Bobman
Tim.. Yes, it was completed. I just made another call too, and it completed but doesn't show up in history on vpanel.
Same here..not listed in panel.
Last call I have listed was about 7:15 tonight.
But, never lost registration for many moons now.
I placed a call to New Jersey 201 487-xxxx at 7:09 PM and at 7:39, the call dropped off. Call log says 30.5 minutes.
New Pap2T.
Yeah, that was right around the time of the latency. You're fine now right?Quote:
Originally Posted by NY Tel Guy
Yes, I attempted to re-dial and it hung for a while and then on the third attempt it went through.Quote:
Originally Posted by VOIPoTim
Tim, Zeus is an alias for sip.voipwelcome.com, correct? I had an incoming call with no voice at 7:23pm MDT. Appears to be cool now.
Yeah it is.Quote:
Originally Posted by bretski
M'kay, that's what I thought. I was connected to sip when the problem occurred.
Call logs still do not appear to be working.
I received a call a few mins after 8 PM central time. And I just did a test call myself a few mins ago. Both calls went to VM. Neither of them showed up in the call logs.
could this have had anything to do with the drop outs on calls I was having today late morning to early afternoon on the east coast?..the other party could not hear me at all several times during 2 calls to different numbers
My wife was using the phone at 1:27PM EDT yesterday and got disconnected. The caller called back, but the call went to failover. I did not observe any loss of registration.
I made a test call to my VOIPo # a short time later and it came through OK.