Tips, tricks and support
The following is a list of best practices recommended for CloudLink site deployments:
If there is no DHCP server on site, configure a MiVoice Office PBX or use another DHCP server.
For standalone platforms, the CloudLink Gateway appliance and MiVoice Office PBX should be installed on the same LAN subnet. If this is not done, disable all SIP ALG functions in the firewall to enable communication between these two components. Additionally, ensure that port blocking is disabled.
When you configure a firewall, ensure that the path to the Internet is open before you set the site rules.
For remote access management, separate the data networks from the voice networks.
Ensure that your end-user mobile carrier supports propagation of incoming caller ID.
To ensure that the Welcome/Deployment emails do not get rejected by the mailbox, you must include the *.mitel.io alias in the user's e-mail whitelist.
Ensure that the user database in the MiVoice Office PBX is updated accurately and Hunt Groups (MiVO250) or User Groups (MiVO400) are labeled with informative names to enable importing contacts into CloudLink applications such as OfficeLink.
When configuring users in a MiVoice Office 250 PBX, ensure that you disable (set to "Off") the "Enable Human-Answer-Supervision" option to improve the customer experience for CloudLink applications such as Mitel OfficeLink and Mitel MiVoice Office.
CloudLink solution supports the following emergency numbers: 110, 112, 118 119, 911, and 999, which are specific to each supported country. To ensure that there are no dialing conflicts, the administrator must configure these emergency numbers in MiVoice Office PBX (MiVO250 or MiVO400).
CloudLink site deployments must be secured with a firewall configured by hostname before they are deployed on a network. See the following Mitel KMS articles related to Network Security and Toll Fraud prevention for the Mitel Office PBX installations.
For a list of ports that must be opened in the firewall configured for CloudLink deployments and the purpose these ports serve, see Port Information.