System Capacities
- The solution currently supports a virtual (VMWare or Azure) or SMB Controller deployment that includes MiVoice Border Gateway paired with a CloudLink Gateway.
If the MiVoice Business system is using a Mitel self-signed certificate, then no certificate is required to be uploaded in the Mitel Administration Portal at the time of onboarding.
Support for up to 2500 users and 5000 devices on a standalone or resilient virtual MiVoice Business deployment. This implies a maximum of 2500 users with 2 devices, or 1666 users with 3 devices, and so on.
(For SMBC only). Support for 150 UC users on a standalone or resilient MiVoice Business deployment. The UC user supports from 1 to 3 devices plus one hot-desk number, allowing up to 450 registered devices.
- The CloudLink Gateway should only be configured with a standalone MiVoice Business deployment or a single/resilient pair within a MiVoice Business cluster.Note: Users on other MiVoice Business platforms are not onboarded by CloudLink.
- Single MBG or clustered MBGs
- A single MBG is required to communicate with CloudLink Gateway. The MBG will continue to support the same feature set it does today for SIP trunking and PBX devices. If the customer deployment is small enough and MBG resiliency not required, the solution might be deployed using one MBG.
The resources required to deploy CloudLink Gateway on MBG depend on the MBG resources required for MBG functionality (that is, Teleworker devices, SIP trunking, call recording, and so on.) and an additional 1 GB of RAM and 1 vCPU for the CloudLink Gateway.
Additional MBGs can be deployed, each on a different virtual machine, and clustered to provide resiliency and scaling for non-CloudLink devices. But the additional MBGs will not communicate with the CloudLink Gateway. The CloudLink Gateway will communicate only with the MSL\MBG it is deployed on.
- MiCollab is not required to be part of the solution, but it is expected to be present in most cases because of MiCollab still being the primary UC application.Note: MiCollab has an embedded MBG. MBG running on MiCollab and the MBG running CloudLink Gateway must be running the same version. See the MiCollab and/or MBG training material or documentation for details.
- The CloudLink solution is primarily an enabler for development of third-party CTI applications on the CloudLink Platform. CloudLink APIs support:
- Call, Answer, Clear/Release, Hold/Retrieve, Consultation Hold, and Transfer
- Call History
- Basic Voice Mail (currently, no support for Visual Voice Mail). Message Waiting Indicator and click-to-call voice mail (to retrieve messages). Support includes EMEM, NuPoint Messaging, and MiCollab Advanced Messaging (MiCAM).
- Engineering guidelines such as the number of users supported is provided in the documentation. As enhancements are expected to Mitel PBX/CloudLink solutions, check the Mitel Documentation Center and Release Notes for new updates.
- For a user to be successfully imported from MiVoice Business into CloudLink, the following user details are required:
- Email Address
- Extension Number
- First or Last Name
As a high-level recommendation for Administrators, observe the following guidelines for MiVB, MiCollab, and MBG:
- Administrators should be familiar with MiVB and MBG (recommend
MiVB and MBG training certification) before making any changes to
the MiVB or MBG. Mitel Product Support assists only technicians
who are certified on the product/solution.Note: If MiCollab is part of the solution, it is recommended that the Administrators of the solution be certified on MiCollab.
- It is assumed that the MiVoice Business is already set up for the users, along with the required call flows, before the CloudLink Gateway is installed and configured.
- This document does not include information on CloudLink Applications and does not focus on CloudLink Onboarding. After an Administrator has successfully integrated a CloudLink Application to the Customer Account on CloudLink and applied services to the users, this service might require users to have a license in CloudLink. This information is available in the CloudLink Application training or documentation.
- Connectivity (SIP Trunk) between the MiVoice Business and MBG, and a SIP Trunk between MBG and the CloudLink Platform will automatically be set up from CloudLink during the synchronization step discussed in the next section. As indicated in the System Requirements section, licenses for connections to CloudLink do not need to pre-exist.
- CloudLink recognizes a user on MiVoice Business only if the user has valid Email Address, Last Name, and Directory Number. If any of these values are not present, the user will not be onboarded.
- CloudLink will onboard only CloudLink Services and it is not responsible for the configuration of other user services or endpoints (that is, MiNet or SIP sets or EHDUs).
- .For initial onboarding of CloudLink Gateway connections to the CloudLink Platform, Administrators of the CloudLink Gateway on MSL must use the CloudLink Portal button to connect to the CloudLink Platform and complete CloudLink Gateway Integrations.