|
Table 3-176
|
ANI4 (for selected countries only) - LED Statuses for Trunk 1
|
|
|
|
|
| Green LED - Firmware Condition
|
|
|
|
| No caller ID signals on the line.
|
|
| Call service provider and ask if feature is available.
|
|
| Line is not connected to trunk channel 1.
|
|
| Connect line to trunk channel 1.
|
|
| The incoming signal is lower than -36 dBm (as defined in Bellcore SR3004 for the lowest caller ID signal (space - signal)): the Mitel chip on ANI4 shows no reaction.
|
|
| 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.
|
|
| The LED or the microcontroller is defective.
|
|
|
| The system has not yet started.
|
|
|
|
|
| The Mitel chip interprets the signal on the line as an FSK carrier signal. However, this could mean that there is noise or speech on the line, too.
|
| The firmware is in the state of recognition.
|
|
|
|
|
| A valid caller ID signal (correct channel seizure/mark - bit sequence + valid message byte) on the line is being recognized at the moment. If a message is not displayed on the 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
|
|
|
|
| The received caller ID signal has a checksum error. The LED is reset after the next correct caller ID message is received.
|
|
| If the red LED is on after every call: the FSK signal is provided, but is not Bellcore-compliant on the customer side. This must be corrected by the service provider.
|
|
|
|
|
|