Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Third 3300 MXe Resiliency

Status
Not open for further replies.

alaanajim

Technical User
Aug 3, 2007
55
BH
Hi All,

One of our customers have 2 Mitel controllers, first works as the primary for all call processing and the secondary is working as backup resilient to the primary in case of primary controller failure.

They are planning to have 3rd system as disaster recovery system located at different location.

My question will it be possible to have the third controller as resilient? As per the following scenario. Primary fails and the IP phones fail-over to the secondary controller. The secondary controller fails and the IP phones fail-over to the third controller.

As I can see from the device configuration in OPS MGR or Embedded resilient in MCD 4.1 that there are 2 options Home Element and Secondary Element, there is no third option to select the third resilient controller. Any input that might help.
 
And if third controller fails, then failover to forth then to fifth and then to the Moon. I don't think that it is possible with current software. If they really need to have it, I would make the disaster recovery system the secondary controller. The controller on site can be a cold standby system. If primary controller fails, all the phones will reconnect to remote location and in the mean time you can manually activate the spare system, just make backups every day and restore them to the second controller. It is important to keep it in a separate VLAN or LAN and assign the same IP address as the primary system. The recovery time will be no more then required to move an ethernet cable and external trunks connectors.
 
I have a couple of customers who have the exact setup that you are proposing.
The disaster recovery system is clustered but is seperated in a different building with it's own ISDN trunks and phones.
The way I have set them up is as follows

Main site all phones are hotdesk users (both ACD and desktop) with resiliency to secondary controller with PRI trunk failover.

Disaster recovery site is live and ready to take users at any time, if in the event of a disaster the users can simply go to site and login as a hotdesk user and start taking calls.
The ISDN DDI range at the main site has been mapped to the DDI range at the disaster recovery site. All the main site has to to is invoke the the diversion.
ACD Paths have been setup for hotdesk ACD agents.

One thing I suggest is that you spend some time once programmed to invoke the disaster recovery, that way you can test all scenarios and make changes as needed.



Share what you know - Learn what you don't
 
I think R5 or something will have the ability to make a phone resilient to more then one controller. Otherwise use the method Supernova99 suggests.

The single biggest problem with communications is the illusion that it has taken place.
 
Thanks Guys for the great info. Otherwise I will be in a loop.
 
The only problem is that typicaly when you need to kick in the disaster recovery facility, then the main site is expected to be hard down, so diversion will not work. SIP trunking can give some flexibilty, when calls are re-routed at carrier level.
 
No I have tested it that scenario
As the ISDN lines have been diverted to the DR site then calls will be answered there.
All users login to Hotdesk phones in DR if the Primary site is still working it just logs them out.

You are correct about SIP Trunks, and going forward this is how everyone will provide voice lines as the increased flexibility with geographic numbers being presented and available wherever they are programmed.
So having your main office in one city and your DR hosted in another city will provide a very flexible solution

Share what you know - Learn what you don't
 
interesting topic as I will have a similar setup:
Scenario is main site primary controller
Resillient controller is located a different location

if the primary fails, then failover occurs, no problem
What if the building burns down?

I'm guessing like supernova suggested.
main site all hotdesks. DR site in case building burns down with all the phones in it, will have it's own set of phones also connected to main site controller.
So if primary fails and building burns down one could move staff to secondary facility and these phones will have failed over to resilient controller?

Hope I make sense here ;)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top