Avaya Communication Manager (ACM)#

CTI#

Configuring the telephone system - Peculiarities#

Forwarding#

For call forwarding to work, the ASAI Link must be set to version 5, CM must be 5.0 or higher and AE Service must be set to at least 4.1. The settings can be found on the Avaya Management Console (in the browser https://<CTI server (AES) IP address>) under AE Services > TSAPI > TSAPI Links. Here the ASAI Link Version must be at least 5!

Do Not Desturb#

For the DoNotDisturb function, a Coverage path must be set, i.e. an action must be stored that is run for the status DoNotDisturb.

Setting the coverage path:

Open Site administration, under Advanced, open Start emulation

Command: change station xxx (xxx => line/device number e.g.: 102)

The Redirection Notification must be deactivated, i.e. n must be set!

Storing the action:

Command: add coverage path xxx (xxx => line/device number e.g.: 102)

Allow DND/SAC/Goto Cover for internal and external (“y”)

Bei Coverage POINTS, enter a target

In this example, all calls to the end device with the number 100 are forwarded, if the user with 102 activated Do Not Disturb in the XPhone Connect Client.

DND - mode at the telephone#

The DoNotDisturb (DND) function communicating the DND status to the system via CSTA corresponds to the key allocation send-all-calls (SAC) at the end device, the key allocation Do not disturb is a pure telephone setting that is not known to the telephone system and also the XPhone Connect Server.

PickUp#

In general, for the PickUp function Temporary Bridged Appearance on Call Pickup = n must be set at the system, since otherwise the call remains on the device called originally and the call control display in the XPhone Connect Client is not correct. If this is not configured, the XPhone Connect Client shows the call taken over as accepted, which can lead to errors in call control in future.

Site Administration > Advanced > Start Emulation

Command: change system-parameters features

XPhone Connect configuration#

System settings > Telephony & Meetings > Telephony > CTI

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

PBX type:

Select Avaya DMCC (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.

Connection to the PBX:

In the field Host name or IP address, enter the Avaya CTI Server IP address. Enter the CSTA port (default: 4721).
Avaya switch name (Avaya Communication Manager), you can enter the corresponding information.

Access parameters:

Logon name & Password: Corresponds to a user, the user needs administrator rights and is required for the CSTA registration.

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

When the configuration is completed, click Save.

Advanced settings#

Problem: If a call is made directly to the central voicebox, a redirect ID is transferred by the XCAPI. It is analysed by the XPhone Connect Server and then results in an incorrect telephone number being displayed. For this redirected ID not to be analysed, an entry must be made in advanced settings. To do this, click on the tab Advanced settings and then add the following value by clicking Add:

Name: IgnoreRedirectdNumberConflict

Value: 1

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

Diagnostics#

You can find information on diagnostics here.

Line configuration#

System settings > Telephony & Meetings > Telephony > Lines

There are no further peculiarities. The corresponding Lines and Users must be set up and configured in the XPhone Connect Server.

Knows limitations#

The following feature is not supported:

CTI control of DECT end devices

XCC#

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

Configuring the PBX#

General#

The connection is only possible via the Session Manager, because SIP signaling uses UDP.
In general, the AnyDevice / Conference numbers must be routed from Communication Manager to Session Manager and from Session Manager to SIP Trunk.

SIP trunk#

Open the routing of the Avaya ACM: System Manager > Elements > Routing

SIP Entity#

Configure an entity of type SIP trunk:

Important

SIP Entity 1 is the local listener of the PBX, i.e. the port on which the SIP packets are to be received. While SIP Entity 2 specifies the destination. In this case, the IP and the port under which the XPhone Call Controller has opened its listener.

Routing - Dial Patterns#

The dial patterns are required for routing to the XCC. Example for the dial pattern 446 (equivalent for 447):

Routing via Dial Pattern#

Here the destination (in this case the corresponding SIP gateway from XCC) for the respective dial patterns is specified:

Configuration of the XPhone Connect Server#

SIP Gateway#

Configure a new SIP gateway:

System settings > Telephony & Meetings > Telephony > SIP > SIP-Trunk Objekt

Select the gateway type Avaya ACM and assign a name. Select the previously created Dialling parameters.

XCC connection to the PBX:

IP address of the XPhone Call Controller: XPhone Call Controller IP (listener) and defined SIP port (default 5060)
IP address of the PBX or SBC: Avaya ACM address and defined SIP port (default 5060).

AnyDevice/Softphone:

Enter the configured number from the Avaya ACM LCR here: e.g. 446 - Alternatively, you can also configure the XCCGatewayInPrefix in the Advanced Settings.

Conference:

Enter the configured numbers from the Avaya ACM LCR here and activate the conference service: e.g. 447