No service here in NYC. Ticket submitted. Also, I've seen the announcement about heavy support requests and possible network problems.
Printable View
No service here in NYC. Ticket submitted. Also, I've seen the announcement about heavy support requests and possible network problems.
and we're back. That's the first outage I've had in so long I can't remember.
I was connected to sip-west01 and the service went down at around 4.30 PM PST. Failover also did not work - my call would be picked up by Voipo voicemail.
I switched to sip-central01 after about an hour and service is back. I switched back to sip-west01 and my Asterisk is still not registering. Traceroute is working to sip-west.
I have a service ticket open (WZI-534463) - I want to know why failover did not work.
Been up and down a few times this evening for me.
Just came back up as I am posting this.
Yeah, another blip at 6.06 PM PST.
[Mar 11 18:06:16] NOTICE[3456] chan_sip.c: -- Registration for '4088494368@sip-central01.voipwelcome.com' timed out, trying again (Attempt #1)
[Mar 11 18:06:36] NOTICE[3456] chan_sip.c: -- Registration for '4088494368@sip-central01.voipwelcome.com' timed out, trying again (Attempt #2)
[Mar 11 18:06:56] NOTICE[3456] chan_sip.c: -- Registration for '4088494368@sip-central01.voipwelcome.com' timed out, trying again (Attempt #3)
[Mar 11 18:07:16] NOTICE[3456] chan_sip.c: -- Registration for '4088494368@sip-central01.voipwelcome.com' timed out, trying again (Attempt #4)
[Mar 11 18:07:36] NOTICE[3456] chan_sip.c: -- Registration for '4088494368@sip-central01.voipwelcome.com' timed out, trying again (Attempt #5)
[Mar 11 18:07:56] NOTICE[3456] chan_sip.c: -- Registration for '4088494368@sip-central01.voipwelcome.com' timed out, trying again (Attempt #6)
Quote:
Originally Posted by zcnkac
I see the same thing you are, from Missouri connecting to Central01. Very high latency and many registration time outs.
Everything is fine on our end, but it seems like there are have been sporadic upstream network issues getting into Dallas where our core equipment is all located.
NTT is showing areas of latency at http://internethealthreport.com/ and it's one of the main providers used in Dallas for our datacenter.
During the latency, my calls were also failing over directly to VOIPo voicemail instead of my failover number.
At around 4:30 p.m. today I had three calls come in (the same person tried three times). They rang my phone but I got dead air when I picked up. Only one of the three calls showed up on my call history, and the caller did not get routed to voice mail. I called him back, and the call was fine. I then tried calling my own number from my cell, and I had no problems. I didn't think anything of it until I read Tim's announcement.
Everything seems OK now.
Our service was down last evening on Line 1 only (the Line 2 light was on green though and it did have dialtone). Same thing again tonight. And the bad part is we have no way of telling when it occurs. Seemed to me that it may be a problem with the ATA, but Customer Service has been un-responsive to this suggestion. Service since the beginning of the year hasn't been the best. During January I've had several episodes of audio dropping after a few minutes then after 10-20 seconds audio would usually come back - I put in a problem ticket on 01/02/10 and the problem persisted and was not resolved until 02/08/10. Last month the issue was that outgoing calls would be disconnected right around the one-minute mark. And now the no dialtone issue. I expect more reliablity, and indeed had had few problems for the first year of my service during 2009. Personally, my wife is between jobs right now and she relies on our phone service to be accessible to potential employers. The service we're currently receiving is a big disappointment.
Quote:
Originally Posted by hines86fan
Your issue sounds like something else since audio issues too.
If using it behind your router do you have port forwarding setup? 99% of the time when there are audio issues, people don't have the port forwarding setup.
You didn't have many issues in 2009, but what you should remember is that the audio ports are random in a large range. It's very likely that the ports are different than in 2009 for you because we're literally 10X the size we were 6 months ago in terms of customers so there is much more volume which cycles through larger ranges of audio ports. So even if you didn't need forwarding in the past, your router may not like new ports it's seeing.
If that's all setup correctly, PM your ticket numbers and I can take a look at the support history.