MiVoice Office Application Suite - Technical Manual
Device Configuration
Device ConfigurationOnce the PBX configuration has been configured the devices will be automatically imported. It is not required to manually maintain the list of devices, this will be done automatically via the OAI connection to the PBX.
The list of devices imported into the system can be seen from the Site Settings -> Phone Systems -> PBX section. Clicking on the Import button under the Devices section will force an import, or additional devices can be manually added if required.
If the MCS is connected to a CT Gateway it will import devices from all nodes the CT gateway is connected to. The MCS will also download details about the nodes themselves, the node details can be configured from the Nodes section, see the Node Configuration section for more details.
Connecting the MCS to a CT Gateway will have an impact on the licenses required to run the system. Please refer to the License Overview section for more information.
When the MCS imports information about all the devices on the telephone system, it imports the device number, description and type. This information is kept up to date by default so there is no need to edit it manually except for the following two types:
DDI numbers cannot be automatically imported from the telephone system. If required, they can be manually added here and kept up to date. Any DDI numbers added here can then be used in other parts of the application.
If a Hot Desk user is logged in when MCS starts up, the MCS will not know the device in question is a Hot Desk device until it first logs out. To manually update the database, find the device under the PBXs section and select 'Edit' Select 'Phantom' from the 'Device Type' drop down and then check the 'Hot desk device' checkbox.
Once the system knows a device is a Hot Desk device it will present the user with a Hot Desk login/logout toggle within Phone Manager.
This property is used in conjunction with the MiVoice Office Call Recorder features when using the IP/SIP Extension recording source. To match the audio on the network to a device on the telephone system, the MCS needs to know either the MAC address or IP Address of the extension.
Each device the MCS has imported provides an option for disabling the monitoring of events. This option should not be used unless instructed by a Mitel engineer. This option cannot be used to avoid Call Logging licenses and will cause problems with the call modeling if used.
This option is only visible when the device is a SIP device (and has not already been configured as a 6900 handset/SIP Hot Desk). This option should be enabled if the device connecting as this extension is a Mitel DECT/Wireless phone (612/622/632/650/5603/5604/5607/5610/5624) or a 3rd Party SIP Extension/Softphone. This will instruct Phone Manager not to start as a softphone and instead provide control (limited on SIP) over the phone.
The details entered on this tab are essential for the operation of Phone Manager Softphones (both Desktop and Mobile) and the 6900 handsets. The MCS passes these credentials to the softphones and 6900 handsets so that they can successfully register as SIP devices with the telephone system.
These credentials are used by handsets/softphones connecting from the local network to the telephone system. They will also be used by remote handsets/softphones if the 'User remote authorization credentials' option is not checked. When using a MiVoice Border Gateway, the internal authorization name must match the extension number of the phone otherwise authentication with the telephone system will fail.
If the 'User remote authorization credentials' option is checked, these credentials will be used for remote sofpthones/69xx handsets when registering with the MiVoice Border Gateway. By default, when the 'Use remote authorization credentials' option is enabled, the name and password fields will be pre-configured with random complex entries.
If the Rest API for the MiVoice Border Gateway has been configured, enabling 'Use remote authorization credentials' against a SIP extension will cause the MCS to provision the SIP extension as a teleworker on the MBG. For more information, please refer to the Remote Connections engineering guidelines.
If using port forwarding, this option does not need to be enabled.
The MCS system can model calls differently depending on the device type. The following three options are available to alter how the calls are modeled:
Enabling this setting will reset any call timers associated with a call that rings the hunt group. This provides a way to reset real-time statistics so that any time spent in call routing announcements can be ignored. Depending on the system-wide setting 'Reset Call timers Only Once per Call', a call's timers will either be reset every time it starts ringing at a hunt group or only the first time it rings at a hunt group.
Enabling this setting will cause any calls that are answered by this device to be treated as NOT answered. This should always be set for devices such as CRAs which play queuing announcements to calls waiting at a hunt group. This prevents calls showing as answered to a CRA when still ringing at the group.
Calls will not be segmented at this device (unless it is the first segment of a call). All call time associated with the segment will be recorded against the call's previous segment.