RR - Request Recording

Layer	CTI
Direction	From CallGem
Type of Service	CG
Interface ID	CT
Message Purpose	This message is a companion to the Request Recording [RR] - Agent to Dialer message. The Request Recording [RR] message requests a full-duplex record session to be initiated or stopped for the specified call session. The telephony layer should respond with a Recording Acknowledge [RA] message once it has attempted to initiate or stop recording.
Example	RR\TDdefault\CNCustCare\SIABC012345\ON
Explanation	A request has been made to record the call with session identifier ABC012345 on the CustCare campaign.
Notes	Related Links: Request Recording [RR] - Agent to CallGem

Parameters

Code

Name

Type

Mandatory?

Min Val

Max Val

Description

CampaignName

string

true

User defined parameter values may include any characters except / \ : * ? " < > | & % + ! ' ;

OperationKey

string

false

Recording operation key - supports concurrent call recording for a single call. The KY parameter on RR and RA messages identifies the recording to be controlled.

MediaFormat

int

false

The media format parameter tells the telephony layer exactly which format the recording is to be saved in. If a media format is not specified, the default media format supported by the gateway is used. Valid values are:

0	G.711 muLaw or ALaw wav
1	16KBit/s Compressed wav

OnOff

boolean

false

If this parameter is specified recording will be enabled. If not specified, recording will be disabled.

RecordingFilename

string

false

1024

Recording Filename parameter

SessionIdentifier

string

true

120

Either the TN or the SI parameter must be used to identify the called party. Session Identifiers.

TenantDescriptor

string

false

This parameter is alphanumeric and identifies to which tenant this message applies.

TelephoneNumber

string

false

Either the TN or the SI parameter must be used to identify the called party. Session Identifiers.

RecordingUniqueIdentifier

string

false

From V10.6.431 - If this recording is the main recording made for this call session it will be assigned a globally unique identifier. This will propagate to the agent layer on the Recording Acknowledge message. The parameter will only be set for recording requests made without an operation key (KY) parameter.