AudioCodes MediaPack MP-112, User Manual

Page: 254 / 622

User's Manual 254 Document #: LTRT-65417
MP-11x & MP-124

If Caller ID is restricted:
•
The From header is set to “anonymous” <anonymous@anonymous.invalid>
•
The ‘Privacy: id’ header is included
•
The P-Asserted-Identity (or P-Preferred-Identity) header shows the caller ID

If Caller ID is allowed:
•
The From header shows the caller ID
•
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 (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.
24.9 Three-Way Conferencing
The device supports three-way conference calls. These conference calls can also occur
simultaneously. The device supports the following conference modes (configured by the
parameter 3WayConferenceMode):

Conferencing managed 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 3WayConferenceMode parameter is set to 0
(default.)

Conferencing managed 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 3WayConferenceMode parameter is set
to 1.