Avaya Aura Application Enablement Services (AES)

This section assumes that installation and basic administration of the Avaya Application Enablement Services server have been performed. The steps in this section describe the licenses validation, configuration of a Switch Connection, a CTI user, a CMAPI port, and creating a CTI link for TSAPI.

Open the AES  web interface by browsing to "https://<ip or domain name>", where "<ip or domain name>" is the IP address or DNS name of the Application Enablement Services server.  Log in  and do following:

Check TSAPI and DMCC  licensing

1. Use Licensing -> WebLM Server Access in the left pane, to display the Web License Manager pop-up screen, and log in using the appropriate credentials  
2. If the licenses are managed centrally by the System Manager, then select Services -> Licenses in the System Manager home screen. Otherwise, the Web License Manager screen is shown immediately.

3. In the Web License Manager screen, select Application_Enablement under Licenses Products to display license capacity and current usage.

4. Check that there are enough licenses for TSAPI Simultaneous Users and Device Media and Call Control. Note that the TSAPI license is used for device monitoring, and the DMCC license is used for media recording.

5. Versadial VSlogger requires TSAPI Basic license for each monitored IP Phone, softphone and ACD Split (Hunt Group) and DMCC Basic license for each recorded IP phone and softphone.If the TSAPI or DMCC service is not licensed, contact the Avaya sales team or business partner for a proper license file.

Configure Administer TSAPI link.

1. Use AE Services -> TSAPI -> TSAPI Links from the left pane of the Management Console. The TSAPI Links screen is displayed, as shown below. If the TSAPI Link is not configured yet, then click Add Link to create one.
2. In the "Add TSAPI Links" screen is displayed next, the Link field is only local to the Application Enablement Services server, and may be set to any available number.
3. For Switch Connection, select the relevant switch connection from the drop-down list. 
4. For Switch CTI Link Number, select the CTI Link number configured in "Check the status of CTI link for TSAPI service" in the "Avaya Communication Manager" section above. Make sure that ASAI Link Version is 6 or higher. Leave the default values in other fields.

Check Switch Connection PE/CLAN IPs.

1. Use Communications Manager Interface -> Switch Connections from the left pane. The Switch Connections screen shows a listing of the existing switch connections.
2. Locate the connection name associated with the relevant Communication Manager and click Edit PE/CLAN IPs button for the corresponding connection.
3. In the Edit Processor Ethernet IP screen, verify that ip-address is configured for Communication Manager and Status is shown "In Use". If the ip-address is not configured, then use Add/Edit Name or IP button to configure it.
4. Navigate back to the Switch Connections screen and verify that the Number of Active Connections is valid

Check Switch Connection H.323 Gatekeeper.

1. Use Communications Manager Interface -> Switch Connections from the left pane. The Switch Connections screen shows a listing of the existing switch connections.
2. Locate the connection name associated with the relevant Communication Manager and click Edit H.323 Gatekeeper button for the corresponding connection.
3. In the Edit H.323 Gatekeeper screen, verify that ip-address is configured for Communication Manager. If the ip-address is not configured yet, then use Add Name or IP button to configure it.

Get Tlink name.

1. Use Security -> Security Database -> Tlinks from the left pane. The Tlinks screen shows a listing of the Tlink names. Locate the Tlink Name associated with the switch connection to Avaya Communication Manager. A new TLink name is automatically generated for the TSAPI service. Locate the TLink name associated with the relevant switch connection, which would use the name of the switch connection as part of the Tlink name. Make a note of the associated Tlink name, to be used later for configuring the Versadial VSLogger server.
2. If Tlink doesn't exist, then follow instructions in AE Services Administration in document Application Enablement Services Administration and Maintenance Guide available at http://support.avaya.com

Configure CTI user for VSLogger.

1. Use User Management -> Add User from the left pane, to display the Add User screen in the right pane.
2. Enter desired values.  Retain the default value of “None” for Avaya Role, and select “Yes” from the CT User drop-down list.
3. Click on Apply at the bottom of the screen. Remember the User Id and Password, to be used later for configuring the VSLogger server.
4. To change the security level for the CTI User (it needs to have unrestricted access privileges), select Administration -> Security Database -> CTI Users -> List All Users from the left pane. Choose the previously created CTI user, and click Edit.
5. The Edit CTI User screen appears. Tick the Unrestricted Access box and Apply Changes at the bottom of the screen

Configure DMCC port.

1. Use Networking -> Ports to set the DMCC server port. Enable either Unencrypted Port or "Encrypted Port** or both as shown in the screen below. Note the port values to use in the following steps for VSLogger server configuration. Click Apply Changes button (not shown) at the bottom of the screen to complete the process.

Enable Security Database.

1. Use Security -> Security Database -> Control from the left pane, to display the SDB Control for DMCC and TSAPI screen in the right pane. Check Enable SDB for DMCC Service and Enable SDB TSAPI Service, JTAPI and Telephony Service, and click Apply Changes.

Restart TSAPI and DMCC services.

1. Use  Maintenance -> Service Controller from the left pane, to display the Service Controller screen in the right pane. Check DMCC Service and TSAPI Service, and click Restart Service.

Configure Versadial VSLogger call recorder

Adutante Server Configuration ( /config/cti.properties  file )



cti.dmcc.avaya.enabled=Y



# The SwitchName (from OAM Switch Connections web page) of the call server

cti.dmcc.avaya.cm1.swname=swname1

# The IpAddress (from OAM Switch Connections web page) of the call server

cti.dmcc.avaya.cm1.address=10.1.100.3


# IP address of the Application Enablement Server

cti.dmcc.avaya.cm1.serverip=10.1.100.2

# AE Server client connection port: 4721(non-SSL) or 4722(SSL)
cti.dmcc.avaya.cm1.serverport=4721


# Credentials for connecting to the AE Server

cti.dmcc.avaya.cm1.username=avaya
cti.dmcc.avaya.cm1.password=avaya


# ---- secured/ unsecured connection values for cm1.secure are true (for port 4722) and false (for port 4721).
cti.dmcc.avaya.cm1.secure=false

# --- observed extensions (:passwords, default = extension)
cti.dmcc.avaya.cm1.dn=1000:1000,1001:1001,1002:1002,1003:1003,1005:1005,1007:1007,1008-1015,1020:1020

# --- recording provider id (vslogger) 
cti.dmcc.avaya.cm1.recorder.id=VSLOGGER1




VSLogger Server  Configuration 

HW Configuration  (CLI interface)

 

cli>(config)hw ipcast

cli>(config-hw_ipcast)enable y

cli>(config-hw_ipcast)numdev 10

cli>(config-hw_ipcast)save

cli>(config-hw_ipcast)exit

cli>(config)reload

 

Channel configuration

 

cli>(config)ch 1

cli>(config-ch_1)enable y

cli>(config-ch_1)nic 1

cli>(config-ch_1)port 2030

cli>(config-ch_1)protocol avayadmcc

cli>(config-ch_1)nortptimeout 3

cli>(config-ch_1) mapto  1000

cli>(config-ch_1)save

cli>(config-ch_1)exit

cli>(config)reload