In this section:

 

Steps to Creating an Effective SMM Translation

Step 1: Add a Condition Rule

If there are any conditions for the SMM Rule, add a Condition Rule. Examples include:

    • Only on a particular phone number

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

Step 2: Select SIP Packets to be changed

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.

  1. Add the SIP Message Rule Table.
  2. Configure which SIP messages will be examined by this Rule Table.
  3. Configure whether the SMM Table will be Mandatory or Optional in the Signaling Group.

Step 3: Select SIP Packet element

  1. Click the name of the newly created SMM Table in the left-hand navigation tree, then add an SMM Rule entry.

  2. Select rule type: Header, Request, Status, or Raw

Step 4: Identify which rule section corresponds to the SIP element to be changed

  1. Add SIP Header Rule.

  2. 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).

    Mapping Between SIP Packet Elements and Corresponding SMM Configurations

    SIP Header Rule FieldCorresponds to SIP message field
    Header NameFrom
    Display Namename
    URI Schemesip
    URI User1010
    Passwordpassword
    URI User Parametersusr=param
    URI HostIP address (i.e., 10.1.1.74)
    URI PortURI port (i.e, 5061)
    URI Parametersuser=phone
    Header ParametersHeader (i.e., tag=254b0000)

Step 5: Select Type of Change to be made

Configure the rule to correspond with the manipulation you require.

  1. Access SIP Header Rule.
  2. Select the Result Type. This setting operates exactly the same as the Translational Table optional/mandatory.
  3. 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?
  4. Configure a Header Name (either from the pre-progammed list or by typing the name of the header if it isn't in the list). Request and Status Rules address only the Request and Status headers; those rules do not require a header to be chosen.
  5. Configure the target rule setting. For example, when changing any calling number of anonymous to 1000, set the User URI Info to Modify and add the configuration/value for the SIP element.
  6. If you created a Condition in Step 1, add it to the Rule entry . In this example, the SMM will only execute if the Calling Number is 'anonymous'.

  7. Select the appropriate type of change to be made.

Step 6: Configure the new rule into either a Signaling Group or Call Route

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.

  • No labels