MiVoice MX-ONE Support - Microsoft Azure

A standard MiVoice MX-ONE system composed by Service Node, Cassandra DB, Media Server, Provisioning Manager and Service Node Manager, which can be deployed in Microsoft Azure on one or several Virtual Machines. The above components can all reside in the same VM or depending on size, traffic and load, can be spread out on more than one VM.

As an example, in larger deployments, it would be recommended to put the Provisioning Manager and/or the Media Server component(s) on separate VMs. It is always recommended to follow the server capacity and deployment guidelines as stated in the MiVoice MX-ONE Dimensioning and Capacity documents in the CPI. The main target for this solution is a centralized system.

For an MX-ONE system to be deployed in Azure, a specific MX-ONE image is required. The MX-ONE image includes SLES 12 SP5.

The figure below shows the high-level architecture of the solution. The MiVoice MX-ONE servers are installed in Azure, while the other Mitel devices/applications such as SIP Phones, SIP clients, Mitel Common Gateways EX and GX and Media Gateway Unit are installed on the customer site (on-premises).

In this setup, the PSTN trunks are terminated in the customer site while SIP trunks might be terminated in Azure.

Secure IP connections in the form of a dedicated network or Azure Express Connect VPN services are always required between the customer site (on-premises) and the customer's MX-ONE environment in Azure Cloud Services. Depending on customer needs and premises, an option with SBC and secure SD-WAN (Software-Defined Networking in a wide area network) over internet should also be considered.