Configure CUCM

Create SIP profile for recorder

Use the Device > Device Settings > SIP Profile menu option in Cisco Unified Communications Manager Administration to create SIP profile for recorder.

The following figure illustrates creating a SIP profile for the recorder.

Create SIP profile for recorder

Make sure that the Deliver Conference Bridge Identifier option is checked. When enabled it allows to deliver additional information (specifically, the b-number that identifies a conference bridge) to the recorder across the SIP trunk. If the check box is left unchecked, the far-end information for the remote conference remains empty. Check the Deliver Conference Bridge Identifier check box on the remote cluster SIP profile as well.

Create SIP profile for recorder 2

Checking this check box is not required for recording, but the conference bridge identifier helps to group multiple call segments belonging to the same conference into one interaction, like shown in below screenshot:

Group calls into interaction

Configure SIP OPTIONS Ping

In multi-server setup, it is recommended to enable SIP Options Ping feature for each recording server. In a single-server setup, this feature should be disabled (see details below).

  • Single-server setup - disable SIP OPTIONS Ping
  • Multi-server setup - enable SIP OPTIONS Ping

Cisco UCM starting from v.8.5(1) supports SIP OPTIONS Ping feature. Cisco UCM periodically sends a SIP OPTIONS (ping) message to each recording server to detect its availability. If the recording server is unavailable – indicated by either no response, response of “408 Request Timeout” response of “503 Service Unavailable”, Cisco UCM marks this recording server as unavailable. It skips that server in the round-robin or sequential list of recording servers. The SIP Options Ping feature allows to detect availability of the recording server earlier, without having to wait until a call is ready to be recorded.

However, in single-node deployments, SIP Options Ping is not recommended. Not only is it not helpful, but it can result in unnecessary failure recovery delays.

Create SIP OPTIONS Ping

Create SIP Trunk Security Profile

Create SIP Trunk Security Profile for each MiaRec recording server.

Use the System > Security > SIP Trunk Security Profile menu option in Cisco Unified Communications Manager Administration to create SIP Trunk Security profile for recorder.

  • Set Incoming Transport Type to TCP+UDP.
  • Set Outgoing Transport Type to TCP (this setting has to match the configuration of MiaRec). TCP is recommended.
  • Uncheck option Enable Digest Authentication
  • Set Device Security Mode parameter to Non Secure.

Create SIP Trunk Security Profile

Create a SIP Trunk that points to the recorder

Use the Device > Trunk menu option in Cisco Unified Communications Manager Administration to create SIP trunk that points to the recorder.

  • Ensure that the Media Termination Point Required check box is unchecked.
  • Select the Run On All Active Unified CM Nodes check box.

Create SIP Trunk

Make sure the SIP Privacy option is set to None, otherwise you will see in call details a text "Anonymous" instead of user's extension.

Create SIP Trunk

In SIP Information section configure:

  • Destination Address should point to ip-address or DNS name of the recorder server
  • Destination Port should match the port on which MiaRec recorder is listening for messages from CUCM (see configuration of MiaRec below)
  • Select the previously created SIP Trunk Security Profile for the recorder
  • Select the previously created SIP Profile for the recorder

Create SIP Trunk

Create a recording profile

Use the Device > Device Settings > Recording Profile menu option in Cisco Unified Communications Manager Administration to create recording profile.

The following figure illustrates creating a recording profile.

Set Recording Destination Address to the directory number that associates the recorder with this recording profile. The only guideline for this number: it should be possible for UCM to route it to the SIP trunk where the recorder is defined. No user is going to directly call this number, this is internal to the system. Make sure it does not collide with your numbering plan. This is why the example shows '7777'.

Set Recording Calling Search Space to the CSS that includes partitions containing the user phones and the partition that you set up for the MiaRec SIP Trunk. Important! Recording will not work if CSS of the Recording Profile and phones do not match! The screenshot below shows None value, but in most production configuration, it should be explicitly set to the correct CSS.

Create Recording Profile

Create a route pattern/group for the recorder

This configuration step depends on how many recorders are used in a cluster, one or multiple.

For a single recorder, create a route pattern.

For multiple recorders in HA configuration, create a route group.

Single server configuration

Use the Call Routing > Route/Hunt > Route Pattern menu option in Cisco Unified Communications Manager Administration to create a route pattern for the MiaRec recorder SIP trunk:

  • Route Pattern should match to the directory number associated with MiaRec recorder. This DN is used to reach the SIP Trunk of MiaRec recorder. No user is going to directly call this number manually. Make sure it does not collide with your numbering plan. This is why the example shows '7777'.

  • Set Route partition to the partition that includes the user phones.

  • In Gateway/Route List select the SIP trunk that points to the announcement player

Reoute Pattern Configuration

Multiple servers configuration

How it works

Cisco Built-in-Bridge redundant recorder

Each recording server in Cisco UCM is configured as a separate SIP Trunk. Cisco UCM will failover automatically from the primary recording server to the secondary in case of failure.

Create a new Route Group

Use the Call Routing > Route/Hunt > Route Group menu option in Cisco Unified Communications Manager Administration to create a route group for the MiaRec SIP trunk:

  • Assign the previously created SIP trunk(s) to this route group at the Find Device to Add to Route Group pane. Select the desired SIP trunk(s) and click on the Add to Route Group button.
  • Set the Distribution Algorithm setting to Top Down. Note, the Circular algorithm is not suitable for call recording SIP Trunk because it causes CUCM to send one side of audio one recorder and another side to another recorder (during playback, you will hear one side of conversation).

Reoute Pattern Configuration

Create a new route list

Select Call Routing > Route/Hunt > Route List menu item and click on the Add New button.

  • Select the appropriate Cisco Unified Communications Manager Group and click on the Save button.
  • Click on the Add Route Group button at the Route List Member Information panel.
  • Select the previously created route group at the Route Group setting, then click Save.
  • At the Route List Configuration page click on the Save button.

Create a new route pattern

Route Pattern should match to the Recording Destination Address in the previously created recording profile:

  • Set Route partition to the partition that includes the user phones.
  • In Gateway/Route List select the route list of which the recorder is a member.

Reoute Pattern Configuration

Enable Built-in-Bridge for all phones (optional)

Built-in-Bridge setting can be enabled on per-phone basis or on system level (default to all phones).

Access the System > Service Parameters menu option in Cisco Unified Communications Manager Administration, select your CUCM server from the Server list and Cisco CallManager from the Service list:

Service Parameter Configuration

To enable Built-in-Bridge on system level change the option Clusterwide Parameters (Device - Phone) -> Builtin Bridge Enable to On:

Clusterwide Builtin Bridge Enable

Codecs configuration

Codecs iLBC, iSAC, L16 and AAC-LD should be disabled for Recording-Enabled devices as they are not supported by MiaRec recording system at the moment.

Use the System > Service Parameters menu option in Cisco Unified Communications Manager Administration to perform the necessary configuration.

Change the following settings of group Clusterwide Parameters (System - Location and Region):

  • iLBC Codec Enabled to Enabled for All Devices Except Recording-Enabled Devices
  • iSAC Codec Enabled to Enabled for All Devices Except Recording-Enabled Devices
  • Default Intraregion Max Audio Bit Rate to 64 kbps (G.722, G.711)

Codecs Configuration

Disable 256kpbs wideband codec

Latest models of Cisco phones support high quality 256kbps wideband codec for phone-to-phone communications withing the same region. Unfortunately, this codec is not supported by Cisco Built-in-Bridge recording method and it should be disabled otherwise internal calls between users will not be recorded.

Navigate to the System > Region menu option in Cisco Unified Communications Manager Administration and change per-region setting Max Audio Bit Rate to either Use System Default or 64 kbps (G.722, G.711) as shown in below screenshot.

256kbps Codecs Configuration

Recording of conference calls

Recording of conference calls on Cisco platform has the following limitations:

  • Cisco UCM doesn't support re-negotiated of audio codecs for calls which are recorded with Built-in-Bridge method.
  • The Cisco Software Conference Bridge supports only G.711 and 256k wideband codecs.

The following call scenario may occur:

  • One user makes a call to another user. If these two users use Cisco phones, then G.722 wideband codec is chosen for such call.
  • Then one of users tries to create a 3-way conference and add the third user to the conference.
  • CUCM creates a software-based conference to mix audio from three users. The software-based conference doesn’t support G.722 codec.
  • CUCM needs to re-negotiate codec with each of users and change it from G.722 to G.711.
  • But CUCM cannot do that because such call is recorded with BiB method and codec is fixed for such call.
  • As a result a user, who tries to create a conference is dropped from a conference.

There are two workarounds for this situation:

  1. Disable G.722 codec for users, which are recorded with BiB method.

  2. Allocate codec transcoding resources on Cisco platform to automatically convert audio from one codec to another on-flight.

To disable G.722 codec, change the setting G.722 Codec Enabled to Enabled for All Devices Except Recording-Enabled Devices.

G.722 Codecs Configuration

Troubleshooting issues with codecs

Follow the instructions in the following article to determine if issue with call recording is caused by codecs: