Register MiVoice Border Gateway

There are several pre-configurations that must be performed on the MiVoice Border Gateway (MBG) before it can be provisioned by Management Portal. It is important to read the Management Portal Engineering Guidelines first, before registering an MBG in Management Portal. If the network configuration includes a MiVoice Border Gateway (MBG) Cluster, it must be registered with the portal so that it can be assigned to a Platform Group. For proper registration, the MBG must exist and be reachable from Management Portal.

When registering an MBG, it must be based on the device types that are allowed to be programmed on the particular MBG:

  • MiNet MBG

  • SIP MBG

  • MiCollab Client

Each Site can select an MBG for each device type and can allow 1 MiNet, 1 SIP, and 1 MiCollab Client device type, while each Platform Group can have multiple Sites with different combinations of MiNet, SIP, and MiCollab Client device MBGs.

PC MiNet Softphone phone types are programmed on the MiCollab Client device MBG; however, Management Portal does not allow a cluster zone to be specified.

DIDs can be assigned against one (or none) of a number of multiple MBG Clusters. For each DID range, an MBG Cluster and SIP Trunk can be selected.

DID Services can be assigned to a MiVoice Business platform or a MiVoice Border Gateway. DIDs are required in both the MBG SIP Trunks and MiVoice Business. The MBG needs DIDs to determine which MiVoice Business gets the call and the MiVoice Business needs them for DID Services.

Embedded MiVoice Border Gateway

Certain Platform Groups have an MBG embedded within that platform. The following platform types contain an Embedded MBG:

  • MiCollab

  • MiVoice Business Express

The Embedded MBG is categorized as follows, based on the type of device that can be programmed on it:

  • MiNet Devices

  • SIP Devices

  • SIP Trunking (Routing Rules)

When creating a Site or registering a DID range for a MiCollab or MiCollab with Voice platform group, the Embedded MBG is included in the list of MBG Clusters, if it was registered. An Embedded MBG appears in the platform list to which it belongs.

When a user is created and assigned to a Site with an Embedded MBG, then the device is programmed on the Embedded MBG, if the Embedded MBG is assigned to the device type that was assigned to the user.

When a Hot Desk device is created and assigned to a Site with an Embedded MBG as the MiNet Device MBG, then the device will be programmed on the Embedded MBG.

When DIDs are registered for a MiCollab or MiCollab with Voice Platform Group, if the Embedded MBG is specified as the MBG, then the routing rules for those DIDs are programmed on the Embedded MBG. If another MBG cluster is specified, then the routing rules for those DIDs are programmed on that MBG.

If a MiCollab or MiCollab with Voice Platform type is not in use, you can delete it (it will also delete the Embedded MBG).

It is possible to register the same MBG twice by mistake, once with the IP address, and once with a Fully Qualified Domain Name (FQDN). Management Portal does not detect that the IP addresses are the same MBG. This does not cause any issues in Management Portal (other than it being treated as two separate MBGs) but may confuse the administrator. It is recommended that MBGs be registered in a consistent manner.

Ensure that Web Services have been enabled on the configured standalone MBG. Otherwise, communication between the MBG and Management Portal will fail.

To register an MBG Cluster and assign it to a Platform Group:

Registering an MBG cluster configures the DNS Server record on the DNS server to provide the MBG FQDN to the MBG cluster member hostname mapping.

  1. From the Platforms tab, click the MiVoice Border Gateways tab.

  2. Click Register MiVoice Border Gateway Cluster.

    If you register an MBG Cluster after adding users, the changes that you make to the Public Facing FQDNs are not updated in the MiCollab Client User Settings. To update the settings and send users the updated MBG information (SIP username, SIP password, and external FQDN), resend the Welcome email.

  3. Enter details and then click Submit.

Make sure you enter the MSL Username and Password in the appropriated fields when registering the MBG. Otherwise, the registration will fail.

Re-enter the MSL Username and Password credentials when doing edit operations (such as when editing a Platform Group).