You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

In this section:

Related articles:

The

Unable to show "metadata-from": No such page "_space_variables"
 supports configuring multiple Session Recording Servers (SRSs) on the ERE using the SRS Group Profile. The SRS Group Profile includes common properties, such as load distribution and number of simultaneous streams, for a list of SRSs. The SRS Group Profile ID is associated with the callRecordingCriteria. Each SRS group will allow configuring up to maximum of eight SRS group data configurations for each SRS Group Profile.

 

Note

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

 

Command Syntax

% set global servers srsGroupProfile <profile name>
	description <0-199 characters>
	loadDistribution <roundRobin | sequence>
	numSimultaneousStream <1-2>
	srsGroupData <0-7>
		cryptoSuiteProfile <cryptoSuiteProfile>
        ipAddress <IP address>
		ipPort <IP port>
		ipTGId <IP TG Id>
		srtp <disable | enable>
        transport <tcp | tls | udp>

 

Command Parameters

SRS Group Profile Parameters

ParameterLength/RangeDescription
<profile name>0-23 charactersSRS Group Profile name.

description        

0-199 characters

<custom text> – Descriptive text about this SRS Group Profile.

loadDistribution     

N/A

The load distribution scheme for this SRS Group Profile.

  • roundRobin
  • sequence (default)

numSimultaneousStream

1-2

The number of simultaneous media streams for this SRS Group Profile. (default = 1)

srsGroupData         

0-7

<Index> – The index number for this SRS group data configuration. The SBC supports up to eight SRS group data configurations.

  • cryptoSuiteProfile –The unique identifier for the crypto suite profile.

    • If cryptoSuiteProfile is configured, the encryption technique towards SRS utilizes the crypto suite of the SBC (crypto suite of CS is discarded).

    • If cryptoSuiteProfile is not configured in the SBC, the encryption technique towards SRS utilizes the negotiated crypto suite details of the respective CS tap leg (ingress tap leg/egress tap leg).
      Note: The cryptoSuiteProfile is configured only under profile security and can be attached to the srsGroupData.

  • ipAddress – Signaling IP address of this SRS (The values "0.0.0.0" or "0::0" are not allowed).
  • ipPort – TCP/UDP port for this SRS.
  • ipTGId – IP TG Id used to initiate the session towards the SRS.
  • srtp – Specifies whether the SRTP is enabled for the SRS or not.
  • transport – The transport type for this SRS.
    • tcp
    • tls
    • udp (default)
 

  • No labels