In this section:
Request commands, such as the request global
command, are available in both System-level and Configure CLI modes.
Request Global
To initiate action on global objects, use the following command syntax.
Command Syntax
> request global callCountReset callTrace action command <start | stop> dnsClearCache dumpActiveRegistration dumpDeletedRegistration dumpGeneratedSubscription mediaCapture disabledByGcid gcid <0-2147483647> siprec terminateCall GCID <0-2147483647>
Command Parameters
SIPREC Commands
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". - 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.
Note
The SIPREC feature is controlled by a system-wide SBC license (SBC-SIPREC). If the license is not available, any SIPREC recording request returned by a PSX is ignored.
Note
To support SIPREC INVITEs over TCP, the sipSigPort configured in the zone sending the request must have transportProtocolsAllowed
set to "
sip-tcp". (Refer to Zone - SIP Sig Port - CLI).
Command Syntax
> request global siprec startRecord callLeg egress ingress gcid <0-2147483647> numOfStreams <1-2> srsFqdn1 <FQDN> srsFqdn2 <secondary FQDN> srsIpAddress <SRS IP address> srsIpAddress2 srsPort <IP port number> srsPort2 <Ip port number> transport <tcp | udp> transport2 <tcp | udp> trunkGroup <TRUNK GROUP NAME> trunkGroup2 stopRecord gcid <0-2147483647> recorderAddress <SRS IP address> recorderFqdn <SRS FQDN> recorderId <session ID> recorderPort <port number>
Command Parameters
Overview
Content Tools