 crazyk4952Premium
join:2002-02-04
united state
kudos:1
 ·Charter
 ·Callcentric
·Vitelity VOIP
·voip.ms
| delay in audio I am prefacing this post with the following comment:
I am not trying to start a voip holy war here. I am merely posting my experience and am soliciting feedback from the community. I am NOT trying to bash on any voip providers here....
I use voip.ms as my primary voip provider. However, I have funded accounts with Callcentric and Anveo that I use for testing purposes.
I thought that I would test the delay with each provider by doing the following:
-Place a call to my cell phone from my Gigaset IP phone
-Mute the microphone on my cell phone
-Speak into the receiver of my IP phone and informally measure the delay until my voice reached my cell phone
I am on the west coast and I am registered to the losangeles server for voip.ms.
It seemed to me that the delay for both voip.ms and callcentric was about the same, at less that 0.5 seconds. This was surprising to me since the Callcentric server is in New York.
However, with Anveo, the delay was over 1 second. This surprised me as well since I thought there server was somewhere in the middle of the US!
I am not sure why I got the above results, but I guess physical proximity to the server does not necessarily mean much!  |
|
 TrevIP Telephony AddictPremium
join:2009-06-29
Victoria, BC
kudos:4 | I hear Anveo has been expanding quite rapidly these days. Perhaps using their new in-orbit gateway wasn't your best choice, however. Extra-terrestrial latency is a killer!
--
Wondering what I do? Find out at »www.digitalcon.ca |
|
gweidenh
join:2002-05-18
Houston, TX
kudos:1 | reply to crazyk4952
What are your ping times to the various sip servers?
When you do a tracert to the same servers, how many hops do they go through? Is one provider noticeably "closer"? ie, less hops?
When you do a tracert to the same servers, do they route differently? ie, does one stay on your ISP's private network longer than the others?
There are many variables to network latency. |
|
|
|
crazyk4952Premium
join:2002-02-04
united state
kudos:1 Reviews:
·Charter
·Callcentric
·Vitelity VOIP
·voip.ms
| said by gweidenh:What are your ping times to the various sip servers?
When you do a tracert to the same servers, how many hops do they go through? Is one provider noticeably "closer"? ie, less hops?
When you do a tracert to the same servers, do they route differently? ie, does one stay on your ISP's private network longer than the others?
There are many variables to network latency.
ping (average of about 10 pings each)
losangeles.voip.ms = 32.4ms
sip.anveo.com = 86.5ms
ping.callcentric.com = 95.5 ms
traceroute
losangeles.voip.ms: 15 hops
sip.anveo.com: > 18 hops
(times out after 72.249.128.110 (72.249.128.110))
ping.callcentric.com: > 18 hops
(times out after gi2-4.core1.nyc1.starlan.com (69.60.129.221))
The visible parts of the routes do not change when multiple traceroutes are done. |
|
gweidenh
join:2002-05-18
Houston, TX
kudos:1 | said by crazyk4952:traceroute
sip.anveo.com: > 18 hops
(times out after 72.249.128.110 (72.249.128.110))
Interesting that it times out... when I do a tracert I get:
1 1 ms 4 ms 1 ms
2 9 ms 20 ms 8 ms
3 8 ms 13 ms 13 ms
4 8 ms 13 ms 9 ms
5 14 ms 14 ms 14 ms pos-3-7-0-0-cr01.dallas.tx.ibone.comcast.net [68
.86.90.29]
6 14 ms 15 ms 14 ms xe-10-3-0.edge3.Dallas1.Level3.net [4.71.198.37]
7 17 ms 16 ms 21 ms COLO4-DALLA.edge3.Dallas1.Level3.net [8.9.232.74
]
8 14 ms 14 ms 14 ms 72.249.128.110
9 15 ms 16 ms 21 ms 69.prd1.tms.anveo.com [72.9.149.69]
I dont know if its related, but I do find it concerning that the tracert times out before it completes to the anveo datacenter. |
|
crazyk4952Premium
join:2002-02-04
united state
kudos:1 Reviews:
·Charter
·Callcentric
·Vitelity VOIP
·voip.ms
| I have removed the first few lines in traceroute, but I don't know why mine times out!
traceroute sip.anveo.com
7 bbr01snjsca-tge-0-2-0-6.snjs.ca.charter.com (96.34.2.252) 26.062 ms 26.035 ms 26.014 ms
8 prr01snjsca-tge-1-4.snjs.ca.charter.com (96.34.3.61) 23.292 ms 24.040 ms 24.323 ms
9 sjoeosr03-gex3-1.pac.sta.suddenlink.net (66.76.175.129) 22.952 ms 24.676 ms 23.347 ms
10 * sjoeosr01-10gex1-3.pac.sta.suddenlink.net (66.76.175.33) 24.869 ms 22.958 ms
11 173-219-251-43-link.sta.suddenlink.net (173.219.251.43) 84.930 ms 85.689 ms 85.834 ms
12 173-219-243-37-link.sta.suddenlink.net (173.219.243.37) 84.434 ms 81.899 ms 85.622 ms
13 173-219-243-24-link.sta.suddenlink.net (173.219.243.24) 87.424 ms 87.401 ms 87.510 ms
14 173-219-243-34-link.sta.suddenlink.net (173.219.243.34) 85.845 ms 85.568 ms 85.383 ms
15 173-219-254-171-link.tex.sta.suddenlink.net (173.219.254.171) 81.621 ms 91.392 ms 91.553 ms
16 173-219-246-93-link.sta.suddenlink.net (173.219.246.93) 90.610 ms 90.571 ms 90.585 ms
17 jbdr1.0.dal.colo4.com (206.123.64.41) 89.234 ms 88.943 ms 87.900 ms
18 72.249.128.110 (72.249.128.110) 90.277 ms 90.211 ms *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
traceroute ping.callcentric.com
7 bbr01snjsca-tge-0-2-0-6.snjs.ca.charter.com (96.34.2.252) 37.234 ms 37.148 ms 37.144 ms
8 prr01snjsca-tge-1-2.snjs.ca.charter.com (96.34.3.35) 28.977 ms 28.700 ms 28.875 ms
9 xe-5-0-6.ar2.sjc1.us.nlayer.net (69.22.153.221) 36.715 ms 36.673 ms 36.678 ms
10 ae0-80g.cr1.sjc1.us.nlayer.net (69.22.143.117) 36.501 ms * 50.651 ms
11 xe-1-2-1.cr1.ewr1.us.nlayer.net (69.22.142.138) 95.883 ms 96.868 ms 96.503 ms
12 ae1-70g.ar2.ewr1.us.nlayer.net (69.31.94.118) 91.791 ms 98.056 ms 98.618 ms
13 as8001.xe-3-0-6.ar2.ewr1.us.nlayer.net (69.31.95.130) 96.666 ms 97.120 ms 96.312 ms
14 0.e1-2.tbr1.tl9.nac.net (209.123.10.130) 97.141 ms 97.123 ms 96.910 ms
15 0.po-4.esd1.tl9.nac.net (209.123.10.65) 96.708 ms 96.759 ms *
16 207.99.81.26 (207.99.81.26) 96.596 ms 96.573 ms 96.367 ms
17 gi1-1.core1.nyc3.starlan.com (69.60.129.237) 94.411 ms 90.574 ms 93.834 ms
18 gi2-4.core1.nyc1.starlan.com (69.60.129.221) 255.712 ms 255.670 ms 255.704 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
|
|
gweidenh
join:2002-05-18
Houston, TX
kudos:1 | reply to crazyk4952
Thats concerning. After the x.x.x.110, there should only be one more hop as shown in my tracert.
The fact that it keeps going until the maximum of 30 hops means something isn't right. It could be as simple as a router blocking the ICMP packet, or it could be indicative of a more significant routing issue. Whether it has anything to do with your perceived 'lag' is unknown.
Onsip has a west coast server. Do a tracert to sip.onsip.com and let me see your results. |
|
crazyk4952Premium
join:2002-02-04
united state
kudos:1 Reviews:
·Charter
·Callcentric
·Vitelity VOIP
·voip.ms
| said by gweidenh:Onsip has a west coast server. Do a tracert to sip.onsip.com and let me see your results.
traceroute sip.onsip.com
7 bbr01snjsca-tge-0-2-0-6.snjs.ca.charter.com (96.34.2.252) 28.317 ms 28.952 ms 29.036 ms
8 sjo-bb1-link.telia.net (213.248.72.101) 27.378 ms 27.554 ms 27.513 ms
9 las-bb1-link.telia.net (213.155.135.186) 37.266 ms 37.435 ms 37.522 ms
10 las-b3-link.telia.net (213.155.134.251) 37.872 ms 38.037 ms *
11 * 204.8.22.60 (204.8.22.60) 35.686 ms 31.468 ms
12 core-proxy3.new-york-1.realtime.jnctn.net (199.7.175.103) 34.562 ms !X 41.852 ms !X 40.204 ms !X
|
|
gweidenh
join:2002-05-18
Houston, TX
kudos:1 | OK, that looks normal and has good latency.
I'm leaning towards a routing issue causing high latency with some of the other providers.
|
|
crazyk4952Premium
join:2002-02-04
united state
kudos:1 Reviews:
·Charter
·Callcentric
·Vitelity VOIP
·voip.ms
| said by gweidenh:OK, that looks normal and has good latency.
I'm leaning towards a routing issue causing high latency with some of the other providers.
OK thanks. I suppose there is nothing I can do about it. Not that big of a deal, I just thought it was a little odd. |
|
gweidenh
join:2002-05-18
Houston, TX
kudos:1 | reply to crazyk4952
for sh*ts and giggles, try sip.flowroute.com
That server is located in Las Vegas. Just trying to get an idea of where the routing issue may lie. |
|
crazyk4952Premium
join:2002-02-04
united state
kudos:1 Reviews:
·Charter
·Callcentric
·Vitelity VOIP
·voip.ms
| said by gweidenh:for sh*ts and giggles, try sip.flowroute.com
That server is located in Las Vegas. Just trying to get an idea of where the routing issue may lie.
traceroute sip.flowroute.com
7 67-148-50-33.dia.static.qwest.net (67.148.50.33) 21.782 ms 17.898 ms 21.527 ms
8 63.146.27.70 (63.146.27.70) 22.736 ms 22.435 ms 22.727 ms
9 0.ae3.XL4.SEA1.ALTER.NET (152.63.106.245) 31.768 ms 32.505 ms 32.710 ms
10 0.xe-11-0-0.XL4.VEG2.ALTER.NET (152.63.2.6) 49.166 ms 47.975 ms 48.777 ms
11 GigabitEthernet7-0-0.GW3.VEG2.ALTER.NET (152.63.113.173) 49.217 ms 49.123 ms 48.595 ms
12 switchcomm-gw.customer.alter.net (208.222.10.174) 53.208 ms 53.974 ms 45.556 ms
13 te4-3.las-core2-1.switchnap.com (66.209.64.145) 51.922 ms 51.806 ms 51.772 ms
14 te2-6.las-agg7s1-1.switchnap.com (66.209.64.34) 51.240 ms 51.488 ms 51.204 ms
15 flowroute.demarc1.switchnap.com (216.115.64.190) 50.094 ms 45.280 ms 49.560 ms
16 216.115.69.189 (216.115.69.189) 93.045 ms 103.432 ms 113.627 ms
17 sip-lv1.flowroute.com (216.115.69.144) 50.390 ms 50.573 ms 50.056 ms
|
|
BinkVillains... knock off all that evil
join:2006-05-14
Denver, CO
kudos:4 | reply to crazyk4952
By default, UNIX traceroute tends to use UDP instead of ICMP, which Windows uses, and some people block these UDP packets (and some block ICMP). You might want to try this again using –P 1, which will mimic Windows’ behavior. |
|
crazyk4952Premium
join:2002-02-04
united state
kudos:1 Reviews:
·Charter
·Callcentric
·Vitelity VOIP
·voip.ms
| said by Bink:By default, UNIX traceroute tends to use UDP instead of ICMP, which Windows uses, and some people block these UDP packets (and some block ICMP). You might want to try this again using –P 1, which will mimic Windows’ behavior.
Oh I thought that all traceroute used ICMP! Anyway here they using the ICMP flag (-P did not work, so I used the -I flag)
sudo traceroute -I sip.anveo.com
7 bbr01snjsca-tge-0-2-0-6.snjs.ca.charter.com (96.34.2.252) 25.956 ms 26.932 ms 27.113 ms
8 prr01snjsca-tge-1-4.snjs.ca.charter.com (96.34.3.61) 23.959 ms 24.364 ms 24.348 ms
9 sjoeosr03-gex3-1.pac.sta.suddenlink.net (66.76.175.129) 22.789 ms 24.061 ms 24.397 ms
10 sjoeosr01-10gex1-3.pac.sta.suddenlink.net (66.76.175.33) 23.584 ms 24.338 ms 24.334 ms
11 * * 173-219-251-43-link.sta.suddenlink.net (173.219.251.43) 82.283 ms
12 173-219-243-37-link.sta.suddenlink.net (173.219.243.37) 85.542 ms 85.556 ms 85.531 ms
13 173-219-243-24-link.sta.suddenlink.net (173.219.243.24) 85.988 ms 86.851 ms 86.996 ms
14 173-219-243-34-link.sta.suddenlink.net (173.219.243.34) 83.804 ms 84.691 ms 84.808 ms
15 * 173-219-254-171-link.tex.sta.suddenlink.net (173.219.254.171) 81.428 ms 85.041 ms
16 173-219-246-93-link.sta.suddenlink.net (173.219.246.93) 79.640 ms 86.031 ms 86.042 ms
17 jbdr1.0.dal.colo4.com (206.123.64.41) 84.216 ms 85.167 ms 85.253 ms
18 72.249.128.110 (72.249.128.110) 85.779 ms 85.780 ms 85.746 ms
19 69.prd1.tms.anveo.com (72.9.149.69) 87.092 ms 85.857 ms 81.260 ms
sudo traceroute -I ping.callcentric.com
7 bbr01snjsca-tge-0-2-0-6.snjs.ca.charter.com (96.34.2.252) 27.015 ms 27.938 ms 27.992 ms
8 prr01snjsca-tge-1-2.snjs.ca.charter.com (96.34.3.35) 24.253 ms 24.514 ms 24.438 ms
9 xe-5-0-6.ar2.sjc1.us.nlayer.net (69.22.153.221) 25.025 ms 25.227 ms *
10 ae0-80g.cr1.sjc1.us.nlayer.net (69.22.143.117) 22.856 ms 22.981 ms 23.956 ms
11 xe-1-2-1.cr1.ewr1.us.nlayer.net (69.22.142.138) 94.699 ms 95.596 ms 123.886 ms
12 ae1-70g.ar2.ewr1.us.nlayer.net (69.31.94.118) 123.081 ms 122.939 ms 122.825 ms
13 as8001.xe-3-0-6.ar2.ewr1.us.nlayer.net (69.31.95.130) 122.207 ms 122.120 ms 121.960 ms
14 0.e1-2.tbr1.tl9.nac.net (209.123.10.130) 121.884 ms 121.703 ms 121.583 ms
15 0.po-4.esd1.tl9.nac.net (209.123.10.65) 97.447 ms 97.371 ms 90.488 ms
16 207.99.81.26 (207.99.81.26) 98.110 ms 98.120 ms 98.087 ms
17 gi1-1.core1.nyc3.starlan.com (69.60.129.237) 97.312 ms 97.476 ms 97.679 ms
18 gi2-4.core1.nyc1.starlan.com (69.60.129.221) 97.552 ms 97.589 ms 97.614 ms
19 www.callcentric.com (204.11.192.10) 91.684 ms 98.024 ms 97.828 ms
sudo traceroute -I losangeles.voip.ms
7 bbr01snjsca-tge-0-2-0-6.snjs.ca.charter.com (96.34.2.252) 26.191 ms 27.120 ms 27.201 ms
8 prr01snjsca-tge-7-3.snjs.ca.charter.com (96.34.3.155) 23.872 ms 24.027 ms 24.010 ms
9 xe-5-0-6.ar2.sjc1.us.nlayer.net (69.22.153.221) 24.889 ms 25.083 ms *
10 * * ae0-80g.cr1.sjc1.us.nlayer.net (69.22.143.117) 22.523 ms
11 xe-5-1-0.cr1.lax1.us.nlayer.net (69.22.142.126) 37.045 ms 37.379 ms 28.238 ms
12 ae1-50g.ar1.lax2.us.nlayer.net (69.31.127.130) 37.722 ms 37.746 ms 38.425 ms
13 as29761.xe-1-0-2.ar1.lax2.us.nlayer.net (69.31.121.254) 32.766 ms 33.529 ms 33.763 ms
14 lax9-r1.core01 (67.215.251.142) 33.497 ms 29.930 ms 33.695 ms
15 hosted.by.pacificrack.com (67.215.241.250) 32.792 ms 33.520 ms 33.620 ms
|
|
gweidenh
join:2002-05-18
Houston, TX
kudos:1 | reply to crazyk4952
Awesome advise Bink! |
|
