User Guide

DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Object Repair Procedures
Page 10-1057PI-LINK (Processor Interface Link)
10
32771
32772
The remote endpoint indicates that the call is up and the
local PBX cannot complete the call. Check trunk status (on
the remote end and local end) if a DS1 trunk is used, or
check the status of the data module if a data module is
used in the link. The commands are status trunk trk-grp/
member or status data-module <ext>. If the destination is
in-service/active, then the commands are busyout trunk
trk-grp/member and release trunk trk-grp/member (on
both sides of the link if this is a DCS link). If a data module
is used in the link, then use a busyout data-module <ext>
command followed by a release data-module <ext>
command. Busy out the Processor Interface Link prior to
busying the trunk or data module. Release the Processor
Interface Link via release link lnk-no command and the
Processor Interface Link re-starts. If this fails, check the
status of the TN765 port using status data <ext> where
<ext> is the extension of the port from the interface
extension in the Display Communication Link form; if the
state is "in-service/idle" then manually call the TN765 port
and transfer the call to appropriate destination, either a
DS1 Trunk Access Code or the data module extension.
See "Link Recovery" if error still occurs. See "Link
Recovery" if error still occurs and link does not establish.
32779
32782
32801
Administration problem; check that the Processor Interface
data module extension exists via the status data-module
<ext-no> command. Verify that the destination extension
exists and that the correct routing pattern is used. In
addition, check that the Processor Interface data module
and the destination extension are administered on the COS
and/or COR forms.
32813 Administration problem; check all administration.
32815 The off-premise call timed-out. Check the "Off-Premises
Tone Detect Timeout Interval" on the Feature-Related
System Parameters Form. The time-out is administered
between 6 and 25 seconds. No response was received
from the remote destination. Check the status of the remote
destination. This might also indicate possible
synchronization problems. Network synchronization
sources should be checked on all networked switches.
Also see the SYNC Maintenance documentation.
32814 Call was answered but not by a remote data module.
Check the remote destination extension and verify that this
is a data module.
Continued on next page