Iars Calls Go To System Operator (Unassigned Extension); Did Or Pri Dial-Plan Routed Calls Not Completed; Excessive Line Noise On Voice And Data Calls - 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
ARS Calls Go to System
Operator (Unassigned Extension)
Possible Cause: System managers in your private network may have set up ARS and remote
access to route outgoing calls to PSTN facilities on switches where these calls are most
economical.
What to Do: If such calls are reaching a system operator (unassigned extension) on a private
networked system, rather than being routed to the PSTN, the coordinating system manager must
check the tandem facilities that carry calls to the system where the operator is located. The
problem is caused when one or more tandem trunks has no switch identifier (the factory setting).
If this is not the problem, call the Technical Support Organization at 1 800 628-2888; consultation
charges may apply.

DID or PRI Dial-Plan Routed Calls Not Completed

There are two possible causes for this occurring
Possible Cause 1: DID and PRI calls cannot be routed to a 5-digit DEFINITY ECS or DEFINITY
ProLogix Solutions system.
What to Do: Verify system programming and the digits received from the PSTN. Refer to "Non-
Local Dial Plan Number" in Chapter 5 of the Network Reference for details on programming
required.
Possible Cause 2: DID or PRI routing not correct.
What to Do: The coordinating system manager should check the DID or PRI routing. These calls
may come into one private networked switch and be routed across the private network to an
extension on another system in the private network. The routing must specify the correct tandem
trunk pools, extension numbers, and digit manipulation.
If the routing is correct, contact the service provider. If the service provider instructs you to do so,
call the Technical Support Organization at 1 800 628-2888; consultation charges may apply.

Excessive Line Noise on Voice and Data Calls

Possible Cause: Clocks are not properly synchronized.
What to Do: The coordinating system manager should check error logs at problem systems. If
slips are occurring at a high rate or an alarm was raised, clock synchronization is a problem. The
coordinating system manager should then check the programming for the PRI tandem trunk(s)
and/or PSTN digital facilities that carry the calls. A single clock source is used for all private
networked systems so that calls are properly synchronized. For details about clock
synchronization in a private network, see "Clock Synchronization" in Chapter 5 of the Network
Reference.
Troubleshooting Guidelines and Preparation
5-28
5
5
5

Advertisement

Table of Contents
loading

Table of Contents