This guide describes how to configure softphone features (SIP) for ProCall Enterprise in conjunction with a Mitel MiVoice MX-ONE.
|ProCall Enterprise||from V 6.1|
Mitel MiVoice MX-ONE
Version 6.1 SP1
Notes on the estos test environment
The softphone functions (SIP) of ProCall were tested in the estos test environment with the telephone system specified above. The tests were performed with a maximum of two lines per SIP end device. The following information was used when setting up the telephone system for logging in/registering the individual SIP lines to the UCServer.
Information on codecs and UDP connections
For the connection of SIP lines to the UCServer, the telephone system must support the G.711 a-law codec for the SIP protocol and should have this set as the preferred codec for all end devices.
Only UDP connections are supported.
Information on the use of call forwarding in the UCServer
If the Call forwarding in the UCServer feature is used, the SIP lines must allow second calls in order to use the Call forwarding on busy feature.
Configuration of the telephone system Mitel MiVoice MX-ONE
Set up as an extension
The SIP line for ProCall participants must be set up as an extension.
Menu – Extension – Extension number – Details
In the test environment, the SIP lines were set up with the following features:
- Extension type = IP
- Protocol = SIP
- Allow 3rd party SIP client
- The specification of an authorization code is optional.
The connection to the PBX is entered under Settings in the UCServer Administration as SIP Softphone connection under Telephony – Lines.
- Add telephone system
Select the Mitel MiVoice MX-ONE.
Enter the connection to the telephone system under Softphone registrations as "SIP softphone".
After setting up the connection, all SIP lines must be added under Softphone registrations.
For the connection to a Mitel MiVoice MX-ONE the following must be specified:
as username "SIP-Name" as password "Login code"
From ProCall 6.1, please note the following settings
On the SIP connection line group it is possible to define what the UCServer signals to the PBX when:
- the client is not logged in or call protection is enabled
- the call is rejected by the client or no devices are available
The required settings depend on the telephone system and its configuration.
Example: The telephone system should redirect incoming calls to the mailbox if the ProCall Client is not logged in.
Problem: The PBX does not evaluate the busy here (486) sent by default from the UCServer and the calls are not redirected.
Possible solution: In the PBX, this setting is set up for Participant unavailable, and Temporarily unavailable (480) is selected for signaling on the UCServer.
Since estos has no influence on the further development of the supported telephone systems by the manufacturer, we cannot guarantee that the instructions described above will also be fully valid for future releases.