PI-LINK (Processor Interface Link)
Issue 4 May 2002
10-1235555-233-123
e. This error occurs when the Processor Interface link fails to be established.
Check all connections and administration. This could also occur as a result
of another error, the failure of Test #182, for example. If the other error on
the link can be cleared, then this error may also clear. See the ‘‘Link
Recovery’’ section.
1, 2 System error.
7 System error. If this error is occurring on all administered links with
the same Aux Data and all links are alarmed, then execute the
reset interface command to restore all the links.
12 One of the two Loop Around Tests failed (#182 or #183). See the
“Link Recovery” section.
13 Hardware problem with DS1 facility is affecting ISDN links. Refer
to DS1-BD Maintenance documentation.
19 A transient state associated with the D-channel backup protocol.
The link is being held in the busy state until call control can be
moved to the new active link. No action needs to be taken.
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.
To Next Page
Loading...
