E1 Pri DCH Loop Clocking1

Meridian 1
International ISDN PRI

Maintenance
Document Number: 553-2901-501

Document Release: Standard 4.00
Date: October 1997
Year Publish FCC TM
1991, 1997
All rights reserved
Printed in Canada
Information is subject to change without notice. Northern Telecom reserves the right to make changes in design
or components as progress in engineering and manufacturing may warrant. This equipment has been tested
and found to comply with the limits for a Class A digital device pursuant to Part 15 of the FCC rules, and the
radio interference regulations of Industry Canada. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This equipment
generates, uses and can radiate radio frequency energy, and if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a
residential area is likely to cause harmful interference in which case the user will be required to correct the
interference at their own expense.
Meridian 1 is a trademark of Northern Telecom.
Maintenance
Page iii
Revision history
October 1997
Issue 4.00 released as Standard for Generic X11 Release 23.

December 1995
Issue 3.00 released as Standard for Generic X11 Release 21B.

August 1995
Issue 2.00 released as Standard for Generic X11 Release 21A.

August 1994
Issue 1.00 released as Standard for Generic X11 Release 20.

August 1993
This document is the standard release for Phase 8b.

October 1992
This document is the standard release for Phase 7C.

June 1992
This publication is the standard release for Phase 7B.

December 1991
This publication is the standard release for Group F (Phase 6B iii).

July 1991
This publication is the standard release for Phase 5.
Maintenance
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Document overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRI operations guide . . . . . . . . . . . . . . . . . . . . . . .
PRI Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRI quick reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRI commands (LD 60) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRI messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DCHI quick reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
D-channel commands (LD 96) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
DCH messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
PRI status check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
PRI start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
Network Call Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Enhanced Trace command output . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Network Call Trace . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tracing a call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Trace function 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example 1: Successful call with trace function 01 . . . . . . . . . . . . .
Example 2: Unsuccessful call with trace function 01 . . . . . . . . . . .
Trace function 02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Feature requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
23
24
24
25
27
29
30
31
Maintenance
vi
PRA fault clearing . . . . . . . . . . . . . . . . . . . . . . . . . .

PRI local alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
PRI remote alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
PRI problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
D-channel problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
Primary Rate Interface (PRI) maintenance . . . . . .
39
PRI commands (LD 60) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
PRI alarm commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42
PRI test commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44
PRI tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRI self-test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRI automatic loop test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRI midnight routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Link diagnostic and remote loop-back tests . . . . . . . . . . . . . . . . . .
44
44
45
46
46
PRI system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DTAxxx messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DTIxxx messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRIxxx messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
48
50
54
PRI error detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bit error rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
55
TN to channel number conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . .
56
Using the error counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Error Counter switch functions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error Counter display functions . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
59
59
Replacing the PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59
PRI cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
62
Pulsed E&M DTI2 signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
63
64
D-channel (DCH) maintenance . . . . . . . . . . . . . . .
65
DCH commands (LD 96) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
553-2901-501
33
65
Standard
4.00
October 1997
vii
DCH tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DCH tests 100 and 101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DCH tests 200 and 201 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68
68
71
DCH system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
DCH traffic (LD 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TFS009 D-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
77
78
MSDL local loopback test (NT6D80) . . . . . . . . . . . . . . . . . . . . . . . . .
82
MSDL remote loopback tests (NT6D80) . . . . . . . . . . . . . . . . . . . . . . .
85
Protocol log (PLOG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
88
Replacing the DCHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
94
Overlay 60 - Loop Maintenance for SYS-12, AXE-10, SWE, SWISSNET,

NUMERIS, EuroISDN, NEAX-61, Asia-Pacific . . . . . . . . . . . . . . . . .
95
Clock Controller (CC) maintenance . . . . . . . . . . . .
97
Clock operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tracking mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Free run (non-tracking) mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reference clock errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatic clock recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatic clock switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
97
97
98
98
99
100
Clock controller commands (LD 60) . . . . . . . . . . . . . . . . . . . . . . . . . .
100
Clock controller messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
101
Replacing the clock controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Clock controller switch settings . . . . . . . . . . . . . . . . . . . . . . . . . . .
102
104
Clock controller cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
105
Maintenance
viii
553-2901-501
Standard
4.00
October 1997
Page 1 of 108
Introduction
Document overview
This document provides operation and maintenance procedures for ISDN
Primary Rate Interface (PRI) capability on the Meridian 1. It covers the
following topics:
Introduction: lists SL-1 ISDN references and explains the format of this
document.
PRI operations guide: presents quick references for Primary Rate
Interface (PRI) and D-channel (DCH) maintenance, a PRI status check,
and PRI start-up procedures.
PRI fault clearing: gives steps for clearing alarm conditions, and for
handling PRI and DCH problems.
Primary Rate Interface (PRI) maintenance: covers PRI maintenance
commands, tests, system messages, error detection, and cabling.
D-channel (DCH) maintenance: covers DCH maintenance commands,
tests, system messages, and tracking information.
Clock Controller (CC) maintenance: describes clock-controller
operation, maintenance commands, system messages, and cabling.
ISDN Signaling Link (ISL) maintenance: covers ISL interfaces, status
formats, start-up procedures, and recovery procedures.
Maintenance
Page 2 of 108
Introduction
References
Refer to the following documents for additional information.
ISDN PRI documents:
International ISDN PRI Product and features
overview
553-2901-101
International PRI Installation
553-2901-201
International ISDN PRI Feature description and

administration
553-2901-301
Meridian 1 documents:
X11 Features and Services
553-3001-306
Basic and Network Alternate Route

Selection General Description
553-2751-100
Electronic Switched Network

General Description
309-3001-100
2-Mb/s Digital Trunk Interface

Feature Description
553-2911-100
2-Mb/s Digital Trunk Interface Installation
553-2911-200
2-Mb/s Digital Trunk Interface General

Maintenance
553-2911-500
2Mb/s Digital Trunk Interface Fault

Clearing Procedures
553-2911-510
MSDL Description
553-3001-195
Option 11
Maintenance procedures and information relating to Meridian 1 Option 11
systems can be found in 553-3911-511.
553-2901-501
Standard 4.00
October 1997
32
Page 3 of 108
PRI operations guide

PRI Interface
Primary Rate Interface (PRI) provides a digital connection from the SL-1 to
other SL-1 PBXs, and to Central Offices complying to compatible signaling
protocols (AXE-10, 1TR6, SwissNet, SYS-12, Numeris VN3, JapanD70,
EuroISDN, NEAX-61, and Asia-Pacific).
2.0 Mb/s PRI NT8D72AA
The 2.048 Mb/s Primary Rate Interface (PRI2) circuit pack, the NT8D72AA,
provides 30 in-band channels to PRI equipment. Voice and data are
transmitted over these in-band "B-channels." Call control is supported
out-of-band over a "D-channel."
1.5 Mb/s PRI QPC720
The 1.5 Mb/s Primary Rate Interface (PRI) circuit pack, the QPC720B,
QPC720C, provides 24 in-band B-channels to PRI equipment. This circuit
pack is used only to support the 1.5/2.0 Mb/s Gateway feature, which allows
a Meridian 1 node using X11 software with supplementary features to act as
a gateway between 1.5 and 2.0 Mb/s PRI trunks.
1.5 Mb/s/2.0 Mb/s on System Option 11
To support 1.5 Mb/s/2.0 Mb/s on system Option 11, the following packs are
required:
the SDPC1 provides functionality equivalent to the QPC720B/C, which
is the 1.5 Mb/s DTI/PRI;
the SDC2/French provides functionality equivalent to the QPC536 and
QPC915, which is the 2.0 Mb/s DTI2 and French DTI, respectively;
the SPC2 provides functionality equivalent to the NT8D72AB/BA,
which is the 2.0 Mb/s PRI2;
Maintenance
Page 4 of 108
B-channels and D-channels

The B-channel is the fundamental channel in PRI. It carries the actual user
information to the far end, by means of digital transmission as part of the
2Mb/s digital data stream. The B-channel does not carry any signaling
messages. The D-channel transmits the standard signaling protocol, carrying
the call set-up and feature-activation information to the destination.
Each D-channel is physically connected to a D-channel Interface (DCHI)
card, either the QPC757C or the NT6D11AB/AE/AF. The DCHI card
provides the PRI link capability.
A maximum of 480 B-channels can be supported by one D-channel. This is
called nB+D capability. Figure 1 shows the maximum configuration, where
16 PRIs provide 30 B-channels each, and one PRI provides 30 B-channels
along with the D-channel that carries the signaling for all 16 PRIs.
With the backup D-channel configuration between two SL-1 switches, there
is one primary D-channel, one backup D-channel, and 480 B-channels. See
the International Primary Rate Access Product Description document
(553-2901-101) for further explanation of the backup D-channel
configuration.
Figure 1
PRI capacity
QPC757C DCHI
PRA
LINK
NT6D11AB DCHI
#1
PRA
LINK
480 B-channels
1 D-channel
480 B-channels
1 D-channel
I/O
Ports
3840 B-channels
8
D-channels
PRA
LINK
#1
I/O
Ports
7680 B-channels
16
D-channels
PRA
LINK
#8
480 B-channels
1 D-channel
#16
480 B-channels
1 D-channel
553-1362
553-2901-501
Standard 4.00
October 1997
Page 5 of 108
PRI quick reference

The NT8D72AA Primary Rate Interface (PRI) card provides a 30-channel
digital trunk to another telephone switch.
With current software, supporting nB+D capability, the D-channel is
configured on logical channel 31 on one of the multiple PRIs. See Figure 2.
Maintenance
Page 6 of 108
Figure 2
NT8D72AA PRI faceplate
N
T
8
D
7
2
OOS:
Card is out of service
ACT:
Card is enabled
LOCAL: Local alarmlocal card or transmission fault

RAI:
Remote alarmfar end fault
LBK:
Loop-back testsee PRI tests
J1
RCV MON:
Access point to regenerated CEPTsignal from

the external network
XMT MON:
MON
RCV
Access point to CEPT signal beingtransmitted
XMT
J1 J2 uffered recovered clocks derived from external carrier

B
facility (Ref 1&2)
J2
J4
J4
CEPT interface to the external digital carrier
J5
D-channel interface (DCHI) for common channel signaling
J3
Standard 18-pair connector to SL-1 Network loop
J6
RS-232 interface to echo canceller (satellite transmission

only). Test port only.
J5
J3
J6
553-2901-501
Standard 4.00
October 1997
Page 7 of 108
PRI commands (LD 60)

Table 1 is a quick reference list of important PRI commands. For a more
extensive list of PRI commands, see the section describing PRI maintenance.
Table 1
PRI commands (quick reference) (Part 1 of 2)
Command
Action
ATLP (0), 1
Disable (default) or enable midnight auto

loop test
CDSP
Clear maintenance display to 00 or blank
CMIN ALL
Clear minor alarm indication on all

attendant consoles
CMIN c
Clear minor alarm indication on attendant

consoles for customer c
DISI loop
Disable loop when all channels are idle
DISL loop
Disable network and DTI/PRI cards of loop
DLBK loop
Disable remote loop back test per RLBK

command
DLBK l ch
Disable remote loop back test per RLBK l

ch command
DSCH l ch
Disable channel ch of loop
ENCH loop
Enable all channels on 2.0 Mb/s DTI/PRI
ENCH l ch
Enable channel ch of DTI/PRI loop
ENLL loop
Enable network and DTI/PRI cards of loop
LCNT (loop)
List contents of alarm counters on one or

all DTI/PRI loops
LOVF c r
List threshold overows for customer c

(0-99) and route r (0-511)
RCNT
Reset alarm counters of all DTI/PRI loops
RCNT loop
Reset alarm counter of DTI/PRI loop
RMST loop
Perform self-test on loop
RMST l ch
Perform self-test on specied channel (2.0

Mb/s DTI/PRI only)
Maintenance
Page 8 of 108
Table 1
PRI commands (quick reference) (Part 2 of 2)
RLBK loop
Close loop at carrier interface point for

testing
RLBK l ch
Close channel ch at carrier interface point
RSET l ch
Reset thresholds for channel ch
SLFT loop
Invoke hardware self-test on loop
SLFT l ch
Invoke partial hardware self-test on channel

ch
STAT
Get status of all loops
STAT loop
Get status of DTI/PRI loop
STAT l ch
Get status of channel ch
PRI messages
Table 2 is a quick reference list of commonly encountered PRI messages. A
complete list of PRI-related messages is given in the PRI maintenance
section.
Table 2
PRI messages (quick reference) (Part 1 of 2)
DTA xxx
DTA102
power is up on the PRI2 card
DTA103
problem in loop or channel message of PRI2
DTA104
channel self-test report for PRI2
DTA105
loop self-test report for PRI2
DTA106 L
PRI2 loop L is in Acceptable state
DTA107 L
PRI2 loop L is in Group 1 maintenance state
DTA108 L
PRI2 loop L is in Group 1 no new calls state.
DTA109 L
PRI2 loop L is in Group 1 out of service state
DTA110 L
PRI2 loop L is in Group 2 maintenance state.
DTA111 L
PRI2 loop L is in Group 2 no new calls state
DTA112 L
PRI2 loop L is in Group 2 out of service state
553-2901-501
Standard 4.00
October 1997
Page 9 of 108
Table 2
PRI messages (quick reference) (Part 2 of 2)
DTA xxx
DTA113 L
PRI2 loop L is in out of service with no auto start
DTA114 L
PRI2 loop L is disabled, and message is not powerup
DTA115 L
PRI2 loop L message received is unsolicited
DTA116 L
PRI2 loop L is in Group 1 no new data calls state
DTA117 L
PRI2 loop L is in Group 2 no new data calls state
DTA203 L E S
A Group 2 error has been detected by the PRI2 card

E = Source of error. This may be:
0 - remote alarm indication
1 - loss of multiframe alignment
2 - loss of frame alignment
3 - alarm indication signal
4 - loss of signal
S = Error status. This may be:
0 - cleared
1 - persisted
2 - occurred
DTA224
loop audit found a channel with an active CR in an invalid Half

Disconnect state
DTA xxx
DTI015
Loop L is not specied as primary or secondary clock reference source
DTI024
PRI is enabled but no response from hardware
DTI030
PRI is enabled but in local alarm
DTI031
PRI is in remote alarm
PRI001
PRI and DCHI are ready
PRI002 to 011
See the PRI error messages in this guide
PRI200
Correct version ID received from PRI
PRI205
Version ID mismatch
Maintenance
Page 10 of 108
DCHI quick reference

The D-channel Interface (DCHI) card provides an asynchronous port and the
DCHI port (SeeFigure 3). The D-channel performs the call set-up and call
modification signaling for one or more 30-channel PRI2 cards. (Switch
settings for the DCHI port are shown in the DCHI replacement section.)
D-channel commands (LD 96)

Table 3 is a quick reference list of DCHI and D-channel commands. For a
complete list of DCHI and D-channel commands, see the section on DCHI
maintenance.
Table 3
DCHI and D-channel commands (quick reference) (Part 1 of 3)
Command
Action
DIS AUTO x
Disable automatic recovery for DCH x
DIS DCH x
Disable DCH x
DIS MSGI x (options)
Disable the monitoring of incoming messages on

D-channel x
DIS MSGI x FEAT CPNW
Disable incoming monitoring for the Network CPNW

ISDN messages on D Channel x.
DIS MSGO x (options)
Disable the monitoring of outgoing messages on

D-channel x
DIS MSGO x FEAT CPNW
Disable outgoing monitoring for the Network CPNW

DIS SERV x
Disable service messages on D-channel x
DLIF DCH x
Force download of D channel x (For PRI UIPE

application)
ENL AUTO x
Enable automatic recovery for DCH x
ENL DCH x (FDL)
Enable DCH x and attempt to establish the link, and

force download to MSDL
ENL MSGI x (options)
Enable the monitoring of incoming messages on

D-channel x
ENL MSGI x FEAT CPNW
Enable incoming monitoring for the Network CPNW

553-2901-501
Standard 4.00
October 1997
Page 11 of 108
Table 3
ENL MSGO x (options)
Enable the monitoring of outgoing messages on

D-channel x
ENL MSGO x FEAT CPNW
Enable outgoing monitoring for the Network CPNW

ENL SERV x
Enable service messages on D-channel x
EST DCH x
Establish multiple frame operation on D-channel x
EST ISPC l ch (N)
Start the data interface establishment process at the

ISPC slave side an ISPC link (where N = the
number of tries counter)
FDIS NCAL <DCH#> <conn_ID>

Force disconnect the specied call-independent
connection
PLOG DCH x
Print protocol error log on DCH x
RLS DCH x
Release D-channel x
RLS ISPC l ch
Stop the data interface establishment process
RST DCH x
Reset D-channel x, inhibit signaling
RST MON
Reset or reactivate monitoring on D-channels with

enabled monitors
SDCH DCH x
Switch to the standby D-channel x
SET MSGI x MON (0)-2
Set monitor output format level for incoming

messages on D-channel x
SET MSGO x MON (0)-2
Set monitor output format level for outgoing

messages on D-channel x
STAT DCH (x)
Get status of one or all D-channels
STAT ISPC l ch
Get status of data interface establishment process at

ISPC slave side ISPC link which has been congured
to convey D-channel signaling
STAT NCAL <DCH#>
List all current call-independent connections on a

given PRI D-channel.
STAT NCAL <DCH#> <conn_ID>

List information pertaining to a specic
call-independent connection
Maintenance
Page 12 of 108
Table 3
STAT MON (x)
Display the incoming and outgoing monitoring status

of one or all D-channels.
STAT SERV (x)
Get the enable/disable status of services messages for

one or all D-channels
TEST 100 x
Perform interrupt generation test on DCH x
TEST 101 x
Perform loop back mode test on DCH x
TEST 200 x
Perform interrupt handler test on DCH x
TEST 201 x
Test interrupt handler-to-link interface path
553-2901-501
Standard 4.00
October 1997
Page 13 of 108
Figure 3
QPC757C (and NT6D11) DCHI faceplate
Q
P
C
7
5
7
Status LED
The DCHI LED indicates the status
of both ports on the DCHI card.
If both ports are configured, the LED
is lit only when both ports are disabled.
J1
Asynchronous port
This port is used for non-PRA applications.
Print the configuration record to determine
how the port is configured.
Port J1 is always an even number
(0, 2, 4, ...14).
Check the async port status with
LD48
STAT ESDI N
J2
D-channel interface
This port is connected to port J5 on
a PRI card. The D-channel is always
channel 24 on a PRI.
Port J2 is always an odd number
(1, 3, 5 ... 15).
Check the D-channel port status with
LD96
STAT DCHI N
553-1373
Maintenance
Page 14 of 108
Figure 4 shows the relationship between LD 96 commands and the DCHI and
D-channel call states.
Figure 4
DCHI/DCH call states
Legend:
Top
DCHI =
OPER
DCHI =
OPER
NEAR END
STATE
FAR END
STATE
Bottom
DCH =
EST
Left
DCH =
EST
DCHI
RST DCH
Right
DCH
EST DCH
ENL DCHI
DCHI =
RST
DIS DCHI
DCH =
RST
EST DCH
RLS DCH
ENL DCHI
DCHI =
OPER
DCH =
RLS
RST DCH
DIS DCHI
DIS DCHI
DCHI =
OPER
DCHI =
DSBL
DCHI =
OPER
DCH =
RST
DCHI =
OPER
DCH =
RLS
DCH =
RLS
DCH =
RLS
553-1395
553-2901-501
Standard 4.00
October 1997
Page 15 of 108
DCH messages
Table 4 is a quick reference list of commonly encountered DCH messages. A
complete list of DCH messages is given in the DCHI maintenance section.
Table 4
DCH messages (quick reference) (Part 1 of 3)
DCH xxx
DCH001
ISDN package not equipped
DCH003
DCHI is disabled
DCH005
undefined link/DCHI state
DCH006
DCHI not responding
DCH007
command invalid at this state
DCH009
invalid command entered
DCH010
invalid parameter #1
DCH011
invalid number of parameters
DCH012
DCHI is not configured
DCH028
Command only valid for D-channels on MSDL card
DCH029
DCH has to be enabled first
DCH030
DCH has to be in test mode first
DCH031
Unable to enable
DCH032
Unable to disable the local loopback sub state because it is not

in the local loopback sub state.
DCH033
Unable to enable the remote loopback sub state because the

sub state is not idle.
DCH034
Unable to disable the remote loopback sub state because it is

not in the remote loopback sub state.
DCH035
Unable to run the local loopback test because the link is not in
a local loopback sub state.
DCH036
Unable to run the remote loopback test because the link is not
in a idle sub state.
DCH038
Invalid DCH number for ENL command.
DCH039
Invalid DCH state for enabling the link.
DCH040
Wrong number of input parameters for the enable command.
Maintenance
Page 16 of 108
Table 4
DCH xxx
DCH041
Input enable command not recognized.
DCH042
MSDL card has to be in operational state.
DCH043
Invalid DCH number.
DCH045
MSDL card is disabled.
DCH046
Invalid maintenance request for DCH link.
DCH300
test 200 failed
DCH301
test 201 failed
DCH302, 303, 304
test 101 failed
DCH305
test 100 failed
DCH1004
PRI is out of service
DCH1005
link release error
DCH1006
link establishment error
DCH1007
interrupt was lost
DCH1008
output request buffer overow
DCH1009
PRI reported DCHI is out of service
DCH1010
DCHI is software disabled
DCH1011
late link establishment
DCH1012
late link release
DCH1013, 1014
invalid DCHI state
DCH1015
receive buffer full
DCH1016
transmit buffer full
DCH1017
no end-of-message
DCH1018
no transmit buffer available
DCH1019
DCHI is hardware disabled
DCH1021
receive buffer is full
DCH1024
The DCH port on the MSDL card could not be enabled

because the MSDL card is not in an operational state.
DCH1025
Did not receive a conrmation from Layer 2 for a MSDL DCH

test state event, therefore a timeout has occurred.
553-2901-501
Standard 4.00
October 1997
Page 17 of 108
Table 4
DCH xxx
DCH1026
An invalid timeout occurred for the DCH test state. No further

action is required for this event.
DCH1027
A invalid test conrmation was received from layer 2. No

further action is required for this event.
DCH1028
The DCH has to be on the MSDL card for the maintenance

task requested.
DCH1029
Resynchronization of the ow control counters failed when a

ow control condition was detected by the MSDL DCH Handler
application.
DCH1030
Output request buffer overow for D channels on the MSDL

card. Increase the size of the output request buffer.
DCH044
Test or DCH maintenance command is not supported for

D-channels congured on the MSDL card.
DCH4283
Both D-channels have been released. Action: Establish the D

channel.
PRI status check

This status check is used to verify that a PRI is working normally. It assumes
the PRI and DCHI are properly installed (for example, correctly cabled) and
operational. If the PRI status is not as shown in the steps below, complete the
check and proceed to PRI fault clearing procedures.
Once all problems are cleared, go to PRI start-up.
Maintenance
Page 18 of 108
Procedure 1
PRI status check (Part 1 of 3)
Step
1
Action
Response
Check the status LEDs on all PRI cards.
For normal operation, only the green ACT

LED is lit.
PRI
OOS
ACT
LOCAL
REMOTE
LBK
553-1340
2
Note whether any other LED is lit and

continue with the status check.
Check the LED on the DCHI faceplate.
If the LED is lit, the D-channel is disabled.

Note: The DCHI LED indicates the status of
both ports on the DCHI card.
If both ports are congured, the LED is lit only
when both ports are disabled.
Check the status of the DCHI port using:

LD 96
STAT DCH x
553-2901-501
Standard 4.00
October 1997
Page 19 of 108
Procedure 1
Step
Response
Check the status of all PRIs using:
Sample response:
LD 60
STAT (L) PRI2 LOOP L - ENBL
STAT
Action
REF CLK - DSBL

SERVICE RESTORE - YES
ALARM STATUS: ACCEPTABLE
CH 01 - IDLE TIE *
TIE *
CH 02 - IDLE
CH 03 - IDLE TIE *
TIE *
CH 04 - IDLE
.
.
CH 31 - D-channel *
6
List PRI alarm counters using:

LD 60
PRI2 LOOP L
MNT
NNDC NNC OOS
BVPxxx
xxx
xxx
xxx
FAPxxx
xxx
xxx
xxx
(Check the out of service counters to
SLPxxx
xxx
xxx
xxx
determine the number of out of service
CRCxxx
xxx
xxx
xxx
occurrences since the last execution of the
G2
xxx
xxx
xxx
xxx
midnight routines.)
TOTAL 24 HOUR BPV- xxxxxxxxx
TOTAL 24 HOUR FAP- xxxxxxxxx
TOTAL 24 HOUR SLP- xxxxxxxxx
TOTAL 24 HOUR CRC- xxxxxxxxx
TOTAL 24 HOUR G2 AIS - xxxxxxxxx
TOTAL 24 HOUR G2 LFAS - xxxxxxxxx
TOTAL 24 HOUR G2 LMAS - xxxxxxxxx
TOTAL 24 HOUR G2 RAI - xxxxxxxxx
TOTAL 24 HOUR G2 LOS - xxxxxxxxx
LCNT (L)
Maintenance
Page 20 of 108
Procedure 1
Step
7
Action
Response
Check DCHI card and D-channel (DCH)

link status using:
LD 96
STAT DCH (N)
(N is the I/O port number)
Check to assure the following PRI cables

are connected correctly:
PRI to DCHI cable
2Mb/s transmission cable from

NT8D72AA to DSX (the digital cross
connect)
553-2901-501
Standard 4.00
October 1997
the DCHI status should be OPER

(operational) and EST (established)
Page 21 of 108
PRI start-up
This procedure provides the steps required to take the PRI and DCH from a
disabled to an operational state.
Procedure 2
PRI start-up (Part 1 of 2)
Step
1
Action
Response
Check the status of all PRI cards.
The PRI shown is disabled.

PRI
DIS
ACT
RED
YEL
LBK
553-1340
If any other LEDs are lit, go to PRI fault

clearing.
Test all PRIs using:
SLFT OK
LD 60
DISL loop
SLFT L
4
Enable all PRIs using:
PRI000
Correct version ID
LD 60
DTA005
remote alarm
ENLL L
DTA007
remote alarm cleared

(provided the far end is
up)
DTA023
PRI loop is up
DCH1010
D-channel is disabled
Maintenance
Page 22 of 108
Procedure 2
PRI start-up (Part 2 of 2)
Step
Response
Enable the D-channel(s) using:
DCH EST Time and Date
LD 96
Action
D-channel is established (provided far end

D-channel is OK).
ENL DCH N
If you do not get the DCH EST response,

see the note at step 6.
6
Perform a PRI status check.

Note: If the status check response is RLS,
establish the link at this point by entering the
command:
EST DCH N
553-2901-501
Standard 4.00
October 1997
Page 23 of 108
Network Call Trace

Network Call Trace is available with X11 release 17 and later to trace a
network call and to diagnose network problems. When a network call is
blocked, trace data is output indicating the reason the call was blocked and
the X11 software procedure responsible.
A network call can be traced by dialing a SPRE code and the NCT feature
code (9912) before the network number. When this is done, call set-up and
status information is output to the system terminal as the call tandems through
the network. The trace information is output to all the system terminals
designated in LD 17 as ADAN = TTY and USER = MTC.
NCT provides useful information such as the following:
the route used
the facility accessed
the routing control imposed
the call-blocked location
There are two Network Call Trace functions: 01 and 02. They output different
information as shown in the following sections.
Enhanced Trace command output

With X11 Release 19 and later, a time stamp is added to the call trace output.
This time stamp appears on the first line of the output.
The TN or digital trunk prints out only when there has been a change to the
call register. The TN or trunk is printed only once.
Sample time stamp output which will appear on the first line:
.14:00:02 12/25/1992
Maintenance
Page 24 of 108
Configuring Network Call Trace

To configure Network Call Trace on the Meridian 1, log in to the system and
do the following:
enter NCT in response to prompt RCAP in LD 17 for each D-channel
(only required when the remote end is Meridian 1 with X11 release 17)
enter CLTA in response to prompt CLS in LD 10 or LD 11 to allow a
telephone to trace calls
Tracing a call
A call can be traced from any attendant console or a telephone with CLTA
class of service (CLS). To trace a call dial the following:
SPRE + 9912 + xx + yyy...
where
SPRE = special function access code (defined in LD 15)
9912 = NCT feature code
xx = call trace function (01, 02)
Dial tone is provided after xx is dialed.
yyy... = digits normally dialed for the network call
553-2901-501
Standard 4.00
October 1997
Page 25 of 108
Trace function 01
This function provides the common information related to ESN routing. It is
the recommended function. The following is the call trace data for function
01:
**** NCT xx ****
<switch specific data>
--- OUT --<outgoing data>
--- IN --<incoming data>
--- STATE --<call state>
Where xx is the call trace ID for a traced call. The output data depends on the
type of call and can be the following:
CAUSE xxxxcall reject cause
CREF xxxxcall reference number
DCHD-channel number
DGT xxxxx...outgoing: digits outpulsed
DGT xxxxx...state: digits received (NODE=TBD), or
digits dialed when the call is rejected (STAT=REJ)
DN xxxDN of ringing set
ENT xxentry in the outgoing route list
FCI xfree calling area index
FRL xfacility restriction level
IFC xxxoutgoing D-channel interface (LD 17 prompt IFC)
D100 = Meridian DMS-100
D250 = Meridian DMS-250
ESS4 = AT&T ESS4
ESS5 = AT&T ESS5
SL1 = Meridian SL-1
S100 = Meridian SL-100
SS12 = Norwegian SYS-12
AXEA = AXE-10 (Australia)
UNKN = unknown data received
LOC xxxxcall reject software location
MODE xxxoutgoing termination
ALOG = analog trunk
Maintenance
Page 26 of 108
DTI = digital trunk interface1.5 Mb/s

DTI2 = digital trunk interface2.0 Mb/s
ISL = ISDN Signaling Link
PRI = Primary Rate Interface
UNKN = unknown data received
NCOS xxNetwork class of service
NODE xxxxtype of node
ORIG = originating node
TAND = intermediate node (tandem)
TERM = terminating node
TBD = node undetermined
RLI xxxESN outgoing route list index
RLS xx xxsoftware release, issue number of node switch
RTE xxxincoming or outgoing route number
SID xxxxsystem identification (LD 17)
STAT xxxxcall state, where xxxx can be
ANS = call answered
BUSY = termination busy
DIAL = call state is dialing (mainpm)
ERR = error detected in this message
OPULSE = digit outpulsing
PROC = call proceeding through this node (tandem)
REJ = call rejected or blocked
REOR = call state is dialing (mainpm)
RING = call ringing
SEIZ = trunk seized
STYP xxterminating station type
500 = single line telephone (LD 10)
BCS = multi-line telephone (LD 11)
ATT = attendant console (LD 12)
TKTP TIE,COT,WAT...incoming or outgoing trunk type
TKTN loop ch, l s c uincoming or outgoing B-channel, ISL trunk TN
TN l s c u
TN of originating telephone
TOD xtime of day schedule
TYP I,E Initial/Extended set
XLT NPA,NXX,LOC...ESN translation type
553-2901-501
Standard 4.00
October 1997
Page 27 of 108
Example 1: Successful call with trace function 01

In this example, the following digits are dialed from a telephone at TN 0 0 5 1.
1+9912++01+78+6000
where,
1 = SPRE (defined in LD 15)
9912 = NCT feature code
01 = call trace function 01
78 = PRI route access code (ACOD)
6000 = remote extension
The resulting trace information is output on the maintenance terminal:
**** NCT # 22 ****
NODE ORIG (SL1)
SID 0
RLS 17 53
--- OUT --TNS 0 0 5 1
DCH 5
IFC SL1
CREF 22
MODE PRI
RTE 24
TKTP TIE
TKTN 18 22
DGT 6000
--- STATE --STAT PROC
**** NCT # 22 ****
NODE ORIG (SL1)
SID 0
RLS 17 53
Maintenance
Page 28 of 108
--- OUT --DCH 5

RTE 24
TKTP TIE
TKTN 18 22
DGT 6000
--- STATE --STYP BCS
DN 6000
STAT RING
553-2901-501
Standard 4.00
October 1997
Page 29 of 108
Example 2: Unsuccessful call with trace function 01

In this example, the same call is made as in example 1, but in this case the
D-channel is down.
The resulting trace information is output on the maintenance terminal:
**** NCT # 22 ****
NODE ORIG (SL1)
SID 0
RLS 17 53
--- OUT --TNS 0 0 5 1
MODE UNKN
--- STATE --DGT 786000
STAT REJ
LOC 99
Maintenance
Page 30 of 108
Trace function 02
Call trace function 02 provides the information from the active (main) call
register, the incoming call state, and the outgoing call state (if any). Trace
function 02 is intended as a debugging tool for system designers.
The information output by function 02 includes the following:
NODE ORIG,TAND,TERM,TBD
SID xxxxsystem identifier
RLS xx xxrelease of software, issue number of node
TNS l s c uTN of the originating set
CREF xxxxcall reference number
Incoming call:
ISTATPM xincoming state progress mark
ITRKPM xincoming trunk progress mark
Outgoing call:
OSTATPM xoutgoing state progress mark
OTRKPM xoutgoing trunk progress mark
Main call register:
Word 0MainPM/AuxPM
Word 1CRlink
Word 2Queue_In
Word 3,4Son_Types/Processes
Word 5Aux_CRlink
Word 6OrigType/TerType
Word 7TTR_TN
Word 8OrigTN
Word 9TerTN
Word 10CallFwdTN
Word 11DISA_Call/XFER_indication
Word 12,13CR_Dialed_DN
Word 14Digitload/Digitunload
Word 15-20digits
553-2901-501
Standard 4.00
October 1997
Page 31 of 108
Feature requirements
Network Call Trace is limited to basic ISDN PRI/ISL calls across Meridian 1
private networks.
NCT collects information only during initial call setup. It does not report on
further call modification, such as Call Transfer.
Network call information is lost and the call trace ceases when any of the
Meridian 1 nodes in which the call is being traced is initialized or any of the
D-channels fails.
Although NCT requires PRI or ISL, calls can be traced to nodes that do not
support Network Call Trace. Calls can also be traced to DTI or analog trunks.
However, only the local node information is provided. These are the trunk
types that are not supported: ADM, AWU, DIC, MDM, MUS, PAG, RAN,
RLM, and RLR.
Call trace information is still output if the call is blocked before the trunk is
seized. If queuing (Ring Again, CBQ or OHQ) is available, then the original
call trace function is activated when the call is offered to the user.
When a remote Meridian 1 without NCT capability receives a Call Trace
message, no call trace information is returned.
Maintenance
38
Page 33 of 108
PRA fault clearing

PRI local alarm
A PRI local alarm can indicate:
2Mb/s digital transmission problems
a PRI card fault
Under any of these alarm conditions, all 30 B-channels are taken out of
service, and:
1
The PRI local alarm faceplate LED is lit.
Calls on the PRI are disconnected automatically.
All 30 channels are disabled.
After a pause of 2.5 seconds, the PRI sends a remote-alarm indication to

the far end switch.
The appropriate DTA message is printed and a minor alarm is raised on

all attendant consoles within the same customer group.
SL-1 software checks every 0-15 minutes (programmable) to see if a

clock-controller or reference-clock error has occurred.
If the 0-15 minute check finds the PRI in local alarm was a primary clock
source, the software switches the clock controller to the secondary reference.
Maintenance
Page 34 of 108
PRA fault clearing
Channel restoration
When the alarm condition improves, the PRI is restored to service as follows:
1
The local alarm is cleared.
After 11 seconds, the PRI stops sending a remote alarm indication to the
far end.
The D-channel automatically attempts to re-establish. If this is

successful, the B-channels are placed into the idle state and made
available for calls.
Procedure 3
Local alarm status check
Step
1
Action
Check PRI status using the following prompts:
LD 60
STAT (L)
Check PRI alarm counters using the following prompts:

LD 60
LCNT (L)
See PRI problems on the following pages.
PRI remote alarm

A remote alarm on the SL-1 indicates the far end is out of service. The fact
that the PRI is receiving the remote-alarm pattern indicates that there is
transmission integrity, but the far end is not ready.
When the PRI receives the remote-alarm signal from the far end, all 30
channels are disabled.
Channel restoration
When the PRI stops receiving the remote alarm, the channels are placed into
the idle state.
553-2901-501
Standard 4.00
October 1997
PRA fault clearing
Page 35 of 108
Procedure 4
Remote alarm status check
Step
Action
Perform a PRA status check.
Contact personnel at the far end to determine what action they are taking.
When the yellow alarm (remote alarm) 24-hour threshold is reached

(DTA006 is printed) do the following:
1
Contact personnel at the far end to determine what action they are taking.
When the far end troubles are cleared, reset the alarm counters and
disable, then enable, the PRI. To do this, use the following commands:
LD 60
LCNT loop
RCNT loop
DISL loop
ENLL loop
list alarm counters

reset alarm counters
disable loop
enable loop
PRI problems
The PRI can have any of the following problems. Determine the cause of the
problem and follow the recommended actions provided in Table 5.
Table 5
PRI problem solving (Part 1 of 2)
Symptom
Action
No connection to far end.

(If the 2Mb/s transmission cable is not
physically connected to the far end,
frame-alignment errors occur.
The channels will be disabled, but the PRI will
be in local-alarm mode. )
Use the Error Counter to verify the 2Mb/s

digital transmission directly from the PRI
faceplate (RCV and XMT) to each connection
(cross-connect, repeater, and other such
equipment).
PRI fails self-test.
Replace the PRI card.
Far-end problems, usually indicated by a

remote alarm.
Do a PRA status check and contact personnel

at the far end for resolution.
Maintenance
Page 36 of 108
PRA fault clearing
Table 5
PRI problem solving (Part 2 of 2)
Symptom
Action
PRI is connected but getting bit-rate or

frame errors.
Use the Error Counter to verify the 2Mb/s

digital transmission from the PRI faceplate
(RCV and XMT) to each connection
(cross-connect, repeater, and other such
equipment).
This can be caused by:
a bad 2Mb/s transmission cable

connection
electrical or electromagnetic interference
carrier problems (for example, defective

repeater)
Conguration settings do not match the far

end.
See that the SL-1 PRI parameters correlate to

the far-end parameters.
These problems can occur during initial

start-up. They may be indicated by:
DTA 018
Frame-slip out-of-service limit
DTA 021
Loss-of-frame-alignment for 3
seconds
DCH 1003 D-channel MDL errors

Cannot enable the PRI. Two reasons follow:
The far end PRI is disabled, indicated by:
PRI 000
PRI is responding
DTA 005
remote alarm occurred
DCH 1010
Contact personnel at the far-end site to resolve

the problem.
Or, there is no 2Mb/s connection, indicated by:

PRI 000
PRI is responding
DTA 021
loss of frame alignment for 3
seconds
DCH 1010
See above, under No connection to far end.
SL-1 initializes and there are no active

B-channels.
553-2901-501
Standard 4.00
October 1997
When a PRI or ISL trunk interfaces with

another SL-1 and the SL-1 initializes, you may
have to disable and then re-enable each
B-channel.
PRA fault clearing
Page 37 of 108
D-channel problems
D-channel problems are indicated when the DCHI releases after being
enabled. This applies to both primary and backup D-channels. For example:
Command
Response
Meaning
DCH 1003
MDL error
DCH 1006
link establishment error
DCH RLS
DCHI released
LD 96
ENL DCH N
If these messages appear, refer to Procedure 5 below.

Procedure 5
D-channel status check
Step
Action
Check the status of the D-channel's PRI.
Clear any PRI problems.
Contact the far end.
Test the DCHI using tests 100, 101, 200

and 201 (the tests must be run in
sequential order).
Response
Print the protocol log using:
If the far-end D-channel is down, the

DCH1006 message is printed.
LD 96
PLOG DCH N
6
Check the DCHI to PRI cable.
Check DCHI card jumper settings.
Check to see that one SL-1 system is

designated as "master" (usually the larger
system), the other as "slave."
Maintenance
64
Page 39 of 108
Primary Rate Interface (PRI) maintenance

PRI commands (LD 60)
PRI diagnostic commands are used to maintain both PRI and clock-controller
operation. See Table 6 for a list of the PRI card and channel commands in
Overlay 60. The commands are organized as follows:
PRI card and channel commands
Alarm and counter commands
Test commands
Table 6
PRI card and channel commands in Overlay 60 (Part 1 of 3)
Command
Description
DISI L
PRI loop L is disabled only when all the channels are idle. The network and
PRI cards are then disabled and status LEDs are lit. Channel status is set to
busy. Enter END to abort.
DISL L
Disables network and PRI circuit packs of loop L. Active calls are
automatically disconnected by on-hook simulation. All channels are
disabled and status LEDs are lit.
DSCH L CH All channels of loop L are disabled.

ENCH L CH All channels of loop L are enabled.
ENLL L
Enables PRI loop L. Channel CH of PRI loop L is enabled. The channel is

placed into the idle state and made available for calls.
STAT
Prints the status of all digital loops.
Maintenance
Page 40 of 108
Table 6
Command
Description
STAT loop
Get status of digital loop. Sample output:

AAA TRK LOOP x - BBBB
SERVICE RESTORE: YES/NO
YEL ALM PROCESS: YES/NO
ALARM STATUS: NO ALARM/RED(local) ALARM
Where: AAA may be:
1.
2.
3.
4.
5.
6.
7.
DTI
DTI2
PRI
PRI2
TIE
DID
DTI LINK (DTI link loop = DLI)
Where: BBBB may be:

1.
2.
3.
4.
5.
DSBL = Hardware of specied digital loop is disabled

ENBL = Hardware of specied digital loop is enabled
RLBK = Hardware of specied digital loop is in remote loop back mode
DISI PENDING = DSI command is in progress
TRACKING = system clock is tracked to this loop
6. IDLE = Hardware of specied digital loop is idle

7. SERVER RCVY = server has not recovered status of DTI LINK loop.
Channels will not be allocated for call processing until this status is
removed by the server
8. BUSY = Hardware of specied digital loop is busy
9. MSBY = Hardware of specied digital loop is in make busy mode
553-2901-501
Standard 4.00
October 1997
Page 41 of 108
Table 6
Command
Description
Where: SERVICE RESTORE may be:

1. YES = restore service automatically if alarm is removed
2. NO = loop can only be manually enabled
Where: YEL ALARM PROCESS may be:
1. YES = yellow alarm processing is enabled
2. NO = yellow alarm processing is disabled
Where: ALARM STATUS may be:
1. NO ALARM = no alarm active
2. RED = red (local) alarm active
Maintenance
Page 42 of 108
PRI alarm commands

See Table 7 for a list of PRI alarm commands and descriptions of these
commands. These commands appear in Overlay 60.
Table 7
PRI alarm commands in Overlay 60 (Part 1 of 2)
Command
Description
CDSP
Clears the maintenance display on active CPU to 00 or blank.
CMIN C
Clears the minor alarm indicator for customer C.
CMIN ALL
Clears the minor alarm indicators for all customers.
LCNT
Prints content of all alarm counters of all PRI loops.
LCNT L
Prints content of all alarm counters of PRI loop L. The counters are:
BPV
FAP
Number of times the loop has entered state due to excessive

frame bit errors.
SLP
Frame slip repetition counter.

The number of times the loop has entered state due to
excessive frame slips.
CRC
Cyclic Redundancy Check (CRC) bit error rate counter.

The number of times the loop has entered state due to CRC
frame errors.
G2
553-2901-501
Bipolar violation bit error rate counter.

Indicates the number of times the loop has entered state due
to excessive bipolar violations.
The number of times the loop has entered state due to

excessive group 2 errors.
Standard 4.00
October 1997
Page 43 of 108
Table 7
PRI alarm commands in Overlay 60 (Part 2 of 2)
Command
Description
TOTAL 24 HOUR BPV
24-hour bit error rate count
TOTAL 24 HOUR FAP
24-hour frame bit error rate count
TOTAL 24 HOUR SLP
24-hour slip count
TOTAL 24 HOUR CRC
24-hour CRC error count
TOTAL 24 HOUR G2 AIS
24-hour alarm indication signal count
TOTAL 24 HOUR G2 LFAS
24-hour loss of frame alignment count
TOTAL 24 HOUR G2 LMAS
24-hour loss of multiframe alignment

count
TOTAL 24 HOUR G2 RAI
24-hour remote alarm indication count
TOTAL 24 HOUR G2 LOS
24-hour loss of signal count
RSET L CH Resets the thresholds for PRI loop L, trunk channel CH.
RCNT
Resets all alarm counters of all PRI loops.
RCNT L
Resets all alarm counters of PRI loop L.
Maintenance
Page 44 of 108
PRI test commands

See Table 8 for a list of the PRI test commands and a corresponding
description of these commands. The PRI test commands are in Overlay 60.
Table 8
PRI test commands in Overlay
Command
Description
ATLP (0) 1
Automatic loop test enable (= 1) or disable (= 0) default.

1 = Loop test enable; this will cause far end to raise and clear remote alarm.
0 = Run the partial loop test; there is no interaction for the far-end loop
(default value).
SLFT L
Invokes PRI self-test on loop L. The loop must be disabled because the test
disrupts call processing.
SLFT L CH
Invokes partial PRI hardware self-test using channel CH of loop L.
RLBK L
Closes the loop at the carrier interface point of the PRI so the far end can
perform an external loop-back test. PRI loop L must be disabled because the
test disrupts call processing.
DLBK L
Disables the remote loop-back test per RLBK L. The loop remains disabled.
DLBK L CH
Disables the remote loop-back test per RLBK L CH. The channel remains
disabled.
RLBK L CH
Per RLBK L, but performed on channel CH. This channel must be disabled
prior to issuing the request.
RMST L
Performs self-test on loop L, providing the far end is in the remote loop-back
mode.
RMST L CH
Performs self-test on channel CH, providing the far end is in the remote
loop-back mode.
PRI tests
PRI self-test
The self-test checks speech-path continuity, zero-code suppression, and
remote-alarm detection. This test is performed manually on a per-channel or
a per-frame basis.
553-2901-501
Standard 4.00
October 1997
Page 45 of 108
The DCHI and PRI must be disabled before performing the self-test or call
processing will be disrupted. To perform the self-test on a specific loop,
follow Procedure 6.
Procedure 6
PRI self-test
Step
1
Action
Disable the DCHI using:
LD 96
DIS DCH N
Disable the PRI loop and run the self-test using:

LD 60
DISL L
SLFT L
PRI automatic loop test

The automatic loop test checks the same functions as the self-test. Unlike the
self-test, it can be run automatically, as part of the midnight routines.
With the ATLP command set to one:
Step
Action
If all 30 channels are idle at midnight, SL-1 software disables the card and performs
a self-test on all channels.
If any of the 30 channels are busy at midnight, software disables one idle channel,
chosen at random, and checks it while the card is enabled.
With the ATLP command set to zero, only one channel is tested. The channel
tested is randomly selected by software; it cannot be specified.
Maintenance
Page 46 of 108
To perform the remote loop-back test, use:

LD 60
ATLP 1 or 0
PRI midnight routines

The following PRI maintenance routines should be included in midnight
routines:
Overlay 45: Background signaling and switching diagnostic
Overlay 95: Automatic trunk maintenance diagnostic
Overlay 48: Link diagnostic
Link diagnostic and remote loop-back tests

The remote loop-back test and the link-diagnostic test are performed
manually on a per-channel or a per-frame (30 channels) basis.
Link diagnostic test
The link-diagnostic test, also called the far-end loop-back test, does not test
the SL-1 PRI. It puts the PRI in loop-back mode so a remote loop-back test
can be performed on equipment at the far end.
The PRI channel or frame being tested must be disabled.
Remote loop-back test
The remote loop-back test, also called the near-end loop-back test, checks the
integrity of the PRI from the SL-1 to the far end. The far end must be in
loop-back mode before this test can be performed.
The PRI channel or frame tested must be disabled.
553-2901-501
Standard 4.00
October 1997
Page 47 of 108
Coordinating the tests

When a technician at the far end asks for loop-back mode on the SL-1:
LD 96
DIS DCH N
Disable the PRI loop and activate loop-back mode using:
LD 60
DISL L
RLBK L
To run the remote loop-back test on the SL-1, follow Procedure 7.
Procedure 7
Remote loop-back test
Step
Action
Call a technician at the far end.
Ask for loop-back mode at that facility.
When loop-back mode at the far end is conrmed:

LD 96
DIS DCH N
Disable the PRI loop and run loop-back test using:
LD 60
DISL L
RMST L
Figure 5 shows the relationship between the remote loop-back test and the
link diagnostic test.
Maintenance
Page 48 of 108
Figure 5
PRI link diagnostic and remote loop-back tests
SL-1
Far End Switch
DCHI
CEPT connection
PRI
RMST L
RLBK L
Running remote loop-back test
In loop-back mode
553-1374
PRI system messages

PRI messages are listed on the following pages with a description.
DTAxxx messages
See Table 9 for the DTA messages.
553-2901-501
Standard 4.00
October 1997
Page 49 of 108
Table 9
PRI alarm messages (Part 1 of 2)
Message
Description
DTA106 L
PRI2 loop L is in Acceptable state
DTA107 L
PRI2 loop L is in Group 1 maintenance state
DTA108 L
PRI2 loop L is in Group 1 no-new-calls state.
DTA109 L
PRI2 loop L is in Group 1 out-of-service state
DTA110 L
PRI2 loop L is in Group 2 maintenance state.
DTA111 L
PRI2 loop L is in Group 2 no-new-calls state
DTA112 L
PRI2 loop L is in Group 2 out-of-service state
DTA113 L
PRI2 loop L is in out of service with no auto start
DTA114 L
PRI2 loop L is disabled, and message is not powerup
DTA115 L
PRI2 loop L message received was not solicited
DTA116 L
PRI2 loop L is in Group 1 no-new-data calls state
DTA117 L
PRI2 loop L is in Group 2 no-new-data calls state
DTA203 L E S
A Group 2 error has been detected by the PRI2 card

E = Source of error. This may be:
0 - remote-alarm indication
1 - loss of multiframe alignment
2 - loss of frame alignment
3 - alarm-indication signal
4 - loss of signal
S = Error status. This may be:
0 - cleared
1 - persisted
2 - occurred
DTA300 L
A slip repetition has occurred on PRI2 loop L.
DTA301 L
A slip deletion has occurred on PRI2 loop L.
DTA302 L
A slip-repetition overow has occurred on PRI2 loop L.
DTA303 L
A slip-deletion overow has occurred on PRI2 loop L.
DTA304 L
A BPV-unavailable condition has occurred on PRI2 loop L.
DTA305 L
A CRC-unavailable condition has occurred on PRI2 loop L.
DTA306 L
An FAP-unavailable condition has occurred on PRI2 loop L.
Maintenance
Page 50 of 108
Table 9
PRI alarm messages (Part 2 of 2)
Message
Description
DTA307 L
A BPV no-new-calls condition has occurred on PRI2 loop L.
DTA308 L
A CRC no-new-calls condition has occurred on PRI2 loop L.
DTA309 L
An FAP no-new-calls condition has occurred on PRI2 loop L.
DTA310 L
A BPV-maintenance condition has occurred on PRI2 loop L.
DTA311 L
A CRC-maintenance condition has occurred on PRI2 loop L.
DTA312 L
An FAP-maintenance condition has occurred on PRI2 loop L.
DTIxxx messages
See Table 10 for the DTI/PRI error messages.
Table 10
DTI/PRI error messages (Part 1 of 4)
Message
Description
DTI000
Program identifier
DTI001
Invalid input character
DTI002
Invalid command
DTI003
Incorrect number of parameters
DTI004
Incorrect customer number
DTI005
Invalid parameter
DTI006
Loop specified is not a PRI loop.
DTI007
DISI request already active.
DTI008
DISI command is complete.
DTI009 L E
PRI loop failed hardware self-test with error code E.
DTI010 L C
System clock N cannot be switched in to replace active clock.
DTI011 N
System clock N cannot be switched in because loss of service will result to the peripheral signaling pack listed.
DTI012 N
Network pack does not respond from IOTEST; loop L is disabled.
553-2901-501
Standard 4.00
October 1997
Page 51 of 108
Table 10
Message
Description
DTI013 L
No channel is available on loop L for diagnostic test. No self-test is

performed on this loop.
DTI014 L
Loop is in remote loop-back mode; command not allowed.
DTI015 L
Loop L is not specified as primary or secondary clock reference

source.
DTI016
DTI/DTI2/PRI2 packages are not equipped; overlay is not allowed to

load.
DTI017
Previous command in progress; enter END to abort.
DTI018 L
DISI command aborted.
DTI019
The loop/channel is not disabled for self-test or it is already in the requested set/reset loop-back mode.
DTI020 L
Loop L is already disabled. No action is taken.
DTI021
Attempt was made to disable input TTY loop.
DTI022 L
Loop L is already enabled.
DTI023 L C
Cannot disable/enable the specified channel.
DTI025 L C
Terminal is not equipped.
DTI027 L
Loop L is not in LOOP_BACK_TEST mode.
DTI028 L C
No test result received before timeout from the specified loop L or

channel C.
DTI034 L
Switching in clock controller is not allowed.
DTI035
Clock controller does not exist.
DTI037 L
Unable to read partial alarm counts from hardware on loop L

(Following alarm counts are incomplete.)
DTI038 L
No channel is available on loop L for diagnostic. Self-test was not

performed.
DTI039 L
Continuity test failed on loop L
DTI040 L C
Loopback test failed on channel C of loop L
DTI041 L
Memory test failed; replace Network pack
Maintenance
Page 52 of 108
Table 10
Message
Description
DTI042 L C
No timeslots are available for loopback test, hence test could not be
performed on channel C
(In a loop level test, all channels above C will also be left untested.)
DTI043
Another channel already in loopback mode
DTI044 L
Loop L enabled by midnight routines
DTI045 L
Self test not performed on loop L (since loop L has been manually
disabled)
DTI046 L
Self test not performed on loop L because loop is inaccessible
DTI047 L
Self test not performed on loop L (since loop L is in remote loop-back

mode)
DTI051
Data link is not defined.
DTI052
Tracking rejected. Reference primary is not specified.
DTI053
Unable to track on primary.
DTI054
Tracking rejected. Reference secondary is not specified.
DTI055
Unable to track on secondary.
DTI056
Unable to access clock controller.
DTI057
Unable to free run.
DTI058
Supposed to free run but hardware is tracking on primary.
DTI059
Supposed to free run but hardware is tracking on secondary.
DTI060
Supposed to track on primary but hardware is tracking on secondary.
DTI061
Supposed to track on primary but hardware is free run.
DTI062
Supposed to track on secondary but hardware is tracking on primary.
DTI063
Supposed to track on secondary but hardware is free run.
DTI064
Cannot determine which CPU is in use.
DTI065
System clock must be switched before proceeding.
DTI066
Idle CPU must be switched in for active CPU before proceeding.
DTI067
System clock generator specified is already enabled.
553-2901-501
Standard 4.00
October 1997
Page 53 of 108
Table 10
Message
Description
DTI068
System clock generator specified is not responding
DTI069 L
Unable to track on loop L
DTI070 L
Clock controller cannot be switched; unable to track the reference

loop
DTI071
There is an active call on the B-channel, so the B-channel cannot be

enabled.
DTI072
The DCH link is not established, so the B-channel cannot be enabled.
DTI098 L
Entered command applies only to 1.5Mb/s transmission
DTI099 L
Entered command applies only to 2.0Mb/s transmission
DTI4130
Incompatible protocol between the interface. If error continues, report it.
DTI4131
DTI4132
Maintenance
Page 54 of 108
PRIxxx messages
PRI messages indicate status and error conditions for the PRI card. See
Table 11.
Table 11
PRI specic status and error messages
Message
Description
PRI010 L
Disabling of this loop (L) not allowed.

Associated DCHI must be disabled rst.
PRI011 L
DCH port number mismatch between PDCH block and PPRI loop
block.
Action:
Report this software problem to the technical
assistance center.
PRI278
Loop enabled but cannot enable DCH.
PRI279
Enabling channels on a secondary loop is blocked if the

International nB+D (INBD) package is restricted.
PRI280
Enabling a backup DCH for the TCNZ (NEAX-61) interface is

blocked.
PRI304
The Malicious Call Trace facility ID or control code is not recognized

by the AXE-10 CO.
PRI305
The Malicious Call Trace facility control code is not recognized by

the AXE-10 CO.
PRI306
The user is not subscribed for the Malicious Call Trace facility
request at the AXE-10 CO.
PRI307
CLID length (for the Incoming Trunk Programmable CLID feature)

exceeds the maximum allowed for the Australian interface.
ACTION: Congure the billing number to the allowed maximum.
553-2901-501
Standard 4.00
October 1997
Page 55 of 108
PRI error detection

Bit error rate
Bit-error-rate monitoring detects errors in transmission. See Figure 6.
Bipolar violation (BPV) tracking
In a bipolar pulse stream, pulses alternate in polarity. A bipolar violation has
occurred if, after transmission, two pulses of the same polarity are received in
succession (this could be caused by an electrical disturbance such as noise).
Maintenance
Page 56 of 108
Figure 6
Bipolar violations
normal:
error:
553-1347
Cyclic redundancy check (CRC)

The Cyclic Redundancy Check contains a checksum of all the data in the
frame. The receiving side uses the checksum to verify the data is correct.
The primary difference between BPV and CRC is that bipolar violation
tracking indicates errors on the local span, while CRC indicates errors on an
end-to-end span.
Running the midnight routines prints the number of overflows and clears the
counter.
TN to channel number conversion

PRI channel numbers have an equivalent terminal number (TN). The TN is
output instead of the channel number in some SL-1 messages.
The TN-to-channel-number translation is shown below.
553-2901-501
Standard 4.00
October 1997
Page 57 of 108
Terminal numbers are identified in software by Loop (LL), Shelf (SH), Card
(C), and Unit (U) numbers. Each TN is applied to an individual channel on
the PRI pack (See Table 12).
Table 12
PRI channel numbers and equivalent terminal numbers
Channel number
TN SH C U
Channel number
TN SH C U
00 0001 00
18
10 0010 00
00 0010 00
19
10 0011 00
00 0011 00
20
10 0100 00
00 0100 00
21
10 0101 00
00 0101 00
22
10 0110 00
00 0110 00
23
10 0111 00
00 0111 00
24
11 1000 00
01 1000 00
25
11 0001 00
01 0001 00
26
11 0010 00
10
01 0010 00
27
11 0011 00
11
01 0011 00
28
11 0100 00
12
01 0100 00
29
11 0101 00
13
01 0101 00
30
11 0110 00
14
01 0110 00
TS-0
00 1000 00
15
01 0111 00
TS-16
11 0111 00
16
10 1000 00
Loop Maintenance
00 1001 00
17
10 0001 00
Maintenance
Page 58 of 108
Using the error counter

The Error Counter detects bipolar violations or no-signal periods. It counts,
stores, and displays these occurrences to a maximum of 9999.
The PRI fault detection and isolation procedures described in this section are
performed using a portable test package, which consists of one each of the
following items:
the TTT2028 Mini-Error Counter, plus operation instruction card
a cord equipped with a bantam plug at one end and minihooks at the other
a loop-back plug (shorts pins 3 to 1 and 11 to 9 of a 15 pin D connector)
Using the error counter
!
WARNING
To prevent injury from voltage on the span, always connect the patch
cord into the test set before connecting the other end to the external
signal source.
Step
Action
Response
Plug one end of a patch cord into the input

jack of the test set.
Plug the other end of the patch cord into one

of the monitor jacks (RCV and XMT) of the
PRI pack being tested.
Monitor the Error Counter LED indicators as

described below.
553-2901-501
Standard 4.00
October 1997
Page 59 of 108
Error Counter switch functions

Switch
Function
Display Enable
When held down, the switch enables the Counter display and the
GOOD and O/R LED displays
Reset
Used to zero the counter
Error/Error
Used to select error counting seconds for bipolar violations or

error-seconds
Error Counter display functions

Display
Function
GOOD
Indicates the presence of an acceptable bipolar signal (if bipolar

violations, missing pulses, or an oscillating line are detected, the
indicator is off)
ERR
Flashes when bipolar violations are detected
W/M
Indicates no input (absence of pulse) or an oscillating line
O/R
Over range display turns on when the counter input has exceeded
9999 (the counter resets to 0000)
CNTR
With Error/Error-Second switch in the Error position, the unit counts

errors at a maximum rate of 200 per second
With Error/Error-Second switch in the Error-Second position, the
unit counts error seconds at a rate of one per second
Replacing the PRI

CAUTION
Firmly touch the metal frame of the cabinet to discharge static
electricity from your body before handling circuit packs.
Maintenance
Page 60 of 108
Procedure 8
Replacing the PRI circuit pack
Step
Action
Response
Disable the D-channel using:

LD 96
DIS DCH N
Disable the PRI loop using:

LD 60
DISL L
Disconnect cables on PRI faceplate.
Remove the PRI from the shelf.
Make sure that the new PRI card switch settings are
the same as the faulty PRI card. See Figure 7.
Install the new PRI card in the appropriate slot.
Connect the network loop cable, and the carrier

interface cable.
If the PRI card is dened as a primary or secondary
clock source, connect the clock controller cable(s).
Test the PRI card using:

LD 60
SLFT L
If an error message results, see PRA fault clearing.
Enable the PRI using:

LD 60
ENLL L
10
Enable the D-channel using:

LD 96
ENL DCH N
553-2901-501
Standard 4.00
October 1997
Page 61 of 108
Figure 7
PRI switch settings
NT8D72AA
SW2
7-pole
(See Switch
Settings)
SW3
8-pole
All OFF
553-1503
75 SWITCH SETTING
120 SWITCH SETTING

(DEFAULT)
OR
1
S1
2
S1
553-xxx
Maintenance
Page 62 of 108
PRI cabling
An example of PRI cabling is shown in Figure 8.
Figure 8
PRI cabling
NT8D72AA PRI Card
(Primary Reference)
REF1
J1
QCAD130
to
Clock
Controllers
R E F 2 J2
D-CH
QCAD328A
J5
LOOP
QCAD130
J3
2Mb/s
stream
J4
J2
QCAD124
Network
Card
NT8D7205
or
22 AWG
ABAM
NT8D7207
Cabinet
I/O Panel
Note 1
RS232
QPC757C
DCHI
repeater
Note 2
Cross-Connect
J6
NOTES:
1. Maximum cable distance from PRI card to cross connect 200m (655 ft).
2. Maximum cable distance from PRI card to repeater 229m (750 ft).
553-2901-501
Standard 4.00
October 1997
553-1380
Page 63 of 108
Pulsed E&M DTI2 signalling

Error messages
DTA322 loop channel start-bits pulsed-bits end-bits duration
An invalid pulsed signal has been received from the DTI.
loop = the loop number the signal was received on
channel = the channel number the signal was received on
start-bits = the bit pattern before analysis of the pulse
pulsed-bits = the ABCD bit pattern which was possibly part of a pulsed
signal
end-bits = the ABCD bit pattern received after the pulse
duration = the length of the pulse in msecs.
pulsed bits
end bits
start bits
duration
DTRK500 loop channel

A forward release message has been sent but not acknowledged by a
backward release. Check the configuration of the trunk at each end.
loop = the loop number of the trunk which sent the forward release
channel = the channel number of the trunk which sent the forward
release.
Maintenance
Page 64 of 108
DTA205 loop e
The CI-1 firmware has encountered a problem. Refer to DTIOO9 for
CI-1 microprocessor error codes (e).
DTA205 loop 128

This error message may result from an attempt to use the software with
DTI2 cards prior to QPC915C or QPC536E. New functionality has been
introduced in the DTI2 cards. The old cards will ignore attempts to use
the functionality introduced in these new cards.
Diagnostics
To print the last sent and received signal, use Overlay 80 - Call Trace. The
following print format is used.
ACTIVE TN DTI 008 03
ORIG DTI 008 03 DID RMBR 33 1 CALL TYPE VOD
SICA 3
SENT CONN 0101 RECV CONN 0001
PDCA 1 PAD 15 2 PCML A A
TERM 004 0 03 01 0 SCR 0 401 2317
DIAL DN 401
MAIN PM ESTD
TALKSLOT ORIG 15 TERM 15
QUEU NONE
The SENT bits indicate the steady state on the line once the pulse is complete.
The RECV bits indicate the last bit pattern received on the trunk channel.
553-2901-501
Standard 4.00
October 1997
96
Page 65 of 108
D-channel (DCH) maintenance

DCH commands (LD 96)
Table 13 contains the basic D-channel commands in Overlay 96 (Release 18
and later).
Table 13
D-channel commands, Overlay 96
Command
Description
DIS AUTO x
Disable automatic recovery for DCH x
DIS DCH x
Disable DCH x
DIS MSGI x
(options)
Disable the monitoring of incoming messages on D-channel x
DIS MSGI x
FEAT CPNW
Disable incoming monitoring for the Network CPNW ISDN messages on D

Channel x.
DIS MSGO x
(options)
Disable the monitoring of outgoing messages on D-channel x
DIS MSGO x
FEAT CPNW
Disable outgoing monitoring for the Network CPNW ISDN messages on D

Channel x.
DIS SERV x
Disable service messages on D-channel x
DLIF DCH x
Force download of D channel x (For PRI UIPE application)
ENL AUTO x
Enable automatic recovery for DCH x
ENL DCH x
(FDL)
Enable DCH x and attempt to establish the link, and force download to MSDL
ENL MSGI x
(options)
Enable the monitoring of incoming messages on D-channel x
Maintenance
Page 66 of 108
Table 13
Command
Description
ENL MSGI x
FEAT CPNW
Enable incoming monitoring for the Network CPNW ISDN messages on D

Channel x.
ENL MSGO x
(options)
Enable the monitoring of outgoing messages on D-channel x
ENL MSGO x
FEAT CPNW
Enable outgoing monitoring for the Network CPNW ISDN messages on D

Channel x.
ENL SERV x
Enable service messages on D-channel x
EST DCH x
Establish multiple frame operation on D-channel x
EST ISPC l ch
(N)
Start the data interface establishment process at the ISPC slave side an ISPC
link (where N = the number of tries counter)
FDIS NCAL <DCH#> <conn_ID>

Force disconnect the specied call-independent connection
PLOG DCH x
Print protocol error log on DCH x
RLS DCH x
Release D-channel x
RLS ISPC l ch
Stop the data interface establishment process
RST DCH x
Reset D-channel x, inhibit signaling
RST MON
Reset or reactivate monitoring on D-channels with enabled monitors
SDCH DCH x
Switch to the standby D-channel x
SET MSGI x
MON (0)-2
Set monitor output format level for incoming messages on D-channel x
SET MSGO x
MON (0)-2
Set monitor output format level for outgoing messages on D-channel x
STAT DCH (x) Get status of one or all D-channels
553-2901-501
Standard 4.00
October 1997
Page 67 of 108
Table 13
Command
Description
STAT ISPC l ch Get status of data interface establishment process at ISPC slave side ISPC link
which has been congured to convey D-channel signaling
Maintenance
Page 68 of 108
DCH tests
There are four types of DCH tests. They are:
DCH test 100
DCH test 101
DCH test 200
DCH test 201
The DCH tests 100 and 101 are hardware tests, while the 200 and 201 test the
DCH software.
DCH tests 100 and 101

DCH tests 100 and 101 are isolated hardware tests. See Figure 9. Test 100
checks interrupt generation on the DCHI. Test 101 checks the DCHI
loop-back capability. If either test fails, either a faulty DCHI or a contention
problem is indicated. A test failure will initiate DCH error messages.
Tests 100 and 101 must be run in sequential order (tests 200 and 201 may
follow). Established calls will stay up, but new calls cannot be placed.
DCHI hardware test procedure (Part 1 of 2)
Step
1
Action
Log in to the overlay system.
Then, enter overlay program 96 by entering the command
LD 96
If the DCHI link is disabled, it must be enabled by entering the commands

STAT DCH N (responds DSBL)
ENL DCH N(if a problem caused the disabled state, RLS will
occur; if the disabled state is cleared, status will be EST)
RST DCH N
Place the DCHI link in the reset state (from either the established
or Released state) by entering the commands
STAT DCH N (responds either EST or RLS)
RST DCH N
553-2901-501
Standard 4.00
October 1997
Page 69 of 108
DCHI hardware test procedure (Part 2 of 2)

Step
Action
Activate the rst hardware test by entering the command
Activate the second hardware test by entering the command
TEST 100 N
TEST 101 N
Maintenance
Page 70 of 108
Figure 9
INTERRUPT SIGNAL
DCHI
Command
Register
Transmit
Buffer
Firmware
Receive
Buffer
Meridian SL-1
CPU
D-Channel
Maintenance
Overlay
Status
Register
TEST 100:
DCHI
Command
Register
Interrupt generation
Meridian SL-1
CPU
Transmit
Buffer
Receive
Buffer
Firmware
Status
Register
TEST 101:
D-Channel
Maintenance
Overlay
Loop-back mode
553-1381
553-2901-501
Standard 4.00
October 1997
Page 71 of 108

DCH tests 200 and 201 are software tests. See Figure 10. Test 200 monitors
the DCHI interrupt handler. Test 201 checks the interrupt handler-to-link
interface path. If either test fails, software problems are indicated. A test
failure will initiate DCH error messages.
Tests 200 and 201 must be run sequentially after tests 100 and 101.
Established calls will stay up, but new calls cannot be placed.
DCHI software test procedure
Step
1
Action
Log in to the overlay system. Then, enter overlay program 96 by entering
the command
LD 96
If the DCHI link is disabled, it must be enabled by entering the commands

STAT DCH N (responds DSBL
ENL DCH N(if a problem caused the disabled state, RLS will
occur; if the disabled state is cleared, status will be EST)
RST DCH N
Place the DCHI link in the reset state (from either the established or
Released state) by entering the commands
STAT DCH N (responds either EST or RLS)
RST DCH N
Activate the rst software test by entering the command

TEST 200 N
Activate the second software test by entering the command

TEST 201 N
Maintenance
Page 72 of 108
Figure 10
Interrupt
signal
DCHI
Meridian SL-1
CPU
Interrupt
DCHI
Interrupt
Handler
TEST 200:
Interrupt handler
Input Buffer
DCHI
Interrupt
Handler
Work
Scheduler
Interface
Event
Handler
TEST 201:
Interrupt handler-to-link interface

553-1382
553-2901-501
Standard 4.00
October 1997
Page 73 of 108
DCH system messages

Three fields follow each DCH error code. See Table 14. The first field gives
the port number. Since the information in the second and third fields is not
useful to the craftsperson, disregard those fields.
Traffic reports on D-channel measurements give peg counts that can help
pinpoint problems (see D-channel traffic).
Table 14
D-channel error messages (Part 1 of 5)
Message
Description
DCH001
ISDN package is not equipped.
DCH002
Command not allowed.
DCH003
DCHI is disabled.
DCH004
Only one link can be monitored at one time.
DCH005
Undened link/DCHI state. There is a software/hardware mismatch.

Action:
1. Disable and re-enable the DCHI card.
2. Check DCHI status.
DCH006
DCHI not responding.

Action:
DCH007
Command invalid at this state.
DCH009
Invalid command entered.
DCH010
Invalid parameter #1.
DCH011
Invalid number of parameters.
DCH012
DCHI is not congured.
DCH017
Invalid key entered.
DCH018
Invalid total keys entered.
DCH019
Invalid DCHI table number
DCH020
Tx-buffer not empty
DCH021
Rx buffer not ready.

Action:
Check DCHI status.
Maintenance
Page 74 of 108
Table 14
Message
Description
DCH023
Unexpected loop input.
DCH024
Backup D-channel is not congured.

Action:
Command can only be carried out if backup D-channel is
congured.
DCH025
D-channel is already active.

Action:
Specify other D-channel or "no action."
DCH300
Test 200, interrupt handler interface, failed.

Action:
If test continues to fail, report software problem.
DCH301
Test 201, interrupt handler-to-link interface, failed.

Action:
If test continues to fail, report software problem.
DCH302
DCHI test 101 failed. No interrupt, but good data.

Action:
Replace DCHI.
DCH303
DCHI test 101 failed. There is interrupt, but bad data.

Action:
Replace DCHI.
DCH304
DCH test 101 failed. No interrupt and bad data.

Action:
Replace DCHI.
DCH305
DCHI test 100 failed. Stuck interrupt.

Action:
Replace DCHI.
DCH1001
Invalid primitive-ID.
Action:
Check DCHI status.
DCH1002
Unexpected primitive.
Action:
Check DCHI status.
553-2901-501
Standard 4.00
October 1997
Page 75 of 108
Table 14
Message
Description
DCH1003
MDL error.
Action:
1. There is a protocol problem. If the error continues, check the
DCHI card.
2. If the problem still continues, report it.
DCH1004
PRI is out of service.
DCH1005
Link Release error.

Action:
2. Check the PRI-to-DCHI cable.
3. Check PRI status.
DCH1006
Link establishment error.

Action:
DCH1007
Interrupt was lost.

Action:
If this message appears more than 10 times per day, run DCHI
tests 200 and 201.
DCH1008
Output request buffer overow.

Action:
If this message appears more than ve times per day, reset
D-channel output buffer size using:
LD 17
OTBF
DCH1009
PRI reported DCHI is out of service.

Action:
DCH1010
DCHI is software-disabled.
Maintenance
Page 76 of 108
Table 14
Message
Description
DCH1011
Late link establishment.

Action:
1. If the far end is disabled, no action is needed.
2. If the far end is active, increase the timer threshold:
LD 17
T200
DCH1012
Late link Release.

Action:
1. If the far end is disabled, no action is needed.
2. If the far end is active, increase the timer threshold:
LD 17
T200
DCH1013
Invalid DCHI status due to software/hardware mismatch.

Action:
DCH1014
Invalid DCHI status due to software/hardware mismatch.

Action:
DCH1015
Receive buffer full.

Action:
If this messages appears more than ve times per day, disable
and re-enable DCHI.
DCH1016
Transmit buffer full.

Action:
Check the DCHI card.
DCH1017
No end-of-message.
Action:
Denitely a DCHI problem. Check the DCHI card.
DCH1018
No transmit buffer available.

Action:
1. Check the PRI-to-DCHI cab
553-2901-501
Standard 4.00
October 1997
Page 77 of 108
Table 14
Message
Description
DCH1019
DCHI is hardware disabled.
DCH1040
The requested operation does not apply to the selected interface.

Event:
Attempt to enable SERV messages on an APISDN interface.
DCH4283
Both D-channels have been Released.

Action:
Establish the D-channel.
DCH traffic (LD 2)

Traffic report TFS009 provides accumulated D-channel statistics. This report
can be included in the scheduled traffic report, or printed on demand as
described below.
To enable D-channel measurement in the scheduled traffic reports use the Set
System Traffic Options (SOPS) command. For example, to enable option 9
for D-channel use:
LD 2
SOPS 9
To print current D-channel measurement use the Invoke System Traffic
(INVS) command. For example, to enable option 9 for D-channel use:
LD 2
INVS 9
Maintenance
Page 78 of 108
TFS009 D-channel
TFS009 reports traffic activity for D-channels. Eight fields report activity on
the Multi-purpose Serial Data Link (MSDL) D-channel. Nine fields report
activity associated with the QSIG Path Replacement feature introduced with
X11 Release 23.
Figure 11
TFS009 D-channel report format
System ID
DCH x
TFS009
aaaa
nnnn
bbbb
oooo
cccc
pppp
dddd
qqqq
eeee
rrrr
ffff
ssss
gggg
hhhh
tttt
iiii
jjjj
uuuu
yyyy
kkkk (MSDL only)
vvvv (MSDL only)
llll (MSDL only)
wwww (MSDL only)
mmmm (MSDL only)
xxxx (MSDL only)
tat1 (MSDL only)
tat2 (MSDL only)
DIV_NB
DIV_NEW
DIV_OLD
CNG_NB
CNG_NEW
CNG_OLD
CON_NB
CON_NEW
CON_OLD
FLOW
553-2901-501
FLOWa
FLOWb
Standard 4.00
FLOWc
October 1997
FLOWd
Page 79 of 108
Legend for TFS009 report

SYSTEM
number of all incoming messages received on the
aaaa
bbbb
cccc
dddd
eeee
ffff
gggg
hhhh
iiii
jjjj
yyyy
kkkk
llll
mmmm
tat1
nnnn
oooo
pppp
qqqq
D-channel
number of all incoming call processing messages
received on the D-channel
number of all incoming management messages
number of all incoming maintenance messages
average number of incoming bytes per message
accumulated real time a D-channel was busy
transferring incoming messages in half-millisecond units
(Divide the reported number by 2 for a result in
milliseconds. For example: divide a reported number of
200 by 2 for a result of 100 milliseconds.)
running average of the number of requests queued in
request output message buffer
number of times when no request output message
buffer was available
number of PRA layer-3 protocol errors since the last
trafc report
number of times the D-channel was down
number of established call-independent connections

average incoming link usage (given as a percentage of
the link capacity)
average outgoing link usage (given as a percentage of
the link capacity)
number of connected calls
total number of anti-tromboning operations attempted

since the D-channel trafc was last cleared
Number of optimization requests with the diversion
trigger
number of all outgoing messages sent on the D-channel
number of all outgoing call processing messages sent
on the D-channel
number of all outgoing management messages sent on
the D-channel
number of all outgoing maintenance messages sent on
the D-channel
Maintenance
Page 80 of 108

average number of outgoing bytes per message
rrrr
ssss
accumulated real time a D-channel was busy

transferring outgoing messages in half-millisecond units
(Divide the reported number by 2 for a result in
milliseconds. For example: divide a reported number of
200 by 2 for a result of 100 milliseconds.)
number of times a message with no End of Message
(EOM) mark was received
accumulated real time the D-channel was down since
the last report in units of 2 seconds. For example, if the
value is 10, the down time is 20 seconds
peak incoming link usage (given as a percentage of the
link capacity) over a 5-second period
peak outgoing link usage (given as a percentage of the
link capacity) over a 5-second period
tttt
uuuu
vvvv
wwww
xxxx
tat2
CNG_NB
CNG_NEW
CNG_OLD
CON_NB
CON_NEW
CON_OLD
DIV_NB
DIV_NEW
DIV_OLD
553-2901-501
Standard 4.00
time (in seconds) since the MSDL D-channel trafc

was last cleared
total number of successful anti-tromboning operations
since the D-channel trafc was last cleared
Number of optimization requests with the congestion
trigger
Number of optimization successful with the congestion
trigger: a new path is used
Number of optimization successful with the congestion
trigger but the old path has been retained
Number of optimization requests with the connected
trigger
Number of optimization successful with the connected
number trigger: a new path is used
Number of optimization successful with the connected
number trigger but the old path has been retained
Number of optimization requests with the diversion
trigger
Number of optimization successful with the diversion
trigger: a new path is used
Number of optimization successful with the diversion
trigger but the old path has been retained
October 1997
FLOW
FLOWa
FLOWb
FLOWc
FLOWd
Page 81 of 108
To prevent any application from tying up buffer

resources due to its abnormal conditions or
misbehavior, a ow control mechanism is dened in the
Meridian 1 and at the card level. This ow control
mechanism only applies to the normal interface
(receive and transmit ring buffers, not the expedited
interface).
This ow control mechanism is based on a common
window mechanism. The basic concept is that the
number of outstanding messages that are associated
with a Socket ID in the transmit or receive ring cannot
exceed a predened number, application threshold.
Note that the mechanism is based on the number of
messages per application rather than the number of
buffers per application.
rst ow control hit starts a 128ms timer to allow one
more try
second ow control hit requests the sending of
OK_TO_SEDN_REQ message via a logged SSD
message to MSDL loadware. Start the 128ms timer
third ow control hit asks the data socket to be
resynchronized by MSDL loadware. Start the 128ms
timer
fourth ow control hit starts a 128ms timer such that
the link will be forced to disable after time out.
Maintenance
Page 82 of 108
MSDL local loopback test (NT6D80)

See Figure 12. Before beginning this test, the D-channel must be in test state:
ENL TEST x, where x is the logical DCH number.
To start the local loopback test on the Multi-purpose Serial Data Link
(MSDL) card, use the ENL LLB x command, where x is the logical DCH
number.
Then perform the following test:
TEST LLB x
The test checks both MSDL expedited and normal (ring) interfaces.
The response for the expedited interface that carries urgent signaling and
maintenance messages between the Meridian 1 CPU and the MSDL MPU
follows:
DCH : X XDU TEST CONFIRM TIME : <time of day>
TEST : PASS (or FAIL)
X is the DCH logical number
XDU is the expedient message sent around the loop.
The response for the ring interface that transmits operation data between the
Meridian 1 CPU and the MSDL MPU follows:
DCH : X DU TEST CONFIRM TIME : <time of day>
TEST : PASS (or FAIL)
If the test fails, check the status of the MSDL card, used by this DCH
link, with the STAT MSDL y FULL command, where y is the physical
port (DNUM) of the MSDL card.
If the MSDL card may be faulty, disable the card and perform a reset
self-test.
DIS MSDL y
RST MSDL y
SLFT MSDL x
553-2901-501
If the card passed the test, the problem may lie in incompatible software.
Standard 4.00
October 1997
Page 83 of 108
After completing the test, remove the D-channel from the test state:
DIS TEST DCH x.
Refer to Multi-purpose Serial Data Link description (553-3001-195).
Maintenance
Page 84 of 108

Figure 12
Local loopback test (NT6D80)
Meridian 1 software
DCH
DCH Handler
MSDL Handler
Meridian 1 CPU Bus

MSDL card software
Loopback path
Meridian 1 Interface Module

(Base Code)
MSDL DCH software
Physical Layer (Layer 1) Handler
DCH
(PRI trunk)
553-5436
553-2901-501
Standard 4.00
October 1997
Page 85 of 108
MSDL remote loopback tests (NT6D80)

See Figure 13. Before beginning this test, verify the following:
D-channels on both switches are configured on MSDL cards
DCH links on both switches are set to TEST mode
DCH at Switch B is in remote loopback mode (RLB)
remote capability (RCAP) is MSDL
1
Place DCH links on both systems in TEST mode. Enter ENL TEST DCH
x on Switch A and ENL TEST DCH y on Switch B for the same DCH link.
The DCH links on both switches are automatically placed in idle state
(IDLE).
Place the Switch B DCH link in remote loopback state (RLB) with ENL
RLB DCH x. The DCH link in Switch A must stay in idle.
From Switch A, perform the loopback test with TEST RLB DCH x.
The result of the remote loopback test is displayed on Switch As console
in the following format:
DCH : X RLB TEST CONFIRM TIME : <time of day>
TEST : PASS
TEST : FAIL - NO DATA RCV FAR END
TEST : FAIL - CORPT DATA RCV FAR END
TEST : FAIL - REASON UNKNOWN
TEST : FAIL may indicate a problem in the physical link between the two
switches, or faulty equipment in either switch. Check the connections,
and verify the status of the MSDL and PRI trunk cards used for this link.
Place the Switch B DCH link back to the idle state, with the DIS RLB y
command.
If you think the MSDL card used in either switch has failed, check the
status of the DCH link and the status of the MSDL card by entering STAT
MSDL x FULL.
Maintenance
Page 86 of 108
If the MSDL card may be faulty, disable the card and perform a self-test:
DIS MSDL x
SLFT MSDL x
If the card passed the test, the problem may lie in incompatible software.
Refer to Multi-purpose Serial Data Link description (553-3001-195).
After the test is complete, remove both sides from the test state:
DIS TEST DCH x
DIS TEST DCH y
553-2901-501
Standard 4.00
October 1997
Page 87 of 108
Figure 13
Remote loopback tests (NT6D80)
Switch A
Meridian 1
software
DCH
Switch B
Meridian 1
software
DCH Handler
MSDL card
software
MSDL Handler
Meridian 1
CPU Bus
DCH
DCH Handler
MSDL card
software
MSDL Handler
Meridian 1
CPU Bus
Meridian 1 Interface
Module
Meridian 1 Interface
Module
MSDL DCH Software

Module
MSDL DCH Software

Module
Physical Layer (Layer 1)

Handler
Physical Layer (Layer 1)

Handler
Loopback path
DCH
MSDL Port
DCH
MSDL Port
DCH or ISL link
553-5437
Maintenance
Page 88 of 108
Protocol log (PLOG)

The count of D-channel errors is stored in the Protocol Log (PLOG). The
PLOG is printed by using LD 96 as shown in the PLOG status check below.
Protocol errors can be the result of
PRI transmission problems and re-start procedures, or
a protocol mismatch with the far end
The PLOG counters are cleared after
the PLOG is printed, or
the DCHI card is enabled
Note: When a protocol counter overflows, the PLOG is printed
automatically and the counters are cleared.
When the PLOG has non-zero counters, check the PRI status and alarms as
shown. See Table 15 for the PLOG for X11 Relase 17 and earlier. See
Table 16 for the PLOG for X11 Release 18 and later.
553-2901-501
Standard 4.00
October 1997
Page 89 of 108
Procedure 9
PLOG status check
1
Check the contents of the PLOG using the following:

LD 96
PLOG DCH x
Response with X11 Release 17 and earlier:
DCH x I xxxx
yy zz 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
where:
I = incoming
xxxx = system real time (in hexadecimal)
yy = maintenance indication primitive ID
zz = maintenance indication task ID
00 00 ... = protocol error counters
Response with X11 Release 18 and later:
DCH : XX MAINT CONFIRM TIME: <time of day>
COUNTER
VALUE
1:
12
12:
8
20:
15
N:
XX
2
If there are PRI bit rate or frame errors, assume there is a PRI problem.
If there is no problem with the PRI but there are a large number of
protocol errors, report a protocol problem.
Maintenance
Page 90 of 108
Table 15
Protocol log (X11 Release 17 and earlier)
Format
DCH x I xxxx
yy zz 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Protocol counters
1
count of missing PRI handshakes
count of peer initiated re-establishment link
count of unsuccessful retransmit N200 of SABME
count of unsuccessful retransmit N201 of DISC
count of N(R) errors
count of information elds with length greater than N201
count of undened frames
count of I elds but not allowed
count of FRMR frames
10
count of CRC error frames
11
count of REJ frames
12
count of messages with less than 4 octets
13
count of undened protocol discriminators
14
count of undened message types
15
count of messages missing one or more mandatory information elements
16
count of messages with one or more undened information elements
553-2901-501
Standard 4.00
October 1997
Page 91 of 108
Table 16
Protocol log (X11 Release 18 and later) (Part 1 of 3)
Format
DCH : XX MAINT CONFIRM TIME: <time of day>
COUNTERVALUE
Protocol counters
1
count of missing PRI handshakes
count of peer initiated re-establishment link
count of unsuccessful retransmit N200 of SABME
count of unsuccessful retransmit N200 of DISC
count of N(R) errors
count of information elds with length greater than N201
count of undened frames
count of information elds that are not allowed to contain information
count of FRMR frames received from the far end
10
count of CRC error frames received from the far end
11
count of REJ frames received from the far end
12
count of layer 3 messages with less than 4 octets
13
dummy counter, always zero
14
count of undened layer 3 message types
15
count of layer 3 messages missing one or more mandatory information elements
16
count of layer 3 messages missing one or more undened information elements
17
count of layer 1 reports of no external clock being received
18
count of aborted frames
19
count of SABME frames received with incorrect C/R bit
Maintenance
Page 92 of 108
Table 16
20
count of supervisory frames received with F = 1
21
count of unsolicited DM responses with F = 1
22
count of unsolicited UA responses with F = 1
23
count of unsolicited UA responses with F = 0
24
count of DM responses with F = 0
25
count of times that no response was received from the far end after N200
transmissions retransmissions of RR or RNR
26
count of frames received with incorrect header length
27
number of times owner receiver busy condition was entered
28
number of times peer receiver busy condition was entered
29
count of messages with call reference length greater than 2
30
count of optional IEs received with invalid contents
31
count of mandatory IEs received with invalid contents
32
count of messages received with IEs not ordered correctly
33
count of IEs which were repeated in received messages, but are only allowed to
appear once per message
34
count of IEs received with length exceeding the specied maximum length for the IE
35
count of layer 3 messages from far-end with invalid call reference ag value of 0
36
count of layer 3 messages from far-end with invalid call reference ag value of 1
37
count of layer 3 messages from far-end with invalid global call reference
38
count of layer 3 messages from SL-1 that are too short
39
count of layer 3 messages from SL-1 containing an undened message type
40
count of layer 3 messages from SL-1 missing mandatory IE(s
41
count of layer 3 messages from SL-1 containing unsupported IE(s)
553-2901-501
Standard 4.00
October 1997
Page 93 of 108
Table 16
42
count of layer 3 messages from SL-1 containing invalid operational IE(s)
43
count of layer 3 messages from SL-1 containing invalid mandatory IE(s)
44
count of layer 3 messages from SL-1 with IE(s) out of order
45
count of layer 3 messages from SL-1 containing repeated IE(s)
46
count of layer 3 messages from far-end with an invalid call reference length
47
count of layer 3 messages from SL-1 with an invalid call reference ag value of 0
48
count of layer 3 messages from SL-1 with an invalid call reference ag value of 1
49
count of layer 3 messages from SL-1 with an invalid global call reference
50
count of unexpected layer 3 messages received from the far-end
51
count of unexpected layer 3 messages received from the SL-1
52
count of unexpected layer 3 timer expirations
53
count of protocol messages received when D-channel is not in service or waiting for a
Service Acknowledge message
Maintenance
Page 94 of 108
Replacing the DCHI
CAUTION
Procedure 10
Replacing the DCHI card
Step
1
Action
Disable the D-channel using:
LD 96
DIS DCH N
Disable the asynchronous port on the DCHI card (if equipped) using:
LD 48
DIS ESDI N
Set the ENB/DIS switch to DIS.
Disconnect cables on DCHI faceplate.
Remove the DCHI from the shelf.
Make sure that the new DCHI card switch settings are the same as the faulty DCHI
card. See 553-2901-201 and 553-3001-211 for switch-setting information.
Install the new DCHI card in the appropriate slot.
Connect the faceplate cables to the new DCHI card.
Set the ENB/DIS switch to ENB.
10
Enable the D-channel using:

LD 96
ENL DCH N
553-2901-501
Standard 4.00
October 1997
Page 95 of 108
Overlay 60 - Loop Maintenance for SYS-12, AXE-10, SWE,

SWISSNET, NUMERIS, EuroISDN, NEAX-61, Asia-Pacific
If there is a loop configured with a SYS-12, AXE-10, SWE, SWISSNET,
NUMERIS, EuroISDN, NEAX-61, or Asia-Pacific D-channel, Overlay 60
adds the the D-channel type to the printout displayed upon entering the
overlay. This printout alerts the craftsperson to the relationship of the
difference of the timeslot-to-channel mapping between the MSL-1 and the
D-channel type:
Table 17
SL-1 SYS- 12, AXE- 10 SWE, NUMERIS, SWISSNET, EuroISDN, NEAX-61 channel timeslot
mapping
Channel
SL-1
Network
Timeslot
B-channel
1-15
16-30
1-15
17-31
1-15
17-31
D-channel
31
16
16
Maintenance
108
Page 97 of 108
Clock Controller (CC) maintenance

Clock operation
Tracking mode
In tracking mode, the PRI loop supplies an external clock reference to a clock
controller. See Figure 14. Two PRI loops can operate in tracking mode, with
one defined as the primary reference source for clock synchronization, the
other defined as the secondary reference source. The secondary reference
acts as a back-up to the primary reference.
As shown in the Figure 14, an SL-1 system with a dual CPU may have two
clock controllers (CC0 and CC1). One clock controller acts as a back-up to
the other. The clock controllers should be locked to the reference clock.
Maintenance
Page 98 of 108
Figure 14
Clock controller primary and secondary tracking
primary
REF1
J1
J2
secondary
PRI
PRIMARY
Reference
REF2
J1
Clock
Controller
0
J3
J2
primary
REF1 J1
clock controller back-up
PRI
SECONDARY
Reference
REF2 J2
J2
J1
secondary
Clock
Controller
1
J3
553-1385
Free run (non-tracking) mode

The clock synchronization for a PRI loop may operate in free-run mode if
the loop is not defined as the primary or secondary clock reference
the primary and secondary references are disabled
the primary and secondary references are in local alarm
Reference clock errors

SL-1 software checks every 0-15 minutes (programmable) to see if a
clock-controller or reference-clock error has occurred.
553-2901-501
Standard 4.00
October 1997
Page 99 of 108
In tracking mode, at any one time, there is one active clock controller which
is tracking on one reference clock. If a clock-controller error is detected, the
system switches to the back-up clock controller, without affecting which
reference clock is being tracked.
A reference-clock error occurs when there is a problem with the clock driver
or with the reference system clock at the far end. If the clock controller
detects a reference-clock error, the reference clocks are switched.
Automatic clock recovery

An option for automatic clock recovery can be selected in LD 60 with the
command EREF.
A PRI loop is disabled when it enters a local alarm condition. If the local
alarm is cleared, the loop is enabled automatically. When the loop is enabled,
clock tracking is restored in the following conditions:
1
If the loop is assigned as the primary reference clock but the clock
controller is tracking on the secondary reference or in free run mode, it
is restored to tracking on primary.
If the loop is assigned as the secondary reference clock but the clock
controller is in free run mode, it is restored to tracking on secondary.
If the 15-minute clock check indicates the system is in free-run mode:

1
Tracking is restored to the primary reference clock, if defined.
If the primary reference is disabled or in local alarm, tracking is restored

to the secondary reference clock, if defined.
Note: If the system was put into free-run mode intentionally by the
craftsperson, it will resume tracking on a reference clock at this time.
This occurs unless the clock-switching option has been disabled (LD 60,
command MREF), or the reference clock has been "undefined" in the
database.
Maintenance
Page 100 of 108
Automatic clock switching

If the EREF option is selected in LD 60, tracking on the primary or secondary
reference clock is automatically switched in the following manner:
1
If software is unable to track on the assigned primary reference clock, it

switches to the secondary reference clock and sends appropriate DTC
maintenance messages.
If software is unable to track on the assigned secondary reference clock,

it switches to free-run mode.
Clock controller commands (LD 60)

Table 18
Clock controller commands in Overlay 60
Command
Description
DIS CC x
Disable specied system clock controller x (0 or 1).
DSCK L
Disables the clock for loop L.
DSYL L
Disables remote alarm processing for loop L.
ENL CC x
Enable specied system clock controller x (0 or 1).
ENYL L
Enables remote alarm processing for loop L.
EREF
Enables automatic switching and recovery of primary and secondary

reference clocks when loops associated with these clocks are automatically
enabled.
MREF
Disables automatic switching and recovery of the primary and secondary

reference clocks when loops associated with these clocks are automatically
disabled or in local alarm.
SSCK x
Provides status of system clock x (0 or 1). Indicates the active controller as

well as active primary or secondary reference-clock source or free run.
SWCK
Switches the system clock from the active to the standby clock. The
reference-clock source remains unchanged.
TRCK xxx
Set clock-controller tracking. Where xxx represents one of the following

mnemonics:
PCK
SCLK
track secondary clock
FRUN
553-2901-501
track primary clock

free-run mode
Standard 4.00
October 1997
Page 101 of 108
Clock controller messages

Table 19
Clock controller status and error messages
Command
Description
DTC001
Clock controller tracking on primary source loop.
DTC002
Clock controller tracking on secondary source loop.
DTC003
Clock controller cannot be accessed.
DTC004
Clock controller indicates clock-aging error.
DTC005
Reference clock switched to secondary source from primary.
DTC006
Reference clock switched to free-run mode from secondary or primary.
DTC007
Active reference clock is set to re-track primary.
DTC008
Active reference is free run or the clock controller cannot be accessed.
DTC009
Clock controller has been switched.
DTC010
Universal asynchronous receiver/transmitter (UART) error is detected.
DTC011
Clock control self-test failed; error exists.
DTC012
Clock control has reference-clock problem.
DTC013
Clock control has tracking problem.
DTC014
Clock control set to free run.
DTC015
Clock control set to secondary.
DTC016
Clock controller restored from free run or secondary to tracking on primary.
DTC017
Clock controller restored from free run to tracking on secondary.
DTC018
Cannot switch or restore to a reference clock because automatic

reference-clock switching option is disabled.
Maintenance
Page 102 of 108
Replacing the clock controller
CAUTION
CAUTION
Do not deviate from this procedure. Deviation will not cause the
system to SYSLOAD or initialize, but will stop call processing.
Procedure 11
Step
1
Action
Make sure that the clock controller card being replaced is associated with an
inactive CPU. Switch, if necessary, using:
LD 35
SCPU
Disable the clock controller card being replaced using:

LD 60
DIS CC x
On the clock controller card being replaced, set the ENB/DIS switch to DIS.
Disconnect cables from clock-controller card being replaced.
Remove card from shelf.
Set the ENB/DIS switch to DIS on the clock-controller card being added.
Make sure that the switch settings are correct.
Install new clock-controller card in same slot as the defective card.
Reconnect cable(s) to clock-controller faceplate.
553-2901-501
Standard 4.00
October 1997
Page 103 of 108
Procedure 11
Step
10
11
Action
Set ENB/DIS switch on new clock controller to ENB.
Enable new clock-controller card using:
LD 60
ENL CC x
12
Verify normal service level; rst, switch the active clock to standby using:
LD 60
SWCK x
If an error message results, refer to Maintenance Manual II: Diagnostic Programs
Description And Input/Output Reference (553-2301-511) for the interpretation.
Note: Switching clock controllers using LD 60 will generate ERR20 messages.
These can usually be ignored, but avoid excessive switching, especially when
counters are near the maintenance or out-of-service thresholds. Excessive
switching can generate maintenance or out-of-service threshold messages, or
cause the PRI to be disabled.
Check the counters in LD 60. If necessary, reset the counters using the RCNT
command.
Maintenance
Page 104 of 108
Clock controller switch settings

Switch settings for the QPC775 Clock Controller are given below. See
Table 20.
Table 20
Clock controller switch settings
SYSTEM/CLOCK
CONTROLLER
SW1
SW2
SW3
SW4
(1,2)
JUMPER
1
JUMPER
2
system options 21/21E and

ST/STE (half-group) QPC775
n/a
ON
OFF
ON
n/a
n/a
system options 51/51C,

61/61C and NT single-group
QPC775
n/a
ON
OFF
ON
n/a
n/a
system options 51/51C,

61/61C and NT half-group
QPC775
n/a
ON
OFF
ON
n/a
n/a
system options 71, XN and

XT (multi-group) QPC775
n/a
OFF
OFF
ON
n/a
n/a
system options 81/81C

(multi-group) QPC775
n/a
OFF
OFF
ON
n/a
n/a
553-2901-501
Standard 4.00
October 1997
Page 105 of 108
Clock controller cabling

The clock-controller cabling for SL-1 configurations is shown in the
following diagrams. See Figure 15, Figure 16, and Figure 17.
Figure 15
Clock controller cabling:
Half-group systems (system options 21, 51, 61, ST and NT)
QCAD130 to PRI Card

(Secondary Reference)
REF1
J1
QCAD130
J2
J1
PRI Primary
Reference
R E F 2 J2
No connection
QPC775
Clock
Controller
0
J3
No connection
553-1386
Maintenance
Page 106 of 108
Figure 16
SL-1 system options 51, 61 and NT single-group
QCAD130 to PRI Card

QCAD130
REF1
J1
J2
J1
PRI Primary
Reference
QPC775
Clock
Controller
0
J3
QCAD130
J2
R E F 2 J2
J1
QPC775
Clock
Controller
1
J3
QCAD125
553-1387
553-2901-501
Standard 4.00
October 1997
Page 107 of 108
Figure 17
SL-1 system options 71,81/81C, XN and XT multi-group
QCAD130 to PRI Card

R E F 1 J1
QCAD130
J2
J1
QPC775
Clock
Controller
0
SCG0
J3
PRI Primary
Reference
QCAD110
QPC775
Junctor
QCAD110
R E F 2 J2
QCAD130
J2
J1
SCG1
QPC775
Clock
Controller
1
J3
553-1388
Maintenance
Family Product Manual Contacts Copyright FCC notice Trademarks

Document number Product release Document release Date Publish
Meridian 1

Maintenance
1991,1997 Northern Telecom

All rights reserved
Information is subject to change without notice.
Northern Telecom reserves the right to make changes
in design or components as progress in engineering
and manufacturing may warrant. This equipment has
been tested and found to comply with the limits for a
Class A digital device pursuant to Part 15 of the FCC
rules, and the radio interference regulations of
Industry Canada. These limits are designed to provide
reasonable protection against harmful interference
when the equipment is operated in a commercial
environment. This equipment generates, uses and can
radiate radio frequency energy, and if not installed and
used in accordance with the instruction manual, may
cause harmful interference to radio communications.
Operation of this equipment in a residential area is
likely to cause harmful interference in which case the
user will be required to correct the interference at their
own expense.
Meridian 1 is a trademark of Northern Telecom.
Publication number: 553-2901-501
Document release: 4.00
Date: October 1997
Printed in Canada

E1 Pri DCH Loop Clocking1

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

E1 Pri DCH Loop Clocking1

Hochgeladen von

Copyright:

Verfügbare Formate

Meridian 1

International ISDN PRI

Document Number: 553-2901-501

Year Publish FCC TM

International ISDN PRI

Issue 4.00 released as Standard for Generic X11 Release 23.

Issue 3.00 released as Standard for Generic X11 Release 21B.

Issue 2.00 released as Standard for Generic X11 Release 21A.

Issue 1.00 released as Standard for Generic X11 Release 20.

This document is the standard release for Phase 8b.

This document is the standard release for Phase 7C.

This publication is the standard release for Phase 7B.

This publication is the standard release for Group F (Phase 6B iii).

This publication is the standard release for Phase 5.

International ISDN PRI

PRI operations guide . . . . . . . . . . . . . . . . . . . . . . .

PRI quick reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PRI commands (LD 60) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DCHI quick reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D-channel commands (LD 96) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PRI status check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Call Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

International ISDN PRI

PRA fault clearing . . . . . . . . . . . . . . . . . . . . . . . . . .

PRI remote alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Primary Rate Interface (PRI) maintenance . . . . . .

PRI commands (LD 60) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PRI alarm commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PRI test commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PRI system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PRI error detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TN to channel number conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using the error counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Replacing the PRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Pulsed E&M DTI2 signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D-channel (DCH) maintenance . . . . . . . . . . . . . . .

DCH commands (LD 96) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DCH system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DCH traffic (LD 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MSDL local loopback test (NT6D80) . . . . . . . . . . . . . . . . . . . . . . . . .

MSDL remote loopback tests (NT6D80) . . . . . . . . . . . . . . . . . . . . . . .

Protocol log (PLOG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Replacing the DCHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overlay 60 - Loop Maintenance for SYS-12, AXE-10, SWE, SWISSNET,

Clock Controller (CC) maintenance . . . . . . . . . . . .

Clock controller commands (LD 60) . . . . . . . . . . . . . . . . . . . . . . . . . .

Clock controller messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Replacing the clock controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Clock controller cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

International ISDN PRI

International ISDN PRI

International PRI Installation

International ISDN PRI Feature description and

Basic and Network Alternate Route

Electronic Switched Network

2-Mb/s Digital Trunk Interface

2-Mb/s Digital Trunk Interface Installation

2-Mb/s Digital Trunk Interface General

2Mb/s Digital Trunk Interface Fault

PRI operations guide

International ISDN PRI

PRI operations guide