Just received a call and it went straight to failover.
Printable View
Just received a call and it went straight to failover.
Are you seeing latency into Washington DC too (that's where you're connected)?Quote:
Originally Posted by Xponder1
We've had a handful of reports throughout the day, but haven't been able to reproduce it on our own. Overall call flow, registrations, etc all look normal with only a very small overall dip once take for a few minutes.
We think that there may be some some isolated cases of latency going on with connections from some ISPs to us or with some commonality (maybe a certain backbond provider i the mix) and in the traceroutes posted here saw some packetloss, but thought it was all isolated to Dallas. We passed all that onto our Softlayer people but they're saying no other reports and they can't reproduce it.
So overall, sounds like some network issues still going on but likely isolated to some ISPs/regions since not many reports and we're still trying to find the pattern with Softlayer.
Calls going straight to voicemail this morning. Phone doesn't even ring.
I'm on central, and I have no problems in or out.
Couple of outgoing calls earlier today were fine. Currently it takes forever to connect - I typically press # after dialing the number and previously I would hear the ringing almost right away.Quote:
Originally Posted by burris
Are your problem calls all going to a certain destination? Are they local by chance? The reason I ask is that it looks like almost all the reports of outgoing issues are from your area code so we may need to just re-route those to a different upstream.Quote:
Originally Posted by Russell
I tried my company and my wife's company and they're both in the local area code. I just tried calling SAM's club and it took a long time before I heard a ring. Actually, I never heard the ring, just the person saying hello. If I call my number (it's a direct line at work) I get a popup on my computer with caller-id info. In that case too, I noticed the popup appearing before I heard any ring. Previously I'd hear a ring fairly soon after pressing # - now I wonder if I'm going to experience dead air ... I know the co-worker of mine is extremely unhappy with what he's experienced with VOIPo (he's relatively new to VOIPo) the past few days.Quote:
Originally Posted by VOIPoTim
Open a ticket with the example numbers and support should be able to look at re-routing through an alternate carrier.Quote:
Originally Posted by Russell
I've opened RHS-335816 for the wrong caller-id issue. I've also mentioned how long it takes to ring certain numbers. I called my wife's work number and pressed the # key and it took 14 seconds before I heard a ring.Quote:
Originally Posted by VOIPoTim
Incoming calls have been doing this on several of my phone numbers today. They work for awhile, then don't work. Typically inbound callers tell me they call won't ring through, rings busy after and extended period of time, or connects and then disconnects. For me, it will ring through, but when I answer it silent, then I get a fast busy after about 5 seconds.
I've submitted a ticket on this, but this does seem to be a common problem that's getting worse.