AudioCodes Mediant 2600 - Page 389

Version 6.8 389 Mediant 2600 E-SBC
User's Manual 21. SBC Configuration
Parameter Description
Leave From Right
CLI: leave-from-right
[IPOutboundManipulation_Leave
FromRight]
Defines the number of digits to keep from the right of the
manipulated item.
Prefix to Add
CLI: prefix-to-add
[IPOutboundManipulation_Prefix
2Add]
Defines the number or string to add in the front of the
manipulated item. For example, if you enter 'user' and the user
name is "john", the new user name is "userjohn".
If you set the 'Manipulated Item' parameter to Source URI or
Destination URI
, you can configure this parameter to a string of
up 49 characters. If you set the 'Manipulated Item' parameter to
Calling Name, you can configure this parameter to a string of
up 36 characters.
Suffix to Add
CLI: suffix-to-add
[IPOutboundManipulation_Suffix
2Add]
Defines the number or string to add at the end of the
manipulated item. For example, if you enter '01' and the user
name is "john", the new user name is "john01".
If you set the 'Manipulated Item' parameter to Source URI or
Destination URI
, you can configure this parameter to a string of
up 49 characters. If you set the 'Manipulated Item' parameter to
Calling Name, you can configure this parameter to a string of
up 36 characters.
Privacy Restriction Mode
CLI: privacy-restriction-mode
[IPOutboundManipulation_Priva
cyRestrictionMode]
Defines user privacy handling (i.e., restricting source user
identity in outgoing SIP dialogs).
 [0] Transparent = (Default) No intervention in SIP privacy.
 [1] Don't change privacy = The user identity in the outgoing
SIP dialog remains the same as in the incoming SIP dialog.
If a restricted number exists, the restricted presentation is
normalized as follows:

From URL header: "anonymous@anonymous.invalid"

If a P-Asserted-Identity header exists (either in the
incoming SIP dialog or added by the device), a Privacy
header is added with the value "id".
 [2] Restrict = The user identity is restricted. The restriction
presentation is as follows:

From URL header: "anonymous@anonymous.invalid"

If a P-Asserted-Identity header exists (either in the
incoming SIP dialog or added by the device), a Privacy
header is added with the value "id".
 [3] Remove Restriction = The device attempts to reveal the
user identity by setting user values in the From header and
removing the privacy "id" value if the Privacy header exists.
If
the From header user is anonymous, the value is taken from
the P-Preferred-Identity, P-Asserted-Identity, or Remote-
Party-ID header (if exists).
Note:
 Restriction is done only after user number manipulation (if
any).
 The device identifies an incoming user as restricted if one of
the following exists:

From header user is "anonymous".

P-Asserted-Identity and Privacy headers contain the
value "id".