|Ribbon Documentation Center|
Default values are enclosed in square brackets [ ].
NASS-IMS-Bundled-Authentication (NBA) is used to provide access to the IMS (IP Multimedia Subsystem) network for legacy equipment that cannot support IMS access security (IMS AKA). The authentication algorithm is enhanced to include and select NBA authentication.
The main objective of the NBA is to gain access to the IMS network, based on successful access level authentication. This is achieved by associating an IMS identity with a fixed specific location from where it is authorized to access from. The SBC Core infers an authentication scheme applicable to the user based on response from S-CSCF for initial REGISTER request. If S-CSCF selects NBA, it either sends 200 OK or 403 response. The SBC infers an NBA authentication scheme on receipt of 200 OK and follows procedures associated with NBA. So, P-CSCF switches to either NBA or SIP Digest w/o TLS based on S-CSCF's response. When NBA is in use, receiving a 401 (Unauthorized) response to the REGISTER request is not expected.
When P-CSCF receives a REGISTER from the UE, and once NBA is selected as the authentication scheme, P-CSCF contacts CLF over the e2 interface. P-CSCF performs a"Location Information Query" towards CLF using the E2 interface User-Data-Request and User-Data-Answer message exchange to learn the location information. CLF sends the response to P-CSCF including location information of UE using the given IP address / User-Name. Upon getting a response from CLF, P-CSCF inserts PANI header, appends NASS location information to SIP REGISTER message, and forwards REGISTER message towards IMS core, in order to authenticate UE.
The following parameters configure this feature:
<nassImsAuth>allows configuration related to NASS
<fiber>provision IP connectivity access associated with TISPAN NASS
<accessClass>parameter, when configured to
<tispan-NASS>, allows the SBC to identify if the request arrived on TISPAN NASS
<appId>to provision the diameter e2 interface
<clfRealm>allows configuration so the UDR message sent has a destination realm AVP with a CLF realm value
<ueDefaultLocation>specifies the default UE location name
<nassImsAuth> parameter is a new container, allowing configuration related to NASS. Under
<accessClass> is enhanced with a new value,
<appId> is enhanced with a new value,
The SBC SWe supports two levels of link detection for both standby and active Ethernet ports to monitor the health of the ports and to ensure the health of a standby port before initiating a switchover to it. By default, physical link detection is enabled on all ports configured in Link Monitor. This default mechanism checks for the presence of the cable and that the adjacent device is powered on. If hardware failures are detected they are reported to the SBC processes that monitor ports and a switchover can be triggered if the standby port is available.
A second level of link detection can be enabled that checks connectivity between a port and and a configured destination. The specific mechanism used to check the port depends on the whether the port is in an active or standby state. These probing mechanisms for link detection are available regardless of the number of ports attached to the SWe instance.
The current description for the
probeOnStandby flag (under
linkMonitor) is expanded to account for port redundancy as shown below. This description covers both SWe and non-SWe use of the option.
For the specified Link Monitor, use this flag to enable/disable probing the standby port to monitor the health of that port.
Note: This flag is only visible on SBC 7000 and SBC SWe Cloud systems.
Crankback functionality is triggered based on the presence, absence, or value of a SIP information element, for example, a proprietary header, parameter, or response code. This is provided by enhancing SMM capabilities.
To invoke crankback functionality, SMM is enhanced to include a predefined SMM variable for crank-back invocation. The SMM variable is assigned to one of the predefined action values. To invoke crank-back functionality, the SMM rule is added so that "nextRouteActionOnCrankBack" is set to a predefined action value. Whenever the SMM rules are met, the SBC takes crankback action based on the action value. The user can assign value to this using SMM rules.
nextRouteActionOnCrankBack is a predefined SMM operation parameter that configures crankback invocation for this feature.
Under this parameter are two options,
actionType>, the options <
AttemptNextRoute> determine how crankback is performed.
<generateAttemptRec>, the options
<false> determine if the attempt record will be generated for crankback attempts.
extRouteActionOnCrankBack SMM operation parameter is added. Under it are:
The S8 Home Routing (S8HR) uses the LTE S8 interface for transporting VoLTE traffic between the visited and home network as data traffic. The S8HR does not require IMS in the visited LTE network. In S8HR roaming architecture model of VoLTE, the Packet Data Network Gateway (PGW), Policy Charging and Rules Function (PCRF), and Proxy Call Session Control Function (P-CSCF) are in the Home Public Land Mobile Network (HPLMN) when the UE is roaming in a Visited Public Land Mobile Network (VPLMN). The S8HR roaming architecture provides all the IMS services to the UEs roaming in the VPLMN. In this scenario, the UE does not require any IMS network to network interface (NNI) between the VPLMN and HPLMN. A roaming user receives all the services of the home network in the S8HR model. In S8HR roaming model, the IMS/SIP/RTP traffic is tunneled back to the HPLMN like data traffic.
The visited S8HR user is authenticated using the GPRS-IMS-Bundled Authentication (GIBA) procedure and handles the emergency call. The flags
gibaSupportForS8hrInboundUserare added to the SIP Trunk Group to support the emergency call handling for S8HR model.
To support the emergency call in S8HR model, execute the following command:
To configure the VPLMN and HPLMN profiles, execute the following command:
To configure the flag
gibaSupportForS8hrInboundUser, execute the following command:
To attach the
to the SIP Trunk Group, execute the following command:
To attach the
vplmnProfile to the SIP Trunk Group, execute the following command:
The following parameters are added to the
The following attributes are added to the
Previously, the SBC invoked Media Resource Function (MRF) only for audio streams to achieve transcoding. Non-audio streams were relayed end-to-end even when the audio was sent to MRF.
Teletype (TTY) is the legacy service offered through encoding text characters as tones that are embedded in a carrier (PCMU, PCMA, or EVRC) media stream. The T.140 streams carry text as a separate payload.
With this feature, the SBC invokes MRF for T.140 and TTY interworking to achieve transcoding (see the following call flow). When T.140 and TTY interwork, text characters exchange between the T.140 stream and the tones carried inband with the audio.
This feature modifies the
callDetailStatus parameter by enhancing the
mediaTypeStream<X> statistic to
transcode for text streams when the SBC invokes MRF for T.140 and TTY interworking.
The SBC SWe and SBC SWe Cloud are enhanced to provide the configuration provisioning support using CLI and EMA. The provisioning limits can be configured based on the available RAM capacity. To achieve this functionality, the table
sweConfigProfileSelection is configured under system.
The SBC supports following two configuration profiles to configure the provisioning limits:
small: applicable to the VM RAM >=10 GiB
large: applicable to the VM RAM >=18 GiB
media codecEntry configuration for G.711 adds the
honorToneDetection flag in the
A new Flag rfc7332ValidateMaxForwards is added in SipTrunkGroup signaling configuration in INGRESS side.
The default value for rfc7332ValidateMaxForwards is
disable. If rfc7332ValidateMaxForwards is enabled, the SBC will use the Max-Forwards header value received from the end-user, and decrements this header value by 1 before forwarding it to the other end-user. If the value received from the end-user is 0 or 1, the SBC will discard that request with an error response of "483 - Too Many Hops."
sipTrunkGroup media configuration adds
hpcCallProfile configuration adds the
The SBC supports Rsyslog as a method of sending event messages to a syslog server. It now has enhanced Rsyslog service with a number of new features:
Allow new configuration to specify which /var/log/ files to transfer over syslog
Allow a mechanism to capture Linux session console logs and transfer via syslog
New hyperthreading support affects various table options, parameters, and profiles in:
show table system
JITC requires the audit (.AUD) and security (.SEC) logs to be cryptographically protected. Since both logs are required to be hashed, this functionality is extended to support the hashing of all Event Logs on the SBC.
The SBC can be configured to provide counts of the number of times different SIP responses codes are either sent or received during a statistics interval. Statistics of this type can provide insight into call-related or registration-related failures within the network. You can enable collection of current and interval SIP response code statistics on specific SIP trunk groups or IP peers. By default collecting SIP response code statistics is disabled on SIP trunk groups and IP peers.
When enabled, the statistics are stored in the following four tables. Refer to Interval Statistics - CLI for information on the parameters that control collection of interval statistics.
In addition to identifying the specific trunk group or IP peer to which they apply, entries in the table include:
Two new flags are added, one within IP peer and one within trunk group configuration, to enable collecting SIP response code statistics on specific objects of that type.
The SBC supports SIPREC when the SIPREC specifications were in early drafts (draft-ietf-siprec-xx-06). With the implementation of this feature, the SIPREC standard has evolved to RFCs (RFC 7245, RFC 7865, RFC 7866, and RFC 8068), and provides capability for supporting "dynamically programmable" selection of metadata content.
The profile sipRecMetaDataProfile is introduced to the services to provide the capability to configure the headers that are mapped from the target call leg to the XML and the corresponding metadata XML element name.
In case of a basic call, all information is copied from the initial-INVITE message on the leg where the tap is, to the metadata XML. However, "To" header and "to-tag" is copied additionally from the local information (as to-tag does not present in the INVITE).
In case of SIPREC trigger during REFER based transfer, irrespective of where the SIPREC tap is, all information is copied from the initial-INVITE of the new call leg towards the transfer target (C party).
In case of CLI triggered recording, the existing implementation of sending predefined information in metadata XML remains same (gcid, call-id, from, to). The new configuration of header-metadata mapping is not considered in this scenario.
sipRecMetadataProfile is added to the SRS Trunk Group to configure the metadata format.
The following parameters are added to the profile
The SBC, which continuously captures encrypted signaling packets of SIP over TLS at layer 2, has been enhanced to to capture decrypted signaling packets as well.
The SIP PDUs (Protocol Data Units) are captured at the application layer and continuously streamed to the monitoring server. Configurable Headers are included in SIP PDUs to enable the monitoring server to decode SIP signaling properly. Headers have source and destination IP address/Port information along with additional information which is configurable – this information is needed by the monitoring server in order to correlate the stream received.
The packet is captured at ingress leg without SMM applied and with SMM applied on egress leg, which is essentially what is being sent on the wire. To lessen performance impact, all socket-management activities to the monitoring server use a separate SIPSM (SIP Signaling Monitor ) process receives all signaling packets from the SIP Signaling Gateway (SIPSG) and streams to the configurable external monitoring server either over UDP or TCP.
A profile attached to the signaling port is a trigger for this feature. All feature-related configuration can be set in this profile.
The CLI adds a Monitoring Profile to configure monitoring server, filters, header names and select from the fixed set of information.
The SBC is enhanced to support sending encrypted media streams (Secure Real-Time Transport Protocol (SRTP)) towards the SIPREC recorders.
The following parameters are added to the SRS Group Data to support whether the Secure Real-Time Transport Protocol (SRTP) is enabled for the call or not. The cryptoSuiteProfile is an existing parameter. The parameter cryptoSuiteProfile is configured under profile and security and can be attached to the SRS Group Data.
The Ribbon SBC is enhanced to secure management of user accounts and passwords on its OpenStack versions. Default passwords have been eliminated in favor of injected credentials. SSH keys for users linuxadmin and admin are now pushed using the User Data section of the HEAT template.
Because the sftpadmin account is deleted, the associated CLI is also removed.
This feature implementation globalizes the Request-URI. Currently, when the To-Header Transparency flag is set, it is also sending the Request-URI transparently even when the globalization flag is enabled. When set, the To-Header Transparency should not send the called number in the Request-URI locally. Request-URI globalization should be independent of the To-Header Transparency.
For this feature, Request-URI is globalized when globalization for the called number is enabled and if the To-Header Transparency flag is enabled, Request-URI called number will not be transmitted transparently to the egress leg. To-Header transparency flag will not affect Request-URI globalization.
Enables flag to transparently copy the Request URI from the incoming message to the outgoing message for INVITE, REGISTER, SUBSCRIBE/NOTIFY. Provision this flag on the egress leg (with respect to the message direction).
enumDomainName forwardersData configuration adds the
eDNSType flag and
eDNSBufferSize parameter. The
servers lwresdProfile configuration adds the
Note: The M-SBC does not support this feature.
The SBC uses the signaling interface to send ENUM queries, in addition to sending ENUM queries from the management interface. ENUM queries are properly marked, and packets from the signaling interface receive higher priority, when ENUM queries are sent through the signaling interface.
The signalingIp parameter is added to the type field of the servers lwresdProfile configuration. Set the servers lwresdProfile type to signalingIp to send the ENUM queries through the signaling interface using the sipSigPort IP address. The signaling interface uses port 988 to send and receive the queries.
When lwresdProfile type is configured as signalingIp, configure the addressContext, zone, sipSigPort, and ipInterfaceGroupName parameters with the correct combinations as configured during sipSigPort.
staticRoutefor the ENUM server, and this configuration includes the
servers lwresdProfile typeconfiguration adds the
lwresdProfilecan attach the
enumArsProfileId. Configure this profile ID for black listing and white listing in the
enumArsProfile, which is added to the
A new parameter, sipRegCountDomainStats, is added and can be used with both show status and show table commands. An address context must be specified and specifying a domain is optional. If a specific domain is not specified the command returns per-domain statistics for up to 256 domains. The command returns no data if there are no domain names found.
show status addressContext <AC_Name> sipRegCountDomainStats <DomainName>
show table addressContext <AC_Name> sipRegCountDomainStats <DomainName>
The following existing CLI command is extended to also reset the cumulative domain-based statistics (countAttempt, countCumCompletion, emergAcceptTotal) for all domains:
request addressContext <AC_Name> sipRegCountReset
With the implementation of this feature, the SBC is enhanced to support:
Remove any non-essential headers that are added by the user agent, including the Subject, Call-Info, Organization, User-Agent, Reply-To, and In-Reply-To.
To configure this feature, the
privacyProfile is added to the services.
The following flags are added to the
Command / CLI Object Impacted Deprecated CLI Effective Release
show table systemCongestionStatus
set system congestion
"static" option 4.2.6R0
set system congestion adaptive MCLevel
"mc0" level 4.2.6R0
set profiles system overloadProfile
set profiles system overloadProfile
"memory" option for setDuration, clearDuration, setThreshold, clearThreshold configurations 4.2.6R0
set system admin
request system admin command
show status system serverSoftwareUpgradeStatus
show status addressContext <addressContext name> sipSubCountStatistics
request system admin <system Name> revertSoftwareUpgrade
request system admin <system Name> commitSoftwareUpgrade
5.0.0R0 H.323 IP Signaling Profile
5.1.0R0 Packet Service Profile
show table global siprecStatus
show status system
show table system