Version 6.4 397 March 2012
SIP User's Manual 19. Stand-Alone Survivability (SAS) Application
After manipulation, SAS registers the user in its database as follows:
AOR: 976653434@10.33.4.226
Associated AOR: 3434@10.33.4.226 (after manipulation, in which only the four digits
from the right of the URI user part are retained)
Contact: 976653434@10.10.10.10
The procedure below describes how to configure the manipulation example scenario above
(relevant ini parameter is SASRegistrationManipulation):
To manipulate incoming Request-URI user part of REGISTER message:
1. Open the SAS Configuration page (Configuration tab > VoIP menu > SAS > Stand
Alone Survivability).
2. In the SAS Registration Manipulation table, in the 'Leave From Right' field, enter the
number of digits (e.g., "4") to leave from the right side of the user part. (The Leave
From Right' field defines the number of digits to retain from the right side of the user
part; all other digits in the user part are removed.)
Figure 19-16: Manipulating User Part in Incoming REGISTER
3. Click Submit.
19.2.5.2 Manipulating Destination Number of Incoming INVITE
You can define a manipulation rule to manipulate the destination number in the Request-
URI of incoming INVITE messages when SAS is in emergency state. This is required, for
example, if the call is destined to a registered user but the destination number in the
received INVITE is not the number assigned to the registered user in the SAS registration
database. To overcome this and successfully route the call, you can define manipulation
rules to change the INVITE's destination number so that it matches that of the registered
user in the database. This is done using the IP to IP Inbound Manipulation table.
For example, in SAS emergency state, assume an incoming INVITE has a destination
number "7001234" which is destined to a user registered in the SAS database as
"552155551234". In this scenario, the received destination number needs to be
manipulated to the number "552155551234". The outgoing INVITE sent by the device then
also contains this number in the Request-URI user part.
To Next Page
Loading...
