Voice Networking
8.5.1 IP Console Resiliency
Table 46: Troubleshooting IP Console Resiliency
Symptom
Possible Cause Corrective Action
A resilient IP
console is not
functioning (no
dial tone) after
the primary
controller goes out
of service.
IP Console is
not programmed
correctly for
resiliency.
Ensure that the IP console is programmed
for resiliency. Check that the correct
secondary CEID index appears in the
Remote Directory Numbers form for the IP
console. See “IP Console Resiliency” in the
MiVoice Business Resiliency Guidelines
for
details.
After an IP console
fails over to its
secondary ICP,
you can make calls
from it, but other
IP devices in the
cluster cannot call
it.
Call routing
and ARS are
incorrectly
programmed.
Enter the Locate commands (see
controller to determine the status of the IP
console.
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.
Ensure that the correct secondary CEID
index appears in the Remote Directory
Numbers form for the resilient IP console.
Document Version 1.0
Troubleshooting Guide
244
Содержание MiVoice Business 3300 ICP
Страница 1: ...MiVoice Business Troubleshooting Guide Release 9 4 SP1 Document Version 1 0 June 2022 ...
Страница 10: ...Introduction Document Version 1 0 Troubleshooting Guide 4 ...
Страница 45: ...Figure 4 DNS setting on MSL server manager ...
Страница 323: ...Diagnosing Problems Document Version 1 0 317 Troubleshooting Guide ...