editor
698
edits
Status Tests: Difference between revisions
m
clean up, typos fixed: ie, → i.e.,, etc) → etc.), 854Kb/s → 854Kbit/s (2), 854Kbit/s → 854kbit/s (2)
m (clean up, typos fixed: ie, → i.e.,, etc) → etc.), 854Kb/s → 854Kbit/s (2), 854Kbit/s → 854kbit/s (2)) |
|||
|
This will report back the current sync status of the line, including error counts. This is non-intrusive and should not cause the line to drop.
===Example output
<pre>
BT Test xDSL Status Check:Pass Standalone sub test passed successfully. Pass OK. Circuit In Sync.
Down Sync=6551kbit/s LoopLoss=40.8 dB SNR=13.5 dB ErrSec=0 HECErr=N/A Cells=4001712
</pre>
This shows the line is '''In Sync''', with an '''Up Sync''' of
<pre>
Down Sync=6144Kb/s FTB LoopLoss=33dB SNR=10dB ErrSec=0 HECErr=0 Cells=-1335203176
</pre>
This one shows that the line has a '''FTB''' - Fault Threshold Breach -
==BT FTTC End to End Test==
This will run FTTC/FTTP specific tests and will suggest if it finds a fault or not.
===Example result
No fault found: (but gives further information about the connection, including sync speed etc.):
<pre>
BT Test E2E Access Test/DCN:Inconclusive OR test pass. Unable to find the fault.
This will return the current sync status of the line
===Example result
[[File:TTW-Sync-Result.png|border]]
The 'Get Line Data' will retrieve a history of the line, up to 7 days at most.
===Example result
[[File:TT-tests-GetLineData.png|none|frame|An example of the historical data returned]]
| |||