EU Server - Information Required - Page 2

tomblandford · 04-26-2007, 10:27 AM

Quote:

Originally Posted by JeFFJuH

You might want to contact your ISP, and notify them about your problem.

JeFFJuH, not knowing the customer service levels of NTL, you won't realise just how funny that statement you made is!! When I moved house a few years ago, I spent 70 minutes on the phone being passed around and waiting on hold 3 times - no exageration!

JeFFJuH · 04-26-2007, 10:30 AM

Quote:

Originally Posted by tomblandford

JeFFJuH, not knowing the customer service levels of NTL, you won't realise just how funny that statement you made is!! When I moved house a few years ago, I spent 70 minutes on the phone being passed around and waiting on hold 3 times - no exageration!

I know what you mean!

I have the same experience with my cable ISP.
During peak-hours (6pm to 1am) I have a lot of peaking ping times (3000+ ms), which makes gaming and VoIP almost impossible.

My ISP has been notified about it, and they also announced on their website that they are working on it, but nothing changed since March 30th.

cdab · 04-29-2007, 07:03 AM

Hop Address Min (ms) Max (ms) Avg (ms) +/- (ms)
1 10.109.185.1 7.66 13.00 9.85
2 172.16.100.5 9.90 13.45 11.21 1.35
3 at-inn01a-ra1-ge-0-0-0.aorta.net (80.109.253.9) 7.88 10.50 9.25 -1.96
4 at-vie01a-rd1-pos-1-2.aorta.net (213.46.173.225) 14.85 19.54 17.42 8.17
5 at-vie02a-ri1-pos-4-0.aorta.net (213.46.173.6) 17.51 18.91 18.25 0.83
6 p142-con3-gw29-sw2.vie3-Fa0-1.abovenet.at (212.69.168.1) 16.92 19.39 18.08 -0.18
7 ge-2-4.mpr1.vie4.at.above.net (212.69.169.10) 16.40 18.99 17.40 -0.68
8 64.125.23.145 29.87 32.18 31.27 13.87
9 64.125.23.250 46.43 50.36 47.94 16.66
10 pos2-0.cr1.ams2.nl.above.net (208.184.231.54) 41.05 44.45 42.79 -5.15
11 pos3-0.cr2.ams2.nl.above.net (64.125.31.170) 42.46 46.49 44.80 2.01
12 gi3-0.r1.sbp.leaseweb.net (82.98.242.162) 44.91 46.04 45.46 0.66
13 hosted-by.leaseweb.com (85.17.19.194) 43.59 45.39 44.62 -0.83

trottm · 04-29-2007, 08:28 AM

Tom
I don't want to hijack this thread so will post a new question about Voip on NTL.

JeFFJuH · 05-01-2007, 09:50 AM

Yesterday I found out that my connection to eu.voxalot.com was being routed over the Telia network, instead of a direct peer connection.

This caused a latency of ~40 ms instead of ~10 ms.

It seems that this 'problem' has been solved now.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Voxalot and Sipura/ATA Tutorial: A Comprehensive Walkthrough	ctylor	Voxalot General	5	04-28-2010 12:52 AM
VoIP callback server (feature request)	rybshik	Voxalot Support	11	12-17-2007 04:37 PM
Portforwarding and Nat Handling at Voxalot Server	shibukraj	Voxalot Support	3	02-08-2007 11:20 PM

04-29-2007, 07:03 AM	#13
cdab Junior Member Join Date: Apr 2007 Posts: 6 Thanks: 1 Thanked 1 Times in 1 Posts	Hop Address Min (ms) Max (ms) Avg (ms) +/- (ms) 1 10.109.185.1 7.66 13.00 9.85 2 172.16.100.5 9.90 13.45 11.21 1.35 3 at-inn01a-ra1-ge-0-0-0.aorta.net (80.109.253.9) 7.88 10.50 9.25 -1.96 4 at-vie01a-rd1-pos-1-2.aorta.net (213.46.173.225) 14.85 19.54 17.42 8.17 5 at-vie02a-ri1-pos-4-0.aorta.net (213.46.173.6) 17.51 18.91 18.25 0.83 6 p142-con3-gw29-sw2.vie3-Fa0-1.abovenet.at (212.69.168.1) 16.92 19.39 18.08 -0.18 7 ge-2-4.mpr1.vie4.at.above.net (212.69.169.10) 16.40 18.99 17.40 -0.68 8 64.125.23.145 29.87 32.18 31.27 13.87 9 64.125.23.250 46.43 50.36 47.94 16.66 10 pos2-0.cr1.ams2.nl.above.net (208.184.231.54) 41.05 44.45 42.79 -5.15 11 pos3-0.cr2.ams2.nl.above.net (64.125.31.170) 42.46 46.49 44.80 2.01 12 gi3-0.r1.sbp.leaseweb.net (82.98.242.162) 44.91 46.04 45.46 0.66 13 hosted-by.leaseweb.com (85.17.19.194) 43.59 45.39 44.62 -0.83

04-29-2007, 08:28 AM	#14
trottm Junior Member Join Date: Jan 2007 Posts: 28 Thanks: 2 Thanked 2 Times in 2 Posts	Tom I don't want to hijack this thread so will post a new question about Voip on NTL.

05-01-2007, 09:50 AM	#15
JeFFJuH Senior Member Join Date: Jan 2007 Posts: 193 Thanks: 24 Thanked 25 Times in 20 Posts	Yesterday I found out that my connection to eu.voxalot.com was being routed over the Telia network, instead of a direct peer connection. This caused a latency of ~40 ms instead of ~10 ms. It seems that this 'problem' has been solved now.