Status Tests: Difference between revisions

(15 intermediate revisions by 2 users not shown)

Line 1:

__FORCETOC__

==BT Sync Status Test==

==Overview==

These tests will show the sync status of the line and as well as some other details such as errors etc. They may also state if a fault has been identified.

See below for details on running Status Tests on BT ADSL, BT FTTC and TalkTalk ADSL lines...

⚫

==BT ADSL Sync Status Test==

{{CPbox|#Click on the line you want to run the test on

#Click on the Status Test button}}

⚫

*Available on BT ADSL lines.

===Availability===

⚫

Available on BT ADSL lines.

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:

===Example output===

<pre>

BT Test xDSL Status Check:Pass Standalone sub test passed successfully. Pass OK. Circuit In Sync.

Line 13:

Line 22:

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 ~~854Kb~~/s, and a '''Down Sync''' of ~~6551Kb~~/s.

This shows the line is '''In Sync''', with an '''Up Sync''' of 854kbit/s, and a '''Down Sync''' of 6551kbit/s.

<pre>

Line 21:

Line 30:

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 - ie, the Down Sync ('''6,144''') is less than the Fault Threshold Rate ('''6,374'''). The line speed is below what it should be and would need looking in to. See: [[:Category:~~Slow_ADSL~~]]

This one shows that the line has a '''FTB''' - Fault Threshold Breach - i.e., the Down Sync ('''6,144''') is less than the Fault Threshold Rate ('''6,374'''). The line speed is below what it should be and would need looking in to. See: [[:Category:Slow ADSL]]

==FTTC End to End Test==

==BT FTTC End to End Test==

{{CPbox|#Click on the line you want to run the test on

#Click on the E2E Test button}}

===Availability===

⚫

Available on BT FTTC/FTTP lines.

⚫

*Available on BT FTTC/FTTP lines.

This will run FTTC/FTTP specific tests and will suggest if it finds a fault or not.

Example result:

===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.

Line 41:

Line 55:

</pre>

...then the line is probably not in sync (no sync figures given).

A fault has been found, but BT are aware already:

<pre>

Fail:ASSOCIATE_1002 Service found to be affected by existing network event. If fault is known to be caused by something other than the existing network event, please submit a trouble report

</pre>

(Also seen: ASSOCIATE_1000)

==TalkTalk ADSL Status Tests==

[[File:TTW-tests.png|none|frame|TalkTalk Tests]]

===Get Sync Status===

This will return the current sync status of the line

===Example result===

[[File:TTW-Sync-Result.png|border]]

OperStatus:

This is the Operational Status of the Port in the exchange.

*Activating - Line not in sync. This does not mean a modem/router is plugged in, it just means it's waiting for a modem to sync up

*UP - Line is in sync

==TalkTalk Historical Status Tests==

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]]

[[Category:Line Tests]]