Use these commands to work with Session Recording Server (SRS) Group Clusters. An SRS is the target to which the SBC sends session recordings. Configuration details about SRSs are specified in an SRS Group Profile.

You can add up to four SRS Group Profiles to an SRS Group Cluster to enable sending four simultaneous recordings. An SRS Group Cluster is then associated with the call recording criteria you configure on the SBC. Refer to Servers - Call Recording Criteria - CLI

An SRS Group Cluster has common properties, including its name and a description. It also contains a maximum of four SRS Group Cluster Data configurations, each specifying an index and an SRS Group Profile.

Note: To configure the SRS call recording criteria, refer to Servers - Call Recording Criteria - CLI.

Command Syntax

% set global servers srsGroupCluster <unique srsGroupCluster name> 
   description <0-199 characters>
   minRecordingsCriteria
		minRecordingSession <0-4 characters>
		siprecEstablishmentTimeout <5-300 characters>
		siprecReEstablishmentTimeout <0-300 characters>
   srsGroupClusterData <0-3> 
   srsGroupId <SRS Group Profile name> 


Command Parameters

ParameterLengthDescription

srsGroupCluster

1-256<srsGroupCluster name> – Enter the SRS Group Cluster name.

description

0-199 characters<custom text> – Enter descriptive text about this SRS Group Cluster.

minRecordingSession


0-4

The SBC must establish the minimum number of recording sessions specified in this field within the time.  

Use this parameter to specify the minimum number of recording sessions to establish within the allotted time (siprecEstablishmentTimeout).

The default value is 0.

Modified: for 12.1.3

siprecEstablishmentTimeout


5-300

The time in seconds within which the SBC must establish the minimum number of recording sessions specified by minRecordingSession.

The default value is 60.

Modified: for 12.1.3

siprecReEstablishmentTimeout


0-300

The time in seconds within which the SBC must reestablish the minimum number of recording sessions if a SIPREC session fails in the middle of the recording.

The default value is 0.

Modified: for 12.1.3

srsGroupClusterData

0-3Data rows for the SRS Group Cluster.

srsGroupId

N/ASRS Group Profile to associate with this cluster.


Command Example

admin@TACKH% set global servers srsGroupCluster cliTest description primary srsGroupClusterData 0 srsGroupId srsTest0
[ok][2018-01-21 18:54:45]
[edit]
admin@TACKH% set global servers srsGroupCluster cliTest description secondary srsGroupClusterData 1 srsGroupId srsTest1
[ok][2018-01-21 18:55:02]
[edit]
admin@TACKH% commit
set global servers srsGroupCluster CLUSA minRecordingsCriteria minRecordingSession 2
commit
set global servers srsGroupCluster CLUSA minRecordingsCriteria siprecEstablishmentTimeout 60
Commit
set global servers srsGroupCluster CLUSA minRecordingsCriteria siprecReEstablishmentTimeout 20
commit
Note

In previous releases, the SBC supported running the startRecord command once to establish up to two recording streams either on the Ingress or the Egress call leg. The SBC now supports running the command twice, once for the Ingress call leg and once for the Egress call leg, to establish up to two streams in both directions simultaneously for the quad recording.