In this section:
If there are any conditions for the SMM Rule, add a Condition Rule. Examples include:
Only a specific header (name)
Select a Match Type Token value; this states the SIP Packet element (diversion number, IP address, etc.) for the match. Then, complete of the remainder which provides the value you desire to match.
Decide which type of SIP packets are to be changed (All Messages, All Requests, All Responses, Select Messages). The types of SIP packets to be changed is selected when the SMM Message Rule Table is created.
Click the name of the newly created SMM Table in the left-hand navigation tree, then add an SMM Rule entry.
Select rule type: Header, Request, Status, or Raw
For Header Value, configure the URI User. For example, to change the FROM number to something other than anonymous (i.e, From <sip:anonymous@10.1.1.74>;tag=254b0000).
Configure the rule to correspond with the manipulation you require.
Select the appropriate type of change to be made.
Configure the new rule into either a Signaling Group or Call Route (SMM Rules can be processed either ingress or egress at the Signaling Group).
For details on Signaling Groups or Call Routes, refer to Managing SIP Signaling Groups or Managing Call Routing Tables.
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.