Automatic Line Testing: Difference between revisions
Appearance
Content deleted Content added
m cryptotypgraphic validation |
|||
| (9 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
==Availability== |
|||
| ⚫ | |||
*BT and TT provided ADSL |
|||
*BT provided FTTC or FTTP |
|||
{{CPbox|#Click on the line you want to set testing on |
|||
#Set the options as in the screenshots below}} |
|||
| ⚫ | |||
| ⚫ | |||
It is often useful to run a line test as soon as a line drops, or on a regular basis to help diagnose a fault. For example, if a line is frequently dropping then it is useful to run a line test as soon as it drops to test if it is in sync or not. If the router is keeping sync by dropping, then the fault may not lie in the phone line. |
It is often useful to run a line test as soon as a line drops, or on a regular basis to help diagnose a fault. For example, if a line is frequently dropping then it is useful to run a line test as soon as it drops to test if it is in sync or not. If the router is keeping sync by dropping, then the fault may not lie in the phone line. |
||
| Line 5: | Line 15: | ||
Running tests every hour is useful when diagnosing a fault line as the results will show changed in the line speed, profile and how many errors are occurring. |
Running tests every hour is useful when diagnosing a fault line as the results will show changed in the line speed, profile and how many errors are occurring. |
||
This feature has often been used by staff, |
This feature has often been used by staff, and was added to the customer Control Pages in January 2014, but later removed in October 2016 after receiving complaints from BT regarding the volume of tests performed, causing "a negative impact on [BT's] testing facility". |
||
[[File:Clueless-auto-testing.png|border]] |
|||
| ⚫ | |||
==Type of Tests== |
==Type of Tests== |
||
*For ADSL we will run a 'Status Test' - this will report back the sync speed, the profile, and errored seconds. |
*For ADSL we will run a 'Status Test' - this will report back the sync speed, the profile, and errored seconds. |
||
*For FTTC and FTTP we will run an 'End to End' Test - this will report whether the test equipment has detected a fault and, |
*For FTTC and FTTP we will run an 'End to End' Test - this will report whether the test equipment has detected a fault and, for FTTC, line sync speeds and interleaving depth. |
||
These tests (status and end to end) are non-intrusive and should not cause the line to drop. |
These tests (status and end to end) are non-intrusive and should not cause the line to drop. |
||
| Line 38: | Line 46: | ||
An example ADSL Status test result: |
An example ADSL Status test result: |
||
BT Test XDSLStatusCheckTest:Pass OK.pass OK. Circuit In Sync |
BT Test XDSLStatusCheckTest:Pass OK.pass OK. Circuit In Sync |
||
BRAS= |
BRAS=7150kbit/s FTR=6502kbit/s MSR=8128kbit/s ServOpt=1 I/L=A |
||
Up Sync= |
Up Sync=832kbit/s LoopLoss=6 dB SNR=11.6 dB ErrSec=0 HECErr=0 Cells=6414 |
||
Down Sync= |
Down Sync=8128kbit/s LoopLoss=12 dB SNR=15.5 dB ErrSec=0 HECErr=0 Cells=6205 |
||
[[File:Clueless-auto-testing3.png| |
[[File:Clueless-auto-testing3.png|none|frame|Pins are added to the graph when tests are run]] |
||
[[Category: |
[[Category:Line_Settings]] |
||
[[Category: |
[[Category:Line_Tests]] |
||
[[Category:ADSL]] |
|||