Transfer Call To Non-Local Extension Does Not Return; Conference: Cannot Add Call; Did Calls Not Completed - Avaya MERLIN MAGIX Maintenance And Troubleshooting Manual

Integrated system release 2.0 and earlier
Hide thumbs Also See for MERLIN MAGIX:
Table of Contents

Advertisement

Maintenance and Troubleshooting
Transfer Call to Non-Local Extension Does Not
Return
Possible Cause: If a transfer to a non-local extension cannot be completed (due to the extension
being busy, for example), it only returns when the call is routed over tandem PRI facilities, not
tandem tie trunks or the PSTN trunks that may be used for less preferred routes.
What to Do: Review the routing for the call. See Reviewing the Non-Local Dial Plan and Routing
and check with the coordinating system manager if necessary. If the call is routed over any tandem
tie trunks or over any PSTN facilities, you have solved the problem.
If the call is routed only over tandem PRI facilities, call the Technical Support Organization at 1 800
628-2888; consultation charges may apply.

Conference: Cannot Add Call

Non-local extensions are treated as outside parties for the purpose of transfer. A non-local
conference participant takes up one of the two outside calls permitted in a conference.
A PassageWay Telephony Services client cannot add a non-local extension to a
conference. The user must add the conferee by using a telephone. If a conferee is
dropped, the PassageWay Telephony Services client display does not so indicate. A
PassageWay Telephony Services client, when added to a conference, only sees
information about the conference originator, not about other conferees.
If this is not the problem, call the Technical Support Organization at 1 800 628-2888; consultation
charges may apply.

DID Calls Not Completed

There are several reasons why Direct Inward Dialing (DID) calls across a private network may not
complete, either due to busy facilities or to faulty programming. The coordinating system manager
may need to address the problem.
Possible Cause 1: All programmed and available routes for the call are busy.
What to do: This problem solves itself when traffic decreases. Only address the problem if it
persists.
Note the extension number range for the DID destination. At the system where the call is received
from the PSTN, check that the pattern assigned to the range includes sufficient different routes
with pools (of tandem and/or PSTN facilities) to handle the call volume. This is accomplished by
checking the error for errors 4C01 (Pool Empty), 4C02 (Pool Busy), or 4C03 (Pool Busy and/or
Out-of-Service). If any of these error codes are present, check the pool index on the maintenance
screen to determine if it matches the pool used to deliver the call. If it matches, check occurrence
times and count. If the count is too high and the occurrences indicate the problem occurred within
Troubleshooting Guidelines and Preparation
5-22
5
5
5

Advertisement

Table of Contents
loading

Table of Contents