AudioCodes Mediant 3000

User's Manual 408 Document #: LTRT-89730
Mediant 3000
Parameter Description
prefix ("T~&R_") to the Contact user part.
b. The incoming INVITE is identified as a REFER-resultant
INVITE according to this special prefix.
c. The device replaces the host part in the Request-URI with
the host from the REFER contact. The special prefix
remains in the user part for regular classification,
manipulation, and routing. The special prefix can also be
used for specific routing rules for REFER-resultant INVITEs.
d. The special prefix is removed before the resultant INVITE is
sent to the destination.
 [2] IP Group Name = Sets the host part in the REFER message
to the name defined for the IP Group (in the IP Group table).
 [3] Handle Locally = Handles the incoming REFER request itself
without forwarding the REFER. The device generates a new
INVITE to the alternative destination according to the rules in
the IP-to-IP Routing table (the 'Call Trigger' field must be set to
REFER).
Note: The corresponding global parameter is SBCReferBehavior.
Remote Replaces Mode
[IpProfile_SBCRemoteReplaces
Behavior]
Enables the device to handle incoming INVITEs containing the
Replaces header for the SIP entity (which does not support the
header) associated with the IP Profile. The Replaces header is
used to replace an existing SIP dialog with a new dialog such as in
call transfer or call pickup.
 [0] Standard = (Default) The SIP entity supports INVITE
messages containing Replaces headers. The device forwards
the INVITE message containing the Replaces header to the SIP
entity. The device may change the value of the Replaces
header to reflect the call identifiers of the leg.
 [1] Handle Locally = The SIP entity does not support INVITE
messages containing Replaces headers. The device terminates
the received INVITE containing the Replaces header and
establishes a new call between the SIP entity and the new call
party. It then disconnects the call with the initial call party, by
sending it a SIP BYE request.
 [2] Keep as is = The SIP entity supports INVITE messages
containing Replaces headers. The device forwards the
Replaces header as is in
incoming REFER and outgoing INVITE
messages from/to the SIP entity (i.e., Replaces header's value
is unchanged).
For example, assume that the device establishes a call between A
and B. If B initiates a call transfer to C, the device receives an
INVITE with the Replaces header from C. If A supports the
Replaces header, the device simply forwards the INVITE as is to A;
a new call is established between A and C and the call between A
and B is disconnected. However, if A does not support the
Replaces header, the device uses this feature to terminate the
INVITE with Replaces header and handles the transfer for A. The
device does this by connecting A to C, and disconnecting the call
between A and B, by sending a SIP BYE request to B. Note that if
media transcoding is required, the device sends an INVITE to C on
behalf of A with a new SDP offer.
Play RBT To Transferee Enables the device to play a ringback tone to the transferred party
(transferee) during a blind call transfer, for the SIP entity
associated with the IP Profile (which does not support such a tone