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

[#1]

Thanks for the link:
I'm currently connected to gateway pcl-ag04.
Even though support noted those gateways as working please remember they only work for a short period after power cycling, 20-40 minutes or so later the seem to revert to not working as they should.

[#2]

Do you have a BQM for your connection - http://www.thinkbroadband.com/ping/monitors.html ? It might be worth setting one up if you don't.
The university portal you can't access - can you try a traceroute and see where it fails?

[#3]

Or is it possible after 20-40 minutes you got hopped to a different gateway?
PPP drops and re-establishments can readily happen without a resynch and in such cases happen very quickly.  I have not identified the cause of this when I have seen it.

[#4]

I'm not sure what a BQM is?  What will it do for me?  I tried that link but it's asking me for a login?
I can do a trace route but I don't have my partners login (that'll be tonight before I can test that) , I could trace route one of the other failing URL's?  Would it also help if I performed the trace route on the same URL using both PN and O2?  As O2 never fails to load the page would this give insight?

[#5]

BQM (Broadband Quality Monitor) is like you see in Townman's signature. It's basically a ping is sent to your router every second of the day and the results are collated on a graph. It essentially shows the latency of your connection and any packet loss. You need to sign up (it is free), but it can be useful to see if you have problems on your line.
A traceroute to the URL address is fine (you won't need the login) - it would need to be in the format like community.plus.net (with no http or address after that). Just from your PN connection should be fine. In theory, if site does not load at all for you, the traceroute should fail somewhere.

[#6]

Andy & Ken,
Remember that he BQM needs a static IP address.
Cheers,
Kevin

[#7]

It does, but you can still use one with a dynamic address. Given kenyoung's problems, even a few hours of a BQM graph could be useful.

[#8]

I'm already on a static IP so that will work.  I'll register next, after I have posted this.
Traceroute has been done on the three URL's that I have consistently seen failed page loads when connected to PN.  My partners portal login will have to wait as I did not explain clearly before, I don't have the password or the URL as the login URL is not an issue, it's the post login URL which is affected.
Traceroute has started…
traceroute to voomka.com (192.163.208.88), 64 hops max, 72 byte packets
1  10.0.1.1 (10.0.1.1)  16.319 ms  4.502 ms  4.008 ms
2  lo0-central10.pcl-ag04.plus.net (195.166.128.185)  33.684 ms  29.402 ms  166.649 ms
3  link-a-central10.pcl-gw01.plus.net (212.159.2.172)  22.933 ms  161.174 ms  23.319 ms
4  xe-0-2-0.pcl-cr01.plus.net (212.159.0.204)  172.628 ms  23.520 ms  166.752 ms
5  ae1.ptw-cr01.plus.net (195.166.129.0)  24.841 ms  24.811 ms  164.632 ms
6  ae2.ptw-cr02.plus.net (195.166.129.5)  22.485 ms  22.542 ms  168.040 ms
7  10gigabitethernet5-1.core1.lon1.he.net (5.57.80.128)  32.408 ms  24.930 ms  164.482 ms
8  10ge3-1.core1.lon2.he.net (72.52.92.222)  22.663 ms  26.400 ms  163.524 ms
9  100ge1-1.core1.nyc4.he.net (72.52.92.166)  192.083 ms  151.339 ms  190.186 ms
10  100ge7-2.core1.chi1.he.net (184.105.223.161)  195.404 ms  165.051 ms  195.338 ms
11  10ge3-2.core1.den1.he.net (184.105.213.86)  195.845 ms  150.710 ms  193.831 ms
12  10ge4-2.core1.slc1.he.net (184.105.222.154)  195.048 ms  158.667 ms  192.342 ms
13  * * *
14  * * *
Traceroute has started…
traceroute to offgridquest.com (162.144.62.181), 64 hops max, 72 byte packets
1  10.0.1.1 (10.0.1.1)  5.277 ms  4.039 ms  6.626 ms
2  lo0-central10.pcl-ag04.plus.net (195.166.128.185)  26.782 ms  24.422 ms  50.497 ms
3  link-b-central10.pcl-gw02.plus.net (212.159.2.174)  23.073 ms  24.132 ms  22.595 ms
4  xe-0-2-0.pcl-cr02.plus.net (212.159.0.206)  22.709 ms  27.181 ms  22.551 ms
5  ae2.pcl-cr01.plus.net (195.166.129.6)  25.250 ms  25.492 ms  44.163 ms
6  ae1.ptw-cr01.plus.net (195.166.129.0)  23.565 ms  22.756 ms  22.742 ms
7  * * *
8  100ge1-1.core1.nyc4.he.net (72.52.92.166)  287.554 ms  88.999 ms  94.092 ms
9  100ge7-2.core1.chi1.he.net (184.105.223.161)  107.591 ms  105.859 ms  105.773 ms
10  10ge3-2.core1.den1.he.net (184.105.213.86)  137.092 ms  135.370 ms  450.099 ms
11  10ge4-2.core1.slc1.he.net (184.105.222.154)  147.153 ms  147.047 ms  148.811 ms
12  * * *
13  * * *
Traceroute has started…
traceroute to www.nyc-architecture.com (66.96.132.67), 64 hops max, 72 byte packets
1  10.0.1.1 (10.0.1.1)  4.333 ms  3.905 ms  3.932 ms
2  lo0-central10.pcl-ag04.plus.net (195.166.128.185)  24.165 ms  27.945 ms  23.277 ms
3  link-b-central10.pcl-gw02.plus.net (212.159.2.174)  22.754 ms  24.860 ms  22.369 ms
4  xe-0-2-0.pcl-cr02.plus.net (212.159.0.206)  22.645 ms  24.403 ms  22.536 ms
5  ae1.ptw-cr02.plus.net (195.166.129.2)  23.001 ms  31.943 ms  32.700 ms
6  ae2.ptw-cr01.plus.net (195.166.129.4)  22.496 ms  23.116 ms  22.448 ms
7  te-4-2.car5.london1.level3.net (217.163.45.249)  22.917 ms  22.909 ms  22.849 ms
8  ae-52-52.csw2.london1.level3.net (4.69.139.120)  24.647 ms  23.162 ms  22.952 ms
9  ae-228-3604.edge3.london1.level3.net (4.69.166.158)  23.060 ms  22.495 ms  22.708 ms
10  be3043.ccr22.lon01.atlas.cogentco.com (130.117.15.245)  24.103 ms  24.058 ms  25.308 ms
11  be2317.mpd22.lon13.atlas.cogentco.com (154.54.73.177)  25.591 ms
   be2315.ccr22.lon13.atlas.cogentco.com (154.54.73.109)  24.450 ms  23.910 ms
12  be2391.ccr22.bos01.atlas.cogentco.com (154.54.44.237)  109.748 ms
   be2389.ccr22.bos01.atlas.cogentco.com (154.54.44.181)  109.714 ms  111.895 ms
13  * * *
14  * *

[#9]

That was nice and easy to do - http://www.thinkbroadband.com/ping/share/b61c7bb3bf60258514dc4f6c19944c8c.html

[#10]

You need to enable your router to respond to WAN ping requests - if you have the TG582N, it's under Toolbox > Firewall > Allow PING on your WAN interface.

[#11]

I don't use PN's router, getting around the "double NAT' issue seemed impossible so I use an Apple Airport for the PPPoE connection.
Am guessing that it will not work?

[#12]

It should work - you need to make sure you've got the right static IP set in the monitor.
There might be a setting for the Apple Airport to respond to ping requests.

[#13]

The IP in the monitor was auto filled, I've double checked it and it's definitely correct.
Also, a quick check online of the Apple Airports and it would seem that you are NOT able to disable a ping sent to the WAN connection https://discussions.apple.com/thread/2376279
It looks like port 1 is used for this service, I have got port forwarding set to a server sitting on my network (which has a firewall set to stealth mode) however port 1 is not forwarded to it (it's manly a web and media server)

[#14]

Ah, I have enabled the local host on the PlayStation (which is currently off), if the DMZ (local host) is enabled then all other services that are not mapped go to the local host?  (I.E. the ping is being routed to a device that is off?)
In the mean time I have disabled the local host on my router to see if this makes a difference.

[#15]

Ah...that would be the reason.
So if you set your PS as the DMZ, all ping requests would be forwarded to it. If the PS is off, it won't respond etc.
Out of interest, can you try seeing if you can use the TuGo service with DMZ turned off?