Three-Way Conferencing - AudioCodes Mediant 800B MSBR User Manual


FXS and FXO interfaces - to determine the presentation of the caller ID (allowed or
restricted).

To maintain backward compatibility - when the strings 'Private' or 'Anonymous' are
set in the Caller ID/Name field, the caller ID is restricted and the value in the
Presentation field is ignored.
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.

30.10 Three-Way Conferencing

The device supports three-way conference calls. Multiple, concurrent three-way conference
calls are also supported. The device supports the following 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.)

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.

Local, On-board Conferencing: The conference is established on the device without
the need for an external Conferencing server. This feature includes local mixing and
transcoding of the 3-Way Call legs on the device, and even allowing multi-codec
conference calls. The number of simultaneous, on-board conferences can be limited
using the MaxInBoardConferenceCalls parameter. The device supports up to five
simultaneous, on-board, three-way conference calls. This mode is configured by
setting the 3WayConferenceMode parameter to 2.
User's Manual 440
Mediant 800B MSBR
Document #: LTRT-12813