AudioCodes Mediant 500 E-SBC, User Manual

Page: 292 / 920

User's Manual 292 Document #: LTRT-10437
Mediant 500 E-SBC
An example of configured message manipulation rules are shown in the figure below:
Figure 18-4: Message Manipulations Page

Index 0: Adds the suffix ".com" to the host part of the To header.

Index 1: Changes the user part of the From header to the user part of the P-Asserted-
ID.

Index 2: Changes the user part of the SIP From header to "200".

Index 3: If the user part of the From header equals "unknown", then it is changed
according to the srcIPGroup call’s parameter.

Index 4: Removes the Priority header from an incoming INVITE message.
Table 18-2: Message Manipulations Parameter Descriptions
Parameter Description
Index
[MessageManipulations_Ind
ex]
Defines an index number for the new table record.
Note: Each rule must be configured with a unique index.
Manipulation Name
CLI: manipulation-name
[MessageManipulations_Ma
nipulationName]
Defines an arbitrary name to easily identify the Message
Manipulation rule.
The valid value is a string of up to 16 characters.
Manipulation Set ID
CLI: manipulation-set-id
[MessageManipulations_Ma
nSetID]
Defines a Manipulation Set ID for the rule. You can define the same
Manipulation Set ID for multiple rules to create a group of rules. The
Manipulation Set ID is used to assign the manipulation rules to an IP
Group (in the IP Group table) for inbound and/or outbound
messages.
The valid value is 0 to 19. The default is 0.
Matching Characteristics
Message Type
CLI: message-type
[MessageManipulations_Me
ssageType]
Defines the SIP message type that you want to manipulate.
The valid value is a string (case-insensitive) denoting the SIP
message.
For example:

Empty = rule applies to all messages

Invite = rule applies to all INVITE requests and responses

Invite.Request = rule applies to INVITE requests

Invite.Response = rule applies to INVITE responses

subscribe.response.2xx = rule applies to SUBSCRIBE
confirmation responses
Note: Currently, SIP 100 Trying messages cannot be manipulated.
Condition
CLI: condition
[MessageManipulations_Co
ndition]
Defines the condition that must exist for the rule to apply.
The valid value is a string (case-insensitive).
For example:

header.from.url.user== '100' (indicates that the user part of the