Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fixed incorrect and missing information.

Add_workflow_for_techpubs
AUTH1
JIRAIDAUTHSBX-66500
REV5
REV6
REV3
REV1

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 call recording criteria you configure on the SBC. Refer to Servers - Call Recording Criteria - CLI

An SRS Group Cluster has common properties which include 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.

Info

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

 

Command Syntax

Code Block
% set global servers srsGroupCluster <SRS<unique GroupsrsGroupCluster Id>name> 
   description <description><0-199 characters> 
   srsGroupClusterData <0..3 Range> -3> 
   srsGroupId <SRS Group Id>Profile name>

 

Command Parameters

Caption
0Table
1Command Parameters for srsGroupCluster
ParameterLengthDescription 

srsGroupCluster

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

description

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

srsGroupClusterData

0-3  Data rows for the SRS Group Cluster.

srsGroupId

1-256

N/ASRS Group Cluster Name 
 
Profile to associate with this cluster.
 

Command Example

Code Block
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
Info

In previous releases, the SBC supported executing the startRecord CLI command once to establish up to two recording streams on either the ingress or egress call-leg. The SBC now supports executing the command twice: once for ingress call-leg and once for the egress call-leg, to establish up to two streams in both directions simultaneously for quad recording.

 

Pagebreak