Mitel Configuration

Mitel SRC Certificate Management

Launch the Mitel Standard Linux Server Manager application by using the following URL: http://[address]/servermanager, where [address] is the IP address of the Mitel SRC server.
After logging into the Server Manager, click the Certificate Management option from the Security menu. The Manage Certificates page displays.
The Subject of the certificate request will be "CN=QMS.<server name>", where <server name> is the NetBIOS name of the QMS server. Click the Certificate ID link in the Queued CSRs section. The certificate appears in a new window with the Cancel, Reject, and Approve buttons.
Click Approve to accept the certificate. The success message displays.
After a few seconds, depending on network traffic and server loads, the Call Recording Service should receive the certificate download and move to the "Running" state. QMS is now operational.

Mitel SRC Licensing Considerations for QMS High-Availability

Under a QMS High-Availability configuration, two or more servers running the QMS Call Recording Service will communicate with the Mitel SRC server to get the audio streams for recording a call. In order to get the recording streams for a call, a QMS Call Recording Service must open a tap on the Mitel SRC server for the agent and call. Each tap requires a Mitel tap license. In a QMS High-Availability environment, therefore, two Mitel tap licenses will need to be available to record the agent, one tap license for each QMS Call Recording Service. If both QMS Call Recording servers are connecting to one Mitel SRC server or SRC server pool, that single SRC server or pool will need to contain enough Mitel tap licenses to cover two tap licenses per recorded agent. If two stand-alone Mitel SRC servers are being used, each SRC server will need to contain enough tap licenses to allocate one license per recorded agent.

Configuring the SSL Tunnel Manually

Integration of Quality Management Suite through SRC is created by a tunnel between the Quality Management Suite Server and the Mitel SRC. When tunnel is created, there is a certificate that needs to be accepted for a persistent TCP connection.

To set up the SSL Tunnel, complete the following steps.

Download MiSslTunnelServer.exe from http://telrexsupport.com/builds/MiSslTunnelServer.exe
Copy the exe file to the Quality Management Studio installation directory.
Open a command prompt.
Run the following command with the IP address of the Mitel SRC server (the IP address is 192.168.2.129 in this example):

MiSslTunnelServer -f missltunnel.ini -p password -caCN QMS -caAddr 192.168.2.129 -tunListen 127.0.0.1:23232 -tunConnect 192.168.2.129:6810 -tunCA 192.168.2.129

This command generates a certificate request that is sent to the Mitel SRC server, which is a certificate authority.

When the MiSslTunnelServer process reaches the QUEUED state, you need to launch the Mitel Standard Linux Server Manager application by using the following URL: http://[address]/servermanager, where [address] is the IP address of the Mitel SRC server.
After logging into the Server Manager, click the Certificate Management option from the Security menu. The Manage Certificates page displays.
Click the Certificate ID link in the Queues CSRs section. The certificate appears in a new window with the Cancel, Reject, and Approve buttons.
Click Approve to accept the certificate. The success message displays.
Once the approved certificate is downloaded by the MiSslTunnelServer application, the SSL tunnel can be tested by establishing a test connection.

Testing the SSL Tunnel

To test the SSL Tunnel, complete the following steps.

Open a command prompt.
Enter the following command at the command prompt:
```
telnet 127.0.0.1 23232
```
A blank telnet window opens.
Paste the following XML text into the telnet window to test the established tunnel:
```
<register_request><id>QMS</id><protocol_version>1.3</protocol_version></register_request>
```
If an XML response is received, it confirms that the tunnel is established correctly.
Press Ctrl+C to close the MiSslTunnelServer application. Once complete, the MiSslTunnelServer application creates the missltunnel.ini file. The [Windows] System32 directory must have a copy of this file.