On-Demand SIPREC using SIP 200 OK Responses

The device supports on-demand SIPREC sessions that are triggered (started) by the receipt of SIP 200 OK responses. The 200 OK response must contain AudioCodes proprietary X-AC-Action header with the value ‘start-siprec’ to initiate recording.

Once the device is triggered by a 200 OK response to start a SIPREC session, it can then be triggered to pause, resume, or stop recording at any stage of the call by the receipt of SIP INFO messages. For more information, see On-Demand SIPREC using SIP INFO Messages.

●

This feature applies only to SIP 200 OK messages received in response to initial SIP INVITE requests.

●

This feature doesn't require any configuration in the SIP Recording Rules table.

●

Upon the receipt of a SIP 200 OK response with the X-AC-Action header, the device doesn't trigger SIPREC in the following scenarios:

✔

The X-AC-Action header doesn't contain any parameters.

✔

The X-AC-Action header contains the 'start-siprec' parameter, but not the 'recording-ip-group' or 'recording-ip-group-set' parameter.

✔

Six SIPREC sessions are currently active (maximum).

✔

The X-AC-Action header contains the 'start-siprec' parameter on a recorded-side while there is an active SIPREC session on the other side.

●

The feature is applicable only to the SBC application.

The X-AC-Action header in the incoming SIP 200 OK response can also indicate the IP Group representing the SIPREC Session Recording Server (SRS), and the leg of the call to record. This information is provided in the X-AC-Action header using the following parameters and syntax:

X-AC-Action: start-siprec;<SRS Type>=<SRS Name>;recorded-side=peer

where:

■

<SRS Type> indicates if the SRS is an IP Group or IP Group Set:

●

recording-ip-group - SRS is defined by an IP Group(s). For configuring IP Groups, see Configuring IP Groups.

●

recording-ip-group-set - SRS is defined by an IP Group Set(s). For configuring IP Group Sets, see Configuring IP Group Sets.

■

<SRS Name> specifies the name or index number of the IP Group or IP Group Set. To specify multiple IP Groups or IP Group Sets, separate each with a comma (without spaces).

■

recorded-side=peer is an optional parameter indicating that recording must be done on the peer side. If this parameter is absent, the device records the side that received the X-AC-Action header.

The following shows an example of an incoming SIP 200 OK response that triggers the device to start a SIPREC session for the call and uses IP Group "SIPREC SRS" as the SRS:

SIP/2.0 200 OK
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKac1275750210
From: <sip:100@127.0.0.1;user=phone>;tag=1c232314132
To: <sip:200@127.0.0.1;user=phone>;tag=KQFIDPYDOBRHFIBVVBVE
Call-ID: 179268804129202415845@127.0.0.1CSeq: 1 INVITE
Contact: <sip:100@127.0.0.1>
X-AC-Action: start-siprec;recording-ip-group="SIPREC SRS"
Supported: em,100rel,timer,replaces
Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE
Server: Sip Message Generator V2.2.2.0
Content-Type: application/sdp
Content-Length: 214

If you want to record calls whose incoming SIP 200 OK responses lack the 'X-AC-Action: start-siprec' header, use SIP Message Manipulation rules to add the header.

If the X-AC-Action header contains only start-siprec, use the device's Message Manipulation feature (see Configuring SIP Message Manipulation) to add the parameters 'recording-ip-group' and optionally, 'recorded-side=peer'. The following shows an example of a Message Manipulation rule that indicates the use of a specific IP Group:

■

'Name': SRS for Start SIPREC by 200 OK

■

'Manipulation Set ID': 0

■

'Message Type': Message.Response.200

■

'Condition': Header.X-AC-Action contains 'start-siprec'

■

'Action Subject': Header.X-AC-Action

■

'Action Type': Modify

■

'Action Value': 'start-siprec;recording-ip-group="SIPREC SRS"'

Once configured, assign the Manipulation Set ID to the IP Group that sends the SIP 200 OK responses (i.e., not IP Group of SRS).

●

The manipulated parameters of the X-AC-Action header in the incoming 200 OK response are not reflected in the message of the outgoing leg.

●

If you want to record calls whose incoming SIP 200 OK responses lack the 'X-AC-Action: start-siprec' header, you can also use SIP Message Manipulation rules to add the header.