Skip to end of metadata
Go to start of metadata
Table of Contents

About this Page

  • This document details the steps required to produce an effective SIP Message Manipulation.

Prerequistes

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

  1. 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.

      Figure : When Called Number Is Anonymous

      • 1a: Add a Condition Rule
      • 1b: 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.
  2. 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.

    Figure : Creating an SMM Rule Table

    • 2a: Add a SIP Message Rule Table
    • 2b: Select which SIP Messages will be examined by this Rule Table
    • 2c: Will this SMM Table be Mandatory or Optional within the Signaling Group?
  3. 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!

      Figure : Select Appropriate SMM Rule Type

      • 3: Add one of the Rule Types: Header, Request, Status, or Raw
  4. 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
      From: <sip:anonymous@10.1.1.74>;tag=254b0000

      Figure : Identify Rule Section

      Use the references below if you're uncertain about which configuration to use

       Click here to see the mapping between SIP packet elements and their corrsponding SMM configurations

      Figure : Mapping Between SIP Packet Elements and Corresponding SMM Configurations

  5. Select the appropriate type of change to be made
    Configure the rule to correspond with the manipulation you require.

    Figure : Steps to Create SMM Rule

    • 5a: Select the Result Type. This setting operates exactly the same as the Translational Table optional/mandatory.
    • 5b: Set the Action to Add, Remove, Copy, or Modify. The available options will vary based upon the type of rule you're adding. If you think about it, you can't _add a Request URI or Status Line; the SIP packet already has one, right?
    • 5c: For a Header Rule, you'll need supply a Header Name either from the pre-progammed list or by simply typing the name of the header if it doesn't appear in the list. Request and Status Rules address only the Request and Status headers, so those rules don't require the user to pick a header.
    • 5d: Configure the target rule setting. In the case of the example for changing any calling number of anonymous to 1000, set the User URI info to Modify and add the configuration/value you want the SIP element changed to.
    • 5e: If you created a Condition in Step 1, add it to the Rule entry now. In this example, the SMM will only execute if the Calling Number is 'anonymous'.
  6. 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.

    Figure : Configure SMM Into Signaling Group

Important Notes

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.

  • No labels