Three-Way Conferencing - AudioCodes E-SBC User Manual

CHAPTER 28 Configuring Supplementary Services
● The 'Privacy: none' header is included
● The P-Asserted-Identity (or P-Preferred-Identity) header shows the caller ID
The caller ID (and presentation) can also 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
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.

Three-Way Conferencing

The device supports three-way conference calls. Three-way conferencing occurs when an endpoint
connected to the FXS or BRI port initiates a call and invites two remote IP-based participants. The
device also supports multiple, concurrent three-way conference calls.
The feature is applicable only to FXS and BRI interfaces.
The device supports the following three-way 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. To enable this mode,
configure 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:
(P- Asserted- Identity
Mediant 1000 Gateway & E-SBC | User's Manual
or P- Preferred- Identity).
- 665 -
Use the parameter