No dial tone but still have internet

[juiceuk]

I have no dial tone and cannot make or receive calls but I still have the internet Its syncing lower than normal and disconnecting a fair bit. I've reported it to talk talk and have an engineer coming some time tomorrow pm which I thought was pretty good if they turn up. I've unplugged everything, tried different phones and tried the test socket.       

Upstream Speed:   448 kbps
Downstream Speed: 3296 kbps

noise margin upstream: 18 db
output power downstream: 19 db
attenuation upstream: 31 db

noise margin downstream: 11 db
output power upstream: 12 db
attenuation downstream: 50 db

Pings seem all right

C:\Windows\system32>ping -t www.idnet.net

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 43, Received = 43, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 28ms, Average = 24ms
Control-C


Find it quite funny I still have a pretty decent internet connection with the voice line not working.

[Rik]

The voice line is DC and requires a continuous circuit, ADSL is RF and doesn't - though it's obviously less efficient without.

Call your voice provide and report the fault. Don't mention ADSL (unless your VP is IDNet.)

[juiceuk]

I've got an engineer booked for sometime tomorrow pm. The hard-line phone seems to have no power so no current makes sense, interested to know what would be the cause of this type of fault?

[Rik]

A line break, either a cable has snapped or a joint has.

[juiceuk]

Thanks for that Rik 

[Rik]

NP.

[juiceuk]

All Sorted, knew the engineer well so had a good chat too

Upstream Speed:   448 kbps
Downstream Speed: 6240 kbps


noise margin upstream: 27 db
output power downstream: 19 db
attenuation upstream: 18 db

noise margin downstream: 12 db
output power upstream: 12 db
attenuation downstream: 35 db

[Rik]

He should have the target noise margin reset as part of the fault clearance, but as he would have been a voice engineer,  I'd suggest calling support and getting them to reset it. Potentially, then, you will be well into the 7M connection range.