Page History

Use the following procedure to configure the

Triggering Call Recording From PSX

1. Configure the

   Spacevars
   0 product

    for a basic call.
   
   
2. Install SIPREC license on the

   Spacevars
   0 product

    using the EMS.
   
   

3. Configure the external PSX.

   Code Block
   language none
   % set system policyServer localServer PSX_LOCAL_SERVER mode outOfService state disabled % set system policyServer remoteServer <psx name> ipAddress <psx_ip> portNumber <psx_port> state enabled mode active

4. Create a recorder profile on the PSX and configure call recording criteria of the recorder profile.

   Include Page
   Recordertype_recordingtype Recordertype_recordingtype

   Caption
   0 Figure 1 Create Recorder Profile

   Caption
   0 Figure 1 Configure Call Recording Criteria

5. Create a SIP signaling port on the

   Spacevars
   0 product

    towards the recorder, and enable SIPREC. The Supported Transport protocols must match the protocol used in PSX. If TLS is used, set the corresponding TLS Profile in the SIP Sig port.

   Code Block
   language none
   % set addressContext <ADDRESS-CONTEXT> zone <ZONE> sipSigPort <SIP SIGNALLING PORT> siprec enabled

   Info
   title Note
   A Trunk group is configured towards the SRS server. As this is not a call processing TG, only the following TG attributes are used by the SBC when allocating resources towards SRS for a Recording session: Media IP Inteface Group Name SIP Signaling Port ( with "siprec" attribute enabled)

6. Create a trunk group from the

   Spacevars
   0 product

    for recording., including the following configurations:

   1. Configure Media IP Interface Group name

   2. Configure Metadata profile

      Info
      title Note
      Ensure the name of the trunk group is is identical to the one used above while creating the Recorder profile in the PSX.

7. Add static routes toward

   the recorder.
   

   If a secondary recorder is also configured on the PSX for redundancy, create IP peers with both primary and secondary recorder IP addresses and enable options ping for these recorders. While recording, if the primary Session Recording Server (SRS) is identified as DOWN by the

   Spacevars
   0 product

    through options ping mechanism, a recording session is initiated towards the secondary SRS and the recording continues.

   Code Block
   language none
   % set profiles services pathCheckProfile <path_check_profile> protocol sipOptions recoveryCount <count> replyTimeoutCount <count> sendInterval <interval> %set addressContext default zone $sbx_zone_rs_v4 ipPeer <IP_PEER_SRS> ipAddress <ip> ipPort <port> pathCheck profile <path_check_profile> state enabled

1. The SIP SRS (SIPREC Recording Servers) redundancy requires the SRS servers to be provisioned as ipPeers in the SBC under specific zone and a pathCheck profile must be assigned with pathCheck pings enabled on IP Peer level. Follow these steps to configure pathCheck Profile for an SRS IP:

1. 1. Create a pathCheck Profile

1. 1. .
      

      Code Block
      language text
      % set profiles services pathCheckProfile <pathCheckProfile_name> protocol sipOptions % commit

   2. Configure the SRS as an ipPeer in the SIPREC zone (the zone containing the Trunk Group configured for the SRS) and attach the pathcheck profile to it

1. 1. .
      

      Code Block
      language text
      % set addressContext <addressContext_name> zone SIPREC_ZONE ipPeer <ipPeer_name> ipAddress <SRS IP> ipPort <port> pathCheck profile <pathCheckProfile_name> state enabled % commit

   2. Check the pathCheck status

1. 1. .
      

      Code Block
      language text
      > show table addressContext <addressContext_name> zone SIPREC_ZONE peerPathchkStatus

Triggering Call Recording From ERE

The SRS groups and Call Recording Criteria are configured using ERE.

1. Create a SIP signaling port on the SBC towards the recorder, and enable SIPREC.

   Code Block
   language none
   % set addressContext <ADDRESS-CONTEXT> zone <ZONE> sipSigPort <SIP SIGNALLING PORT> siprec enabled

   Info
   title Note
   To support SIPREC INVITE over TCP, the sipSigPort, which is configured in the zone for SIPREC must have transportProtocolsAllowed as sip-tcp.

   Code Block
   % set addressContext <ADDRESS-CONTEXT> zone <ZONE> sipSigPort <SIP SIGNALLING PORT> transportProtocolsAllowed sip-tcp

2. Create a trunk group from the SBC for recording.

   Code Block
   % set addressContext <ADDRESS-CONTEXT> zone <ZONE> sipTrunkGroup <sipTrunkGroup>

   Info
   title Note
   The same trunk group name must be used in CLI startRecord command and Start Record command of EMA GUI.

3. Add static routes toward the recorder.

4. Create Call Recording Criteriaan SRS Group profile.

   1. CLI method:

      Code Block
      % set global servers

   callRecordingCriteria <call_recording_criteria_ID> srsGroupId

   1. srsGroupProfile <srs_group

   _ID>
   calledPartyId <called_party_number> callingPartyId <calling_party_number> egressTgId <egressTrunkGroup_ID> ingressTgId <IngressTrunkGroup_ID> nextHopIP <ipv4/ipv6_address_of_the_next_hop> nextHopIP <ipv4/ipv6address_of_the_next_hop> previousHopIP <ipv4/ipv6address_of_the previous_hop> recordingStopCriteria <manual | numOfCalls> numberOfCalls <Range 0 .. 99999> recorderType <SIPRec | mct> recordingDuration <Range 0..3600> recordingType <allLegs | bothLegs | egressLeg | ingressLeg> criteriaState <disable | enable>

   Create an SRS Group profile.

   Code Block% set global servers srsGroupProfile <srs_group_Id> loadDistribution <roundRobin | sequence>

   1. name> loadDistribution <roundRobin | sequence> description <string, min: 0 chars, max: 199 chars> numSimultaneousStream <range 1..2> srsGroupData <Priority_range 0..7> ipAddress <signaling ipv4/ipv6address_of_the_SRS> ipPort <signaling_port_of_the_SRS> ipTGId <Ip_Trunkgroup_Id> srtp <disable | enable> cryptoSuiteProfile <cryptoSuiteProfile> transport <udp | tcp>

      Info
      title Note
      The option cryptoSuiteProfile is visible only when the flag srtp is enabled.

   2. EMA method:

      Caption
      0 Figure 1 Enabling SRTP
      Image Added

5. Start recording from the CLI or EMA.

   Info
   title Note
   When recording is initiated from CLI/EMA, disable call recording criteria (or check that call recording criteria does not match); otherwise, recording is not initiated through CLI/EMA.

    

   1. CLI method

      To configure siprec startRecord request, execute the following command both on the ingress and egress legs:

      Code Block
      language none
      % request global sipRec startRecord gcid <GCID> callLeg ingress numOfStreams <Number of recorders 1 or 2> srsIpAddress <SRS IP ADDRESS> srsPort <SRS PORT> transport <tcp | udp> trunkGroup <TRUNK GROUP NAME> srsIpAddress2 <SRS IP ADDRESS> srsPort2 <SRS Port> transport2 <tcp | udp> trunkGroup2 <SIP Trunk Group> % request global sipRec startRecord gcid <GCID> callLeg egress numOfStreams <Number of recorders 1 or 2> srsIpAddress <SRS IP ADDRESS> srsPort <SRS PORT> transport <tcp | udp> trunkGroup <TRUNK GROUP NAME> srsIpAddress2 <SRS IP ADDRESS> srsPort2 <SRS Port> transport2 <tcp | udp> trunkGroup2 <SIP Trunk Group>

   2. EMA method

      On the SBC main screen, navigate to All > Global > SIPrec. Select Start Record command from the commands drop-down list.

      Caption
      0 Figure 1 EMA Start Record Command
      Image RemovedImage AddedImage Removed Image Added

      Click startRecord.

6. To stop recording, use one of the methods below.

   1. CLI method:

      Code Block
      language none
      % request global sipRec stopRecord gcid <GCID> recorderAddress <IP Address> recorderPort <Port Number>

   2. EMA method:

      On the SBC main screen, navigate to All > Global > SIPrec. Select Stop Record command from the commands drop-down list.

      Caption
      0 Figure 1 EMA Stop Record Command
      Image RemovedImage AddedImage Removed Image Added

      Click stopRecord.

7. To view the details of the calls being recorded from CLI or EMA
   

   1. CLI method:

      Info
      title Note
      If only the GCID value is mentioned in the stopRecord, all the multiple recordings for that GCID are stopped at once.

      Code Block
      language none
      show table global SipRecStatus RECORDING GCID RECORDER ADDRESS RX RTP ADDRESS TX RTP ADDRESS LEG ------------------------------------------------------------------------------ 1 10.54.80.200:5070 10.54.80.200:13471 10.54.80.200:13467 ingress 131072 10.54.80.200:5070 10.54.80.200:13471 10.54.80.200:13467 ingress [ok]

   2. EMA method:

      On the SBC main screen, navigate to All > Global > SIP rec Status
      

      Caption
      0 Figure 1 SIPREC Status Example
      Image Removed

1. 1. Image Added

2.  Create a SRS Group Cluster
   

   1. CLI method:
      For more information, refer to Servers - SRS Group Cluster - CLI
      

   2. EMA Method:
      For more information, refer to Global - Servers - Srs Group Cluster - Srs Group Cluster Data

3. Create Call Recording Criteria.

   Code Block

   % set global servers callRecordingCriteria <call_recording_criteria_ID> srsGroupId <srs_group_ID> calledPartyId <called_party_number> callingPartyId <calling_party_number> egressTgId <egressTrunkGroup_ID> ingressTgId <IngressTrunkGroup_ID> nextHopIP <ipv4/ipv6_address_of_the_next_hop> nextHopIP <ipv4/ipv6address_of_the_next_hop> previousHopIP <ipv4/ipv6address_of_the previous_hop> recordingStopCriteria <manual | numOfCalls> numberOfCalls <Range 0 .. 99999> recorderType <SIPRec | mct> recordingDuration <Range 0..3600> recordingType <allLegs | bothLegs | egressLeg | ingressLeg> criteriaState <disable | enable>

 pagebreak