OpenScape Voice

CTI (CSTA)

System requirements

OpenScape Voice

• V9

XPhone Connect Server

• Supported from XPhone Connect Server V6.0

Configuring the PBX

The CSTA settings are used to define the maximum number of CSTA sessions (max. 256), the CSTA IP addresses and the maximum number of endpoints to be monitored.

Administrator rights enable you to activate the CSTA interface; please proceed as follows:

1. Open the OpenScape Voice configuration.

2. Go to Configuration > OpenScape Voice.

3. Click the Administration icon.

4. Go to Signalling Management > CSTA.

5. Open the CSTA settings dialogue.

6. Go to the Signalling Manager tab.

7. Configure the number of the Maximum CSTA sessions field (1-256, default = 64).

8. The maximum number of monitor points is defined in the Maximum Monitored Endpoints field (1-100000, default = 100000).

9. The corresponding IP addresses for the CSTA connection are configured in the CSTA Manager Virtual IP1 / IP2 fields. Usually, the IP1 can be used here for the XPhone Connect Server connection.

10. The TCP Listener Port Number can not be modified (value: 1040).

11. The CSTA system status is shown in the corresponding field. This is a dynamic value requiring the Refresh button to be pressed in order to see the current value.

12. Then click Save, to save the configuration!

13. Change to the Applications tab.

14. You can create a new application via Add:

    • Enter a unique name here.

    • Select OpenScape as the Application type.

    • Use the IP address of the XPhone Connect Server as the Application IP address.

    • Change to the Active Device List tab.

    • Check here whether all secondary locations required (Service ID) are listed and ensure that Monitored is activated.

    • Then click Save, to save the configuration!

XPhone Connect configuration

Now go to the Web Administration of XPhone Connect Server.

System settings > Telephony & Meetings > Telephony > CTI

Click new landline gateway in the table header. The Create new landline gateway dialogue opens:

PBX type:

Select Unify OpenScape Voice (CSTA).

Name:

Enter a unique name here.

Dialling parameter:

Select a dialling parameter.

Deactivated:

Set this flag if this gateway is to be pre-configured but not activated.

Host name or IP address:

Enter the host name or the IP address of the telephone system here. The port information refers to the configured port for the CSTA service (default:) 1040).

System settings > Telephony & Meetings > Telephony > CTI > New Landline gateway

When the configuration is completed, click Save.

Diagnostics

You can find information on diagnostics here.

XPhone Connect Line configuration

System settings > Telephony & Meetings > Telephony > Lines

The corresponding lines and users must be set up and configured in the XPhone Connect Server.

Advanced settings for PBX nodes

Advanced settings are optional and only required in special cases. If desired or required by your company structure, you can use Add to specify the following additional parameters:

Name	Description	Value
CreateLineVerify	Lines are verified before creation; i.e. invalid phone numbers are filtered. Type: Numerical decimal or hexadecimal (starts with 0x) value	0: off 1: On (default)

When the configuration is completed click Apply and then Save to save the settings.

UM

Hint

For the Unified Messaging connection, please use the technical documentation from TE-Systems. This describes the connection via XCAPI.

Tip

• Perform the setup of OpenScape Voice and XCAPI according to the TechNotes of the TE-Systems company. (Download via TE-Systems Community ).

• XCAPI documentation can be found in the XPhone Connect installation image under Software\Server\3rdParty\xcapi\XCAPI_Documentation.zip.

SIP trunk to XCAPI

The IP address of the XCAPI endpoint at the XPhone Connect Server is 10.10.170.40 and reacts to the SIP port 5060.

Open the XCAPI endpoint profile (EPP_XCAPI) and make sure the following settings are in place:

Open the XCAPI endpoint (EPP_XCAPI) and make sure the following settings are in place:

XCAPI configuration

Open the** XCAPI configuration > Controller > [PBX]** and note the following settings:

XCC

The SIP gateway for the AnyDevice and conference service functions is configured completely independently of the SIP gateway for the UM functions.

You can find an XCAPI documentation in the XPhone Connect installations image under \Software\Server\3rdParty\xcapi\XCAPI_Documentation.zip.

SIP To Header:

The extension is always entered for from internal and the complete number in E-164 format is always entered for from external in To Header.

SIP From Header:

• External: From Header contains the number in E-164 format, e.g.: +498912345222.

• Internal: From Header* contains the number in E-164 format, e.g.: +498912345222.

SIP Diversion Header:

Matched every telephone system, in general ^[^<]*<(?:tel|sip):([+]?\d+)\D+.*$.

Special configuration of the PBX

1. + as prefix.

   • A tick in the telephone system configuration (Edit Endpoint) under Attributes for Send International Numbers in Global Number Format (GNF) ensures that a + is put in front of an international telephone number

2. Adjustments for E.164 signalling.

   • The following rules must be added under Display Number Modification:

• The first rule ensures that telephone numbers form external lines remain international.

• The second rule ensures that telephone numbers from XPhone Connect to external lines remain international.

The third rule ensures that telephone numbers from XPhone Connect to the participant are shortened to the extension.

XCC SIP Trunk

The SIP trunk for the XCC on the XPhone Connect server has the IP address 10.10.170.40 and listens to SIP port 5064.

Open the XCC Endpoint Profile (EPP_XCC) and pay attention to the following settings:

Open the XCC Endpint (EP_XCC) and pay attention to the following settings:

SIP Trunks in XPhone Connect Server

In XPhone Connect Server Web Administration, open System settings > Telephony & Meetings > Telephony > SIP > New SIP Trunk and make the following settings:

Have you found a mistake on this page?

Or is something not formulated well or too vague? Then we look forward to receiving an e-mail, preferably with a suggestion for improvement, to doku@c4b.de. Thank you very much!