Panel |
---|
In this section: |
Section |
---|
Column |
---|
|
|
Panel |
---|
title | Table of Contents Column |
---|
Info |
---|
| - This document details the steps required to produce an effective SIP Message Manipulation.
|
|
Prerequistes
|
Tip |
---|
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
Step 1: Add a Condition Rule
If there are any conditions for the SMM Rule, add a Condition Rule.
...
Examples include:
In the example below, the Called Number must be 'anonymous'. This condition will be applied later in the SIP Message Rule. Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | When Called Number Is Anonymous |
---|
| Image Removed |
|
Panel |
1a: Add a Condition Rule1b:
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.
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Creating an SMM Rule Table |
---|
| Image Removed |
|
Panel |
2a: Add a Add the SIP Message Rule Table.- 2b: Select Configure which SIP Messages messages will be examined by this Rule Table.
- Configure whether the 2c: Will this SMM Table will be Mandatory or Optional within in the Signaling Group?What .
Step 3: Select SIP Packet element
...
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!
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Select Appropriate SMM Rule Type |
---|
| Image Removed Image Removed |
|
Panel |
3: Add one of the Rule TypesSelect rule type: Header, Request, Status, or Raw
Step 4: Identify which rule section corresponds to the SIP element to be changed
- Add SIP Header Rule.
For Header Value, configure the URI User. For example,
you want to change.Example: If you wanted to change the FROM number to something other than anonymous
(i.e, From
: <sip:
anonymous@10anonymous@10.1.1.74>;tag=254b0000
Panel |
---|
|
).
FigureIdentify Rule Section | Image Removed Use the references below if you're uncertain about which configuration to use |
Panel |
---|
Expand |
---|
Click here to see the mapping between SIP packet elements and their corrsponding SMM configurations | Click here to see the mapping between SIP packet elements and their corrsponding SMM configurations | Caption |
---|
0 | Figure |
---|
1 | Mapping Between SIP Packet Elements and Corresponding SMM Configurations |
---|
| Image Removed Image RemovedImage Removed |
|
Select the appropriate type of change Mapping Between SIP Packet Elements and Corresponding SMM Configurations |
|
SIP Header Rule Field | Corresponds to SIP message field |
---|
Header Name | From | Display Name | name | URI Scheme | sip | URI User | 1010 | Password | password | URI User Parameters | usr=param | URI Host | IP address (i.e., 10.1.1.74) | URI Port | URI port (i.e, 5061) | URI Parameters | user=phone | Header Parameters | Header (i.e., tag=254b0000) |
|
Step 5: Select Type of Change to be made
Configure the rule to correspond with the manipulation you require.
- Access SIP Header Rule.
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Steps to Create SMM Rule |
---|
| Image Removed |
|
Panel |
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 Configure a Header Name (either from the pre-progammed list or by simply typing the name of the header if it doesnisn'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 do not require a header to be chosen.
- 5d: Configure the target rule setting. In the case of the example for For example, when changing any calling number of anonymous to 1000, set the User URI info Info to Modify and add the configuration/value you want for 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'.
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).
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Configure SMM Into Signaling Group |
---|
| Image Removed |
|
Info |
---|
For details on Signaling Groups or Call Routes, refer to Managing SIP Signaling Groups or Managing Call Routing Tables. |
Important Notes
Info |
---|
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. |