About configuring Avaya SBC for recording media sessions

Last Updated : Sep 18, 2025 |

Avaya SBC supports a SIPREC-based solution to enable recording media sessions between Avaya SBC and a SIP Recording Server for SIP calls between remote workers and SIP trunk calls. The SIPREC configuration for remote worker and SIP trunking are the same, except for differences in server flow configuration towards the recorder. Audio recording supports IPv6, IPv4, and ANAT addressing on the SIPREC interface.

In a conference call recording scenarios, some recording vendors require additional information to identify mixed media streams coming from the conference bridge. Hence, conference media stream participant information is updated with configured conference URI. Avaya SBC and the recording vendor use this conference URI to identify the mixed media streams.

For Hairpin calls, Avaya SBC records the media only once and optimizes the subsequent SIPREC sessions. Avaya SBC provides an option to enable or disable this optimization. Optimization should be disabled where customer is looking for each individual participant media (stereo recording) for participants involved in a call.

In Lineside SIPREC solution, Avaya SBC avoids creating SIPREC sessions for unauthenticated SIP calls.

For SIPREC capacities, see Avaya Session Border Controller Overview and Specification.

Avaya SBC supports SIPREC with transcoding when the main call is transcoded. Avaya SBC does not support transcoding to the Recorder. You must ensure that G.729AB or G.711 is configured on either side of the media rules, although transcoding can happen with different codecs.

This chapter contains procedures for administering the SIPREC recording configuration. Before adding configurations for SIPREC recording, you must first configure SIP trunking on Avaya SBC.

Licensing for SIPREC sessions

A single SIPREC session requires one standard license and one advanced license for every non-encrypted recorded call. A single SIPREC session on an encrypted call also requires one standard license and one advanced license. However, an encrypted call with multiple SIPREC sessions requires one standard license and multiple advanced licenses depending on the number of SIPREC sessions.

For example, a SIP trunk call that is being recorded across three destinations requires one standard license and one advanced license for the SIP trunk call, plus two additional advanced licenses, for a total of one standard license and three advanced licenses. The same rules apply for an encrypted SIP trunk being recorded across three destinations: one standard license and three advanced licenses.