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.