No external release on pbx, Disconnect – AT&T System 25 User Manual
Page 216
MAINTENANCE
ERROR MESSAGE
AND DESCRIPTION
POSSIBLE SOLUTION
Memory Management Error:
B u s
Possible
s o f t w a r e error.
If
error that occurs while accessing
problem
persists,
c h e c k o r
the “other than protected” RAM.
replace CPU/Memory CP. A
A warm start is logged after this
warm start or retranslation of the
e r r o r .
system could be a possible fix for
this problem.
Memory ROM Checksum Error:
If this problem persists, replace
Memory has failed the ROM test.
CPU/Memory CP.
Message Corruption: (Other than
If consistent error for particular
CPU/Memory)
Down-link
port CP, check TDM bus drivers
message checksum error.
on the CP. If error is associated
with many CPs, drivers on CPU
may be bad.
Also check 1/O
cables and TDM bus terminator.
M e s s a g e From Non-Translated
Translate the CP and its port, or
Port: Untranslated port CP sent
remove the CP from system.
an up-link message.
No External Release On PBX
Check associated trunk
( s e e
Disconnect:
CO
did not release
Figure 4-4). Error is cleared from
within 4-5 minutes on DID or
log when trunk release occurs
ground start trunk after System 25
belatedly.
disconnected. M e s s a g e
s e n t
every 4-5 minutes until release.
N o
F r e e Buffer:
(STARLAN
If the reset is not successful,
Interface CP) This error resets the
reseat board. If the reseat fails,
C P .
replace CP.
No Loop Current On Incoming
Swap CP with similar CP. If
Call:
CP does not detect dc
problem follows the boards,
current on answered incoming
replace CP. If problem persists,
call. Call will drop.