AudioCodes Mediant 500L - Using the Proprietary SIP X-AC-Action Header

User's Manual 724 Document #: LTRT-10532
Mediant 500L Gateway & E-SBC
Parameter Description
characters. If you set the 'Manipulated Item' parameter to Calling
Name, you can configure the parameter to a string of up 36
characters.
Privacy Restriction Mode
privacy-restriction-mode
[IPOutboundManipulation_Pr
ivacyRestrictionMode]
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 sett
ing 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".
36.3 Using the Proprietary SIP X-AC-Action Header
You can use AudioCodes proprietary SIP header, X-AC-Action in message manipulation
rules to trigger certain actions. These actions can be used to support, for example,
interworking of SIP-I and SIP endpoints for the ISUP SPIROU variant (see Enabling
Interworking of SIP and SIP-I Endpoints on page 747).
The following actions are supported by the X-AC-Action header:
 To disconnect a call (optionally, after a user-defined time):
X-AC-Action: 'disconnect'
X-AC-Action: 'disconnect;delay=<time in ms>'
 To resume a previously suspended call:
X-AC-Action: 'abort-disconnect'
 To automatically reply to a message without forwarding the response to the
other side:
X-AC-Action: 'reply'
 To automatically reply to a message with a specific SIP response without
forwarding the response to the other side: