Page History

...

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

   Caption
   0 Table 1 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. 

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.
   
   

...