Hi - I have been posting my TCL cable performance issues under the Voip forum here on GZ (http://www.geekzone.co.nz/forums.asp?forumid=43&topicid=48878&page_no=1#277683).

 I note that there are other users/TCL customers expressing similiar frustrations with TCL international performance for youtube and gaming from their Cable broadband connections.  I am wondering if Olof from the TCL IP engineering team can comment please on the issue I am encountering in using voiupbuster.com from a cablebroad band connection here in Christchurch. We have used it very successfully for years and only experienced these non-usability issues over the last few months.
Also Fyi some feedback to my post from a Telecom bigtime broadband user is that he is not having the same problems with Voipbuster that I am experiencing over TCL cable.
Many Thanks...

Here is a copy of my last post fyi:
Hi - An update for those interested - We have now been accessing voipbuster via their SIP server and my Linksys WRP400 for about 5 days now. This certainly improves the performance with the more b/w efficient G729a codec than the web soft client method. However last night we were back to un-useable performance over our TCL cable broadband when trying to call Europe - had to revert to the PSTN to call.

I still think the performance of TCL international links have been degrading over the last few months and this is impacting Voipbuster? I note similiar international peformance grumbles/issues from some users in the TCL GZ forum; Youtube Users (buffering) and gamers (ping times and disconnects) with TCL Cable int'l broadband. I see that Olof/TCL IP team have been working to try and rectify this, putting in some caching for Youtube. I see that there is now a consistent significant time out showing up in my Tracert to Voipbuster.com particularly in the 3rd routing hop at from TCL cable to their international gateway and in Europe (see copy of my trace routes if below you are interested). This 3 hop timeout is not evident in national/NZ traffic request (this tracert incl below), so my guess it is something to do with TCL's international traffic management ??

I also see that TCL/Reach are now using different transit carriers on their routes to Europe - there appears to be significant congestion on route?? I think I will open another posting in the TCL section and see if Olof will comment on Voip international performance.

C:\Documents and Settings\Owner>tracert www.voipbuster.com

Tracing route to www.voipbuster.com []
over a maximum of 30 hops:

1 31 ms <1 ms <1 ms
2 11 ms 11 ms 10 ms 121-72-239-1.cable.telstraclear.net [121.72.239.
3 * * * Request timed out.
4 21 ms 22 ms 22 ms ie1-g-0-0-0.telstraclear.net []
5 23 ms 22 ms 23 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.
6 22 ms 22 ms 21 ms
7 147 ms 148 ms 147 ms i-3-1-0.wil-core02.bx.reach.com []

8 148 ms 148 ms 148 ms i-1-1.tlot03.bi.reach.com []
9 154 ms 148 ms 156 ms gin-eql-icore1.tatacommunications.com [206.223.1
10 148 ms 149 ms 148 ms if-11-0-0-28.mcore3.LAA-LosAngeles.as6453.net [2]
11 224 ms 224 ms 225 ms if-4-0.mcore3.NJY-Newark.as6453.net []

12 308 ms 308 ms 308 ms
13 307 ms 308 ms 320 ms
14 302 ms 301 ms 303 ms ix-13-3.icore1.F2C-Frankfurt.as6453.net [195.219
15 * * * Request timed out.
16 302 ms 301 ms 301 ms
17 300 ms 359 ms 301 ms

Trace complete.

  Reply # 277683 posted on 29-NOV-2009 09:58
send private message user's profile quote this post edit my reply

C:\Documents and Settings\Owner>tracert www.clear.net.nz

Tracing route to clear.net.nz []
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms
  2    10 ms     8 ms     9 ms  121-72-239-1.cable.telstraclear.net [121.72.239.
  3    21 ms    22 ms    25 ms  cs2-e3-5-acld.auckland.clix.net.nz [203.167.243.
  4    23 ms    23 ms    22 ms  front2-clix.clear.net.nz []
  5    23 ms    21 ms    23 ms  www.clearnet.co.nz []

Trace complete.

C:\Documents and Settings\Owner>