This guide describes how to configure softphone features (SIP) for ProCall Enterprise in conjunction with an OpenScape 4000 from Unify.
|from V 7.0
Atos Unify OpenScape 4000
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.
Note on the use of call forwarding in the UCServer
If the Call forwarding feature is used in the UCServer, the SIP lines must allow second calls in order to use the Call forwarding on busy feature.
Configuration of the telephone system OpenScape 4000
The line settings to be used for ProCall can be made in the web-based OpenScape 4000 Assistant.
Menu – Configuration Management
View – Object
The UFIP type must be set up under Device combination and Device family.
In the SIP user tab, the phone number of the participant must be entered as the user ID.
A password must be stored in the Basic 2 tab under IP phones (HFA/UFIP). (The default password created when creating a user is: 12345).
Tab Basic 2
The selection of Uncompressed voice connection according to G711 under Features for IP connections is strongly recommended.
The settings are made in the UCServer administration under Telephony – Lines:
- Add telephone system
Select Unify OpenScape 4000.
- Enter the connection to the PBX under Softphone registrations as "SIP Softphone".
All SIP lines must be added in this connection setting.
For the connection to the Unify OpenScape 4000, the following must be specified:
as Username the "User ID" as Password the "Password"
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.
Configure feature codes/pickup
The Feature codes tab is used to configure how a call is fetched (pickup).
Pickup via UCServer
(from ProCall Enterprise V 8.3)
In the Pickup section you can execute the pickup internally in the UCServer.
This implements the pickup of a call by the UCServer itself, which brings improved functionality and does not require call group management within the cloud PBX.
Example screenshot: configure pickup - Properties for line group - Feature Codes - Execute pickup internally in the UCServer
Pickup via feature code
Alternatively, you can let the telephone system handle call pickup.
To do this, you must enter the speed dial code valid for the telephone system under Pickup – Pickup Feature code.
The extension from which the call is to be retrieved is specified as a variable with <NUMBER>, for example with the string *59<NUMBER>. However, the speed dial code *59 can also be configured differently on the system to be 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.