Contents
- Access (UNI) Scenarios
- Minimal Out-Of-The-Box Configuration
- SIP UE Registration with AS
- SIP UE Registration Through IMS
- Basic Service Availability - DNS
- Call Termination with Primary Path Failure
- Protocol Repair
- CAC - CPS - Bandwidth Policing
- Denial of Service (DoS) Protection
- Distributed Denial of Service (DDOS) Protection
- Transmission Protocol Support
- Encryption Support
- Placing Call Restrictions on a Subscriber
- Configuring Residential Access
- Access VoLTE Deployments
- Peering (NNI) Scenarios
- SBC in a Network-Network Interface
- SBC in NNI as IBCF
- NNI-Basic Route Selection
- NNI-Complex route selection
- Availability-Reachability tracking by SBC
- Bi-lateral agreement enforcement through SBC
- SBC support for SIP-I to tunneling ISUP Signaling
- SBC as an IPX
- SBC Support for NNI Transmission Protocols
- SBC Support for NNI Encryption
- Peering Configuration Across Carriers
- Peering Configuration Across Carriers with Overlapping Addresses
- Peering VoLTE Deployments
- PCV Interworking Enhancement
- Configuring the Default Value of the ttc-Parameter of the PCV Header
- Session Timer Procedure Support in Early-dialog UPDATE
When networks using different levels of trust are interconnected, the prevailing security model is to create a gate through which all inter-network communications must pass; that is, a single point (or very limited number of points) at which security policies are enforced. In most scenarios, the greatest concern is generally when an external untrusted network communicates with a trusted network. The Ribbon SBC is positioned at the network border to guard the internal network (core network) from security threats.
The SBC can be deployed between two service provider networks in a peering environment (NNI), or between an access network and a backbone network to provide service to residential and/or enterprise customers.
Peering - (NNI) Deployment
To learn about Enterprise deployment scenarios, refer to Enterprise Deployment Scenarios.
To learn about H.323 deployment scenarios, refer to H.323 Deployment Scenarios.
Overview
Content Tools