traceroute is another way to see delays. the delays look fine as long as they are within 150ms from end to end. however, more importantly jitter is more critical to Voice. if you concern the quality of service, ask SLA from your trunk provider
On Wed, Jan 14, 2009 at 11:20 AM, Bruce Nik <[email protected]> wrote: > > Hi guys, > > What can one decipher out of this? What does a tracert like this tell you > (Let's say you want to sip trunk from s01 to 208.69.56.54 : > > r...@s01 [~]# traceroute 208.69.56.54traceroute to 208.69.56.54 > (208.69.56.54), 30 hops max, 38 byte packets 1 64.86.25.1 (64.86.25.1) > 0.672 ms 0.656 ms 0.664 ms 2 border-tor.velcom.com (206.53.48.253) > 0.766 ms 0.776 ms 0.652 ms 3 > Vlan451.msfc4.TTT-Scarborough.as6453.net(209.58.7.9) 0.577 ms 0.646 ms > 0.454 ms 4 > if-6-2.mcore3.TTT-Scarborough.as6453.net (206.82.134.65) 0.742 ms 0.306 > ms 0.449 ms 5 Vlan464.icore1.TTT-Scarborough.as6453.net (206.82.131.17) > 0.924 ms 1.062 ms 0.654 ms 6 > Vlan4.icore1.CT8-Chicago.as6453.net(206.82.141.1) 21.911 ms > Vlan428.icore1.CT8-Chicago.as6453.net (206.82.131.14) 17.313 ms 17.387 > ms 7 ix-9-1.icore1.CT8-Chicago.as6453.net (206.82.141.38) 16.502 ms > 18.121 ms 16.140 ms 8 te3-4.mpd02.ord01.atlas.cogentco.com(154.54.25.69) > 16.008 ms > vl3491.ccr02.ord01.atlas.cogentco.com (154.54.6.209) 16.028 ms > vl3499.mpd02.ord01.atlas.cogentco.com (154.54.5.9) 16.002 ms 9 > te3-4.ccr02.mci01.atlas.cogentco.com (154.54.5.173) 39.505 ms 39.878 ms > te2-2.ccr02.mci01.atlas.cogentco.com (154.54.25.77) 39.949 ms10 > te9-4.ccr02.dfw01.atlas.cogentco.com (154.54.5.221) 39.817 ms 39.687 ms > 39.461 ms11 te2-2.ccr01.iah01.atlas.cogentco.com (154.54.25.218) 44.796 > ms 45.071 ms 45.123 ms12 te4-7.ccr01.dca01.atlas.cogentco.com(154.54.2.81) > 47.139 ms 47.469 ms 47.638 ms13 > te3-3.ccr02.jfk02.atlas.cogentco.com (154.54.5.245) 47.785 ms > te7-8.ccr02.jfk02.atlas.cogentco.com (154.54.1.234) 47.860 ms > te2-3.ccr02.jfk02.atlas.cogentco.com (66.28.4.125) 47.748 ms14 > te2-2.ccr02.bos01.atlas.cogentco.com (154.54.5.242) 53.626 ms 53.153 ms > 53.139 ms15 te4-4.mpd01.ymq02.atlas.cogentco.com (66.28.4.198) 62.247 > ms 61.736 ms 61.965 ms16 > te2-4.mpd01.yyz02.atlas.cogentco.com(154.54.7.213) 69.283 ms > te3-8.mpd01.yyz02.atlas.cogentco.com (154.54.25.25) 70.074 ms > te2-4.mpd01.yyz02.atlas.cogentco.com (154.54.7.213) 69.188 ms17 > vl3804.na31.b011027-3.yyz02.atlas.cogentco.com (38.20.41.74) 75.088 ms > 71.550 ms vl3504.na31.b011027-3.yyz02.atlas.cogentco.com (38.20.41.70) > 70.287 ms18 38.104.159.118 (38.104.159.118) 70.524 ms 69.993 ms 71.113 > ms19 * > > > If I do this from home, I get 13 hops and both of these two ips are hosted > and they have a higher number of hops. Anyhow, would a SIP trunk of 50 calls > btw the two IPs be a reliable one or not? or am I not providing enough info. > Maybe I should do a ping to see for the delay? > > Thanks, > > > > _________________________________________________________________ > > -- Patrick Song Thinking globally, Networking locally CCVP, CCNP, M.Eng Cell:1-647-868-2950
