[VoiceOps] Optimum Online's "Fuzzy" VoIP Routing

J. Oquendo joquendo at e-fensive.net
Mon Apr 2 14:14:28 EDT 2012


Anyone else seeing something wrong with this picture? I have a client 
using Optimum Online as their provider for business VoIP (don't ask), 
and they're complaining of issues.

Aside from them losing registration due to latency (they disconnect 
frequently), I decided to see if there was anything on my end I may have 
missed.

On this one proxy they're connected to, there are I don't even know how 
many clients, yet they're the only ones that keep dropping. I know the 
deductive reasoning here (client's end) just curious how many others have:

1) had issues dealing with Optimum Online
2) seen port based routing on this level out of Optimum


[joquendo at fbsd /home/joquendo]# head -n 13 opt-*

==> opt-80 <== tcptraceroute to port 80

  6  4.68.63.157 (4.68.63.157)  12.682 ms  9.610 ms  9.953 ms
  7  CSC-HOLDING.edge4.NewYork1.Level3.net (4.28.130.62)  14.091 ms  
9.132 ms  9.982 ms
  8  * * *
  9  * * *
10  ool-4353e68e.dyn.optonline.net (67.83.230.142)  6.622 ms  9.577 ms  
9.948 ms
11  * * *

==> opt-5060 <== tcptraceroute to port 5060

  6  4.68.63.157 (4.68.63.157)  9.960 ms  9.335 ms  9.922 ms
  7  CSC-HOLDING.edge4.NewYork1.Level3.net (4.28.130.62)  10.007 ms  
9.284 ms  9.940 ms
  8  * * *
  9  * * *
10  dstswr2-ge3-16.rh.nrwlct.cv.net (67.83.230.134)  6.468 ms  9.886 ms  
9.958 ms
11  * * *

==> opt-8080 <==

  6  4.68.63.157 (4.68.63.157)  9.342 ms  9.306 ms  10.003 ms
  7  CSC-HOLDING.edge4.NewYork1.Level3.net (4.28.130.126)  9.963 ms  
9.075 ms  9.987 ms
  8  * * *
  9  * * *
10  ool-4353e68e.dyn.optonline.net (67.83.230.142)  6.483 ms  9.734 ms  
9.998 ms
11  * * *

==> opt-3128 <==

  6  4.68.63.157 (4.68.63.157)  4.562 ms  3.935 ms  3.933 ms
  7  CSC-HOLDING.edge4.NewYork1.Level3.net (4.28.130.126)  5.955 ms
     CSC-HOLDING.edge4.NewYork1.Level3.net (4.28.130.10)  11.422 ms  
10.366 ms
  8  * * *
  9  * * *
10  ool-4353e68e.dyn.optonline.net (67.83.230.142)  35.487 ms  28.940 
ms  28.441 ms
11  * * *

------------ To make sure it wasn't my machine, jumped on a Linux machine:

myvoip-proxy:~# traceroute -p 5060 173.220.xx.xx
traceroute to 173.220.xx.xx (173.220.xx.xx), 30 hops max, 40 byte packets

  5  64.215.195.230 (64.215.195.230)  3.083 ms  3.330 ms  2.984 ms
  6  CSC-HOLDING.edge4.NewYork1.Level3.net (4.28.130.126)  5.004 ms 
CSC-HOLDING.edge4.NewYork1.Level3.net (4.28.130.62)  4.461 ms 
CSC-HOLDING.edge4.NewYork1.Level3.net (4.28.130.126)  4.830 ms
  7  * * *
  8  * * *
  9  ool-4353e68e.dyn.optonline.net (67.83.230.142)  6.021 ms  5.850 ms  
5.857 ms
10  * * *
11  * * *

myvoip-proxy:~# traceroute -p 80 173.220.xx.xx
traceroute to 173.220.xx.xx (173.220.xx.xx), 30 hops max, 40 byte packets

  5  64.215.195.230 (64.215.195.230)  3.110 ms  3.236 ms  2.986 ms
  6  CSC-HOLDING.edge4.NewYork1.Level3.net (4.28.130.126)  4.727 ms 
CSC-HOLDING.edge4.NewYork1.Level3.net (4.28.130.62)  5.358 ms 
CSC-HOLDING.edge4.NewYork1.Level3.net (4.28.130.10)  6.252 ms
  7  * * *
  8  * * *
  9  ool-4353e68a.dyn.optonline.net (67.83.230.138)  6.027 ms  5.870 ms  
5.858 ms
10  * * *
11  * * *

Whenever I send traffic to port 5060 it ALWAYS takes another route. 
Wondering if Optimum is filtering "reverse" QoS - "no one does VoIP like 
we do!"

-- 
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
J. Oquendo
SGFA, SGFE, C|EH, CNDA, CHFI, OSCP, CPT, RWSP, GREM

"It takes 20 years to build a reputation and five minutes to
ruin it. If you think about that, you'll do things
differently." - Warren Buffett

42B0 5A53 6505 6638 44BB  3943 2BF7 D83F 210A 95AF
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2BF7D83F210A95AF




More information about the VoiceOps mailing list