EasyManuals Logo

AudioCodes mediapack MP-500 User Manual

AudioCodes mediapack MP-500
574 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #525 background imageLoading...
Page #525 background image
Version 5.8 525 October 2009
SIP User's Manual 9. IP Telephony Capabilities
9.14.9 Three-Way Conferencing
The device supports three-way conference calls. These conference calls can also occur
simultaneously.
The following example demonstrates three-way conferencing. This example assumes that a
telephone "A" connected to the device wants to establish a three-way conference call with
two remote IP phones "B" and "C":
1. User A has an ongoing call with IP phone B.
2. User A places IP phone B on hold (by pressing the telephone's flash hook button,
defined by the parameter HookFlashCode).
3. User A hears a dial tone, and then makes a call to IP phone C.
4. IP phone C answers the call.
5. User A can now establish a three-way conference call (between A, B and C) by
pressing the flash-hook button, defined by the parameter ConferenceCode (e.g.,
regular flash-hook button or "*1").
Notes:
• Instead of using the flash-hook button to establish a three-way
conference call, you can dial a user-defined hook-flash code (e.g., "*1"),
configured by the parameter HookFlashCode.
• Three-way conferencing is applicable only to FXS interfaces.
The device supports the following conference modes (configured by the parameter
3WayConferenceMode):
îš„ Conferencing controlled by an external AudioCodes Conference (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. For this mode, the parameter 3WayConferenceMode is set to 0
(default.)
îš„ Conferencing controlled by an external, third-party Conference (media) server:
The Conference-initiating INVITE sent by the device uses only the ConferenceID as
the Request-URI. The Conference 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 Conference server
using this conference URI. For this mode, the parameter 3WayConferenceMode is set
to 1.
To enable three-way conferencing, the following parameters need to be configured:
îš„ Enable3WayConference
îš„ ConferenceCode = '!' (default, which is the hook flash button)
îš„ HookFlashCode
îš„ 3WayConferenceMode (conference mode)

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the AudioCodes mediapack MP-500 and is the answer not in the manual?

AudioCodes mediapack MP-500 Specifications

General IconGeneral
BrandAudioCodes
Modelmediapack MP-500
CategoryGateway
LanguageEnglish

Related product manuals