Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Verba uses Cisco External Call Control (ECC) to trigger prompts for the calls controlled by CUCM.

For more information on ECC, click here.

The Cisco ECC feature relies on an external application (hosted on Verba servers in this case) that responds to external call control requests configured on various trigger points, such as translation patterns, route patterns, etc. Cisco UCM provides an XML/HTTP API for ECC request, called Cisco Unified Routing Rules XML Interface (CURRI).

Outbound call flow

  1. Internal person calls an external number.

  2. ECC is triggered on the route pattern.

  3. CUCM sends a routing request to the Verba Announcement service (XML/HTTP API)

  4. The Verba Announcement service decides based on the announcement configuration what to do with the call, or if the call can be established without an announcement. It returns an appropriate routing decision to the CUCM.

  5. CUCM redirects the call to the Verba Announcement server.
  6. The Verba Announcement service calls the original callee.
  7. When the call established, the announcement played.
  8. The Verba Announcement service connects the two calls, then leaves the call.

Prerequisites

new SIP Trunk pointing to the Verba Announcement server has to be created. Note that it requires a custom SIP Trunk Security Profile.

Configuring Cisco for Recording Announcement

Verba_note

If the inbound announcement is configured already, then the existing External Call Control Profile can be used, so Step 1-5 can be skipped.


Step 1 -
 Open the Cisco Unified Call Manager web interface and go to the Call Routing \ External Call Control Profile menu.

Step 2 - Click on the Add New button.

Step 3 - Provide a Name, and set the Primary Web Service setting the following way: http://verba_server_hostname:10205/ciscoannouncement/

Step 4 - Set the Call Treatment on Failures setting to Block Calls.

Step 5 - Click on the Save button.

Step 6 - Go to the Call Routing \ Route/Hunt \ Route Pattern menu.

Step 7 - Select the Route Pattern pointing to the Gateway or to the  Route List / SIP Trunk pointing outside.

Step 8 - Set the External Call Control Profile setting to the one created earlier.

Step 9 - Click on Save button then on the Apply Config.

Step 10 - Repeat Step 7-9 on all outgoing Route Patterns.

Configuring Verba for Cisco Recording Announcement

Step 1 - On the Verba web interface, navigate to System > Servers > Select the server which is hosting the Announcement service  > Click on the Service Activation tab.

Step 2 - Activate the Verba Cisco Announcement Service by clicking on the  icon.

Step 3 - Click on the Change Configuration Settings tab. Expand the Cisco Recording Announcement section.

Step 4 - Add a new SIP port by clicking on the  icon at the SIP Ports setting.

Step 5 - At the right panel, provide the SIP Port number. This has to be port the SIP Trunk connecting to the Verba server on. 

Info
titleSecure 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 uploaded 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 6 - Provide a directory number at the Service's Phone Number setting. This directory number must be a number not used by anything else.

Step 7 - Set the Internal Number Pattern setting. This has to be a regex which matches to all internal line numbers.

 

 

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

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

Step 11 - Start the Verba Announcement Service by clicking on the  icon.

Setting up Extensions for Outbound Announcement

Step 1 - In the Verba web interface, go to Users > Users menu.

Step 2 - Select the user from the list.

Step 3 - Under the Cisco Recording Announcement section set the Play Notification for Outbound Calls setting.

 Step 4 - Click the Save.

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

Configuring custom prompts for users (optional)

Step 1 - Login to the Announcement server, and go to the C:\Program Files (x86)\Verba\resources\announcement folder.It is possible to configure custom notification sounds on a per user basis. To achieve this follow these steps:

Step 2 - Copy the .wma files to the conferenceinbound and outbound folders.

Step 3 - Open the Verba web interface, click on the System / Servers and select the Media Repository server, or select the appropriate Configuration Profile at System / Configuration Profiles

Step 4 - Click on the Change Configuration Settings tab. Expand the Web Application section.

Step 5 - Expand the Lync recording Announcement node, and add the names of the .wma files to the PSTN Inbound Announcement Prompt Files and the Conference Announcement Prompt Files, one in a line.

Step 6 - Click the  icon to save your settings.

Step 7 - The system will notify you that the changes need to be applied to the server by restarting the involved services. Execute the required tasks.

Step 8 - Repeat the steps on each Media Repository server.

To configure the custom prompt for the users please see the User Configuration configuration.