These instructions describe how to configure softphone functions (SIP) for ProCall Enterprise in connection with a bintec elmeg be.IP plus telephone system.
|ProCall Enterprise||from V 6.4|
|PBX bintec elmeg be.IP plus||Version R 10.2 Rev6 SP2|
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 during the setup of the telephone system for the login/registration of the individual SIP lines to the UCServer.
Note 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.
Configuration of the telephone system be.IP plus
The lines to be used for ProCall are set up under menu item: End devices – Other phones on the VOIP tab.
Each SIP line used for ProCall requires the activation of a "VoIP/SIP in LAN" license.
The logon data required for the softphone line logon is defined under "Numbering – User settings" on the user object.
The internal phone number is required as the SIP login name for the login.
- The password must be entered for the user under Basic settings on the "Authorization" tab in the Password for IP phone registration field.
The settings are made in the UCServer administration:
- Add telephone system
Enter the connection to the telephone system under Softphone registration as "SIP softphone" under "Lines".
All SIP lines must be added in this connection setting.
For the connection to the bintec-elmeg be.IP plus, the following must be specified:
as Username Internal phone number as Password Password for IP phone registration
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.
Known problems and limitations
If a call is forwarded from an internal terminal without being answered, the call is terminated.
If the second call is accepted and forwarded, the first and second callers are connected.
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.