The Verba Avaya Recorder is separated into two different services: The Verba Avaya DMCC/JTAPI Service and the - Media Recorder portion of the - Verba Unified Call Recorder Service. These services can run on the same machine or different servers.

The DMCC/JTAPI service is essentially the interface towards the AES and CM servers, and the Unified Call Recorder is recording the media stream itself.

Configuring the Verba Unified Call Recorder service

Step 1 - In the Verba web interface go to System / Servers, select the Recording Server and click on the Service Activation tab.

Step 2 - Activate the Verba Unified Call Recorder Service by clicking on the icon.

Step 3 - Click on the Change Configuration Settings tab.

Step 4 - Expand the Unified Call Recorder section.

Step 5 - Under Media Recorder / Incoming Connection, configure the authentication credentials for the connections with the Avaya DMCC service. Define the User and Password values. These credentials will be used later when configuring the connections in the Avaya DMCC service.

Step 6 - Save the changes by clicking on the icon.

Step 7 - A notification banner will appear on the top. Click on the click here link, so you will be redirected to the Configuration Tasks tab. Click on the Execute button in order to execute the changes.

Step 9 - Go to the Service Control tab, and start the Verba Unified Call Recorder service by clicking on the icon.

Configuring the Verba Avaya DMCC service

Step 1 - In the Verba web interface go to System / Servers, select the Recording Server and click on the Service Activation tab.

Step 2 - Activate the Verba Avaya DMCC/JTAPI Service by clicking on the icon.

Step 3 - Click on the Change Configuration Settings tab.

Step 4 - Expand the Avaya Recorder node.

Step 5 - Configure the settings under the Avaya DMCC node:

Setting Name	Description
AES IP Address	The IP Address of the AES server. One Recording Server can only connect to one AES server
AES Port Number	Communication port of the AES server
AES User Name	The user in AES that has the rights for DMCC to execute the necessary commands
AES User Password	The password of the AES User
AES Secure Connection	Set to Yes if you want the channel between the AES and the Verba server to be secure. In this case, you need to set the Trust Store location and password as a minimum
AES JKS Trust Store File	Location of the Trust Store. This needs to contain the public certificate of the AES
AES JKS Trust Store File Password	The password of the Trust Store
AES JKS Key Store File	Location of the Key Store. An additional security layer can be set in the AES. In that case, it will be expecting an additional key, that needs to be added to the Key Store
AES JKS Key Store File Password	The password of the Key Store
Communication Manager IP Address	The IP address of your Avaya Communication Manager. If there are ESS servers, then list them separated by commas (,) after the primary CM. Only one of the two entries need to be set (either the IP or the hostname)
Communication Manager Name	The name of your Avaya Communication Manager. If there are ESS servers, then list them separated by commas (,) after the primary CM. Only one of the two entries need to be set (either the IP or the hostname)
AES API Version	Define the version of the AES
Preferred Codec	The comma (,) separated list of supported codecs
Dependency Mode for Multiple Registration	DEPENDENT or INDEPENDENT
Registration Retry Interval (seconds)	Upon failed registration, the component will wait for this amount of time before trying again
Default Device Password	The default password for extensions
Internal Domain, Number Pattern	A regex pattern that should match the internal directory numbers
Secondary Recording Server	Sets whether the Recording Server should be considered as secondary or not
Ignore Recording Rule Entries Without Device Password	On the extension configuration page, the password for the extension can be set. If this option is set to yes, then the extensions, where the passwords are not set will not be recorded
Advanced Recording Rules Enabled	Enables XML-based advanced recording rules
Enable Beep Tones	Enables recording beep tones. The tone frequency can be adjusted in the Avaya Communication Manager SAT with the "change tone-generation" command.
Worker Thread Count	Amount of worker threads
Work Folder	The system will place temporary files into this folder

Step 6 - Configure the settings under the Avaya JTAPI node:

Setting Name	Description
Avaya Tlink Name	Tlink name to the Communication Manager. This is displayed on the interface of the AES
JTAPI User Name	The name of the AES user that has the necessary rights to communicate through JTAPI (This can be the same user as is used for DMCC in the previous section)
JTAPI User Password	The password of the AES user
JTAPI JKS Trust Store File	Location of the Trust Store. This is needed if the AVAYATlink is configured for secure communication. This needs to contain the public certificate of the AES.
JTAPI JKS Trust Store File Password	The password of the Trust Store
Disable Agent ID Handling	The use of agent IDs can be disabled
Hunt Group for Monitored Agent(s)	special/"dummy" group that includes all agents. This is needed for JTAPI to gather additional information on the users
Agent Status Check Interval (seconds)	The system queries the agents for their status with a time interval that is set here

Step 7 - Under the Media Recorders node click on the icon at the Media Recorder Servers setting.

Step 8 - In the right panel select the Recording Server at the Host setting. Provide the username and password configured in the Verba Unified Call Recorder Service above for the connections. Set the Port to 10500.

Step 9 - Click on the Save button at the bottom.

Step 10 - Save the changes by clicking on the icon.

Step 11 - A notification banner will appear on the top. Click on the click here link, so you will be redirected to the Configuration Tasks tab. Click on the Execute button in order to execute the changes.

Step 12 - Go to the Service Control tab, and start the Verba Avaya DMCC/JTAPI service by clicking on the icon.

Browser not supported