Deploying SBC For SIPREC

In This Section:

Triggering Call Recording From PSX

Configure the
Unable to show "metadata-from": No such page "_space_variables"
for a basic call.
Install SIPREC license on the
Unable to show "metadata-from": No such page "_space_variables"
using the EMS.

Configure the external PSX.

% 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

Create a recorder profile on the PSX and configure call recording criteria of the recorder profile.
Note
- If there is more than one SRS associated with the SRS Cluster, the SBC records on both the legs (Ingress and Egress). The first two recordings are on Ingress leg and the rest on Egress.
- For Quad SIPREC, there are four recordings triggered. Two recordings are triggered on the Ingress leg and two on the Egress leg.
- If there is more than one SRS Group configured, it is recommended to set recordingType to "both legs" or "all legs".
Create Recorder Profile

Configure Call Recording Criteria
Create a SIP signaling port on the
Unable to show "metadata-from": No such page "_space_variables"
towards the recorder, and enable SIPREC.
```
% set addressContext <ADDRESS-CONTEXT> zone <ZONE> sipSigPort <SIP SIGNALLING PORT> siprec enabled 
```
Create a trunk group from the
Unable to show "metadata-from": No such page "_space_variables"
for recording.

Note

Ensure the name of the trunk group is is identical to the one used above while creating Recorder profile in PSX.
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
Unable to show "metadata-from": No such page "_space_variables"
through options ping mechanism, a recording session is initiated towards the secondary SRS and the recording continues.
```
% 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 
```

Note

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:

Create a pathCheck Profile:

% set profiles services pathCheckProfile <pathCheckProfile_name> protocol sipOptions
% commit

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:

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

Check the pathCheck status:

> 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.

Create a SIP signaling port on the SBC towards the recorder, and enable SIPREC.
```
% set addressContext <ADDRESS-CONTEXT> zone <ZONE> sipSigPort <SIP SIGNALLING PORT> siprec enabled 
```
Note

To support SIPREC INVITE over TCP, the sipSigPort, which is configured in the zone for SIPREC must have transportProtocolsAllowed as sip-tcp.
```
% set addressContext <ADDRESS-CONTEXT> zone <ZONE> sipSigPort <SIP SIGNALLING PORT> transportProtocolsAllowed sip-tcp
```
Create a trunk group from the SBC for recording.
```
% set addressContext <ADDRESS-CONTEXT> zone <ZONE> sipTrunkGroup <sipTrunkGroup>
```
Note

The same trunk group name must be used in CLI startRecord command and Start Record command of EMA GUI.
Add static routes toward the recorder.

Create Call Recording Criteria.

% 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>

Create an SRS Group profile.

% set global servers srsGroupProfile <srs_group_Id> loadDistribution <roundRobin | sequence> 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> transport <udp | tcp>

Start recording from the CLI or EMA.

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:
```
% 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.
  
  EMA Start Record Command
  
  Click startRecord.
To stop recording, use one of the methods below.
1. CLI method:
```
% 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.
  
  EMA Stop Record Command
  
  Click stopRecord.
To view the details of the calls being recorded from CLI or EMA
1. CLI method:
  
  Note
  
  If only the GCID value is mentioned in the stopRecord, all the multiple recordings for that GCID are stopped at once.
```
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
  
  SIPREC Status Example