Incoming calls go directly to voicemail... sometimes

Posts: 2257 · Posted: Fri Apr 07, 2006 3:12 pm Post subject:

Nothing obvious there.

What I was looking for was high latency or some sort of connection problem that might cause the Vonage SIP (Session Initiation Protocol) packet not to reach your Vonage device. This is where packets would come from to tell you that you have a call. However, from that one sample, your connection looks pretty good.

Those SIP packets should be coming from sip.vonage.net - if you have the capability you may want to monitor your router or firewall for packets to/from sip.vonage.net and do a few test calls, and maybe do a couple of tracerts there to see if you are having any trouble connecting there.

Vonage chose (probably wisely) to make the sip.vonage.net server non-pingable, so you cannot test connectivity directly to it. However, a few trace routes can at least tell you if there is an issue between your Vonage device and Vonage's SIP servers.

Posts: 12 · Vonage Forum Associate Joined: Mar 27, 2006 Posts: 12

Where do you suggest I tracert to? doing a tracert to sip.vonage.com gets me timing out when I start to get close...

Thanks again

Posts: 2257 · Posted: Fri Apr 07, 2006 3:44 pm Post subject:

What are your latency numbers before you get to the "timed out" portion? Once you hit that portion, you're simply talking to servers that are not programmed to respond to pings.

Frankly, it's quite possible that you have a problem with your Vonage adapter, or something else. I'm just looking for any way that the SIP packets may not be reaching your Vonage adapter. Of course, there's no guarantee that IS the problem..

Here are three traces from my machine (My gateway is edited out) to sip.vonage.net to give you an idea. At a guess, I'd say if you are having trouble getting to New Jersey, you may have a connectivity problem to Vonage's SIP server.

Code:

>tracert sip.vonage.net

Tracing route to sip.vonage.net [12.144.47.38]
over a maximum of 30 hops:

1 3 ms <1 ms <1 ms 192.168.1.1
2 12 ms 10 ms 61 ms gw-66-xxxxxx.suscom-maine.net [66.63.xxxxxx]
3 46 ms 9 ms 15 ms ge-suscom-gw-2.gwi.net [207.5.143.237]
4 18 ms 11 ms 8 ms brwkcor1-df-suscomr2-df.gwi.net [207.5.143.133]
5 34 ms 39 ms 17 ms 340c-dist-r1--g6-0--sonet.gwi.net [66.63.104.73]
6 36 ms 18 ms 16 ms ptld-uplink-r1-g2-0--sonet.gwi.net [66.63.104.6]
7 25 ms 21 ms 20 ms bos-edge-03.inet.qwest.net [65.112.16.181]
8 23 ms 37 ms 23 ms bos-core-02.inet.qwest.net [205.171.28.33]
9 62 ms 24 ms 81 ms jfk-core-01.inet.qwest.net [205.171.8.18]
10 30 ms 24 ms 25 ms jfk-brdr-02.inet.qwest.net [205.171.230.25]
11 28 ms 29 ms 70 ms qwest-gw.n54ny.ip.att.net [192.205.32.169]
12 40 ms 39 ms 62 ms tbr1-p010401.n54ny.ip.att.net [12.123.3.57]
13 32 ms 102 ms 78 ms gbr1-p10.n54ny.ip.att.net [12.122.11.2]
14 29 ms 42 ms 29 ms ar1-p310.nbknj.ip.att.net [12.123.214.97]
15 * * * Request timed out.
16 ^C

>tracert sip.vonage.net

Tracing route to sip.vonage.net [12.144.47.38]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 12 ms 11 ms gw-66-xxxxx.suscom-maine.net [66.63.xxxx]
3 37 ms 8 ms 11 ms ge-suscom-gw-2.gwi.net [207.5.143.237]
4 125 ms 25 ms 182 ms brwkcor1-df-suscomr2-df.gwi.net [207.5.143.133]

5 28 ms 92 ms 35 ms 340c-dist-r1--g6-0--sonet.gwi.net [66.63.104.73]

6 26 ms 45 ms 89 ms ptld-uplink-r1-g2-0--sonet.gwi.net [66.63.104.6]

7 45 ms 49 ms 24 ms bos-edge-03.inet.qwest.net [65.112.16.181]
8 23 ms 21 ms 44 ms bos-core-02.inet.qwest.net [205.171.28.33]
9 34 ms 30 ms 48 ms jfk-core-01.inet.qwest.net [205.171.8.18]
10 42 ms 23 ms 35 ms jfk-brdr-02.inet.qwest.net [205.171.230.25]
11 24 ms 43 ms 129 ms qwest-gw.n54ny.ip.att.net [192.205.32.169]
12 42 ms 40 ms 124 ms tbr1-p010401.n54ny.ip.att.net [12.123.3.57]
13 79 ms 29 ms 126 ms gbr1-p10.n54ny.ip.att.net [12.122.11.2]
14 64 ms 37 ms 36 ms ar1-p310.nbknj.ip.att.net [12.123.214.97]
15 * ^C

>tracert sip.vonage.net

Tracing route to sip.vonage.net [12.144.47.38]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 16 ms 11 ms 38 ms gw-66-xxxx.suscom-maine.net [66.63.xxxx]
3 175 ms 75 ms 175 ms ge-suscom-gw-2.gwi.net [207.5.143.237]
4 44 ms 11 ms 22 ms brwkcor1-df-suscomr2-df.gwi.net [207.5.143.133]

5 177 ms 48 ms 37 ms 340c-dist-r1--g6-0--sonet.gwi.net [66.63.104.73]

6 123 ms 21 ms 14 ms ptld-uplink-r1-g2-0--sonet.gwi.net [66.63.104.6]

7 104 ms 41 ms 59 ms bos-edge-03.inet.qwest.net [65.112.16.181]
8 59 ms 58 ms 51 ms bos-core-02.inet.qwest.net [205.171.28.33]
9 29 ms 54 ms 34 ms jfk-core-01.inet.qwest.net [205.171.8.18]
10 23 ms 25 ms 28 ms jfk-brdr-02.inet.qwest.net [205.171.230.25]
11 38 ms 52 ms 28 ms qwest-gw.n54ny.ip.att.net [192.205.32.169]
12 102 ms 35 ms 66 ms tbr1-p010401.n54ny.ip.att.net [12.123.3.57]
13 88 ms 61 ms 68 ms gbr1-p10.n54ny.ip.att.net [12.122.11.2]
14 28 ms 32 ms 35 ms ar1-p310.nbknj.ip.att.net [12.123.214.97]
15 * ^C

Posts: 12 · Vonage Forum Associate Joined: Mar 27, 2006 Posts: 12

Quote:

Tracing route to sip.vonage.net [12.144.47.38]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 2 ms 1 ms 1 ms 192.168.0.1
4 87 ms 89 ms 89 ms ppp-70-224.XXXX.dsl.applwi.ameritech.net [70.
224.xxxx]
5 * 34 ms 44 ms dist1-vlan60.applwi.sbcglobal.net [67.38.56.242]

6 86 ms 88 ms 88 ms bb1-g1-1.applwi.sbcglobal.net [67.38.56.115]
7 84 ms 80 ms 87 ms bb1-p12-1.chcgil.ameritech.net [151.164.191.93]

8 * 102 ms 88 ms ex1-p0-0.eqchil.sbcglobal.net [151.164.42.147]
9 * 90 ms 97 ms ex2-p11-0.eqchil.sbcglobal.net [151.164.40.126]

10 94 ms 88 ms 88 ms sl-st20-chi-0-0.sprintlink.net [144.223.241.57]

11 103 ms 87 ms 88 ms sprint-gw.cgcil.ip.att.net [192.205.32.149]
12 * * 84 ms tbr1-p032501.cgcil.ip.att.net [12.123.6.30]
13 * 53 ms 45 ms tbr1-cl14.n54ny.ip.att.net [12.122.10.1]
14 126 ms 124 ms 116 ms gbr2-p10.n54ny.ip.att.net [12.122.11.6]
15 118 ms 106 ms 123 ms ar1-p3110.nbknj.ip.att.net [12.123.214.101]
16 * * * Request timed out.

Hmmmm seems to me sbcglobal and att are having a few issues....

Keep in mind tho that I'm still working on a 700 mb download (only 4 more of them to go.. Wink

)

Thanks again for the discussion Nate... I appreciate it.

Dusty

Posts: 2257 · Posted: Fri Apr 07, 2006 3:58 pm Post subject:

[quote="pcguy"]

Quote:

Tracing route to sip.vonage.net [12.144.47.38]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 2 ms 1 ms 1 ms 192.168.0.1

OK, first, you are going through at least three routers in your local configuration. That's a tad complex.

Second, what the heck is hop 2 from you? A local device in your route that won't respond to pings from the inside? Odd...

Posts: 12 · Vonage Forum Associate Joined: Mar 27, 2006 Posts: 12

Ok... first I thought I knew what that was all about... now its really weird that I think about it more...

My set up is the following (it was different before I changed things around note a previous post where I changed my network layout...)

DSL Modem (192.168.0.1)
|
RTP300 (192.168.15.1)
|
Router (192.168.1.1)
|
The rest of my network (which gets complicated lol)

So when I do a tracert... it goes from my local PC thru my network (which consists of a 16 port hub) to the router at 192.168.1.1 then to the RTP300 at 192.168.15.1 and finally to my DSL modem at 192.168.0.1 and out to the net...

But based on that, the request timing out in the pinging would be the Vonage Router.... correct?????

Posts: 2257 · Posted: Fri Apr 07, 2006 7:10 pm Post subject:

Move that RTP300 inside your network if you can. You may be putting too much load on the poor dear. Wink

Posts: 12 · Vonage Forum Associate Joined: Mar 27, 2006 Posts: 12

I had the bugger inside my network... and only had the phone attached... that's when the problems started, so I decided to try to hook it directly to the modem to eliminate the possibility of the rest of my network screwing it up...

I WOULD like to move it back inside my network, but trying to get all these bugs shaken out first.. Wink

Thanks!
Dusty