Communication Server - Technical Manual
Mitel MiVoice Office 400 Requirements
The system can connect to a Mitel MiVoice 250 telephone system. Follow the procedures below to provide the required information for a successful implementation.
The following Mitel MiVoice Office 400 versions are currently supported:
The following recording devices are supported:
The following MiVoice Office 400 Configurations are supported:
An SMDR call logging connection is the only currently support method of integration with the MiVoice Office 400 system.
Follow the steps below to enable the SMDR configuration between the Xarios Call Recorder and the telephone system.
Call logging needs to be enabled on the MiVO 400 controller. This will mean that after every call made, the telephone system will connect to the call recorder to supply SMDR call information.
To enable Call Logging, browse to the MiVoice Office 400 administration web interface and enable 'Expert Mode'.
Navigate to the 'Charges -> General' section from the settings tree.
Locate the 'Call Logging' section and enable the following settings:
Press the 'Apply' button at the top of the screen to save the settings.
In the previous section, the MIVO 400 was configured to send the call recorder SMDR call information. By default, it will only do this for outgoing calls. Follow the steps below to ensure that call data is provided for all users and for incoming calls.
Navigate to the 'Configuration -> Users -> User List' section.
Click on each user in turn and check that the 'Journal' option is enabled. This setting can be found within the 'Other Settings -> Charging' section and is enabled by default.
Once all users have been checked, navigate to the 'Configuration -> Routing -> List View -> Call distribution' section.
Click on each call distribution rule in turn and check that the 'Enable ICL data' is checked. This can be found in the 'Settings -> Call logging and call limitation' section.
The call logging configuration is now complete. The process above can be repeated on each controller if there is more than one controller in the cluster.
If the SMDR connection does not seem to be working correctly (the recorder is working but calls are not being tagged correctly), follow the steps below to identify the issue.
Check these services to ensure that the XCS SMDR Service is running.
If there are any firewalls installed, check that port 1080 has been opened for incoming connections.
If the IP address of the call recorder has been entered into the Call Logging configuration on the MiVoice Office 400, check that the call recorder's IP address is static and has not changed.
If all the configuration seems correct, use Wireshark to monitor traffic on port 1080 to see whether the MiVoice Office 400 is pushing the SMDR data to the call recorder. If it is, the problem will either be a firewall or the XCS SMDR Service not running. If it is not, the Call Logging/Journal configuration on the MiVoice Office 400 will be incorrect.
Configure the Mirror port as described here: Mirror Ports
Configure the Packet Filters as described here: Packet Filters
Configure the IP addresses as described here: Addresses
When using SIP trunks where calls match CLI and DDI in the same second, it may not be possible to get 100% match success rate
The system relies on the device information configured on the recorder and on the Mitel MiVoice Office 250 system to be kept up to date. Without this calls may not be recorded or tagged with the correct information.
Any programming changes that are made to any of the Mitel MiVoice Office 250 nodes will be picked up automatically and no manual changes are required unless they are to do with the trunk numbering and then this needs to be manually updated.