MiVoice Border Gateways

If there are any MiVoice Border Gateways configured to support teleworker extensions on the telephone system, the MiVoice Office Application Suite needs to know about their internal IP Addresses.

The MiVoice Border Gateways have an effect on two aspects of MiVoice Office Application Suite operation:

IP Extension call recording -> The internal address of the MiVoice Border Gateway is required so that system can correctly self-learn the IP addresses of IP Extensions and can filter out the duplicated traffic from the internal address of the gateway.
6900 Handsets -> The internal address of the gateway is used to identify when a 6900 handset is local to the system or remote.

Enter all internal addresses that are necessary. There may be more than one if there is more than one MiVoice Border Gateway or it has more than one internal address.

Rest API

MiVoice Office Application Suite supports the MiVoice Border Gateway's API for provisioning. This allows the MCS server to automatically provision SIP Users on the MBG to simplify the deployment of Teleworkers using:

6900 Phones
Phone Manager Desktop Softphone
Phone Manager Mobile Softphone

The settings for enabling and using the MBG's Rest API are listed below. For information on how the teleworker deployment works and how to enable the API on the MBG, please refer to the Remote Connections engineering guidelines.

The MiVoice Office Application Suite supports the Rest API for one MBG only. If more than one IP address is configured for MBGs, the first address will be used for Rest API access.

Teleworker licenses on the MiVoice Border Gateway are required for each SIP User provisioned.

Enable Rest API

This setting controls the MCS server's interaction with the MiVoice Border Gateway (MBG). When enabled, the MCS will actively add/delete/update SIP Users on the MBG.

Once the Rest API has been enabled and configured, MiVoice Office Application Suite will be able to provision all SIP Users on the MBG. Any SIP Users that are configured on the MBG for uses other than 6900 or Phone Manager Softphones will still need to be configured on the MiVoice Office Application Suite.

Name / Consumer ID / Shared Secret

These settings are required by the MCS to communicate with the MBG. They must match those configured on the MBG in order for the MCS to be able to request API access.

For information on configuring the API link to the MBG, please refer to the Remote/Teleworker Connections engineering guidelines.

Request Access Token

This process can be used to setup the connection between the MCS and the MBG so that the MCS can automatically provision teleworker phones.

For information on configuring the API link to the MBG, please refer to the Remote/Teleworker Connections engineering guidelines.

Provisioning Teleworker Phones

This process can be used to provision (or un-provision) any SIP phones as Teleworkers on the MBG. Pressing the button will display the SIP phone device picker which will show which phones have already been provisioned on the MBG and which phones have not.