Filter
Top Products
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Object Repair Procedures
Page 10-409DID-TRK (DID Trunk)
10
1 – Verify trunk administered wink/immediate-start parameter.
2 – Refer problem to CO.
e. This is a software audit error that does not indicate any hardware
malfunction. Run the Short Test Sequence and investigate associated
errors (if any).
f. This error type indicates that the circuit pack has been removed or has
been insane for more than 11 minutes. To clear the error, reinsert or
replace the circuit pack.
g. Rotary dial pulse on-hook longer than 105 msec – Break between rotary
pulses is too long.
1 – Test trunk by performing an incoming test call.
2 – Refer problem to CO.
h. Rotary dial rate below eight pulses/sec – More than 135 msec between
two successive breaks.
1 – Verify trunk administered interdigit-timing parameters.
2 – Refer problem to CO.
i. Rotary dial rate above 12 pulses/sec – Less than 75 msec between two
successive breaks.
1 – Verify trunk administered interdigit-timing parameters.
2 – Refer problem to CO.
j. Digit detection – Co is starting new rotary dial digit within 150 msec of
previous digit.
1 – Verify trunk administered interdigit timing parameters.
2 – Refer problem to CO.
k. Loop current active – CO not releasing trunk after PBX disconnect. Occurs
when the PBX end drops first and the CO does not release the trunk within
four minutes.
1 – Verify the interface to the network with a hand telephone set. If calls
are placed correctly, then refer problem to the CO.
2 – If unable to place calls or this equipment is not available, check the
status on port using the status trunk command. If active but not
connected, disconnect bridging clips at the network interface. Check
status on the trunk. If trunk went idle, then replace clips. If trunk is still
active but unable to place calls, refer problem to the CO.
l. Late CO trunk release – This event only happens after the occurrence of
Error Type 513. The CO released the trunk four minutes after the PBX
dropped the call. This event decrements the severity (error count) of Error
Type 513, or may mean the problem related to Error Type 513 has been
fixed.
1 – Verify that Error Type 513 does not occur again. Refer to Error 513.