AudioCodes Mediant 800B User Manual page 27

User's Manual
Configuration Terms
IP-to-IP Routing
IP-to-IP Inbound and
Outbound Manipulation
SBC Routing Policy
Call Admission Control
Accounts
Version 7.0
IP-to-IP routing rules define the routes for routing calls between SIP
entities. As the SIP entities are represented by IP Groups, the routing
rules typically employ IP Groups to denote the source and destination of
the call. For example, to route calls from the IP PBX to the SIP Trunk, the
routing rule can be configured with the IP PBX as the source IP Group
and the SIP Trunk as the destination IP Group.
Instead of IP Groups, various other source and destination methods can
be used. For example, the source can be a source host name while the
destination can be an IP address or based on an LDAP query.
IP-to-IP inbound and outbound manipulation lets you manipulate the user
part of the SIP URI in the SIP message for a specific entity (IP Group).
Inbound manipulation is done on messages received from the SIP entity;
outbound manipulation is done on messages sent to the SIP entity.
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 IP-to-IP 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 an SBC Routing Policy, which in turn, is assigned to IP-to-
IP routing rules. As most deployments require only one SBC Routing
Policy, the default Routing Policy is automatically assigned to the
manipulation rules and to the routing rules.
SBC 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 (CAC) lets you configure the maximum number of
permitted concurrent calls (SIP dialogs) per IP Group, SIP Interface,
SRD, or user.
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.
27
Description
Mediant 800B Gateway and E- SBC
1. Introduction