Configuring Message Manipulation Rules

Note the following before you configure message manipulation rules:

Incorrect header manipulation rules applied to headers that are responsible for dialog management, such Call-ID, Via, and Contact, and local and remote tags, might cause all calls to fail.
Manipulating some SIP header fields can result in malformed SIP messages that might cause unexpected behavior such as call failure.
Some header fields have special treatment that causes them to act differently when the header is manipulated. For example, the Expire header value is set using timer C, which you can configure in the CLI. Therefore, manipulation of this header field has no effect.
In some cases, rules do not take effect because some fields, such as Call-ID, can be managed and overridden by the software.
If you receive unexpected results from your header manipulation rules, begin troubleshooting your rules by checking the regular expressions in your rules.
You can configure up to 1000 manipulation rules for a BSG.

To configure message manipulation rules:

Create a new message manipulation rule, assign it a name, and enter the actions configuration.
[edit services border-signaling-gateway gateway bsg-1 sip]user@host# edit message-manipulation-rules manipulation-rule hm-rule actions
Create a configuration for a SIP header field.
[edit services border-signaling-gateway gateway bgf-1 sip message-manipulation-rules manipulation-rule hm-rule actions]user@host# edit sip-header accept-language
Add field values that you want to manipulate.
[edit services border-signaling-gateway gateway bgf-1 sip message-manipulation-rules manipulation-rule hm-rule actions sip-header accept-language]user@host# set field-value remove-regular-expression Frenchuser@host# set field-value add Japanese

After you set up message manipulation rules, apply them by adding the rules to new transaction policies.