Before I open a ticket...anybody else have this happen today? This has happened several times now since earlier this morning. Outbound call completes, then disconnects after a few seconds. Weird...
Printable View
Before I open a ticket...anybody else have this happen today? This has happened several times now since earlier this morning. Outbound call completes, then disconnects after a few seconds. Weird...
I am having trouble with inbound calls, phone rings but goes busy when answered while caller hears nothing (dead air) or this number is no longer in service message. Outbound calls also working sporadically.
I went ahead and opened a ticket, as it's still happening. Calls to my cell phone work fine, but every land-line I've called today has failed.
No problems with inbound, as far as I've seen.
All afternoon I have been having problems with my adapter reaching VOIPo. All other provider connections seem OK. I had to call in on a backup number with another provider.
Inbound calls have been giving a "disconnected" message to callers on and off.
We have had a few network spikes this afternoon that cascaded through systems and caused some delayed/failed database queries, but not much. We're still working with our datacenter to try to isolate the traffic and firewall it away.
Here is an example:
http://img4.imageshack.us/img4/9580/sl11.png
I've had this problem for weeks, and seeing it today as well. Opened up a ticket tonight: SVZ-434024... finally tired of the wife nagging about horrible phone service; she immediately uses her cell phone now :(
These attacks seem very similar to the ones VOIPo suffered from when they were at The Planet datacenters. I hope they can figure out the source and try and put a stop to it. Someone is out to get VOIPo for sure in my opinion.
Just had a similar problem. My home phone and cell phone (Network unavailable number) both rang. Picked up the home phone and dead air. Picked up the cell phone, talked for less than minute, and it disconnected.
Got a call again from the same person after a minute and this time it worked well.
Tim: FWIW this has been happening all day, from about 8:30am MST on.
I had the identical problem. A tech support person ended up switching my accounts to access a different server system and it went away. But I'm glad to know I'm not alone in this, but things seem to have settled down now.Quote:
Originally Posted by bretski
Peace,
Gene
I experienced the drop at ~ 10:40 AM EST this morning. It took about 10 minutes before I could redial the number (got busy after about 30 seconds or it never connected). All has been OK since that time.
I had to restart my adapter just now because I could not receive calls and all calls had been going to failover all morning.
Can you do a traceroute to sip-central01.voipwelcome.com and see how it looks?Quote:
Originally Posted by Xponder1
This is what mine looks like..
Tracing route to sip-central01.voipwelcome.com [174.37.45.134]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms my.router [192.168.1.1]
2 10 ms 9 ms * 65.14.126.34
3 10 ms 10 ms 9 ms 65.14.253.61
4 15 ms 16 ms 16 ms 12.83.4.136
5 16 ms 15 ms 15 ms 12.83.9.93
6 16 ms 15 ms 15 ms axr00asm-0-3-1.bellsouth.net [65.83.236.14]
7 16 ms 15 ms 14 ms 65.83.238.182
8 44 ms 43 ms 42 ms cr1.ormfl.ip.att.net [12.122.106.6]
9 44 ms 42 ms 45 ms cr2.hs1tx.ip.att.net [12.122.1.5]
10 43 ms 44 ms 43 ms cr1.dlstx.ip.att.net [12.122.28.157]
11 42 ms 43 ms 41 ms 12.123.18.17
12 * * * Request timed out.
13 42 ms 43 ms 43 ms border3.tge3-1-bbnet1.ext1.dal.pnap.net [216.52.
191.22]
14 42 ms 42 ms 42 ms te2-1.cer03.dal01.dallas-datacenter.com [216.52.
189.30]
15 42 ms 42 ms 42 ms po3.dar02.dal01.dallas-datacenter.com [66.228.11
8.211]
16 42 ms 42 ms 41 ms po2.fcr04.dal01.dallas-datacenter.com [66.228.11
8.218]
17 42 ms 42 ms 42 ms sip [174.37.45.134]
Trace complete.
This is mine to east..
Tracing route to sip-east01.voipwelcome.com [208.43.68.151]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms my.router [192.168.1.1]
2 10 ms * 9 ms 65.14.126.34
3 10 ms 9 ms 9 ms 65.14.253.61
4 16 ms 16 ms 14 ms 12.83.4.136
5 17 ms 21 ms 16 ms 12.83.4.201
6 16 ms 15 ms 15 ms 65.83.236.122
7 16 ms 14 ms 15 ms 65.83.238.142
8 45 ms 45 ms 44 ms cr2.ormfl.ip.att.net [12.123.34.138]
9 46 ms 46 ms 45 ms cr1.attga.ip.att.net [12.122.5.142]
10 45 ms 46 ms 46 ms cr2.wswdc.ip.att.net [12.122.1.174]
11 45 ms 44 ms 45 ms 12.123.10.137
12 * * * Request timed out.
13 43 ms 43 ms 43 ms border1.te7-1-bbnet1.wdc008.pnap.net [216.52.127
.36]
14 44 ms 44 ms 44 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [6
6.151.100.66]
15 44 ms 43 ms 43 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208
.43.118.134]
16 45 ms 43 ms 43 ms sip [208.43.68.151]
Trace complete.
Things have been very calm today, but if you notice an issue, it would be great if you could post a traceroute right when we notice it.
I had a variety of problems around about 9 am EST. Outbound calling: dead air, busy signal, etc.Quote:
Originally Posted by Hawkmeister
Things seem back to normal today. I did manually reboot my ATA for $#!ts and giggles.
Traceroutes to Central show 25-26 ms.
It does not look very good.Quote:
Originally Posted by VOIPoTim
When was the option for us to change servers removed from Vpanel?Code:chris-desktop (0.0.0.0) Fri Nov 6 15:27:31 2009
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. Access_Denied 0.0% 116 0.7 1.0 0.6 29.1 2.7
2. 10.33.128.1 0.0% 116 8.1 8.2 5.2 19.0 1.7
3. COX-68-12-19-182-static.coxinet.net 0.0% 115 29.7 12.4 5.5 181.2 22.8
4. COX-68-12-19-74-static.coxinet.net 0.0% 115 19.2 17.9 5.6 184.8 29.8
5. COX-68-12-19-2-static.coxinet.net 0.0% 115 9.2 13.2 5.7 73.2 13.7
6. dalsbbrj02-ae2.0.r2.dl.cox.net 0.0% 115 17.5 17.8 12.6 115.4 10.8
7. te3-1.cer03.dal01.dallas-datacenter.com 0.0% 115 15.4 19.0 12.8 156.7 15.6
8. po3.dar01.dal01.dallas-datacenter.com 33.9% 115 13.2 18.1 13.1 136.6 14.1
9. po1.fcr04.dal01.dallas-datacenter.com 0.0% 115 14.9 23.5 13.1 192.9 26.7
10. sip-central01.voipwelcome.com 0.0% 115 17.6 16.4 12.7 48.0 3.9
http://forums.voipo.com/showthread.p...light=voipotimQuote:
Originally Posted by Xponder1
kk tyQuote:
Originally Posted by burris
Oh and Tim here is another view for you (longer period of time)
Code:My traceroute [v0.75]
chris-desktop (0.0.0.0) Fri Nov 6 16:35:38 2009
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. Access_Denied 0.0% 3288 0.7 0.7 0.6 30.3 3.0
2. 10.33.128.1 0.0% 3288 7.7 8.2 5.2 38.5 3.2
3. COX-68-12-19-182-static.coxinet.net 0.1% 3288 8.9 9.1 5.4 199.5 9.3
4. COX-68-12-19-74-static.coxinet.net 0.0% 3288 8.6 16.1 5.4 232.3 28.4
5. COX-68-12-19-2-static.coxinet.net 0.1% 3288 6.2 11.8 5.5 109.5 11.6
6. dalsbbrj02-ae2.0.r2.dl.cox.net 0.0% 3288 14.8 18.3 12.3 159.8 12.7
7. te3-1.cer03.dal01.dallas-datacenter.com 0.1% 3287 14.7 17.7 12.5 232.3 15.9
8. po3.dar01.dal01.dallas-datacenter.com 17.2% 3287 14.6 19.0 12.6 244.7 19.8
9. po1.fcr04.dal01.dallas-datacenter.com 0.1% 3287 16.6 19.9 12.8 247.1 19.3
10. sip-central01.voipwelcome.com 0.1% 3287 17.4 15.8 12.4 43.0 3.2
Xponder1 - Can you try a trace to sip-east01.voipwelcome.com and zeus.voipwelcome.com also to compare?
Quote:
Originally Posted by Xponder1
If anyone else is seeing problems on traces into Dallas, please post them. We have seen a few abnormalities on their end today, but cannot consistently reproduce it and they deny it exists.
Code:Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. Access_Denied 74.8% 144 1.0 0.8 0.7 1.4 0.2
2. 10.33.128.1 0.0% 144 8.6 8.9 5.3 20.0 2.5
3. COX-68-12-19-184-static.coxinet.net 0.0% 144 9.4 10.7 5.6 205.0 16.5
4. COX-68-12-19-88-static.coxinet.net 0.0% 144 9.9 23.5 7.0 210.6 39.8
5. COX-68-12-19-4-static.coxinet.net 0.0% 144 7.3 15.2 6.9 97.1 13.8
6. ashbbbrj02-ae0.0.r2.as.cox.net 0.7% 144 52.9 58.7 49.4 125.4 11.8
7. border1.te7-1-bbnet1.wdc008.pnap.net 0.0% 144 49.3 54.8 49.3 99.9 5.8
8. te1-1.cer01.wdc01.washingtondc-datacenter.com 2.1% 143 53.4 66.6 50.1 329.8 41.3
9. po1.fcr01.wdc01.washingtondc-datacenter.com 0.0% 143 55.3 54.9 49.8 124.4 6.7
10. sip-east01.voipwelcome.com 0.0% 143 58.0 54.3 50.1 66.8 3.2
Code:Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. Access_Denied 0.0% 118 0.7 1.1 0.6 19.6 2.0
2. 10.33.128.1 0.0% 118 18.7 9.2 5.2 18.7 2.3
3. COX-68-12-19-184-static.coxinet.net 0.0% 118 11.0 10.5 5.4 107.0 9.4
4. COX-68-12-19-90-static.coxinet.net 0.0% 118 16.1 23.5 6.7 197.6 34.3
5. COX-68-12-19-4-static.coxinet.net 0.0% 118 14.9 14.9 7.4 82.2 12.3
6. dalsbbrj02-ae2.0.r2.dl.cox.net 0.8% 118 52.8 20.4 13.6 141.6 14.1
7. te3-1.cer03.dal01.dallas-datacenter.com 0.8% 118 28.7 19.7 13.6 164.7 15.4
8. po3.dar01.dal01.dallas-datacenter.com 1.7% 118 16.4 19.0 13.5 122.9 11.6
9. po1.fcr04.dal01.dallas-datacenter.com 0.0% 117 98.6 21.0 13.7 182.6 17.5
10. sip-byod.voipwelcome.com 0.0% 117 16.5 16.9 13.3 29.3 2.1
Based on the results I posted I think I need to call and yell at Cox.
Looking ok from here. (Little intermittent latency on my first hop.)
Tracing route to sip-central01.voipwelcome.com [174.37.45.134]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 172.31.125.1
2 54 ms 12 ms 14 ms 24.113.35.1
3 36 ms 11 ms 12 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 14 ms 18 ms 17 ms wavebroadband-gw.g11-0.oly-cor0.noanet.net [64.146.232.253]
5 17 ms 14 ms 14 ms srp3-0.wtn-cor0.noanet.net [66.119.192.25]
6 14 ms 12 ms 21 ms te1-3.cer01.seattle-datacenter.com [206.81.80.140]
7 * 76 ms 78 ms te8-6.dar01.dal01.dallas-datacenter.com [66.228.118.193]
8 126 ms 78 ms 76 ms po1.fcr04.dal01.dallas-datacenter.com [66.228.118.214]
9 79 ms 81 ms 82 ms sip-central01.voipwelcome.com [174.37.45.134]
Trace complete.
Here's a Neo Trace from me to Dallas..
NeoTrace Trace Version 3.25 Results
Target: sip-central01.voipwelcome.com
Date: 11/6/2009 (Friday), 7:56:12 PM
Nodes: 18
Node Data
Node Net Reg IP Address Location Node Name
1 - - 192.168.1.2 Hollywood burris
2 1 - 192.168.1.1 Unknown
3 2 - 65.14.126.34 Miami
4 3 - 74.253.183.225 Unknown
5 4 - 12.83.4.136 Unknown
6 5 - 12.83.9.93 Unknown
7 6 1 65.83.236.14 Atlanta axr00asm-0-3-1.bellsouth.net
8 6 - 65.83.238.182 32.778N, 79.933W
9 7 2 12.122.106.6 Orlando cr1.ormfl.ip.att.net
10 8 2 12.122.1.5 Houston cr2.hs1tx.ip.att.net
11 9 2 12.122.28.157 Dallas cr1.dlstx.ip.att.net
12 10 - 12.123.18.17 Dallas
13 11 - 12.90.228.14 Unknown
14 12 3 216.52.191.22 Dallas border3.tge3-1-bbnet1.ext1.dal.pnap.net
15 13 4 216.52.189.30 Dallas te2-1.cer03.dal01.dallas-datacenter.com
16 14 4 66.228.118.211 Dallas po3.dar02.dal01.dallas-datacenter.com
17 15 4 66.228.118.218 Dallas po2.fcr04.dal01.dallas-datacenter.com
18 16 - 174.37.45.134 Dallas sip
Packet Data
Node High Low Avg Tot Lost
1 0 0 0 1 0
2 2 2 2 1 0
3 11 11 11 1 0
4 13 13 13 1 0
5 17 17 17 1 0
6 15 15 15 1 0
7 18 18 18 1 0
8 29 29 29 1 0
9 47 47 47 1 0
10 45 45 45 1 0
11 44 44 44 1 0
12 43 43 43 1 0
13 42 42 42 1 0
14 43 43 43 1 0
15 42 42 42 1 0
16 42 42 42 1 0
17 44 44 44 1 0
18 50 50 50 1 0
Network Data
Network id#: 1
OrgName: Internet Assigned Numbers Authority
OrgID: IANA
Address: 4676 Admiralty Way, Suite 330
City: Marina del Rey
StateProv: CA
PostalCode: 90292-6695
Country: US
Network id#: 2
OrgName: BellSouth.net Inc.
OrgID: BELL
Address: 575 Morosgo Drive
City: Atlanta
StateProv: GA
PostalCode: 30324
Country: US
Network id#: 3
OrgName: BellSouth.net Inc.
OrgID: BELL
Address: 575 Morosgo Drive
City: Atlanta
StateProv: GA
PostalCode: 30324
Country: US
Network id#: 4
AT&T WorldNet Services ATT (NET-12-0-0-0-1)
12.0.0.0 - 12.255.255.255
AT&T Worldnet Services ATTSVC-12-80-0-0 (NET-12-80-0-0-1)
12.80.0.0 - 12.83.255.255
Network id#: 5
AT&T WorldNet Services ATT (NET-12-0-0-0-1)
12.0.0.0 - 12.255.255.255
AT&T Worldnet Services ATTSVC-12-80-0-0 (NET-12-80-0-0-1)
12.80.0.0 - 12.83.255.255
Network id#: 6
OrgName: BellSouth.net Inc.
OrgID: BELL
Address: 575 Morosgo Drive
City: Atlanta
StateProv: GA
PostalCode: 30324
Country: US
Network id#: 7
AT&T WorldNet Services ATT (NET-12-0-0-0-1)
12.0.0.0 - 12.255.255.255
AT&T Worldnet Services ATTSVI-12-122-0-0 (NET-12-122-0-0-1)
12.122.0.0 - 12.123.255.255
Network id#: 8
AT&T WorldNet Services ATT (NET-12-0-0-0-1)
12.0.0.0 - 12.255.255.255
AT&T Worldnet Services ATTSVI-12-122-0-0 (NET-12-122-0-0-1)
12.122.0.0 - 12.123.255.255
Network id#: 9
AT&T WorldNet Services ATT (NET-12-0-0-0-1)
12.0.0.0 - 12.255.255.255
AT&T Worldnet Services ATTSVI-12-122-0-0 (NET-12-122-0-0-1)
12.122.0.0 - 12.123.255.255
Network id#: 10
AT&T WorldNet Services ATT (NET-12-0-0-0-1)
12.0.0.0 - 12.255.255.255
AT&T Worldnet Services ATTSVI-12-122-0-0 (NET-12-122-0-0-1)
12.122.0.0 - 12.123.255.255
Network id#: 11
AT&T WorldNet Services ATT (NET-12-0-0-0-1)
12.0.0.0 - 12.255.255.255
AT&T Worldnet Services ATTSVC-12-90-0-0 (NET-12-90-0-0-1)
12.90.0.0 - 12.91.255.255
Network id#: 12
Internap Network Services Corporation PNAP-8-98 (NET-216-52-0-0-1)
216.52.0.0 - 216.52.255.255
InterNAP Network Services, PNAP-DAL PNAP-DAL-INAP-BB-1 (NET-216-52-190-0-1)
216.52.190.0 - 216.52.191.255
Network id#: 13
Internap Network Services Corporation PNAP-8-98 (NET-216-52-0-0-1)
216.52.0.0 - 216.52.255.255
InterNAP Network Services, PNAP-DAL PNAP-DAL-INAP-BB-2 (NET-216-52-189-0-1)
216.52.189.0 - 216.52.189.255
Network id#: 14
SoftLayer Technologies Inc. SOFTLAYER-4-1 (NET-66-228-112-0-1)
66.228.112.0 - 66.228.127.255
SoftLayer Technologies Inc. SOFTLAYER-4-1-DAL01 (NET-66-228-118-0-1)
66.228.118.0 - 66.228.118.255
Network id#: 15
SoftLayer Technologies Inc. SOFTLAYER-4-1 (NET-66-228-112-0-1)
66.228.112.0 - 66.228.127.255
SoftLayer Technologies Inc. SOFTLAYER-4-1-DAL01 (NET-66-228-118-0-1)
66.228.118.0 - 66.228.118.255
Network id#: 16
OrgName: SoftLayer Technologies Inc.
OrgID: SOFTL
Address: 1950 N Stemmons Freeway
City: Dallas
StateProv: TX
PostalCode: 75207
Country: US
Registrant Data
Registrant id#: 1
See Registrant Pane for registrant contact information.
Registrant id#: 2
Registrant:
AT&T Corp
55 Corporate Drive
Bridgewater, NJ 08807
US
Registrant id#: 3
Registrant:
Internap Network Services
250 Williams St
Suite E-100
Atlanta, GA 30303
US
Registrant id#: 4
Registrant:
AS36351.com
ATTN: DALLAS-DATACENTER.COM
c/o Network Solutions
P.O. Box 447
Herndon, VA. 20172-0447
_____
NeoTrace Copyright ©1997-2001 NeoWorx Inc
Leaving the technical part out, I'll just report that I too have been experiencing this problem off and on all day today.
After the issues I had yesterday and this morning, it seems pretty solid. I've made and received a number of calls. I even called my son in Spain, the better to use my 60 minutes of International calls, and the connection was fabulous.
Our pings and traceroutes here are solid right now.
Peace,
Gene
No dial tone around 5:15 Pacific time. Service has returned. Currently do have a dial tone.
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.