Troubleshooting guide

Voice Networking
153
Resiliency
IP Device Resiliency
Table 52: Troubleshooting IP Device Resiliency
Symptom Possible Cause Corrective Action
All resilient devices are
not functioning (no dial
tone) after the primary
ICP goes out of service.
Secondary ICP is not in
service.
Ensure that the secondary ICP is operating.
IP phones are not
provisioned as resilient.
Enter the Locate commands on the secondary ICP to
determine the status of the IP phone.
Check that the correct secondary CEID index appears in
the Remote Directory Numbers form for each resilient IP
phone. If not, provision the IP phones for resiliency,
using the System Administration Tool. Refer to the
System Administration Tool Online help.
Cluster is not programmed
correctly.
Enter the Locate commands (see “Locating Resilient
Devices” on page 211) on the secondary controller to
determine the status of the IP Phone.
Refer to Voice Networking -> Configure Network in
the System Administration Tool Online Help for
procedures
on the following tasks:
1. Ensure that the optional software required for
clustering is enabled at each element.
2. Ensure that each resilient IP device is connected to a
controller that has Release 4.0 or later.
3. Ensure that each element in the cluster is assigned a
unique CEID in its Cluster Elements form.
4. Ensure that ARS is programmed correctly to route
calls to all the other elements in the cluster.
5. In the Cluster Elements form ensure that you have
programmed the Feature DN fields.
6. In the ICP/PBX Networking form of each element,
ensure that the PBX Number matches the CEID index
number that is programmed in the Cluster Elements
form.
7. Check that the correct secondary CEID index
appears in the Remote Directory Numbers form for
each resilient IP phone.
Page 1 of 6