Diagnosing Problems
1.
Press and hold down the volume up and volume down keys.
2.
Dial
33284
.
3.
Release the volume up and volume down keys.
4.
Select
Network
.
5.
Select
ICP Server IP(s)
.
Select
Current ICP Server
to display the IP address of the current ICP controller.
10.15 Checking T1/E1 Resiliency Alarms
Trunk Alarms
If the primary controller is supporting the resilient trunks, the resilient trunks are recorded
in the Trunks category of the Alarm command output. During a failover from the primary
to secondary controller, the failover of the T1/E1 trunks will generate an alarm on the
primary controller if the programmed trunk alarm threshold is exceeded. After the trunks
fail back to the primary, the system checks the trunk alarm category to determine if the
alarm threshold is still exceeded. If the trunks are operating normally on the primary, and
the alarm threshold is no longer exceeded, then the system clear the trunk alarm.
During normal operation, resilient trunks that are supported by the T1/E1 Combo MMC
in the primary controller are “Not Seizable” on the secondary controller. These “Not
Seizable” trunks do not generate alarms on the secondary controller. Instead, the
secondary controller includes the resilient trunks in the system total of the “Inactive
Trunks” alarm category.
After a failover, the secondary controller controls the resilient trunks. The resilient trunks
are temporarily listed in the “Trunk” alarm category of the secondary controller. After the
resilient trunks fail back to the primary controller, the trunks reappear in the “Inactive
Trunk” alarm category of the secondary controller.
Digital Link Alarms
On the primary controller, digital links that are associated with resilient trunks generate
alarms if the links are not in a healthy state. On the secondary controller, the digital links
for resilient trunks are included in the system total of the “Digital Links” alarm category.
Netsync Alarms
You can program a resilient trunk on the primary controller as a netsync source.
However, do not program a resilient trunk on the secondary controller as netsync source
because the system will generate a minor netsync alarm.
Document Version 1.0
329
Troubleshooting Guide
Summary of Contents for MiVoice Business 3300 ICP
Page 1: ...MiVoice Business Troubleshooting Guide Release 9 4 SP1 Document Version 1 0 June 2022 ...
Page 10: ...Introduction Document Version 1 0 Troubleshooting Guide 4 ...
Page 45: ...Figure 4 DNS setting on MSL server manager ...
Page 323: ...Diagnosing Problems Document Version 1 0 317 Troubleshooting Guide ...