Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Noprint
Panel
borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Content

Back to SBC Network Deployment Scenarios

Panel

In this section:

Table of Contents

The SBC can be deployed using SIPREC by configuring call recording from the PSX or ePSX.

Triggering Call Recording From PSX

...

 

Use the following procedure to configure the

Spacevars
0product
 and PSX to establish call recordings triggered from the PSX. 

Procedure

  1. Configure the

...

  1. Spacevars
    0product
     for a basic call.

  2. Install SIPREC license on the

...

  1. Spacevars
    0product
     using the EMS.

  2. Configure the external PSX

...

  1. .

    Code Block
    languagenone
    % 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
  2. Create a recorder profile

...

  1. on the PSX.

    Caption
    0Figure
    1Create Recorder Profile

    Image Modified

  2. Configure Call recording criteria

...

  1. on the PSX.

    Caption
    0Figure
    1Configure Call Recording Criteria

    Image Modified

  2. Create a SIP signaling port

...

  1. on the

    Spacevars
    0product
     towards the recorder, and enable SIPREC.

    Code Block
    languagenone
    % set addressContext <ADDRESS-CONTEXT> zone <ZONE> sipSigPort <SIP SIGNALLING PORT> siprec enabled 
  2. Create a trunk group from the

...

  1. Spacevars
    0product
     for recording.

    Note
    Ensure the name of the trunk group is is identical to the one used above while creating Recorder profile in PSX.
  2. Add static routes toward the recorder.

  3. If a secondary recorder is also configured

...

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

...

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

    Code Block
    languagenone
    % 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

...

Triggering Call Recording From CLI

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

...

languagenone

...

  1.  

...

  1.  

...

  1.  

...

  1.  enabled 

...

Create a trunk group from the SBC for recording.

...

...

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

 

...

CLI method.

Code Block
languagenone
% request global sipRec startRecord gcid <GCID> callLeg <ingress/egress> trunkGroup <TRUNK GROUP NAME> srsIpAddress <SRS IP ADDRESS> srsPort <SRS PORT> 

...

EMA method:

Caption
0Figure
1EMA Start Record Command

Global > Siprec

Image Removed

...

CLI method:

Code Block
languagenone
% request global sipRec stopRecord gcid <GCID>

...

EMA method:

Caption
0Figure
1EMA Stop Record Command

Global > Siprec

Image Removed

...

CLI method:

Code Block
languagenone
> show table global sipRecStatus
           RECORDER       RX RTP               TX RTP       RECORDING 
GCID       ADDRESS        ADDRESS             ADDRESS         LEG
1     10.54.96.8:5060   10.54.96.8:8000   10.54.96.8:8002   ingress

...

0Figure
1SIPREC Status Example

Global > Siprec Status

...

Pagebreak