AudioCodes MediaPack MP-11 Series User Manual

Version 7.2 551 Mediant 1000B Gateway & E-SBC
User's Manual 26. Configuring Supplementary Services
The value of the ‘Presentation’ field that is defined in the ‘Caller Display Information’ table
can be overridden by configuring the ‘Presentation’ parameter in the ‘Tel to IP Source
Number Manipulation’ table. Therefore, this table can be used to set the presentation for
specific calls according to Source / Destination prefixes.
The caller ID can be restricted/allowed (per port) using keypad features KeyCLIR and
KeyCLIRDeact (FXS only).
AssertedIdMode defines the header that is used (in the generated INVITE request) to
deliver the caller ID (P-Asserted-Identity or P-Preferred-Identity). Use the parameter
UseTelURIForAssertedID to determine the format of the URI in these headers (sip: or tel:).
The parameter EnableRPIheader enables Remote-Party-ID (RPI) headers for calling and
called numbers for Tel-to-IP calls.
26.10 Three-Way Conferencing
The device supports three-way conference calls. Three-way conferencing occurs when an
endpoint connected to the device's FXS or BRI port initiates a call and invites two remote
IP-based participants. The device also supports multiple, concurrent three-way conference
calls.
The device supports the following three-way conference modes:

Conference Managed by External, AudioCodes Conferencing (Media) Server:
The conference-initiating INVITE sent by the device uses the ConferenceID
concatenated with a unique identifier as the Request-URI. This same Request-URI is
set as the Refer-To header value in the REFER messages that are sent to the two
remote parties. This mode is configured by setting the 3WayConferenceMode
parameter to 0 (default.)
To join a conference, the Request-URI includes the Conference ID string preceded by
the number of the participants in the conference and terminated by a unique number.
INVITE messages with the same URI join the same conference. For example:
INVITE sip:4conf1234@10.1.10.10

Conference Managed by External, Third-party Conferencing Server: Two optional
modes of operation:
• The conference-initiating INVITE sent by the device uses only the ConferenceID
as the Request-URI. The Conferencing server sets the Contact header of the 200
OK response to the actual unique identifier (Conference URI) to be used by the
participants. This Conference URI is included (by the device) in the Refer-To
header value in the REFER messages sent by the device to the remote parties.
The remote parties join the conference by sending INVITE messages to the
Conferencing server using this conference URI. This mode is configured by
setting the 3WayConferenceMode parameter to 1.
• The conference-initiating INVITE sent by the device uses only the ConferenceID
as the Request-URI. The Conferencing server sets the Contact header of the 200
OK response to the actual unique identifier (Conference URI) to be used by the
participants. The Conference URI is included in the URI of the REFER with a
Replaces header sent by the device to the Conferencing server. The
Conferencing server then sends an INVITE with a Replaces header to the remote
participants. This mode is configured by setting the 3WayConferenceMode
parameter to 3.
When the device is used for Gateway and SBC applications, it can also support
conference calls initiated by third-party network entities (e.g., Skype for Business)
that use the same Conference server. To support these conference calls, you can
do one of the following:
♦ Configure the third-party network entity with a Conference ID that is different
from the Conference ID configured for the device.

AudioCodes MediaPack MP-11 Series Specifications

General

Brand	AudioCodes
Model	MediaPack MP-11 Series
Category	Gateway
Language	English