Troubleshooting guide

Troubleshooting Guide
156
While on a call at a
resilient phone, the
primary ICP goes out of
service, and the call is
immediately dropped
(no call survival). After
you hang up the IP
phone and go off-hook
again, the IP phone
remains out of service.
Network failure (for
example a Layer 2 switch
that connects the IP phone
to both the primary and
secondary ICPs goes
down).
Program redundancy into the network layer.
After an IP phone fails
over to its secondary
ICP, you can make
calls from it, but other
TDM phones, trunks, or
IP devices in the cluster
cannot call it.
Call routing is not set up
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
instructions on the following tasks:
1. Ensure that each element in the cluster is assigned a
unique CEID in its Cluster Elements form.
2. Ensure that ARS is programmed correctly to route
calls to all the other elements in the cluster.
3. In the Cluster Elements form ensure that you have
programmed the Feature DN fields correctly.
4. 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.
5. Check that the correct secondary CEID index
appears in the Remote Directory Numbers form for
each resilient IP phone.
6. If an SX-2000 system is in the call path, ensure that
the system has LW 32 Release 1.1 or later software.
Table 52: Troubleshooting IP Device Resiliency (continued)
Symptom Possible Cause Corrective Action
Page 4 of 6