|
|
|
|
|
|
Generally, you will work with Avaya support representatives to identify the cause of the problem and correct it. However, you may find that some problems are easy to identify and resolve on your own.
The following table describes some of these problems and suggests actions you can take to identify them:
Problems |
Description |
Suggested action |
Cable issues |
Disconnection or poor connection of cables to the back of the IR system |
Check the cable connections. Checking cable connections explains the location and function of these cables. |
Feature licensing problems |
Problems include: expired licensing, incorrect assumptions about features licensed, or, renaming of the IR system that may cause loss of feature licensing |
Determine the features you can use. The Feature Licensing screen identifies the features you are entitled to use. |
Changes to or problems with your organization's LAN system |
These may result in poor communications or no communication with required servers. |
Check with your LAN administrator if you suspect problems in this area. |
Incorrect system administration |
If changes were made recently, there may be errors in channel assignments, server assignments, and other such configuration information. |
System administration errors may degrade or stop the affected voice response services. |
Inadequate system resources |
If your IR system is experiencing delays and speech breaks, it may be overloaded. |
Managing IR system performance explains how to check the load on your system and how to reduce load. |
Voice response application errors |
If new applications were recently implemented, or existing applications were revised, there may be problems with the code. Additionally, large, complex voice response applications may affect system resources. |
Modifying voice response applications lists key guidelines for making applications efficient. If you suspect application problems, contact the vendor or internal staff who develop your applications. |
