Configuring Verba for Cisco network-based recording

The Cisco network-based recording option in Verba allows recording voice/audio calls forked either at the gateways or at the phones. This recording option relies on the standard Cisco recording and monitoring APIs to provide a seamless integration with the Cisco collaboration solution.


In order to use the Cisco network-based recording options, the configuration of the Cisco Unified Communication Manager and the recordeddevicesis required.
For the configurations steps see Configuring Cisco UCM for network based recording.

Firewall configuration

Refer to Firewall configuration for Cisco recording deployments for more information.

Configuring the Verba Unified Call recorder service for Cisco network-based recording

Step 1 - In the Verba Web Interface go to System > Servers > Select your Recording (or Single) Server  > Click on the Service Activation tab.

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

Step 3 - Activate the Verba Cisco JTAPI Service by clicking on the  icon.

Step 4 - Click on the Change Configuration Settings tab.

Step 5 - Expand the Cisco JTAPI Configuration \ Basics node.

Step 6 - Add a new JTAPI connection by clicking on the  icon.

Step 7 - In the right panel, provide the JTAPI UserPassword, and the IP address of the CUCM. If there are more nodes, then provide them separated by comma.

Step 8 - Click Save.

Connecting to multiple CUCM clusters with JTAPI

It's also possible to connect to multiple CUCM clusters with a single Verba Recording Server. Additional connections can be configured by clicking on the icon.

Legacy configuration

If the Verba server is connecting to only one CUCM cluster, then the legacy settings can be used also. In this case, the configuration can be provided at the Cisco UCM IP Address(es), JTAPI User Name and JTAPI User Password settings.

Step 9 - Expand the Unified Call Recorder \ Media Recorder \ Cisco JTAPI Integration node. Set the Cisco JTAPI Integration Enabled setting to Yes.

Step 10 - Provide the Verba Cisco JTAPI service connection(s) at the Cisco JTAPI Services setting with the "servername:port" format, one per line. If it is on the same server and using the default port, then enter localhost:11200.

Step 11 - Under the Unified Call Recorder \ Recording Providers \ General node, set a value for the Internal Domain, Numbers Pattern parameter. The value is a regular expression that defines the internal phone numbers or number ranges to accurately identify the direction of the recorded calls.

In multi-tenant environments, if an internal pattern regular expression is defined in both the environment and the Unified Call Recorder service configuration, the pattern specified in the environment configuration is used to determine the internal values, not the pattern defined in the Unified Call Recorder service configuration.

Step 12 (Optional) - If secure SIP Trunk connection is used, then under the SIP / SIPREC node click on the  icon at the Secure SIP Ports setting. In the right panel, provide an incoming port and the certificate settings, then click Save. Note that the port 5060 cannot be used by default because it's configured at the SIP Port setting already, so that has to be changed first in that case.

Secure SIP Trunk Connection

If secure SIP Trunk connection is required, the following settings have to be set:

SSL/TLS Certificate: The thumbprint of the Verba server certificate being used for the connection. This has to be the same certificate which was upload to the CUCM.

SSL/TLS Trust List: The thumbprint of the CUCM server certificate, or the thumbprint of the CA certificate which issued the CUCM server certificate. Alternatively, "*" can be used. In this case, every certificate going to be trusted, whose CA certificate can be found in under the Trusted Root Certificate Authorities folder. If left empty, every certificate going to be trusted.

Alternatively, .crt/.cer and .key files can be used. In this case, UNC paths can be provided in the SSL/TLS Certificate and the SSL/TLS Key settings, and the SSL/TLS Key Password has to be provided.

Step 13 - Under the SIP / SIPREC node click on the  icon at the SIP Trunk Status Monitoring setting.

Step 14 - In the right panel provide the CUCM IP address at the Destination IP Address setting and set the Timeout (seconds) setting. If the default values were used in the SIP Profile at the CUCM side, then set it to 120.

Step 15 - Click on the Save button on the bottom. If multiple SIP trunks are connecting from separate CUCMs or there are multiple CUCM nodes for the same SIP trunk, then repeat the steps 13-14.

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

Step 17 - 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 18 - Click on the Service Control tab.

Step 19 - Start the Verba Cisco JTAPI Service and the Verba Unified Call Recorder Service by clicking on the  icon.

Step 20 - Repeat the steps on all Recording servers if there are multiple.

Configure extensions

In order to make a directory number recorded, several CUCM side configuration steps also required. For the configuration steps, see Adding a new extension for recording in Cisco UCM.

After finalizing the configuration of the recording services, make sure you have added the extensions you want to record to the Verba extension list. This can be done manually (Extension details) or using Active Directory Synchronization.

Configure Cisco Cube 2N recording

For Cisco Cube 2N recording follow the steps of the network-based recording configuration. It is important to the both of the recorder server need to have own JTAPI service, what connect for the same CUCM with the same JTAPI user. On the secondary recorder server set the Unified Call Recorder \ Secondary Recording Service setting to Yes and repeat the steps from the step 16.

Configuring advanced network-based recording

With the advanced network-based recording configuration load-balancing and mid-call failover can be achieved. For the configuration steps see Configuring recording high availability.

Service configuration reference

For the service configuration references see: