Comcast vs. Vonage

Posts: 33

Today I have experienced dropped audio for two callers after approximately 10-minutes into the conversation. This intermittent condition has been going on for almost three months with no resolution from Comcast and/or Vonage. I will make no assumptions but feel that we, the paying subscribers, deserve some answers and a time-line for a resolution.

Received Calls
Date Time From Duration (hh:mm:ss)
Mar 27, 2006 04:57 PM 17088704103 00:03:00
Mar 27, 2006 04:26 PM 17082679092 00:01:00
Mar 27, 2006 03:04 PM 17088486956 00:09:00
Mar 27, 2006 02:51 PM 17088486956 00:13:00
Mar 27, 2006 12:16 PM 17732516222 00:51:00
Mar 27, 2006 10:57 AM 17083430228 00:01:00

Modem;
Motorola SB 5100
Software Version: SB5100-2.3.2.5-SCM01-NOSH
Hardware Version: 3
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4

Downstream Value
Frequency 705000000 Hz Locked
Signal to Noise Ratio 37 dB
Power Level 2 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading

Upstream Value
Channel ID 3
Frequency 24000000 Hz Ranged
Power Level 42 dBmV

Wireless-G Broadband Router with 2 Phone Ports
Firmware Version: 1.00.60

COMCAST TECHNICIAN WEB SPEED TEST
Elmhurst/Chicago Area 4 Server
IP Address: 24.14.95.XXX
UPSTREAM: 723Kbps
DOWNSTREAM: 6932Kbps

PING 68.87.224.2 (68.87.224.2): 56 data bytes
64 bytes from 68.87.224.2: icmp_seq=0 ttl=59 time=10.0 ms
64 bytes from 68.87.224.2: icmp_seq=1 ttl=59 time=70.0 ms
64 bytes from 68.87.224.2: icmp_seq=2 ttl=59 time=0.0 ms
64 bytes from 68.87.224.2: icmp_seq=3 ttl=59 time=10.0 ms
64 bytes from 68.87.224.2: icmp_seq=4 ttl=59 time=10.0 ms
64 bytes from 68.87.224.2: icmp_seq=5 ttl=59 time=10.0 ms
64 bytes from 68.87.224.2: icmp_seq=6 ttl=59 time=0.0 ms
64 bytes from 68.87.224.2: icmp_seq=7 ttl=59 time=10.0 ms
64 bytes from 68.87.224.2: icmp_seq=8 ttl=59 time=0.0 ms
64 bytes from 68.87.224.2: icmp_seq=9 ttl=59 time=10.0 ms

--- 68.87.224.2 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 0.0/13.0/70.0 ms

traceroute to 68.87.224.2 (68.87.224.2), 30 hops max, 40 byte packets
1 * * * Request timed out.
2 68.86.116.5 (68.86.116.5) 10 ms 10 ms 10 ms
3 68.87.230.90 (68.87.230.90) 10 ms 10 ms 10 ms
4 68.87.230.101 (68.87.230.101) 10 ms 10 ms 10 ms
5 68.86.114.65 (68.86.114.65) 20 ms 10 ms 10 ms
6 ubr01.chattanooga.tn.chatta.comcast.net (68.87.224.2) 10 ms 10 ms 10 ms

Trace complete.

Vonage Speed Test
My Results
Download 5,211,704 bps
Upload 674,688 bps
QOS 88%
RTT 50 ms
MaxPause 86 ms

PING vonage.com (216.115.22.200): 56 data bytes
64 bytes from 216.115.22.200: icmp_seq=0 ttl=114 time=30.0 ms
64 bytes from 216.115.22.200: icmp_seq=1 ttl=114 time=50.0 ms
64 bytes from 216.115.22.200: icmp_seq=2 ttl=114 time=30.0 ms
64 bytes from 216.115.22.200: icmp_seq=3 ttl=114 time=30.0 ms
64 bytes from 216.115.22.200: icmp_seq=4 ttl=114 time=30.0 ms
64 bytes from 216.115.22.200: icmp_seq=5 ttl=114 time=30.0 ms
64 bytes from 216.115.22.200: icmp_seq=6 ttl=114 time=30.0 ms
64 bytes from 216.115.22.200: icmp_seq=7 ttl=114 time=40.0 ms
64 bytes from 216.115.22.200: icmp_seq=8 ttl=114 time=40.0 ms
64 bytes from 216.115.22.200: icmp_seq=9 ttl=114 time=40.0 ms

--- vonage.com ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 30.0/35.0/50.0 ms

traceroute to vonage.com (216.115.22.200), 30 hops max, 40 byte packets
1 * * * Request timed out.
2 68.86.116.5 (68.86.116.5) 10 ms 10 ms 10 ms
3 68.87.230.85 (68.87.230.85) 10 ms 0 ms 10 ms
4 68.87.230.81 (68.87.230.81) 10 ms 30 ms 10 ms
5 68.87.230.250 (68.87.230.250) 20 ms 10 ms 10 ms
6 12.125.194.9 (12.125.194.9) 10 ms 0 ms 0 ms
7 tbr1-p011901.cgcil.ip.att.net (12.123.4.226) 30 ms 30 ms 30 ms
8 tbr1-cl14.n54ny.ip.att.net (12.122.10.1) 30 ms 30 ms 40 ms
9 gar1-p300.nyzny.ip.att.net (12.123.3.89) 30 ms 30 ms 30 ms
10 12.118.100.38 (12.118.100.3 Cool

30 ms 30 ms 30 ms
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Sad

Posts: 423 · Vonage Forum Evangelist Joined: Oct 03, 2005 Posts: 423

This is the hottest thread of all time! even better than the one about Voip in Qatar...I missed about 20 pages of it though...So give me the reader's digest version...I know what Vonage is saying about this... I wanna know what Comcast is saying. Are people still unable to open the Vonage website from comcast network?

Posts: 33

Today I have been able to connect to the Vonage site from a CHSI connection. Very Happy

Posts: 63 · Posted: Tue Mar 28, 2006 12:52 pm Post subject:

JimBob, I lost a few calls this morning as well. Connection was fine, but just got cut off all of a sudden. I do 24/7 line monitoring on my Comcast line and have not seen any network issues so it's either something on Vonage's side or "something else."

Posts: 33 · Posted: Tue Mar 28, 2006 4:37 pm Post subject: Dropped Audio Issues

As per a reliable source, the dropped audio issues should be resolved by Saturday April 1, 2006. Comcast is cutting in new pipes to resolve capacity issues caused by the rapid deployment of Voip traffic from their Digital Voice, and other Voip providers. Brief service interruptions can be expected until Comcast is finished with their upgrades.

Posts: 63 · Posted: Tue Mar 28, 2006 5:10 pm Post subject:

Thanks Jim, good to know. I'm a bit surprised I haven't seen any blip on my line monitor report given the work Comcast is doing.

Posts: 26 · Vonage Forum Junior Joined: Dec 29, 2005 Posts: 26

I wonder if all the Comcast customers who pay for these service interruptions appreciate what a good deal they are getting *laughs!

Posts: 30 · Vonage Forum Junior Joined: Apr 14, 2005 Posts: 30

JimBob wrote:

As per a reliable source, the dropped audio issues should be resolved by Saturday April 1, 2006. Comcast is cutting in new pipes to resolve capacity issues caused by the rapid deployment of Voip traffic from their Digital Voice, and other Voip providers. Brief service interruptions can be expected until Comcast is finished with their upgrades.

April 1st is April Fools day......... lol bet it's not finished......

Posts: 3 · New Forum Member Joined: Mar 27, 2006 Posts: 3

I understand that in Canada, Voip customers will have to pay and extra 10 bucks per month to the services that supply the Voip service. Will you keep your Vonage, if you have to pay 10 bucks more per month for it? Can comcast do the same here?

Posts: 3 · New Forum Member Joined: Mar 27, 2006 Posts: 3

justice wrote:

I understand that in Canada, Voip customers will have to pay an extra 10 bucks per month to the services that supply the Voip service. Will you keep your Vonage, if you have to pay 10 bucks more per month for it? Can comcast do the same here?

I probably messed that up... here's the article I was referring to:http://www.earthtimes.org/articles/show/5690.html

.....TORONTO - The verbal war between Vonage Canada and cable company Shaw Communications continued to simmer on Wednesday after Shaw responded to Vonage's complaints regarding the $10 Quality of Service Enhancement fee being demanded by it.

Shaw is charging customers this fee for what it refers to as "a quality of service feature that will enhance (Internet telephony) services when used over the Shaw High Speed Internet network."..........