SIP User's Manual  208  Document #: LTRT-12804 
  Mediant 800 MSBG 
 
The previous figure shows the following message manipulation rules: 
•  Index 1: adds the suffix ".com" to the host part of the To header. 
•  Index 2: changes the user part of the SIP From header to 200. 
•  Index 3: changes the user part of the From header to the user part of the P-
Asserted-ID. 
•  Index 4: if the user part of the From header equals "unknown", then it is changed 
according to the srcIPGroup call’s parameter. 
•  Index 5: removes the Priority header from an incoming INVITE message. 
2.  Add an entry and then configure it according to the table below. 
3.  Click the Apply button to save your changes. 
4.  To save the changes to flash memory, see ''Saving Configuration'' on page 336. 
 
 
Note:  For a detailed description on the syntax for configuring SIP message 
manipulation rules, see ''SIP Message Manipulation Description'' on page 
506. 
 
Table  3-35: Message Manipulations Parameters 
Parameter  Description 
Manipulation Set ID 
[ManSetID] 
Unique manipulation set ID that you can later assign to an IP Group (see 
''Configuring IP Groups'' on page 119). In the IP Group, this
 manipulation 
rule can be applied on the inbound and/or outbound message. 
Matching Characteristics 
Message Type 
[MessageType] 
SIP message type that you want to manipulate.  
The valid value is a string depicting 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 
[Condition] 
Condition that must exist for the rule to apply.  
The valid value is a string.  
For example: 
  header.from.url.user== 100  (indicates that the user part of the From 
header must have the value "100") 
  header.contact.param.expires > 3600 
  header.to.url.host contains 'domain' 
  param.call.dst.user != 100 
Note: Currently, SDP body message types are not supported.