Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: TimPNRHA on March 29, 2017, 06:36:11 PM
-
Good Evening,
I have my primary controller that has 2 dual t1/e1 framers servicing 3 PRI, this controller is expanded and is a part of 19 member cluster. I just purchased a secondary expanded controller for this site for HA and Resilience.
My plan is to take 1 on pri from the first module on the primary controller and move it to the secondary controller, On the primary controller I will have 50 sets configured as with the secondary controller as their failover.
Currently all of my speed dials are set to s/c, I am unable to duplicate the speed dials from the primary controller to the secondary, this is vital as from the CO all 69 channels are have the DID's configured on them in the event of PRI Failure as well I am doing FoIP.
Can someone help me with the configuration required on the secondary controller.
Sorry this is the end of the day and may head hurts so hopefully this makes sense.
Thank you,
-
I guess I am not seeing the issue... why can you not just share the system speed call form and have all your speed calls replicated across both controller? Or the more correct way, why not move them to the DID Translation table and share that form?
We do this in lots of places... why do you think this will be impossible?
-
From MOL
If it is desirable to route the speed call's actual number from each ICP that has the speed call configured, then select "S/C" (SDS will create speed calls on other systems in the cluster).
-
Thank you for the reply's,
To be honest this was one of the forms that we did not Share when we built the cluster, we are currently running 6.0 SP3. Is there a limitation on the on how many speed call records there can be?
-
It's 2,000 by default, I think, although you can change it.
-
Again... DID's in the system speed call table has been depreciated, you should migrate those to the DID Translation Table.
-
Just re-reading the initial post - if you are adding a new controller to the cluster to act as a resilient pair to an existing controller, you shouldn't move a PRI to it, you should put 3 combo cards in the existing controller and patch the 2nd port on the 3 combo cards to the ports in the dual cards that you've moved from the old controller to the new one.