AudioCodes Mediant 800 User Manual page 869

CHAPTER 35 SBC Manipulations
Table 35-1: Inbound Manipulations Table Parameter Descriptions
'Routing Policy'
routing-policy-name
[IPInboundManipulation_
RoutingPolicyName]
General
'Index'
[IPInboundManipulation_
Index]
'Name'
manipulation-name
[IPInboundManipulation_
ManipulationName]
'Additional Manipulation'
is-additional-
manipulation
[IPInboundManipulation_
IsAdditionalManipulation]
'Manipulation Purpose'
purpose
[IPInboundManipulation_
ManipulationPurpose]
Match
Assigns an Routing Policy to the rule. The Routing Policy
associates the rule with an SRD(s). The Routing Policy also
defines default LCR settings as well as the LDAP servers if the
routing rule is based on LDAP routing (and Call Setup Rules).
If only one Routing Policy is configured in the Routing Policies
table, the Routing Policy is automatically assigned. If multiple
Routing Policies are configured, no value is assigned.
To configure Routing Policies, see
Policy Rules.
Note: The parameter is mandatory.
Defines an index number for the new table record.
Note: Each table row must be configured with a unique index.
Defines an arbitrary name to easily identify the manipulation rule.
The valid value is a string of up to 40 characters. By default, no
value is defined.
Determines whether additional SIP URI user part manipulation is
done for the table entry rule listed directly above it.
■ [0] No = (Default) Regular manipulation rule (not done in
addition to the rule above it).
■ [1] Yes = If the above row entry rule matched the call,
consider this row entry as a match as well and perform the
manipulation specified by this rule.
Note: Additional manipulation can only be done on a different SIP
URI, source or destination, to the rule configured in the row
above as configured by the 'Manipulated URI' parameter (see
below).
Defines the purpose of the manipulation.
■ [0] Normal = (Default) Inbound manipulations affect the
routing input and source and/or destination number.
■ [1] Routing input only = Inbound manipulations affect the
routing input only, retaining the original source and destination
number.
■ [2] Shared Line = Used for the Shared-Line Appearance
feature. This manipulation is for registration requests to
change the destination number of the secondary extension
numbers to the primary extension. For more information, see
Configuring BroadSoft's Shared Phone Line Call Appearance
for Survivability.
- 829 -
Mediant 800 Gateway & E-SBC | User's Manual
Configuring SBC Routing