Calls intermittently going directly to voicemail

**oldcqr** · 04-04-2010 08:04 PM

Anyone else experiencing incoming calls going directly to voicemail tonight? (4/4/2010 10PM EST)?

I'm calling my voipo line from my cell phone and about 50% of the time it rings. The other half of the time, the call goes directly to voicemail.

Naturally, I've rebooted everything a couple of times....

It's a shame.. Everything had been working for the past 2 weeks, and the service was gaining my trust.

**oldcqr** · 04-04-2010 08:10 PM

Hmmm.....

C:\Users\Mike>tracert sip-central01.voipwelcome.com

Tracing route to sip-central01.voipwelcome.com [174.37.45.134]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms myrouter.home [192.168.1.1]
2 8 ms 6 ms 7 ms L100.TAMPFL-VFTTP-76.verizon-gni.net [96.254.233
.1]
3 9 ms 11 ms 10 ms G3-1-876.TAMPFL-LCR-08.verizon-gni.net [130.81.1
10.228]
4 10 ms 9 ms 9 ms so-6-1-0-0.TPA01-BB-RTR2.verizon-gni.net [130.81
.29.242]
5 68 ms 64 ms 64 ms ge-1-0-0-0.ATL01-BB-RTR2.verizon-gni.net [130.81
.17.48]
6 69 ms 96 ms 72 ms 0.ge-x-x-0.XT2.ATL4.ALTER.NET [152.63.80.13]
7 89 ms 86 ms 87 ms 0.ge-7-2-0.XL4.DFW7.ALTER.NET [152.63.0.54]
8 87 ms 89 ms 86 ms TenGigE0-7-4-0.GW4.DFW13.ALTER.NET [152.63.101.4
9]
9 89 ms 89 ms 89 ms internapGIGE1-gw.customer.alter.net [65.208.15.2
30]
10 87 ms 89 ms 86 ms border3.tge4-1-bbnet2.ext1.dal.pnap.net [216.52.
191.83]
11 91 ms 88 ms 86 ms te2-1.cer03.dal01.dallas-datacenter.com [216.52.
189.30]
12 * 273 ms 209 ms po3.dar01.dal01.dallas-datacenter.com [66.228.11
8.209]
13 86 ms 87 ms 89 ms po1.fcr04.dal01.dallas-datacenter.com [66.228.11
8.214]
14 88 ms 84 ms 86 ms sip-central01.voipwelcome.com [174.37.45.134]

Trace complete.

**usa2k** · 04-04-2010 08:24 PM

The tracert seems to be a strong indicator.

Code:

C:\Users\jn\Pictures\dwn>tracert sip-central01.voipwelcome.com

Tracing route to sip-central01.voipwelcome.com [174.37.45.134]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     9 ms     9 ms     8 ms  te-8-2-ur02.canton.mi.michigan.comcast.net [68.85.85.89]
  4     9 ms     9 ms     9 ms  te-9-2-ur02.vanburen.mi.michigan.comcast.net [68.87.190.118]
  5    14 ms    13 ms     8 ms  te-0-6-0-4-ar01.taylor.mi.michigan.comcast.net [68.87.190.41]
  6    23 ms    22 ms    33 ms  pos-2-8-0-0-cr01.mclean.va.ibone.comcast.net [68.86.90.105]
  7    42 ms    42 ms    42 ms  pos-1-10-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.86.126]
  8    67 ms    63 ms    65 ms  pos-1-14-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.153]
  9    62 ms    61 ms    62 ms  pos-0-0-0-0-pe01.1950stemmons.tx.ibone.comcast.net [68.86.86.90]
 10    64 ms    63 ms    64 ms  softlayer-cr01.dallas.tx.ibone.comcast.net [75.149.228.34]
 11    63 ms    75 ms    63 ms  po2.dar02.dal01.dallas-datacenter.com [66.228.118.207]
 12    63 ms    64 ms    61 ms  po2.fcr04.dal01.dallas-datacenter.com [66.228.118.218]
 13    64 ms    63 ms    64 ms  sip-central01.voipwelcome.com [174.37.45.134]

Trace complete.

Looking fine at the moment from my direction (Canton, MI)
I don't pass through that router.

I suggest to submit a ticket

**oldcqr** · 04-04-2010 08:32 PM

I've done several now, and about 1/2 the time they go south. And when they do it is at hop 12.

Code:

  1     1 ms     2 ms     1 ms  myrouter.home [192.168.1.1]
  2     7 ms     7 ms     9 ms  L100.TAMPFL-VFTTP-76.verizon-gni.net [96.254.233
.1]
  3    10 ms    11 ms    11 ms  G3-1-876.TAMPFL-LCR-08.verizon-gni.net [130.81.1
10.228]
  4    12 ms    12 ms     9 ms  so-6-1-0-0.TPA01-BB-RTR2.verizon-gni.net [130.81
.29.242]
  5    66 ms    64 ms    64 ms  ge-1-0-0-0.ATL01-BB-RTR2.verizon-gni.net [130.81
.17.48]
  6    66 ms    66 ms    67 ms  0.ge-x-x-0.XT2.ATL4.ALTER.NET [152.63.80.13]
  7    83 ms    86 ms    83 ms  0.ge-7-2-0.XL4.DFW7.ALTER.NET [152.63.0.54]
  8    92 ms    84 ms    89 ms  TenGigE0-7-1-0.GW4.DFW13.ALTER.NET [152.63.101.2
5]
  9    83 ms    84 ms    87 ms  internapGIGE1-gw.customer.alter.net [65.208.15.2
30]
 10    88 ms    89 ms    91 ms  border3.tge4-1-bbnet2.ext1.dal.pnap.net [216.52.
191.83]
 11    82 ms    81 ms    82 ms  te2-1.cer03.dal01.dallas-datacenter.com [216.52.
189.30]
 12    87 ms    86 ms     *     po3.dar01.dal01.dallas-datacenter.com [66.228.11
8.209]
 13    86 ms    85 ms    88 ms  po1.fcr04.dal01.dallas-datacenter.com [66.228.11
8.214]
 14    87 ms    87 ms    87 ms  sip-central01.voipwelcome.com [174.37.45.134]

**scott2020** · 04-04-2010 09:07 PM

Originally Posted by oldcqr

I've done several now, and about 1/2 the time they go south. And when they do it is at hop 12.

Code:

  1     1 ms     2 ms     1 ms  myrouter.home [192.168.1.1]
  2     7 ms     7 ms     9 ms  L100.TAMPFL-VFTTP-76.verizon-gni.net [96.254.233
.1]
  3    10 ms    11 ms    11 ms  G3-1-876.TAMPFL-LCR-08.verizon-gni.net [130.81.1
10.228]
  4    12 ms    12 ms     9 ms  so-6-1-0-0.TPA01-BB-RTR2.verizon-gni.net [130.81
.29.242]
  5    66 ms    64 ms    64 ms  ge-1-0-0-0.ATL01-BB-RTR2.verizon-gni.net [130.81
.17.48]
  6    66 ms    66 ms    67 ms  0.ge-x-x-0.XT2.ATL4.ALTER.NET [152.63.80.13]
  7    83 ms    86 ms    83 ms  0.ge-7-2-0.XL4.DFW7.ALTER.NET [152.63.0.54]
  8    92 ms    84 ms    89 ms  TenGigE0-7-1-0.GW4.DFW13.ALTER.NET [152.63.101.2
5]
  9    83 ms    84 ms    87 ms  internapGIGE1-gw.customer.alter.net [65.208.15.2
30]
 10    88 ms    89 ms    91 ms  border3.tge4-1-bbnet2.ext1.dal.pnap.net [216.52.
191.83]
 11    82 ms    81 ms    82 ms  te2-1.cer03.dal01.dallas-datacenter.com [216.52.
189.30]
 12    87 ms    86 ms     *     po3.dar01.dal01.dallas-datacenter.com [66.228.11
8.209]
 13    86 ms    85 ms    88 ms  po1.fcr04.dal01.dallas-datacenter.com [66.228.11
8.214]
 14    87 ms    87 ms    87 ms  sip-central01.voipwelcome.com [174.37.45.134]

I see the same latency from Missouri on that same router hop. I can't get my trace to paste in for some reason!

It isn't every time, about half I suppose.

**oldcqr** · 04-05-2010 10:51 AM

The tracert and ping are looking much better, but I'm still going to voicemail 1/2 the time.

Ugh. Ticket time.

Edit: Nope, I take that back. The latency looks better, but sure enough hop 12 is still dropping packets.

**Russell** · 04-06-2010 07:25 AM

Originally Posted by oldcqr

The tracert and ping are looking much better, but I'm still going to voicemail 1/2 the time.

Ugh. Ticket time.

Edit: Nope, I take that back. The latency looks better, but sure enough hop 12 is still dropping packets.

I too have had flaky service the past several days. Example: I got a call two minutes ago and only line 1 rang. Could well be related to what I describe in http://forums.voipo.com/showthread.php?t=2323.

**gigaman** · 04-07-2010 08:27 AM

I'm seeing the same issue....both yesterday and today....some calls going directly to vmail.

**oldcqr** · 04-07-2010 10:51 AM

Support swapped me to a different server and then once again had me forward every UDP port from 5004 to 65535. I did so, but by that time things were working fine on their own.

The next day everything was still working, so I removed the port forwarding as a test. As of right now everything is working well. It's definately something outside of my network/configuration/etc.

**scott2020** · 04-07-2010 11:12 AM

VOIPo had some connectivity issues yesterday in the afternoon I believe. It wasn't posted here (since forums were down), only on Twitter I believe. I don't do Twitter but someone told me about it. It seems Dallas gets hit a lot with latency from wherever in the world, and VOIPo has a lot of "stuff" in Dallas. I seem to remember Tim mentioning enhancements coming soon, which will be nice considering Dallas seems to get hammered a lot.