Deploying SBC For SIPREC

Use the following procedure to configure the

Unable to show "metadata-from": No such page "_space_variables"

and PSX to establish call recordings triggered from the PSX.

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.

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.

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

Triggering Call Recording From CLI

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 
```
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>
```
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.
Start recording from the CLI or EMA.

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 trunkGroup <TRUNK GROUP NAME> srsIpAddress <SRS IP ADDRESS> srsPort <SRS PORT> transport <tcp | udp>

% request global sipRec startRecord gcid <GCID> callLeg egress trunkGroup <TRUNK GROUP NAME> srsIpAddress <SRS IP ADDRESS> srsPort <SRS PORT> transport <tcp | udp>
```
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>
```
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:
```
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

Space shortcuts

Page tree

Triggering Call Recording From PSX

Triggering Call Recording From CLI