Read the SIP Message Manipulation Overview
Requires Sonus SBC2000/1000 Version 2.2 or later
This document assumes the reader is familiar with the Transformation Table's Optional/Mandatory and User Value features.
Steps to Creating an Effective SMM Translation
- If there are any conditions for the SMM Rule, add a Condition Rule.
Some example conditions might be:
- Only on a particular phone number
Only a specific header (name)
In the example below, the Called Number must be 'anonymous'. This condition will be applied later in the SIP Message Rule.
Decide which type of SIP packets are to be changed. The types of SIP packets to be changed is selected when the SMM Message Rule Table is created.
- What SIP Packet element needs to be changed?
- Click the name of the newly created SMM Table in the left-hand navigation tree, then add an SMM Rule entry.
Which type of Rule? Use the diagram below!
- Identify which rule section corresponds to the SIP element you want to change.
Example: If you wanted to change the FROM number to something other than anonymous
Select the appropriate type of change to be made
Configure the rule to correspond with the manipulation you require.
Configure your new rule into either a Signaling Group or Call Route.
SMM Rules can be processed either ingress or egress at the Signaling Group.
Like the Transformation Table's User Values, the SMM feature supports a method to copy values into user-controlled, generic tokens, SG User Values. The SG User Values can be transported from ingress to egress SG, or be utilized in a Transformation Table (e.g. to move a P-Asserted number to the Calling Number at the Call Route level rather than the Signaling Group level). See this SMM Document for an example of the SG User Value used with a Translation Table.