Integration

The following example shows MBG and CloudLink Gateway on a Virtual Machine with MSL. Azure will incorporate the MSL, MBG, CLGW and MiVB on a Virtual Machine but otherwise the description/information is consistent.
Figure 1. MiVoice Business with CloudLink Integration

MiVoice Business with CloudLink Integration is an attempt to simplify the architecture of this solution in a way that MiVoice Business Partners and customers can understand.

The CloudLink Solution is divided into four primary components:
  • The PBX (for example; MiVoice Business)
  • A Virtual Machine with CloudLink Gateway and MiVoice Border Gateway
    • CloudLink Gateway and MiVoice Border Gateway are both blades available for installation from Mitel Standard Linux.
    • Virtual Machine with VMware or Azure is supported.
  • CloudLink Platform
  • CloudLink Applications (Mitel or developed by third-party

For the CloudLink Platform to fully interwork with Mitel PBXs (that is, MiVoice Business), it requires Mitel's Border Gateway and the Mitel's CloudLink Gateway. The MiVoice Border Gateway and CloudLink Gateway are both deployed on the same Virtual Machine.

In Figure 1, you will find arrows indicating interface connections. The following will explain each interface:

Interface 1 (Between CloudLink Application and CloudLink Platform)

The CloudLink Platform provides Third-Party Developers with APIs to develop their own CloudLink applications. CloudLink provides APIs to help develop Telephony, Messaging and Administrative applications to interwork with MiVoice Business solution. More details can be found on Mitel’s Developer Portal.
Note: It is possible that Mitel will provide an application using the same APIs. An example is Mitel One for the MiVoice Office 400.

Interface 2 (Between CloudLink Platform and CloudLink Gateway)

The CloudLink Platform interworks with the CloudLink Gateway to use the Telephony, CTI and Database APIs provided by the MiVoice Business. The main role of the CloudLink Gateway is to provide a common and standardized set of APIs to the CloudLink Platform so that the CloudLink Platform requires minimal knowledge of the intricacies of the Mitel PBXs it supports.

Interface 3 (Between MiVoice Border Gateway and CloudLink Platform)

The CloudLink Platforms interworks with the MiVoice Border Gateway to provide SIP Trunking for CloudLink applications (not currently used in Mitel CloudLink APIs). In the CloudLink or MiVoice Business solution, the MiVoice Border Gateway supports all of its current functionality in addition to supporting the CloudLink Platform and CloudLink Gateway.

Interface 4 (Between CloudLink Gateway and MiVoice Border Gateway)

The MiVoice Border Gateway provides APIs to the CloudLink Gateway to allow CloudLink to automatically provision the MiVoice Border Gateway during the configuration process (CloudLink Gateway Configuration), which includes the configuration of SIP Trunking.

Note:

MiVoice Border Gateway is typically used for Softphone functionality. CloudLink applications that do not include Softphone/Telephony services might not require MiVoice Border Gateway.

Interface 5 (Between CloudLink Gateway and MiVoice Business)

The CloudLink Gateway accesses existing CTI and Database interfaces on the MiVoice Business. From the MiVoice Business perspective, the CloudLink Gateway just looks like any other application that uses similar interfaces, such as MiCollab or OIG. Similar to Interface 4, the MiVoice Business is automatically configured to work with the CloudLink solution once the solution is deployed and the customer is CloudLink onboarded.

Interface 6 (Between MiVoice Business and MiVoice Border Gateway)

As mentioned earlier, the MiVoice Border Gateway and MiVoice Business interwork to support SIP Trunking integration with CloudLink.