SBC R7.

0
Introduction

2015
IP to IP Application

• IP-to-IP application is no longer supported

• This application has been superseded by the SBC application

• Continued support for the IP-to-IP application will still be

available (until further notice) to customers running Version
6.8 or earlier
SIP Interface and SRD 6.8 Restrictions

• SIP interface :
• Must belong to one and only one SRD
• Per application type
• The reason for this restriction is for the sake of routing simplicity

• SRD :
• SRD is bounded to a specific layer 3 network

• Deployments Requiring Multiple SRDs

• SBC must perform NAT traversal
• SBC is configured with 2 different physical network interfaces
• Security rules for different networks
Multiple SRD’s R6.8 Example

• All the SRD entities must be on the same Layer 3 network

SRD 1 IP PBX LAN

SIP Interface 1
Physical Network 1 IP Interface 1
Media Realm 1

SRD 2 – SIP Trunk

SIP Interface 2
IP Interface 3 Physical Network 2 IP Interface 2
Media Realm 2

SIP Interface 3

Media Realm 3

SRD 3 - far-end users SRD 4

 SIP Trunk SRD R6.8 Example
Lync ITSP

E-SBC
SRD 1 SRD 2

Media Port Pool Media Port Pool

(Ports 7000-7500) SBC Tables: (Ports 6000-6500)
Classification
Routing Tables SBC SIP Interface
SBC SIP Interface Manipulation (UDP Port 5060)
(TLS Port 5067)
WAN
Enterprise Gateway Tables:
LAN IP-to-Tel
GW/IP2IP SIP Tel-to-IP GW/IP2IP SIP
Interface Routing Tables Interface
(UDP Port 5050) Manipulation (TCP Port 5070)

FXS E1

Lync clients Analog Lines

PSTN
 SIP Trunk SRD R7.0 Example
Lync E-SBC ITSP

DefaultSRD_0

Media Port Pool Media Port Pool

(Ports 7000-7500) SBC Tables: (Ports 6000-6500)
Classification
Routing Tables SBC SIP Interface
SBC SIP Interface Manipulation (UDP Port 5060)
(TLS Port 5067)
WAN
Enterprise Gateway Tables:
LAN IP-to-Tel
GW/IP2IP SIP Tel-to-IP GW/IP2IP SIP
Interface Routing Tables Interface
(UDP Port 5050) Manipulation (TCP Port 5070)

FXS E1

Lync clients Analog Lines

PSTN
 CMR Process - (Classify, Manipulate, Route)

Incoming Outgoing
Message Message
Classification Routing

Pre Inbound Outbound

classification MMS MMS
Manipulation
(SIP Interface) Inbound Outbound
Source and/or Source and/or
Destination Destination
Optional Number Number
CMR not changed in R7.0 Manipulation Manipulation
Main SBC concept changes in R7.0
• SIP Interface can serve more than one Application type
• Multiple SIP interfaces (e.g. WAN and LAN) can be bounded to a
single SRD
• SRD is not bounded to a specific layer 3 network
• DefualtSRD_0 and other entities are auto created
• On most single tenant use cases, SRD configuration is no longer
needed
• SRD function transitioned to become a tenant

• SRD fields added or moved to the SIP Interface

• SIP Interface in R7.0 “acts” like SRD in R6.8
- SIP Interface field is added to Proxy-set table, Routing tables and others
- The SIP interface now points media realm
- SIP Interface has Call Admission Control assigned
Main SBC concept changes in R7.0 (cont.)

• Multi Tenancy Environment

• Routing Policy
- Dedicated
- shared

• SBC Operation Mode

• B2BUA
• Call Stateful Proxy
Multi Tenancy/SRD Environment

• SBC device - serves a large number of enterprises

• Support and secure the IP communications requirements of

multiple enterprises simultaneously

• Provides per tenant configuration :

• Monitoring
• Reporting
• Analytics
• Alarms
• Interfacing

• Call admission control (CAC) can be effectively allocated per tenant

Routing Policy

• Routing Policies are intended only for multi-tenancy networks

• Routing policy should be used in case there is a need to

associate different routing decisions to different SRD’s

• Routing Policies allow each SRD (Tenant) to have it’s own:

• Routing rules
• Manipulations rules
• LCR
• LDAP based routing configuration
Routing Policy (cont.)

• The Routing Policy can be assigned to

• SRD table

• Classification table

• IP-to-IP Routing table

• IP to IP Inbound Manipulation table

• IP to IP Outbound Manipulation table

Multi Tenancy Configuration

• Isolated Tenant/SRD
• This tenant is totally isolated from other tenants, having its own
dedicated interfaces and routing rules

• Shared Tenant/SRD
• This tenant shares its interface/s with all the other tenants in
the network (e.g SIP Trunk)
Multi-tenant Architecture - Example
SBC Multi-Tenancy SIP resources

• Having multiple customers configured on a single SBC can lead to

“bleeding effect”

• Bleeding symptom may occur as a result of

• Configuration changes in one tenant may affect others
• Real time traffic of one tenant may affect others

• It is recommended to assign each tenant its own dedicated resources

• SIP Interface
• IP Group
• Proxy set
• Routing
• Classification
• Number manipulations
 Entities and Tables Relations (Partially)
SRD

SIP Interface IP Group Proxy set Routing Policy

Proxy Address
Assigned to :
 Admission Control table
 Proxy Set
 Classification table
 IP-to-IP Routing table
 Inbound IP Routing table
 Tel to IP Routing table Outbound Routing Table Inbound
Number Number
Configured per SIP Interface : Manipulations Manipulations
• Media Realm
• Direct media
• Maximum registered users
• Allow or deny unregistered/new
users
Configuration – General Recommendations

• Operate with a single SRD (Default SRD)

• Multi Tenancy Environment

• Not to define Routing Policy or multiple RP unless a specific
need was raised
• Assign each tenant its own dedicated resources :
- SIP Interface
- IP Group
- Proxy set
- Routing
- Classification
- Number manipulations
Configuration – General Recommendations (Cont.)
• If the SBC device is not operating in a multi-tenant
environment and multiple SRDs were used in an earlier
release, it is highly Recommended to gradually change the
configuration to a single SRD due to its many benefits

SBC R7.0

SRD 0

SRD 1 Default
SRD 1 0
SRD_0

SRD 2
Colorized SRD

• Distinguish color allocated for any new SRD is Created

• Wherever an entity in a table

is assigned to SRD the
colored box is displayed
alongside the SRD's name
SRD Cloning (duplicating)

• The SRD clone is assigned a unique name

• The SRD clone has identical settings as the original SRD

• All configuration entities associated with the original SRD are

also cloned associated

• Cloning can be done from the GUI or by CLI command

SRD 2 cloned Example

<unique ID>_<index of original SRD>_CopyOf_<name or index if no name of original SRD>.

SRD Filtering
• Filter all configuration tables throughout the Web GUI
according to a specific SRD
Proxy Set Tables

• Proxy set Parent table

• Proxy Address child Table

table
Routing Policy Related Tables

SBC Routing Policy

Table

IP to IP IP to IP
SRD Table Classification IP to IP
Inbound Outbound
Table Routing
Manipulation Manipulation

Note
If Routing Policy is assigned to a Classification rule in the Classification table, it overrides
the Routing Policy assigned to the SRD in the SRD table
Stateful Proxy Mode

• This feature provides support for the SBC device to operate as

a Stateful proxy server

• This capability enables the device to forward SIP messages

transparently (unchanged) between SIP endpoints

• When operating in Stateful proxy, the following dialog

elements are not changed by the SBC:
• Call identifiers
• Routing headers
• Replaces the value in the User-Agent/ Server header
Upgrading to R7.0 Notes
• Upgraded from an earlier release to R7.0
• The previous SRD configuration is fully preserved (functionality)
• The same number of SRDs is maintained
• The SIP Interface replaces the associated SRD in several tables
• SBC Routing Policy table is added and some tables are associated
- IP-to-IP Routing
- Inbound Manipulation
- Outbound Manipulation

• Constraints exist when upgrading from R6.8 to R7.0

• CLI Script file of 6.8 cannot be loaded to a 7.0 device
• Incremental ini file of 6.8 cannot be loaded to a 7.0 device
Upgrading From R6.8 to R7.0 – Reflected Changes examples (1)
R6.8

R7.0 - The same number of SRDs is maintained

R6.8

R7.0 – New fields added to the table – Pre classification set, Media Realm and others
Upgrading From R6.8 to R7.0 – Reflected Changes examples (2)

R7.0 – New table added

R6.8

R7.0 – New fields added to the table – SIP Interface, Routing Policy and others
Upgrading From R6.8 to R7.0 – Reflected Changes examples (3)

R7.0 – Parent table

R7.0 – Proxy IP Address child table

Contact us

training@audiocodes.com

Thank you

31