In This Section:
Use the following procedure to configure the SBC to establish call recordings triggered from the PSX or from the ERE.
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.
When SIPREC is selected as the Recorder Type, and Recording Type is selected as “both legs” and “all legs”, the SBC by default records the ingress leg.
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
Create a trunk group from the SBC for recording.
Ensure the name of the trunk group is is identical to the one used above while creating Recorder profile in PSX.
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 SBC 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
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
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.
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.
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
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>
EMA method
On the SBC main screen, navigate to All > Global > SIPrec. Select Start Record command from the commands drop-down list.
Click startRecord.
CLI method:
% request global sipRec stopRecord gcid <GCID> recorderAddress <IP Address> recorderPort <Port Number>
EMA method:
On the SBC main screen, navigate to All > Global > SIPrec. Select Stop Record command from the commands drop-down list.
Click stopRecord.
CLI method:
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]
EMA method:
On the SBC main screen, navigate to All > Global > SIP rec Status