![]() |
Keep in mind that:
Test Result | Description |
---|---|
Test OK | AT&T tested the circuit and no faults were detected in either the AT&T network or the access portion of the circuit. |
Acceptable FLTS, test OK | AT&T testing detected a very minor anomalous condition. |
Customer Data Level Marg Long | The analog signal was not strong enough depending on the purchased service. If you are currently experiencing problems with this circuit and have not generated a ticket, please create one now. |
[ 1 | 2 | 3 | 4 | 5 | 6 | 7 | 9 | H | J | K | N | Y ]
Vercode | Results |
---|---|
1A | TEST OK |
1B | CSU (Customer Service Unit) OK BUT DSU (Digital or data service unit) FAULT |
1C | CSU LBK (Loopback) FAULT, OCU (Office Channel Unit) OK |
1F | IOC (Interoffice Channel) FAULT BETWEEN TPS (Test Points) |
1G | LBK FLT (Fault) BTWN DEV (Device) and TP |
1J | ABNORM NTWK CTRL Codes |
1K | IOC FLT BTWN TPS |
1M | CXR (Carrier) FAIL-CANT ACCESS |
1Q | TOK BUT PERM LBK CLRD |
1S | ACCESS POINT TERMINATED ACCESS POINT UNMAPPED |
1U | TEST POINT TERMINATED |
1V | TEST OK |
1W | STREAMER CAME CLEAR PERM LOOPBACK CAME CLEAR |
1X | STRMR-SVC DOWN PERM LOOPBACK, SVC DOWN |
1Z | STRMR ISLTD-SVC UP PERM LBK ILSTD, SVC UP |
[ Help Index | Top of Vercode Tables | Top of Page | Glossary ]
Vercode | Results |
---|---|
2A | MASTER LEG FAULT |
2F | OCU Failed to loop |
2G | OCU Loopback Error |
2H | CSU FAILED TO LOOP CSU LOOPBACK ERRORS |
2I | Secondary Channel Fault at the OCU |
2J | FLT NOT SECTIONALIZED |
[ Help Index | Top of Vercode Tables | Top of Page | Glossary ]
Vercode | Results |
---|---|
3A | TEST OK |
3B | CSU OK BUT DSU FAULT |
3C | DSU OR PERM LBK FLT |
3D | CSU OR LOOP FLT |
3E | LEC (Local Exchange Company) FAULT |
3F | IOC FAULT |
3G | CXR FAILURE |
3H | TIMED LOOPBACK_ TP TERMD |
3I | QTOK BUT CUST DATA FLT |
3K | GARBL LEG ISLTD-SVC UP |
[ Help Index | Top of Vercode Tables | Top of Page | Glossary ]
Vercode | Results |
---|---|
4G | NO L/B W/WO PR REVERSL |
[ Help Index | Top of Vercode Tables | Top of Page | Glossary ]
Vercode | Results |
---|---|
5P | DIG MON, ASC (Digital Monitor Abnormal Service Code) |
5Q | DIG MON, MCOS (Digital Monitor Mux Code Out Of Sync) DIG MON, UMC |
5R | xxxx OCU (N) DIDN'T LOOPBACK xxxx OCU (L) DIDN'T LOOPBACK ...where xxxx=2047, FF00, 40, 7E00, 32 |
5S | xxxx OCU (N) LOOPBACK EXCESSIVE ERROR xxxx OCU (L) LOOPBACK EXCESSIVE ERROR ...where xxxx=2047, FF00, 40, 7E00, 32 |
5T | xxxx OCU (N) LOST SYNC xxxx OCU(L) LBK LOST SYNC ...where xxxx=2047, FF00, 40, 7E00, 32 |
5V | DSU(N) DIDNT LOOPBACK (Customer Service Unit Non Latching) DSU(N) LBK EXCESSIVE ERRORS (Digital or Data Service Unit Non Latching) CSU(L) DIDNT LOOPBACK (Customer Service Unit Latching) CSU(N) DIDNT LOOPBACK (Customer Service Unit Non Latching) |
[ Help Index | Top of Vercode Tables | Top of Page | Glossary ]
Vercode | Results |
---|---|
6S | PERMANENT LOOPBACK NOT CLEARED |
[ Help Index | Top of Vercode Tables | Top of Page | Glossary ]
Vercode | Results |
---|---|
71 | NO DATA FROM BRIDGE |
72 | DATA FAULT FROM BRIDGE |
73 | NO DATA FROM MASTER |
74 | DATA FAULT FROM MASTER |
7K | STREAMER ON REMOTE LEG |
[ Help Index | Top of Vercode Tables | Top of Page ]
Vercode | Results |
---|---|
93 | 2004-2804 HZ LOOPBACK FREQ RUN LONG LBK 404 LONG LBK 1804 LONG LBK 2804 LONG LBK 404 HOT LBK 1804 HOT LBK 2804 HOT freq1-freq2 HZ FREQ RUN LONG freq1-freq2 HZ FREQ RUN HOT |
94 | 2004-2804 HZ LOOPBACK FREQ RUN MARG LONG LBK 404 MARG LONG LBK 2804 MARG LONG LBK 404 MARG HOT LBK 1804 MARG HOT LBK 2804 MARG HOT freq1-freq2 HZ LBK FREQ RUN MARG LONG freq1-freq2 HZ LBK FREQ RUN MARG HOT |
9I | EDP (Enhanced Data Parameters) LBK BAD S/N (Signal to Noise) EDP LOOPBACK NOISY |
9V | LBK IMPULSE NOISE BAD LBK DROPOUTS BAD LBK GAIN HITS BAD |
[ Help Index | Top of Vercode Tables | Top of Page | Glossary ]
Vercode | Results |
---|---|
HA | TEST OK |
HF | TEST FAILED, PLS RETRY |
HJ | LOOPBACK DEVICE WAS IN LBK,IT CLEARED |
HN | INCOMPLETE TESTING UNABLE TO ACCESS TP |
HS | FURTHER ANALYSIS RQD |
HY | ACCEPTABLE FLTS, TESTOK |
[ Help Index | Top of Vercode Tables | Top of Page | Glossary ]
Vercode | Results |
---|---|
JP | TEST OK |
[ Help Index | Top of Vercode Tables | Top of Page | Glossary ]
Vercode | Results |
---|---|
KA | LOOPBACK DEVICE NOT RELEASED |
KC | LOOPBACK DIDNT LOOP BACK |
KD | LOOPBACK BAD FREQUENCY |
KE | 1004 HZ LOOPBACK LEVEL LONG 1004 HZ LOOPBACK LEVEL HOT |
KF | 1004 HZ LOOPBACK LEVEL MARG LONG 1004 HZ LOOPBACK LEVEL MARG HOT |
KG | LOOPBACK NOISY LOOPBACK NOISE NOT MEASURED |
KH | LBK VERY LOW LEVEL CUST RCV OVERALL LVL VERY LOW |
KI | FAR END LBK UNRESOLVED |
KO | CUSTOMER DATA LEVEL LONG CUSTOMER DATA LEVEL HOT LOW CUST DATA LEVEL, MASTER STN |
KP | CUSTOMER DATA LEVEL MARG LONG |
KQ | NO CUSTOMER DATA |
[ Help Index | Top of Vercode Tables | Top of Page | Glossary ]
Vercode | Results |
---|---|
NE | REJECTED - CKT DATA INCOMPLETE |
NF | REJECTED - MULTIPT DATA ERROR |
NG | REJECTED - AUTOTEST UNAVAILABLE |
NH | REJECTED - RESULTS UNAVAILABLE |
NJ | REJECTED - CKT NOT FOUND |
NK | REJECTED - DUPLICATE TEST |
NY | REJECTED - SET TABLE ERROR |
NZ | REJECTED - INCOMPAT STRATEGY |
[ Help Index | Top of Vercode Tables | Top of Page | Glossary ]
Vercode | Results |
---|---|
YC | PERMANENT LOOPBACK CLEARED(top) 2047 CSU(L) LOOPBACK PASS(top) NO CTRL CODE DETECTED(top) CSU(L) LBK ALL PATTERNS PASS (top) 2047 DSU(N) LOOPBACK PASS 2047 CSU(N) LOOPBACK PASS A-Z:INTEROFC - ALL PATTERNS PASS 2047 A-Z:INTEROFFICE TEST PASS 2047 OCU(L) LOOPBACK PASS CSU(L) EQUIPPED FOR SEC CHAN (Secondary Channel) MJU LOOPBACK PASS NO PERM LOOPBACK NOISY SEG TERMD-SVC DN NOISY SEG TERMD-SVC UP OCU(L) EQUIPPED FOR SEC CHAN PERM LBK CLEARED PERM LBK TERMD, SVC DN PERM LBK TERMD, SVC UP PERMANENT LOOPBACK NOT DETECTED STREAMER TERMD, SVC DN STREAMER TERMD, SVC UP |
YE | MISCELLANEOUS ERRORS |
YG | SEGMENT TERMINATED TP DATA INCOMPLETE ADDITIONAL ANALYSIS REQUIRED CMD (Command) FAILURE |
YH | LOOPBACK PASS 1004 HZ LBK TSTS PASSED CONTINUITY PASS LBK GAINSLOPE TEST PASSED ACC FAIL, BUT TEST DONE CUSTOMER DATA OK IOT (Interoffice Test) GAINSLOPE TEST PASSED |
YJ | DGCT (Digital Control Table) TABLE ERROR |
[ Help Index | Top of Vercode Tables | Top of Page | Glossary ]
Condition Codes
This section explains some test results for DS1 circuits and the
corresponding condition codes that may appear in the
Detailed Test Results section of the
View Test Results for Circuit screen.
Test Result | Description |
---|---|
Requires Follow-up | An anomaly was detected and additional technical assistance is required to resolve the anomaly. For instance, the initial testing did not isolate the problem to a single element of the circuit. Therefore, the ticket (if created) needs to be referred by AT&T to a technical test group. If you are currently experiencing problems with this circuit and have not generated a ticket, please create one now. |
Possible AP Problem | An anomaly was detected and isolated to outside AT&T's network to the customer's equipment or access provider (AP) equipment. If a ticket was generated, AT&T needs to refer the ticket to the AP for further analysis. If you are currently experiencing problems with this circuit and have not generated a ticket, please create one now. |
Possible CPE Problem | An anomaly was detected and isolated to outside AT&T's network to the customer's equipment or access provider (AP) equipment, with a high indication that the source of the anomaly is in the customer's equipment. |
AP Problem | An anomaly was detected and isolated to the access portion of the circuit (that is, the access provider [AP] equipment). If you are currently experiencing problems with this circuit and have not generated a ticket, please create one now. |
AT&T Problem | An anomaly was detected and isolated to the AT&T network. If you are currently experiencing problems with this circuit and have not generated a ticket, please create one now. |
[ 0 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 100 | ]
Condition Code |
Technical Narrative |
---|---|
001 | Request Format Invalid |
002 | CLFI not found in DSTS |
003 | Configuration is not testable according to DSTS records |
004 | Another user is currently testing the CLFI |
005 | CLFI is currently under scheduled intrusive macro testing |
006 | Current Maximum Requests Exceeded: [XXX] |
007 | Request rejected. Facility has equipment in use on another facility |
[ Help Index | Top of Condition Code Tables | Top of Page | Glossary ]
Condition Code |
Technical Narrative |
---|---|
200 | Test OK after AT&T equipment was cleared of initial loop/signal condition |
201 | Test OK after NI/CSU loop removed |
202 | NI/CSU loop was present and could not be removed |
203 | Network Test OK but AT&T was unable to get data from CPE |
[ Help Index | Top of Condition Code Tables | Top of Page | Glossary ]
Condition Code |
Technical Narrative |
---|---|
301 | CSU or access problem from customer premises to AT&T |
302 | CSU or access problem from AT&T to customer premises Alarm Indication Signal received from Customer site |
303 | CSU or access problems from customer to AT&T on both ends of circuit Performance errors received from Customer site |
304 | CSU or access problems from customer to AT&T and IOC errors found |
305 | CSU or access problems from AT&T to customer premises and IOC errors found |
306 | CSU or access problems from AT&T to customer premises on both ends of circuit |
307 | CSU or access problems from and to customer premises on one end of circuit |
308 | CSU or access problems from and to customer premises on both ends of circuit |
309 | CSU or access problems from one end and to other end of customer premises |
320 | CSU failed on a Transmit High Density Test |
321 | CSU failed on a Transmit All Zeros Test |
322 | CSU failed on a Transmit 3 in 24 Test |
323 | CSU failed on a Transmit Quasi-Random Test |
324 | CSU failed on a Transmit Predefined Test Signal Test. Test Pattern was 1:7 |
325 | CSU failed on two or more test patterns |
326 | CSU failed on tests on both ends of the facility |
327 | CSU failed on a Transmit All Zeros Test and opposite CLLI has an NI problem |
328 | CSU failed on a Transmit 3 in 24 Test and opposite CLLI has an NI problem |
329 | CSU failed on a Transmit Quasi-Random Test and opposite CLLI has an NI problem |
330 | CSU failed on a Transmit Predefined Test Signal Test. Test Pattern was 1:7 and opposite CLLI has an NI problem |
331 | CSU failed on two or more test patterns and opposite CLLI has an NI problem |
340 | CSU or Access failed on a Transmit High-Density Test |
341 | CSU or Access failed on a Transmit All Zeros Test |
342 | CSU or Access failed on a Transmit 3 in 24 Test |
343 | CSU or Access failed on a Transmit Quasi-Random Test |
344 | CSU or Access failed on a Transmit Transmit Predefined Test Signal 1:7 |
350 | Baseline access arrangement - CSU or Access problems between Customer and AT&T |
351 | Baseline access arrangement - Looped CSU failed on a Transmit High-Density Test |
352 | Baseline access arrangement - Looped CSU failed on a Transmit All Zeros Test |
353 | Baseline access arrangement - Looped CSU failed on a Transmit 3 in 24 Test |
354 | Baseline access arrangement - Looped CSU failed on a Transmit Quasi-Random Test |
355 | Baseline access arrangement - Looped CSU failed on a Predefined Test Signal 1:7 |
356 | Baseline access arrangement - Test OK after NI/CSU loop removed |
357 | Baseline access arrangement - NI/CSU loop was present and could not be removed |
358 | Baseline access arrangement - Network Test OK but AT&T was unable to get data from CPE |
359 | Baseline access arrangement - Non-Responding CSU at location. Cannot test customer loop |
360 | Baseline access arrangement - Looped NI failed on a Transmit High-Density Test |
361 | Baseline access arrangement - Looped NI failed on a Transmit All Zeros Test |
362 | Baseline access arrangement - Looped NI failed on a Transmit 3 in 24 Test |
363 | Baseline access arrangement - Looped NI failed on a Transmit Quasi-Random Test |
364 | Baseline access arrangement - Looped NI failed on a Transmit Predefined Test Signal 1:7 |
367 | Baseline access arrangement - NI test pattern failed, unable to loop down Ni, CSU not tested |
368 | Baseline access arrangement - NI testing ran clean, unable to loop down NI, CSU not tested |
369 | Baseline access arrangement - Non-responding or no loopable smart jack at the Network Interface |
397 | Customer loop cannot be tested due to IU in terminal emulation mode. Test was not able to be completed. Further analysis is required |
399 | Non-Responding CSU at location. Cannot test customer loop |
[ Help Index | Top of Condition Code Tables | Top of Page | Glossary ]
Condition Code |
Technical Narrative |
---|---|
420 | Network Interface failed on a Transmit High Density Test |
421 | Network Interface failed on a Transmit All Zeros Test. Terminating the intrusive testing on this portion |
422 | Network Interface failed on a Transmit 3 in 24 Test. Terminating the intrusive testing on this portion |
423 | Network Interface failed on a Transmit Quesi-Random Test. Terminating the intrusive testing on this portion |
424 | Network Interface failed on a Transmit Predefined Test Signal Test 1/7 |
425 | Network Interface failed on two or more test patterns Network Interface failed on a Transmit 55 Octet Test |
426 | Network Interface failed on both ends of the facility |
497 | Network Interface loop cannot be tested due to IU in terminal emulation mode |
498 | Network Interface testing ran clean, unable to loop down NI, CSU not tested |
499 | Non-responding or no loopable smart jack at the Network Interface. Terminating the intrusive testing on this portion |
[ Help Index | Top of Condition Code Tables | Top of Page | Glossary ]
Condition Code |
Technical Narrative |
---|---|
500 | Intermediate AT&T IOC locations were not sectionalized |
501 | AT&T IOC errors detected in one direction |
502 | AT&T IOC errors detected in both directions |
503 | AT&T equipment according to WORD document found in an unmapped state |
504 | AT&T equipment found in looped condition; could not remove |
520 | AT&T IOC failed on a Transmit High Density Test |
521 | AT&T IOC failed on a Transmit All Zeros Test |
522 | AT&T IOC failed on a Transmit 3 in 24 Test |
523 | AT&T IOC failed on a Transmit Quasi-Random Test |
524 | AT&T IOC failed on a Transmit Predefined Test Signal Test. Test Pattern was 1:7 |
525 | AT&T IOC failed on two or more test patterns AT&T IOC failed on a Transmit 55 Octet Test |
526 | AT&T IOC failed on both ends of of the facility |
599 | IU failed to loop up |
[ Help Index | Top of Condition Code Tables | Top of Page | Glossary ]
Condition Code |
Technical Narrative | |
---|---|---|
600 | (A/Z) This section tested OK. No problems found Facility tested OK, but one end is considered to be part of AT&T IOC (e.g., 4ESS) | |
601 | CSU or Access or AT&T IOC problems between Customer and AT&T | |
602 | Network Interface passed tests but CSU not loopable and problems remain | |
620 | AT&T IOC or NI failed on a Transmit High-Density Test | |
621 | AT&T IOC or NI failed on a Transmit All Zeros Test | |
622 | AT&T IOC or NI failed on a Transmit 3 in 24 Test | |
623 | AT&T IOC or NI failed on a Transmit Quasi-Random Test | |
624 | AT&T IOC or NI failed on a Transmit Predefined Test Signal 1:7 | |
625 | AT&T IOC or NI failed on a Transmit 55 Octet Test | |
640 | CSU or Access or AT&T IOC failed on a Transmit High-Density Test | |
641 | CSU or Access or AT&T IOC failed on a Transmit All Zeros Test | |
642 | CSU or Access or AT&T IOC failed on a Transmit 3 in 24 Test | |
643 | CSU or Access or AT&T IOC failed on a Transmit Quasi-Random Test | |
644 | CSU or Access or AT&T IOC failed on a Transmit Predefined Test Signal 1:7 | |
699 | Non-responding or no loopable smart jack at Network Interface |
[ Help Index | Top of Condition Code Tables | Top of Page | Glossary ]
Condition Code |
Technical Narrative |
---|---|
702 | Loss of Signal alarm condition detected on access link. |
[ Help Index | Top of Condition Code Tables | Top of Page | Glossary ]
Condition Code |
Technical Narrative |
---|---|
800 | Facility tested OK. No problems found |
802 | Loss of Signal alarm condition detected on AT&T IOC link in office |
803 | AIS alarm condition detected on AT&T IOC link in office |
804 | UAS alarm condition detected on AT&T IOC link in office |
805 | LOF alarm condition detected on AT&T IOC link in office |
[ Help Index | Top of Condition Code Tables | Top of Page | Glossary ]
Condition Code |
Technical Narrative |
---|---|
901 | IU failed to loopdown or Test Signal still present |
902 | IU Hardware Diagnostic Condition encountered. Terminating session |
997 | Test Setup Failed. DSTS could not establish needed test equipment |
998 | Cleanup Failed. Failure Reason=XXX. Notify technician |
999 | DSTS System Problem |
[ Help Index | Top of Condition Code Tables | Top of Page | Glossary ]
[ Help Index | Top of Condition Code Tables | Top of Page | Glossary ]
Condition Code |
Technical Narrative |
---|---|
10002 | Indication of multiple problems (e.g., a test fails at both the A and Z ends of the circuit). The unit’s digit implies the number of segments with a fault |
10003 | Indication of multiple problems (e.g., a test fails at both the A and Z ends of the circuit). The unit’s digit implies the number of segments with a fault |
10004 | DS3 alarm detected during testing. Test detected higher level failure |
10620 | Network Interface failed on a Transmit High-Density Test |
10621 | Network Interface failed on a Transmit All Zeros Test |
10622 | Network Interface failed on a Transmit 3 in 24 Test |
10623 | Network Interface failed on a Transmit Quasi-Random Test |
10624 | Network Interface failed on a Transmit Predefined Test Signal 1:7 |
10640 | CSU or Access failed on a Transmit High-Density Test |
10641 | CSU or Access failed on a Transmit All-Zeros Test |
10642 | CSU or Access failed on a Transmit 3 in 24 Test |
10643 | CSU or Access failed on a Transmit Quasi-Random Test |
10644 | CSU or Access failed on a Transmit Predefined Test Signal 1:7 |
10699 | Non-responding or no loopable smart jack at the Network Interface |
Copyright © 2017 AT&T. All rights reserved.
Version 34.01