Table of Contents
Advertisement
Table 8-2 Hardware Error Types and Remedies (continued)
Error Type:Name
24:PBX Integration
(continued)
08 =
09 =
0A =
0B =
PB60019−01
Source
Problem with the
This error pertains only to certain
integration card
integrated message servers. The following
outlines the probable cause and suggested
remedy for that error, depending upon the
DATA fields.
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
Check the digit display telephone line configuration in
REMEDY:
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.
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.
Check the digit display telephone line configuration in
REMEDY:
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.
INTEGRATION TYPE CONFIGURED DOES NOT MATCH
INTEGRATION CARD INSTALLED:
Be sure configuration in the
REMEDY:
Octel 200/300 matches the integration card type.
CAN'T FORWARD A PORT VIA MIC SINCE EXTENSION TO
FORWARD PORT TO IS NOT DEFINED
System Errors and Traffic Pegs
Remedy
able for the
SLOTS T
8-13
Priority
2
Octel 200/300
S.4.1
Advertisement
Chapters
Table of Contents
