About this Page
- A sneak peek into the SBC 1000/2000's new SIP Header Manipulation Feature. This new feature permits any SIP header to be added, deleted, or modified.
- This SIP Header Manipulation example uses the Literal manipulation option and shows how perform Header Manipulation only when certain criteria are met.
- This document uses the Conditional Rules feature to limit Message Manipulation to very specific instances.
Requires Sonus SBC2000/1000 Version 2.2
Because you can never tell just what the other side might send or need, the SBC1000/2000 version 2.2 will include a feature to manipulate any SIP header.
- SIP Headers can be added, deleted, or modified.
- Manipulation can be done for every SIP message, or separately for SIP Requests or SIP Responses.
- Manipulations can set to occur based upon user specified matching criteria.
- Manipulations can be executed at the ingress or egress SG. At the ingress, inbound SIP messages are modified to permit proper handling by the SBC's routing function. At the egress, SIP messages already processed by the SBC are modified to meet the SIP requirements of the upstream device.
PAI Static Modification
In today's sneak peek, we modifiy the PAI at the egress SG for a PSTN > SBC > Lync call. This is an example of a static replacement--a replacement that will take place on every SIP packet that leaves the SBC bound for Lync.
Near the end of the document, we'll add a configuration that will make the PAI modification conditional, only changing the PAI when certain criteria is met.
Configure the SBC1000/2000
Select the new Message Manipulation entry in the navigation tree
Add a SIP Message Rule Table
Set how the rule will be applied. It can be applied to All SIP Messages, only Requests, only Responses, or Selected Messages.
Add an entry to the new table.
Set the Header Action to Modify and the Header Name to P-Asserted-Identity. As you can see, any SIP Header can be manipulated.
To set the new PAI value, click Add/Edit...
... and add the new value in the Edit Message Field
Click OK to complete adding the entry to the table.
In the SG, Enable the Message Manipulation
Add the new Message Manipulation to the Outbound Message Manipulation Table
In the debugging output below, you can see the PAI change from +15103644064 to 555
Conditional PAI Modification
By adding a Conditional Rule to the Message Rule, you can perform the manipulation only when it matches a particular condition. In the example below, the PAI would only be modified if the call is from +15103644064.
Add a Conditional Rule Table entry
Add the Description and set the Match Type from the pulldown. In this case, we're looking to match the calling number, which is represented by the from.uri.userinfo.user token.
Set the Operation to Equals. Set the Match Value Type to Literal and put the number to be matched into the Match Value.
With the Match information configured, it's time to modify the Message Rule so that it only runs when the Condition is met. In the Message Rule, click the Condition Expression Add/Edit button.
Set it for Match All Conditions and select the Conditional Rule you just finished programming in the previous steps. Click Apply.
Click Apply to complete the update to the Message Rule.
The SIP Header feature cannot generate a new SIP packet. Only arriving or leaving SIP packets changed via the SIP Header function.