AudioCodes Mediant 500 MSBR, User Manual

Page: 573 / 1248

Version 7.2 573 Mediant 500 MSBR
User's Manual 30. Configuring Supplementary Services
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.
♦
Configure the device with an Inbound Manipulation rule that is applied to
calls received from the third-party network entity so that the device considers
conference calls as regular calls and forwards them to the Conference
server without getting involved in the conferencing setup.
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
Note: Three-way conferencing using an external conference server is supported only
by FXS interfaces.

Local, On-board Conferencing: The conference is established on the device without
the need for an external Conferencing server. The device supports up to five
simultaneous, on-board, three-way conference calls. This feature supports local
mixing and transcoding of the three-way conferencing legs on the device and multiple
codec conference calls. You can configure the maximum number of simultaneous, on-
board conferences, using the MaxInBoardConferenceCalls parameter.The mode is
configured by setting the 3WayConferenceMode parameter to 2.