Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: Crowtalks on February 28, 2017, 04:02:29 PM

Title: can we cluster MiVoice Office and vMCD
Post by: Crowtalks on February 28, 2017, 04:02:29 PM
One of our sales people is proposing a campus environment across several cities using a Mitel Anyware solution and a single site MiVoice Office 250.

I know you can cluster a 3300 and a 5000 (MiVoice Office and MiVoice Business for the purists), but the sales guy swears we can't cluster a 500 with the virtual MCD product.

I want to know if he is delusional or correct?

Jim
Title: Re: can we cluster MiVoice Office and vMCD
Post by: acejavelin on February 28, 2017, 04:24:46 PM
One of our sales people is proposing a campus environment across several cities using a Mitel Anyware solution and a single site MiVoice Office 250.

I know you can cluster a 3300 and a 5000 (MiVoice Office and MiVoice Business for the purists), but the sales guy swears we can't cluster a 500 with the virtual MCD product.

I want to know if he is delusional or correct?

Jim
Your sales guy is correct... they are two completely different systems, you might as well try clustering a 3300 with an Avaya IP office, basically saying you can't.

What you can do is have them talk to each other via SIP, you will need SIP trunking licenses on both systems and there is a document on doing it on Mitel Online. They don't share any data or information, but you can get calling between the systems to work.
Title: Re: can we cluster MiVoice Office and vMCD
Post by: Crowtalks on March 01, 2017, 08:48:34 AM
Thanks, what would the doc be called, or something close where I can find it on Edocs

Thanks, Jim
Title: Re: can we cluster MiVoice Office and vMCD
Post by: sarond on March 01, 2017, 09:14:37 AM
There is a how-to on KMS. (Mitel Connect - Knowledge Management System)
Doc number: HT1144 (Programming SIP Trunks Between 5000 & 3300)
Title: Re: can we cluster MiVoice Office and vMCD
Post by: Crowtalks on March 01, 2017, 01:38:30 PM
Thanks heaps!

Jim