This manual describes how to set up softphone functions (SIP) for ProCall Enterprise specifically for the IP811 PBX from innovaphone and what you should pay attention to.

ProCall Enterprisefrom V 6.2
PBX innovaphone IP811Release: 12r2, 13r1

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 call forwarding when busy.

Configuration of the telephone system innovaphone IP811

ISDN exchange line

To use the softphone functions (SIP), it is absolutely necessary to activate the No encryption setting for SRTP in the gateway setting of the external line.

SIP type exchange line

Some SIP providers support the "Comfort Noise" feature, which is passed on from the PBX to the UCServer. This causes delays in voice transmission. The behavior is known and documented at innovaphone:
It is recommended to disable this function in the telephone system.

When setting up the user object, there are no special settings to consider if the user object is only set up for a SIP line or the additional telephone for registration via the extension number.

In this case, the "Number" and the optional "Password" are relevant for the connection of the line in the UCServer.

If the phones are set up via the "Provisioning Server" or the MAC address of the phone is manually stored in the user object, the extension number must be specified under "Hardware Id" so that it can be registered by the UCServer.

In this case, additional configurations are required in the UCServer (see below).

UCServer configuration

The settings are made in the UCServer administration:

  1. Add telephone system 
    The connection to the telephone system is entered as a SIP softphone connection under Lines.
    All SIP lines must be added in this connection setting.

  2. You must specify the following to connect to an innovaphone IP811:

    as username"Number"
    as password"Password"

    The specification of the password for the user object is optional.

When registering the SIP line via hardware id

If the SIP line is registered via the "Hardware id" in the PBX, it is additionally displayed as a TAPI line in the UCServer (at the latest after restarting all components).

For the UCServer, the line is thus available 3 times (2 times via TAPI, 1 time via SIP connection), and 3 "devices" are assigned to the user:

The "SIP line" provided via the system TSP cannot be used and must be deactivated in the UCServer under Lines!

From ProCall version 6.1.1, please note the following settings

On the line group of the SIP connection, you can define what the UCServer signals to the PBX when:
• The client is not logged in or call protection is activated.
• The call is rejected at 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 busy here (486), which is 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 on the UCServer Temporarily Unavailable (480) is selected for signaling.

Version note

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.