Siemens HiPath 5000 Service Manual page 437

Table 3-166 ANI4 (for selected countries only) - LED Statuses for Trunk 1
LED
Green LED - Firmware Condition
Off No caller ID signals on the line.
Line is not connected to trunk channel 1.
The incoming signal is lower than –36 dBm (as de-
fined in Bellcore SR3004 for the lowest caller ID sig-
nal (space - signal)): the Mitel chip on ANI4 shows no
reaction.
The LED or the microcontroller is defective.
The system has not yet started.
On The Mitel chip interprets the signal on the line as an
(but FSK carrier signal. However, this could mean that
glowing there is noise or speech on the line, too.
weakly) The firmware is in the state of recognition.
On A valid caller ID signal (correct channel seizure/mark
(for ap- - bit sequence + valid message byte) on the line is be-
prox. ing recognized at the moment. If a message is not
1 s) displayed on the optiset E or optiPoint 500 telephone,
there may be too much noise on the line. In other
words, some bits in the signal have "tipped over" into
the other logical status. The firmware builds the
checksum for the received caller ID message byte
and compares this checksum with the one received.
Red LED - Checksum Status
On The received caller ID signal has a checksum error.
The LED is reset after the next correct caller ID mes-
sage is received.
Off Checksum is OK.
P31003-H3560-S403-54-7620, 09/05
HiPath 3000 V6.0, HiPath 5000 V6.0, Provisional Service Manual
Meaning
Boards for HiPath 3000
Action
Call service provider and
ask if feature is available.
Connect line to trunk chan-
nel 1.
Call service provider and
ask if feature is available.
If so, the signal that appears
on the customer side is too
low (not Bellcore-compliant).
This must be corrected by
the service provider.
Replace ANI4 board.
Start up system.
–
–
If the red LED is on after ev-
ery call: the FSK signal is
provided, but is not Bellcore-
compliant on the customer
side. This must be corrected
by the service provider.
–
boards.fm
Options
3-347