Three-Way Conferencing - AudioCodes MP-124 User Manual

SIP User's Manual
In addition, the caller ID (and presentation) can be displayed in the Calling Remote-Party-ID
header.
The 'Caller Display Information' table (CallerDisplayInfo) is used for the following:
FXS interfaces - to define the caller ID (per port) that is sent to IP.
FXO interfaces - to define the caller ID (per port) that is sent to IP if caller ID isn't
detected on the Tel side, or when EnableCallerID = 0.
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.

9.15.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:
Version 5.8
•
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.
431
9. IP Telephony Capabilities
September 2009