Mitel MiVoice Business 3300 ICP, Руководство по устранению неисправностей

Страница: 253 / 366

Voice Networking
Table 48: Troubleshooting T1/E1 Trunk Resiliency
Symptoms Possible Cause Corrective Action
Users cannot make T1/E1
calls through T1/E1 MMC
modules in the primary or
secondary controllers.
Links are connected
in reverse:
You have
programmed T1/E1 trunk
resiliency correctly, but the
physical connections are
reversed. The Input port on
the secondary controller
is connected to the PSTN
and the Failover port on
the secondary is connected
to the main port on the
primary.
Reverse the connections.
See “Configuring T1/
E1 Trunk Resiliency” in
the MiVoice Business
Resiliency Guidelines
for a
configuration diagram.
The physical connections
are correct and the primary
controller is out of service,
but users cannot make T1/
E1 calls through the T1/
E1 MMC on the secondary
controller.
Secondary is not
programmed as resilient :
In the Digital Links form of
the secondary controller,
the Resiliency Link box
is not checked, or you
have not programmed the
“Primary System Name”
and “Secondary System
Name”.
The physical connections
are correct. However,
alarms for the Trunk Alarm
category on the secondary
controller are exceeding
the threshold limit. In
addition, if the primary
controller is out of service,
users cannot make T1/
E1 calls through the T1/
E1 MMC on the secondary
controller.
Both links are designated
as primary controller : In
the Digital Link Assignment
forms of both controllers,
the “Primary System
Name” is set to the name
of the Local controller.
In the Digital Links form of
the secondary controller:
• Select the T1/E1 link
and click Change .
Check the “Resilient
Link” box.
• From the Resilient Link
ID drop-down menu,
select a link identifier (1
to 4) for the secondary
link. This link ID must
match with the link ID
that you assigned to the
primary link.
• Set the Primary System
Name to the system
name of the primary
controller.
• Set the “Secondary
System Name” to the
name of the secondary
(Local) controller.
Document Version 1.0
247 Troubleshooting Guide