Setting up Your AudioCodes SBC for SIPREC

This section describes how to set up your AudioCodes Session Border Controller for SIPREC, thereby enabling it to communicate with the Interaction Insights SIP Recording Server (SRS).

This section describes steps relevant for the SIPREC configuration. For additional information, refer to the User's Manual of the relevant SBC product, which can be downloaded from https://www.audiocodes.com/library/technical-documents.

➢ Do the following:
1. Verify your SBC has an appropriate SIPREC license (see Verify SIPREC License on SBC).
2. Set up secure signaling (TLS) and secure media (SRTP) context between the SBC and the SRS (see Set up TLS and SRTP Contexts).
3. Configure the SRS on your SBC (see Configure SRS on SBC).
4. Configure SIPREC rules for recording (see Configure SIPREC Rules).
5. For setting up double recording (for geo-redundancy, only applicable for Pro licenses):
a. Configure the redundant SRC on your SBC (see the above steps).
b. Configure the SBC to connect between corresponding recordings (see Set up Double SIPREC Recording).

Verify SIPREC License on SBC

SIPREC functionality is a licensed feature. Therefore, prior to configuring the SBC for SIPREC, make sure that its license key contains the SIPREC license feature.

➢ To verify SIPREC license on SBC:
1. Access the SBC's Web interface.
2. Open the License Key page (Setup menu > Administration tab > License folder > License Key).
3. Verify that the license key includes the "SIPREC Sessions" license and that it displays the correct number of licensed SIPREC sessions, as shown in the example below:

Your SBC license must contain at least the number of concurrent sessions licensed in your Interaction Insights tenant.

Set up TLS and SRTP Contexts

Generate a TLS context and an SRTP context to secure the communication of signaling and media between the SBC and the SRS. For instructions, refer to your SBC User Manual.

While configuring:

● Load a matching certificate to the SBC that is signed by the same Trusted Root CA as the SRS.
● Configure a matching port on both the SBC and the SRS for securing TLS communication.

Configure SRS on SBC

The SRS must be configured on the SBC as a SIPREC IP group so that the SBC can send SIPREC messages (call recordings) to the SRS server.

The following procedure describes how to configure the SRS on the SBC including:

■ SRS as a Proxy Set
■ SRS as an IP Group
➢ To configure the SRS:
1. Configure the address of the SRS, which is represented by the SBC as a Proxy Set configuration entity:
a. Open the Proxy Sets table (Setup menu > Signaling & Media tab > Core Entities folder > Proxy Sets).
b. Click New, and then configure a Proxy Set as follows:
◆ Enter a Name for the Proxy Set to identify the Sip Recording application.
◆ Assign a SIP Interface for SBC
◆ Assign the TLS Context you set up before (see Set up TLS and SRTP Contexts)

a. Click Apply.
2. Configure the SRS entity, which is represented by the SBC as an IP Group configuration entity. The address of the IP Group is determined by the Proxy Set that you configured in the previous step.
a. Open the IP Groups table (Setup menu > Signaling & Media tab > Core Entities folder > IP Groups).
b. Click New, and the configure the IP Group, assigning the Proxy Set.

c. Click Apply.

Configure SIPREC Rules

Prior to configuring SIPREC rules, your Interaction Insights tenant must have been configured on Azure. Check with your Live Platform Administrator.

A SIPREC rule defines the following:

■ IP Groups whose calls you want to record:
● 'Recorded IP Group' defines the SBC leg interfacing with the IP Group that you want to record
● 'Peer IP Group' defines the other IP Group(s) with which the 'Recorded IP Group' is making or receiving calls
■ Calling party that you want to record ('Caller'):
● Recorded Party records only calls made by the 'Recorded IP Group' (i.e., outgoing calls)
● Peer Party records only calls made by the 'Peer IP Group' (i.e., incoming calls)
● Both records calls made by both parties
■ SRS to where the SBC sends the recorded packets

Make sure that the calling party definition match the Call Direction definition of the related Device Recording Profile or Profiles (see Managing Device Recording Profiles). If they differ, requested calls may not be recorded.

Create as many SIPREC rules as needed to cover all requested recording scenarios.

The following example describes how to configure a SIPREC rule to record all calls made or received by the IP Group entity called "BranchNY-Users", and send the recordings to the SRS.

➢ To configure the rule:
1. Open the SIP Recording Rules table (Setup menu > Signaling & Media tab > SIP Recording folder > SIP Recording Rules).
2. Click New, then configure the rule:

3. Click Apply.

Set up Double SIPREC Recording

This section is only relevant for Interaction Insight tenants with a Pro license, where geo-redundancy is implemented.

First, set up the SBC with the redundant SRS (see the above steps). Once set up, the SBC will fork the SIPREC stream to both SRS instances, thus providing double recording.

To match duplicate recordings as belonging to the same call, both SRS instances must receive:

■ The same SIPREC metadata, and
■ The same AC‑Session‑ID header value

The AC-Session-ID, if enabled, is created and inserted at the beginning of a SIP call in the SIP INVITE message header. To enable it on the SBC, set the following parameter in the global INI file:

SendAcSessionIDHeader = 1