AudioCodes Mediant 500 MSBR, User Manual

Page: 701 / 1248

Version 7.2 701 Mediant 500 MSBR
User's Manual 38. SBC Manipulations
INVITE sip: 1000 @10.2.2.3;user=phone;x=y;z=a SIP/2.0
To: <sip: 1000 @10.2.2.3;user=phone>
to
INVITE sip: 9721000 @ITSP;user=phone;x=y;z=a SIP/2.0
To: <sip: 9721000 @ITSP;user=phone>

Destination IP Group name (SIP URI host name) from "10.2.2.3" to "ITSP":
INVITE sip:1000@ 10.2.2.3 ;user=phone;x=y;z=a SIP/2.0
To: <sip:1000@ 10.2.2.3 ;user=phone>
to
INVITE sip:9721000@ ITSP ;user=phone;x=y;z=a SIP/2.0
To: <sip:9721000@ ITSP ;user=phone>
38.1 Configuring IP-to-IP Inbound Manipulations
The Inbound Manipulations table lets you configure up to 205 IP-to-IP Inbound
Manipulation rules. An Inbound Manipulation rule defines a manipulation sequence for the
source or destination SIP URI user part of inbound SIP dialog requests. You can apply
these manipulations to different SIP dialog message types (e.g., INVITE or REGISTER)
and SIP headers as follows:

Manipulated destination URI user part are done on the following SIP headers:
Request-URI, To, and Remote-Party-ID (if exists)

Manipulated source URI user part are done on the following SIP headers: From, P-
Asserted-Identity (if exists), P-Preferred-Identity (if exists), and Remote-Party-ID (if
exists)
Configuration of Inbound Manipulation rules includes two areas:

Match: Defines the matching characteristics of an incoming SIP dialog (e.g., source
host name).

Action: Defines the action that is done if the incoming call matches the characteristics
of the rule. In other words, the device manipulates the source or destination SIP URI
user part of the SIP dialog (e.g., removes a user-defined number of characters from
the left of the SIP URI user part).
Note: Configure stricter classification rules higher up in the table than less strict rules
to ensure the desired rule is used to manipulate the incoming dialog. Strict refers to
the number of matching characteristics configured for the rule. For example, a rule
configured with source host name and source IP Group as matching characteristics is
stricter than a rule configured with only source host name. If the rule configured with
only source host name appears higher up in the table, the device ("erroneously") uses
the rule to manipulate incoming dialogs matching this source host name (even if they
also match the rule appearing lower down in the table configured with the source IP
Group as well).
To configure and apply an Inbound Manipulation rule, the rule must be associated with a
Routing Policy. The Routing Policy associates the rule with an SRD(s). Therefore, the
Routing Policy lets you configure manipulation rules for calls belonging to specific SRD(s).
However, as multiple Routing Policies are relevant only for multi-tenant deployments (if
needed), for most deployments, only a single Routing Policy is required. As the device
provides a default Routing Policy ("Default_SBCRoutingPolicy"), when only one Routing
Policy is required, the device automatically assigns the default Routing Policy to the routing
rule. If you are implementing LDAP-based routing (with or without Call Setup Rules) and/or