AudioCodes Mediant 500 E-SBC, User Manual

Page: 509 / 920

User's Manual 28. SBC Configuration
Version 6.8 509 Mediant 500 E-SBC
Parameter Description
Prefix to Add
CLI: prefix-to-add
[IPOutboundManipulation_Prefix2Add]
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_Suffix2Add]
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_PrivacyRest
rictionMode]
Determines 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 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
restricted presentation is as mentioned above).

[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).
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".
Note: All restriction logic is performed after the user
number has been manipulated.