AudioCodes Mediant 500 MSBR, User Manual

Page: 572 / 1248

User's Manual 572 Document #: LTRT-10375
Mediant 500 MSBR
30.9.3 Caller ID on the IP Side
Caller ID is provided by the SIP From header containing the caller's name and "number",
for example:
From: “John” <SIP:101@10.33.2.2>;tag=35dfsgasd45dg
If Caller ID is restricted (received from Tel or configured in the device), the From header is
set to:
From: “anonymous” <anonymous@anonymous.invalid>; tag=35dfsgasd45dg
The P-Asserted (or P-Preferred) headers are used to present the originating party’s caller
ID even when the caller ID is restricted. These headers are used together with the Privacy
header.

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.
30.10 Three-Way Conferencing
The device supports three-way conference calls. Three-way conferencing occurs when an
endpoint connected to the device's 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 device supports the following three-way conference modes:

Conference Managed by External, AudioCodes Conferencing (Media) Server: