-
23rd April 2014, 06:32 PM
#11
We are having something similar at the moment.
Internet have been "not quite right" but working OK.
The landline rings in OK (as far as I know) but often when we try to ring out there is no dial tone, ring the Landline from the mobile let it ring once and hang up and dial tone is back, and it rings out OK.
Phoned the provider today and they can't (won't) log a fault as they only have 4 fault types and ours isn't one of them
Tonight the ring form mobile trick didn't work. So I unplugged everything except a corded phone into the first socket, and called that from the mobile, the mobile rang but the landline didn't, but connected when I picked up the landline hand set.
Now it's all working again.
Time to start writing it all down.
Oh it has been wet here.
Tony
-
23rd April 2014, 07:02 PM
#12
We sometimes find our landline has dropped out, but turning it off and on fixes it.
Sent from my GT-P5210 using AULRO mobile app
-
23rd April 2014, 07:16 PM
#13
A handy way to check health of your internet connection is to ping google and look for latency or dropped packets.
If you have a windows machine just type cmd in the run box followed by...
ping www.google.com
PING www.google.com (74.125.237.145): 56 data bytes
64 bytes from 74.125.237.145: icmp_seq=0 ttl=57 time=11.905 ms
64 bytes from 74.125.237.145: icmp_seq=1 ttl=57 time=9.545 ms
64 bytes from 74.125.237.145: icmp_seq=2 ttl=55 time=11.885 ms
64 bytes from 74.125.237.145: icmp_seq=3 ttl=55 time=10.849 ms
64 bytes from 74.125.237.145: icmp_seq=4 ttl=55 time=10.480 ms
64 bytes from 74.125.237.145: icmp_seq=5 ttl=57 time=13.864 ms
64 bytes from 74.125.237.145: icmp_seq=6 ttl=55 time=10.965 ms
You should get a response time of between 10 - 30ms and no dropped packets.
Not much you can do to fix it but at least you can tell your service provider that you have dropped packets 
If you want to get more technical you can do a traceroute to help determine where the problems are occurring.
tracert 74.125.237.145 (PC) or traceroute 74.125.237.145 (MAC/Linux)
traceroute to 74.125.237.145 (74.125.237.145), 64 hops max, 52 byte packets
1 10.57.0.1 (10.57.0.1) 13.381 ms 7.465 ms 7.803 ms
2 sbr5-ge0-3.gw.optusnet.com.au (198.142.163.45) 8.730 ms 10.195 ms 10.254 ms
3 59.154.57.52 (59.154.57.52) 37.790 ms
59.154.57.54 (59.154.57.54) 11.224 ms
59.154.57.52 (59.154.57.52) 9.425 ms
4 72.14.196.210 (72.14.196.210) 12.107 ms 10.177 ms 10.310 ms
5 66.249.95.234 (66.249.95.234) 10.427 ms 11.014 ms 10.053 ms
6 72.14.237.137 (72.14.237.137) 16.279 ms 12.347 ms 11.933 ms
7 syd01s13-in-f17.1e100.net (74.125.237.145) 10.759 ms 11.235 ms 10.736 ms
If your phone keeps playing up but internet is ok and they can't sort it out you could always use a VOIP provider like mynetfone and port your number over.
Cheers
Mark
-
23rd April 2014, 08:34 PM
#14
Almost certainly a problem in the copper.
If you are on ADSL in a residential area you are basically going to be reliant on Telstra somewhere along the way.
Had the same problem last year, eventually our provider agreed with what I had told them the week before and lodged the issue with Telstra.
Telstra will spin the 'due to extreme weather events' excuse and fix it eventually. A couple of weeks later we got a call from a contractor that then took about 2 hours to track it to a point where he could swap the pairs over.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Search AULRO.com ONLY!
|
Search All the Web!
|
Bookmarks