AudioCodes E-SBC User Manual page 704

CHAPTER 28 Configuring Supplementary Services
● 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 device
includes this Conference URI in the SIP 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. To enable this
mode, configure 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. To enable this mode, configure 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:
◆
◆
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
Three-way conferencing using an external conference server is applicable only to 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 device uses resources from DSPs for on-board conferencing calls. However, if there are no
available resources from the device's pool of DSPs, the device obtains resources from idle
FXS ports to establish the conference call. You can specify ports that you don't want to be used
as a resource for conference calls that are initiated by other ports, using the
[3WayConfNoneAllocateablePorts] parameter.
Each on-board three-way conference uses two DSP channels. As one channel is already
provided by the FXS port interface to which the calling party (initiator of the three-way
conference) is connected, the device obtains an additional DSP channel from another FXS port
interface that is idle. However, if your device is installed with an MPM module(s), it obtains the
DSP channel from the module. If the device is not installed with any MPM modules and all FXS
ports are busy, the three-way conference call cannot be made. To enable this mode, configure
the [3WayConferenceMode] parameter to [2].
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.
Mediant 1000 Gateway & E-SBC | User's Manual
- 666 -