Skip to content
jamesdav1's profile

New problem solver

 • 

16 Messages

Wednesday, September 17th, 2014 3:00 PM

Poor Routing

I have Comcast Business Cable in central California and am setting up SIP trunking to a provider with a proxy server in the Los Angeles area (about 200 miles away). Packets between my office and the proxy server are bouncing all over the country causing needless delays. When I do a tracert, packets first go up to Sacramento, then to Los Angeles (same region as the destination), but then bounce to TX, then NY, then to GA then a few more hops to the eventual destination back in Los Angeles. Round trip ping times are in the 70-80ms range which is getting up there for VoIP. I have done the same tracert and pings from AT&T, twtelecom and some other regional ISP's and am consistently seeing 15-30ms ping times and traffic never leaving California on all other providers.

 

My question is, does anyone know if there is a way or department to call at Comcast to have them address this type of routing issue?


My cynical question is, is Comcast deliberately misrouting VoIP traffic to discourage using something other than their voice products?

 

Here is my trace:

 

Tracing route to lax01-01.fs.broadvox.net [208.93.227.212]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.1.5
  2    <1 ms    <1 ms    <1 ms  XXXXXXXXXXX-static.hfc.comcastbusiness.net [XXXXXXXXXX]
  3    36 ms    20 ms    29 ms  73.78.198.1
  4    21 ms    12 ms    10 ms  68.85.105.109
  5     9 ms    11 ms     9 ms  te-0-7-0-0-ur12.sacramento.ca.ccal.comcast.net [68.85.196.133]
  6    16 ms    21 ms    18 ms  he-1-3-0-0-11-cr01.losangeles.ca.ibone.comcast.net [68.86.94.109]
  7    49 ms    48 ms    52 ms  he-0-11-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.87.38]
  8    83 ms    71 ms    70 ms  pos-3-0-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.85.21]
  9    69 ms    66 ms    67 ms  he-0-11-0-0-pe04.56marietta.ga.ibone.comcast.net [68.86.89.90]
 10   114 ms    81 ms    66 ms  64-190-65-130.static.cypresscom.net [64.190.65.130]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14    68 ms    98 ms    69 ms  208.93.227.212

Trace complete.

Problem solver

 • 

305 Messages

10 years ago

I'll agree that it is definitely odd to be doing this. It's possible your IP block is being incorrectly advertised. I'd call up Comcast and ask that they open a request to tier II. If you're lucky you might be able to get them to attach the trace to the request. 

Visitor

 • 

2 Messages

10 years ago

I am having the same trouble with my Broadvox SIP in CA.

 

Mine runs through Georgia to get to CA from NM..