editor
698
edits
Line Diagnostics: Difference between revisions
m
clean up, typos fixed: eg → e.g. (3), 5779Kb/s → 5779Kbit/s (5), 5779Kbit/s → 5779kbit/s (5)
(There are no BE lines anymore (AFAIK)) |
m (clean up, typos fixed: eg → e.g. (3), 5779Kb/s → 5779Kbit/s (5), 5779Kbit/s → 5779kbit/s (5)) |
||
|
==Traffic Dump==
*Available on all lines
This will perform a traffic capture of your line (or lines if you have more than one). You can then view the capture on the page or download a pcap file which can be viewed with other software -
==Sync Status==
Example output:
BT Test xDSL Status Check:Pass Standalone sub test passed successfully.Pass OK. Circuit In Sync
BRAS=
Up Sync=
Down Sync=
==Copper Line Test==
Pass Copper Line Test Successful T300:CIDT LINE TEST OK - END USER EQUIPMENT DETECTED
Sometimes the line test will (cryptically) suggest that a fault needs to be reported to the phone line provider,
BT Test CopperLineTest:Fail Line test failed report fault to OR.fail Line test failed report fault to OR. T023:FAULT - Battery Contact
In this case, report the fault to your phone line provider, if this is BT Retail, then you can report online: https://www.bt.com/faults
If you get a Copper line test error, try the test again with all equipment unplugged, and the NTE5 faceplate removed as the fault could be caused by local wiring or equipment.
<
==BE Line Data and Settings==
*Available on BE Lines
From here you can set the line profile as well as view sync status. This is non-intrusive and should not cause the line to drop.
</
==Kill Buttons==
This option can be useful if there has been a problem between AAISP and BT which has caused your connection to pick up a BT test session (and hence IP) instead of a proper AAISP session/IP.
It can also be useful if you've changed routing options (
===Kill BT / Kill TT ===
==Automatic Tests==
See [[
==Other Control Page pages
<ncl style=bullet maxdepth=5 headings=bullet headstart=2 showcats=1 showarts=1>Category:Control Pages</ncl>
| |||