System Data Synchronization - Mitel MiVoice Business 3300 ICP Troubleshooting Manual

Symptoms
When the primary
controller is out of service,
the T1/E1 trunks are
not transferred to the
secondary controller. No
alarms are generated.
The primary controller
fails over to the secondary
but users are unable to
make calls through the
resilient T1/E1 MMC in
the secondary controller.
When the user attempts to
make an outgoing call, the
system is unable to seize
the T1/E1 trunk.

8.6 System Data Synchronization

Sharing Operations
Document Version 1.0
Troubleshooting Guide
Possible Cause
Both links are designated
as secondary controller
: In the Digital Link
Assignment forms of both
controllers, the "Primary
System Name" is set to
the name of the other
controller. Both controllers
have their own system
name selected as the
"Secondary System
Name".
Route List Assignment
form is programmed
incorrectly. The route list
programming on either
the primary or secondary
controller is reversed.
Voice Networking
Corrective Action
Correct the T1/E1 trunk
resiliency programming in
the Digital Link Assignment
forms of both systems.
Refer to.the MiVoice
Business Resiliency
Guidelines for T1/E1 trunk
resiliency programming.
Correct the route list
programming. Refer to
the MiVoice Business
Resiliency Guidelines for
T1/E1 trunk resiliency
programming.
248