EasyManuals Logo

AudioCodes E-SBC User Manual

AudioCodes E-SBC
1414 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #43 background imageLoading...
Page #43 background image
CHAPTER1 Introduction
Mediant 1000 Gateway & E-SBC | User's Manual
Configuration
Terms
Description
Inbound manipulation lets you manipulate the user part of the SIP URI for
source (e.g., in the SIP From header) and destination (e.g., in the Request-
URI line) in the incoming SIP dialog request. Outbound manipulation lets you
manipulate the user part of the Request-URI for source (e.g., in the SIP From
header) or destination (e.g., in the SIP To header) or calling name, in
outbound SIP dialog requests.
The Inbound and Outbound manipulation are associated with the SIP entity,
by configuring the rules with incoming characteristics such as source IP
Group and destination host name. The manipulation rules are also assigned a
Routing Policy, which in turn, is assigned to IP-to-IP routing rules. As most
deployments require only one Routing Policy, the default Routing Policy is
automatically assigned to the manipulation rules and to the routing rules.
Routing Policy Routing Policy logically groups routing and manipulation (inbound and
outbound) rules to a specific SRD. It also enables Least Cost Routing (LCR)
for routing rules and associates an LDAP server for LDAP-based routing.
However, as multiple Routing Policies are required only for multi-tenant
deployments, for most deployments only a single Routing Policy is required.
When only a single Routing Policy is required, handling of this configuration
entity is not required as a default Routing Policy is provided, which is
automatically associated with all relevant configuration entities.
Call
Admission
Control
Call Admission Control (CAC) lets you configure the maximum number of
permitted concurrent calls (SIP dialogs) per IP Group, SIP Interface, SRD, or
user.
Accounts Accounts are used to register or authenticate a "served" SIP entity (e.g., IP
PBX) with a "serving" SIP entity (e.g., a registrar or proxy server). The device
does this on behalf of the "served" IP Group. Authentication (SIP 401) is
typically relevant for INVITE messages forwarded by the device to a
"serving" IP Group. Registration is for REGISTER messages, which are
initiated by the device on behalf of the "serving" SIP entity.
The associations between the configuration entities are summarized in the following figure:
- 5 -

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the AudioCodes E-SBC and is the answer not in the manual?

AudioCodes E-SBC Specifications

General IconGeneral
BrandAudioCodes
ModelE-SBC
CategoryGateway
LanguageEnglish

Related product manuals