Page History
Add_workflow_for_techpubs | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Panel | |
---|---|
In This Section:
|
Info | ||
---|---|---|
| ||
Related articles: |
Use the following procedure to configure the
Spacevars | ||
---|---|---|
|
Triggering Call Recording from PSX
- Configure the
for for a basic call.Spacevars 0 product - Install SIPREC license on the
using the EMSSpacevars 0 product
using
.Spacevars 0 model3 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
Create a recorder profile on the PSX and configure call recording criteria of the recorder profile.
Include Page _Recordertype_recordingtype _Recordertype_recordingtype
Create Recorder ProfileConfigure Call Recording Criteria
Create a SIP signaling port on the
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.Spacevars 0 product 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)
Create a trunk group from the
for recording, including the following configurations:Spacevars 0 product Configure Media IP Interface Group name
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.
Add static routes toward the recorder.
The SIP SRS (SIPREC Recording Servers) redundancy requires the SRS servers to be provisioned as
ipPeers
in the SBC under specific zone and apathCheck
profile must be assigned withpathCheck
pings enabled on IP Peer level. Follow these steps to configure pathCheck Profile for an SRS IP:Create a pathCheck Profile.
Code Block language text % 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.
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
Check the pathCheck status.
Code Block language text > show table addressContext <addressContext_name> zone SIPREC_ZONE peerPathchkStatus
Triggering Call Recording from ERE
The SRS information and call recording criteria are configured for ERE using the SBC CLI or EMA.
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
assip-tcp.
Code Block % set addressContext <ADDRESS-CONTEXT> zone <ZONE> sipSigPort <SIP SIGNALLING PORT> transportProtocolsAllowed sip-tcp
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.Add static routes toward the recorder.
Create an SRS group profile. SRS group profiles group together a set of SRS servers to receive SIP call recordings.
CLI method:
Code Block % set global servers srsGroupProfile <srs_group 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> fqdn <FQDN _of_the_SRS> fqdnPort <port_of_the_SRS> ipTGId <Ip_Trunkgroup_Id> srtp <disable | enable> cryptoSuiteProfile <cryptoSuiteProfile> transport <udp | tcp>
Info title Notes - The option
cryptoSuiteProfile
is visible only when the flagsrtp
is enabled. - Specify either an FQDN or IP address for the SRS in the
srsGroupData
entry, not both.
- The option
EMA method: Go to All > Global > Servers > Srs Group Profile
Enabling SRTP in an SRS Group Profile
- Create an SRS group cluster. You can add up to four SRS group profiles to an SRS group cluster to enable sending four simultaneous recordings. An SRS group cluster is then associated with call recording criteria you configure on the SBC
CLI method:
For more information, refer to Servers - SRS Group Cluster - CLI- EMA method:
For more information, refer to Global - Servers - Srs Group Cluster - Srs Group Cluster Data
- Create sets of call recording criteria to trigger recording of calls that match.
CLI method:
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>
Refer to Servers - Call Recording Criteria - CLI for more information.
EMA method: Go to All > Global > Servers > Call Recording Criteria
Create New Call Recording Criteria Window
Refer to Global - Servers - Call Recording Criteria for more information.
To Trigger Recording of a Specific Call
Start recording of a specific call from the CLI or EMA using its GCID.
Info | ||
---|---|---|
| ||
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 start a recording, issue a
siprec startRecord
request. Execute the command for both 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>
EMA method:
- On the SBC main screen, navigate to All > Global > SIPrec.
- Select Start Record from the commands drop-down list.
Enter the start record options. Refer to Global - SIPrec for more information.
EMA Start Record Command- Click startRecord.
To Stop a Recording
Use one of the following methods to stop a recording.
CLI method:
Code Block language none % request global sipRec stopRecord gcid <GCID> [recorderAddress <SRS IP address> | recorderFqdn <SRS FQDN>] recorderId <session ID> recorderPort <port number>
Refer to Request Global - CLI for more information.
EMA method:
- On the SBC main screen, navigate to All > Global > SIPrec.
- Select Stop Record from the Commands drop-down list.
Enter the stop record options. Refer to Global - SIPrec for more information.
EMA Stop Record Command- Click stopRecord.
Info | ||
---|---|---|
| ||
Use the following combinations of parameters to specify which recording(s) to stop.
|
To View Information on Calls Being Recorded
To view the details of the calls being recorded from CLI or EMA:
CLI method:
Code Block language none > show table global SipRecStatus RECORDER RECORDING RX RTP TX RTP RECORDER RECORDER GCID ADDRESS LEG ADDRESS ADDRESS FQDN ID 555281 10.11.12.13:5060 ingress 10.11.12.13:8000 10.11.12.13:8002 1614567899
EMA method:
On the SBC main screen, navigate to All > Global > SIP Rec Status
SIP Rec Status Window