In this section:
Default values are enclosed in square brackets [ ].
The SBC now collects interval-based SIP registration statistics per domain. This allows you to retrieve statistics for the current interval or a series of intervals using the SBC CLI.
The following is the syntax for retrieving per-domain SIP registration statistics for the current statistics interval.
> show status|table addressContext <addressContext_Name> sipRegCountDomainCurStats <DomainName>
The following is the syntax for retrieving per-domain SIP registration interval statistics.
> show status|table addressContext <addressContext_Name> sipRegCountDomainIntStats <DomainName>
The following statistic fields appear in the output.
To support specifying FQDNs for SRS servers, this feature adds FQDN-related parameters in the following four contexts.
To enable configuring SRS servers with FQDNs, the SBC adds fqdn
and fqdnPort
parameters to the srsGroupData
components in an SRS group profile.
% set global servers srsGroupProfile <profile name> description <0-199 characters> loadDistribution <roundRobin | sequence> numSimultaneousStream <1-2> srsGroupData <0-7> cryptoSuiteProfile <cryptoSuiteProfile> fqdn <FQDN> fqdnPort <0-65535> ipAddress <IP address> ipPort <0-65535> ipTGId <IP TG Id> srtp <disable | enable> transport <tcp | tls | udp>
Parameter | Length/Range | Description | M/O |
---|---|---|---|
fqdn | up to 63 characters | Specifies an FQDN for the SRS server. Specify either an FQDN or IP address for the SRS entry, not both. | O |
fqdnPort | 0-65535 | Specifies a TCP/UDP port number for the SRS FQDN. This option only becomes available after you configure an FQDN for the SRS. | O |
To enable initiating a recording through CLI using an FQDN, the SBC adds the srsFqdn1
and srsFqdn2
parameters for specifying a target SRS server in a SIPREC start record (startRecord
).
% request global siprec startRecord callLeg egress ingress gcid <0-2147483647> numOfStreams <1-2> srsFqdn1 <FQDN> srsFqdn2 <secondary FQDN> srsIpAddress <SRS IP address> srsIpAddress2 <secondary SRS IP address> srsPort <IP port number> srsPort2 <secondary IP port number> transport <tcp | udp> transport2 <tcp | udp> trunkGroup <trunk group name> trunkGroup2 <secondary trunk group name>
Parameter | Length/Range | Description |
---|---|---|
srsFqdn1 | up to 63 characters | Specifies the FQDN of the SRS server to use for this recording. If you specify both an FQDN and individual IP address, the IP address takes precedence. |
srsFqdn2 | up to 63 characters | Specifies the FQDN of a secondary SRS server to use if the media stream is forked. |
The SBC adds the recorderFqdn
and recorderId
parameters in SIPREC stop records (stopRecord
) to enable specifying the FQDN of an SRS server or a unique identifier for the recording session among the criteria that you can use to identify which recording session to stop.
% request global siprec stopRecord gcid <0-2147483647> recorderAddress <SRS IP address> recorderFqdn <SRS FQDN> recorderId <session ID> recorderPort <port number>
Parameter | Length/Range | Description |
---|---|---|
recorderFqdn | up to 63 characters | Specifies the FQDN of the SRS server on which to stop a recording. |
recorderId | Specifies the unique identifier of the recording session to stop. The user can determine the recorderId for a session using the show table global SipRecStatus command. |
An ANI-DNIS loop refers to a situation when more than one call request shares the same combination of ANI (Automatic Number Identification) and DNIS (Dialed Number Identification Service) values. This feature adds a new aniDnisZoneloopDetection
object to zones. This object has a state parameter to control whether ANI-DNIS loop detection is enabled and a parameter that defines the limit for loop instances per ANI-DNIS pair.
% set addressContext <addressContext name> zone <zone name> aniDnisZoneloopDetection aniDnisZoneLoopInstances <1..1250> aniDnisZoneState <disabled | enabled>
Parameter | Default | Description |
---|---|---|
| 1 | Use this parameter to specify an integer limit on call requests containing matching ANI-DNIS pairs. When the limit is reached, the SBC rejects any subsequent call requests for the same ANI-DNIS combination. The valid range is 1 to 1250. |
| disabled | Use this parameter to enable or disable ANI-DNIS loop detection for the specified zone.
|
Refer to Zone - ANI-DNIS Loop Detection - CLI for more information.
This feature adds a new signaling parameter for SIP trunk groups that controls whether the SBC locally handles OOD REFER requests.
% set addressContext <addressContext name> zone <zone name> sipTrunkGroup <trunkGroup name> signaling localOODReferSupport <disabled | enabled>
Parameter | Description |
---|---|
| Enable this flag to have the SBC locally handle out-of-dialog (OOD) REFER requests.
|
Refer to SIP TG - Signaling - Local OOD REFER Support - CLI for more information.
This feature adds a new configuration object, the Register Contact Profile, and a new zone option to assign a profile to a zone.
% set profiles signaling registerContactProfile <profile name> contactIncludeVariables <hostpart | userpart>
Parameter | Description |
---|---|
registerContactProfile <profile name> | Specifies a name for the Register Contact Profile of up to 23 characters. |
| Specifies the element or elements within the Contact header to use as additional keys when creating or retrieving registration control blocks (RCBs). The options are:
If specifying more than one value, separate the values with a comma, such as: |
% set addressContext <addressContext name> zone <zone name> registerContactProfileName <registerContactProfile name>
Parameter | Description |
---|---|
| Specifies the name of a Register Contact Profile to assign to a zone. The SBC uses the Contact header elements specified in the profile as additional keys when it creates or retrieves RCBs. |
For more information refer to Creating Multiple User Registrations Based on Contact Headers in REGISTER Messages.