O2's Tu Go service No call volume on incoming or outgoing calls

[#1]

Quote from: AndyH

It could be the Openreach modem

Taking a step back, the OpenReach modem has been the only consistent item in the many many tests that I have done.  Perhaps it is indeed faulty.

[#2]

I suggest trying some more traceroutes for different sites, to see if the traceroute always fails at around the 12th or 13th hop, or perhaps that was just coincidence. Also see if the websites that work always have shorter traceroutes.

[#3]

Hi ejs
Here are the trace routes as requested;

Quote

Traceroute has started… traceroute to www.amazon.com (176.32.98.166), 64 hops max, 72 byte packets 1  10.0.1.1 (10.0.1.1)  4.426 ms  4.092 ms  3.771 ms 2  lo0-central10.pcl-ag02.plus.net (195.166.128.183)  178.411 ms  187.606 ms  21.953 ms 3  link-a-central10.pcl-gw01.plus.net (212.159.2.164)  21.488 ms  22.244 ms  20.672 ms 4  xe-10-1-0.pcl-cr01.plus.net (212.159.0.196)  143.300 ms  157.692 ms  27.385 ms 5  xe-11-2-0.edge3.london2.level3.net (212.187.201.213)  160.736 ms  21.005 ms  23.555 ms 6  vl-3201-ve-128.ebr2.london2.level3.net (4.69.202.177)  329.422 ms  186.417 ms  187.032 ms 7  ae-41-41.ebr1.paris1.level3.net (4.69.159.82)  187.184 ms  188.554 ms  187.649 ms 8  ae-71-71.csw2.paris1.level3.net (4.69.161.82)  187.673 ms  188.562 ms  186.128 ms 9  ae-72-72.ebr2.paris1.level3.net (4.69.161.97)  187.355 ms  185.723 ms  186.680 ms 10  ae-41-41.ebr2.washington1.level3.net (4.69.137.50)  186.362 ms  186.028 ms  186.909 ms 11  ae-72-72.csw2.washington1.level3.net (4.69.134.150)  188.533 ms  157.718 ms  186.784 ms 12  ae-2-70.edge3.washington1.level3.net (4.69.149.81)  187.062 ms  187.534 ms  186.622 ms 13  * * * 14  * * * 15  * * *

Quote

Traceroute has started… traceroute to www.amazon.co.uk (178.236.6.251), 64 hops max, 72 byte packets 1  10.0.1.1 (10.0.1.1)  8.084 ms  4.510 ms  4.152 ms 2  lo0-central10.pcl-ag02.plus.net (195.166.128.183)  23.478 ms  22.641 ms  22.260 ms 3  link-b-central10.pcl-gw02.plus.net (212.159.2.166)  21.551 ms  23.361 ms  21.346 ms 4  xe-10-1-0.pcl-cr02.plus.net (212.159.0.198)  24.670 ms  24.055 ms  21.712 ms 5  ae1.ptw-cr02.plus.net (195.166.129.2)  21.493 ms  22.380 ms  25.565 ms 6  195.66.237.175 (195.66.237.175)  22.132 ms  22.705 ms  22.043 ms 7  178.236.3.57 (178.236.3.57)  31.516 ms  32.303 ms  32.247 ms 8  176.32.106.29 (176.32.106.29)  34.147 ms  32.519 ms  34.317 ms 9  178.236.0.181 (178.236.0.181)  33.005 ms  32.036 ms  36.711 ms 10  178.236.0.213 (178.236.0.213)  34.330 ms  40.200 ms  32.887 ms 11  178.236.14.108 (178.236.14.108)  34.141 ms  34.279 ms  35.210 ms 12  178.236.14.114 (178.236.14.114)  33.845 ms  32.504 ms  33.586 ms 13  178.236.6.251 (178.236.6.251)  31.424 ms  31.688 ms  31.157 ms

Quote

Traceroute has started… traceroute: Warning: www.bbc.co.uk has multiple addresses; using 212.58.246.92 traceroute to www.bbc.net.uk (212.58.246.92), 64 hops max, 72 byte packets 1  10.0.1.1 (10.0.1.1)  4.327 ms  3.977 ms  4.610 ms 2  lo0-central10.pcl-ag02.plus.net (195.166.128.183)  21.824 ms  21.944 ms  24.877 ms 3  link-a-central10.pcl-gw01.plus.net (212.159.2.164)  22.041 ms  21.404 ms  24.522 ms 4  xe-10-1-0.pcl-cr01.plus.net (212.159.0.196)  21.625 ms  21.319 ms  25.042 ms 5  ae1.ptw-cr01.plus.net (195.166.129.0)  22.204 ms  21.326 ms  21.363 ms 6  kingston-gw.thdo.bbc.co.uk (212.58.239.6)  21.794 ms  23.804 ms  22.061 ms 7  * * * 8  ae0.er01.cwwtf.bbc.co.uk (132.185.254.93)  22.159 ms  22.478 ms  22.557 ms 9  132.185.255.165 (132.185.255.165)  23.610 ms  24.320 ms  23.424 ms 10  bbc-vip013.cwwtf.bbc.co.uk (212.58.246.92)  22.628 ms  22.359 ms  22.359 ms

Quote

Traceroute has started… traceroute: Warning: www.bbc.com has multiple addresses; using 212.58.246.95 traceroute to www-bbc-com.bbc.net.uk (212.58.246.95), 64 hops max, 72 byte packets 1  10.0.1.1 (10.0.1.1)  4.436 ms  7.050 ms  3.850 ms 2  lo0-central10.pcl-ag02.plus.net (195.166.128.183)  23.298 ms  21.770 ms  21.713 ms 3  link-b-central10.pcl-gw02.plus.net (212.159.2.166)  21.592 ms  21.711 ms  21.602 ms 4  xe-10-1-0.pcl-cr02.plus.net (212.159.0.198)  23.288 ms  22.461 ms  26.123 ms 5  ae1.ptw-cr02.plus.net (195.166.129.2)  35.521 ms  22.345 ms  37.283 ms 6  ae2.ptw-cr01.plus.net (195.166.129.4)  21.576 ms  21.967 ms  21.279 ms 7  kingston-gw.thdo.bbc.co.uk (212.58.239.6)  21.711 ms  22.908 ms  21.629 ms 8  * * * 9  ae0.er01.cwwtf.bbc.co.uk (132.185.254.93)  161.883 ms  23.006 ms  165.374 ms 10  132.185.255.165 (132.185.255.165)  24.216 ms  164.926 ms  23.320 ms 11  bbc-vip016.cwwtf.bbc.co.uk (212.58.246.95)  22.499 ms  160.795 ms  23.304 ms

Quote

Traceroute has started… traceroute to star.c10r.facebook.com (31.13.64.81), 64 hops max, 72 byte packets 1  10.0.1.1 (10.0.1.1)  4.498 ms  3.785 ms  3.770 ms 2  lo0-central10.pcl-ag02.plus.net (195.166.128.183)  36.416 ms  24.056 ms  23.678 ms 3  link-b-central10.pcl-gw02.plus.net (212.159.2.166)  21.551 ms  21.502 ms  21.615 ms 4  xe-10-1-0.pcl-cr02.plus.net (212.159.0.198)  22.771 ms  21.426 ms  21.323 ms 5  ae2.pcl-cr01.plus.net (195.166.129.6)  23.343 ms  42.801 ms  29.321 ms 6  xe-11-1-0.edge3.london2.level3.net (212.187.201.209)  22.918 ms  21.627 ms  21.411 ms 7  vl-3201-ve-128.ebr2.london2.level3.net (4.69.202.177)  28.499 ms  29.378 ms  29.049 ms 8  ae-42-42.ebr1.paris1.level3.net (4.69.159.86)  30.182 ms  27.965 ms  28.300 ms 9  ae-81-81.csw3.paris1.level3.net (4.69.161.86)  28.166 ms  29.282 ms  28.376 ms 10  ae-3-80.edge3.paris1.level3.net (4.69.168.134)  28.098 ms  28.149 ms  27.979 ms 11  telia-level3.paris1.level3.net (4.68.111.194)  29.823 ms  30.321 ms  29.820 ms 12  prs-bb1-link.telia.net (213.155.134.224)  29.774 ms  30.303 ms  29.264 ms 13  adm-bb3-link.telia.net (213.155.137.146)  34.093 ms    adm-bb3-link.telia.net (213.155.136.20)  34.873 ms    adm-bb3-link.telia.net (213.155.137.136)  34.469 ms 14  adm-b5-link.telia.net (80.91.246.101)  37.808 ms  34.830 ms    adm-b5-link.telia.net (80.91.253.171)  34.579 ms 15  facebook-ic-156922-adm-b5.c.telia.net (62.115.11.50)  34.392 ms  34.116 ms  33.961 ms 16  po126.msw01.05.ams2.tfbnw.net (74.119.76.211)  34.873 ms  34.732 ms  34.029 ms 17  edge-star-shv-05-ams2.facebook.com (31.13.64.81)  33.774 ms  34.729 ms  42.193 ms

Quote

Traceroute has started… traceroute: Warning: www.twitter.com has multiple addresses; using 199.16.156.198 traceroute to twitter.com (199.16.156.198), 64 hops max, 72 byte packets 1  10.0.1.1 (10.0.1.1)  3.554 ms  4.084 ms  4.055 ms 2  lo0-central10.pcl-ag02.plus.net (195.166.128.183)  21.856 ms  158.130 ms  23.907 ms 3  link-a-central10.pcl-gw01.plus.net (212.159.2.164)  21.843 ms  162.758 ms  21.966 ms 4  xe-10-1-0.pcl-cr01.plus.net (212.159.0.196)  144.603 ms  21.917 ms  165.502 ms 5  xe-11-1-0.edge3.london2.level3.net (212.187.201.209)  21.562 ms  22.174 ms  144.490 ms 6  vl-3101-ve-127.ebr1.london2.level3.net (4.69.202.169)  22.143 ms  22.816 ms  21.971 ms 7  ae-46-46.ebr1.london15.level3.net (4.69.159.70)  162.688 ms  22.072 ms  22.121 ms 8  ae-43-43.ebr1.london1.level3.net (4.69.167.26)  164.173 ms  31.045 ms  155.507 ms 9  ae-57-112.csw1.london1.level3.net (4.69.153.118)  22.000 ms  22.116 ms  21.797 ms 10  ae-122-3508.edge4.london1.level3.net (4.69.166.13)  141.577 ms  22.207 ms  22.161 ms 11  twitter-inc.edge4.london1.level3.net (212.113.14.238)  163.349 ms  25.499 ms  166.162 ms 12  xe-1-2-1.iad-cr2.twttr.com (199.16.159.125)  96.547 ms  97.280 ms  96.270 ms 13  ae53.atl1-er1.net.twttr.net (199.16.159.75)  113.025 ms  112.994 ms  112.607 ms 14  199.16.156.198 (199.16.156.198)  113.045 ms  112.368 ms  109.324 ms

[#4]

I take it all of those traceroutes are sites you're able to access?
It's a really strange problem because if it was a faulty network device, then you would expect it to affect everything on Port 80 rather than selective sites.

[#5]

Sorry Andy, yes these are all sites that I can access.  The only one that failed was Amazon.com even though I loaded each page successfully before the trace route.
I totally agree that it is as mad as the Mad Hatters tea party.
In all my years working in IT I've never seen anything like this

[#6]

You seem to have tried everything. The PPPoE connection *should* rule out an issue with your equipment.
I would think replacing the Openreach Modem might be a good idea. Do you have one you could borrow from some friends to test?
Edit: Something else I am wondering - is it possible for Plusnet to do the equivalent of a traffic dump (TCP Dump) their end?

[#7]

It might be worth trying with a lower MTU such as 1430 configured on your computer. I doubt that will help, but in case it does, you could also try setting a MTU of 1492 on your computer.
ADSL connections typically have a MTU of 1500, but PPPoE normally limits the MTU to 1492.

[#8]

Quote from: ejs

I doubt that will help, but in case it does, you could also try setting a MTU of 1492 on your computer. ADSL connections typically have a MTU of 1500, but PPPoE normally limits the MTU to 1492.

it would seem that your doubts are indeed sound.  Both the suggested values do not fix the issue.
I tried both a wifi connected PC and one one ethernet, changing their respective values has not helped http://support.apple.com/kb/ht2532

[#9]

Hi kenyoung,
I've just replied to Ticket: 84535862 advising another step to try.  As advised it appears your router is logged in with the wrong realm (@plus.net instead of @plusdsl.net), if you could update this to correctly end in @plusdsl.net and see if this works.
Thanks,
Dan.

[#10]

Hey, I held off posting this for a while to ensure that all tests were complete.
It would seem that this issue is as simple as logging onto a almost (but not quite) fully functioning domain (plus.net)
Updating the username to be USERNAME@plusdsl.net has resolved the issue.  It would seem that the plus.net domain is not correctly configured.
I believe that it should be either retired or made a mirror of plusdsl.net in order to ensure that this does not happen to anyone again