...
This document details how to change the incoming RURI number using the TO header number. This solution was originally generated to eliminate a problem from an incoming INVITE.
Panel |
---|
|
Caption |
---|
| Image Modified |
|
You can see that the number on the RURI is not a number at all, but an IP address.
...
Select the new Message Manipulation entry in the navigation tree
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | SIP Message Rule Table |
---|
| Image Modified |
|
Add a SIP Message Rule Table
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Add Message Rule Table |
---|
| Image Modified |
|
Set how the rule will be applied. It can be applied to All SIP Messages, only Requests, only Responses, or Selected Messages. Since the Request URI only appears in a SIP Request, select Add Requests type of Header Manipulation.
Panel |
---|
|
Caption |
---|
| Image Modified |
|
Add an entry to the new table. Expand the arrows as shown to reach the lower levels of header matching.
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Add SIP Request Line Rule |
---|
| Image Modified |
|
Set the URI User (info) to Modify and click the Add/Edit button.
Panel |
---|
|
Caption |
---|
| Image Modified |
|
Set the Type of Value to Token and the Value to to.uri.userinfo.user (selected from the pop-up box generated by clicking the arrow to the right of the field). This setting says to set the Request URI from the number listed in the TO header (userinfo.user=number).
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Edit Message Field |
---|
| Image Modified |
|
Click the OK button.
Panel |
---|
|
Caption |
---|
| Image Modified |
|
Add the new rule to the incoming SG.
Panel |
---|
|
Caption |
---|
| Image Modified |
|
Info |
---|
In the debugging output below, the RURI Header Manipulation rule was modified to take the number from the FROM header, not the TO header so that it would be easier to follow the header manipulation function in the debug. |
...