Troubleshooting Guidelines
Table
Condition |
| Cause/Resolution |
The telephone had been | AND the telephone was | CAUSE: Loss of communication with the |
working, but does not | recently moved. | PBX. |
work now, (continued) |
| RESOLUTION: As above, but pay |
|
| |
|
| particular attention to the possibility that |
|
| the telephone is being routed to a |
|
| different DHCP server, or even a |
|
| different PBX switch. If so, the new |
|
| server or switch may need to be |
|
| administered to support the telephone. |
|
|
|
The telephone works, but the audio quality is poor, specifically:
the network was recently changed (servers upgraded or replaced, your DEFINITY/MultiVantage switches, etc.).
the user hears echo when speaking on a handset.
the user hears echo on a headset, but not on a handset.
the user is on speakerphone and hears no echo, but the far end hears echo.
CAUSE: Loss of communication with the PBX.
RESOLUTION: As above.
CAUSE: Echo from
RESOLUTION: Verify which trunk is causing the echo, and swap the trunk’s Trunk Termination parameter on the PBX.
CAUSE: Improper headset adapter.
RESOLUTION: Replace adapter with Avaya’s M12LU or
CAUSE: Room acoustics
RESOLUTION: Ensure there are six inches or so of blank space to the right of the telephone. If that is insufficient, use the handset.
Error Conditions