Filter
Top Products
System Errors and Traffic Pegs 8-13
Octel 200/300 S.4.1PB60019−01
Table 8-2 Hardware Error Types and Remedies (continued)
Error Type:Name PriorityRemedySource
24:PBX Integration
(continued)
Problem with the
integration card
This error pertains only to certain
integrated message servers. The following
outlines the probable cause and suggested
remedy for that error, depending upon the
DATA fields.
2
08 = COULDN’T GET CALL INFO, PROBABLY GLARE, WILL TRANSFER TO
ASSIST:
The integration card was not able to determine the call
information on the last call that came in on Port DATA-3.
DATA-2 = REPLY TYPE (38 = BAD DISPLAY, 39 = GLARE)
DATA-3 = PORT CALL CAME IN ON (1...16)
DATA-4 = UNUSED
REMEDY:
Check the digit display telephone line configuration in
the PBX. Pay particular attention to the port appearances
on the keys. If the configuration is correct and the
problem persists, call your technical support center.
09 = GOT CALL, BUT NO CALL RECORD (OR CALL RECORD WAS
TOO LATE):
DATA-2 = PORT # CALL CAME IN ON
DATA-3 = NOT USED
DATA-4 = NOT USED
The call rang in on the port but the port the integration card (e.g.,
SLIC, ATTIC) didn’t send the call information. Therefore, the
Octel 200/300 port answered the call after five rings and played the
generic company greeting.
REMEDY: Check the digit display telephone line configuration in
the PBX. Pay particular attention to the port appearances
on the keys. If the configuration is correct and the
problem persists, call your technical support center.
0A = INTEGRATION TYPE CONFIGURED DOES NOT MATCH
INTEGRATION CARD INSTALLED:
REMEDY: Be sure configuration in the SLOTS Table for the
Octel 200/300 matches the integration card type.
0B = CAN’T FORWARD A PORT VIA MIC SINCE EXTENSION TO
FORWARD PORT TO IS NOT DEFINED