User's Manual

Version 1.1 SIP4.4 Feature Matrix Page 16
8.0 Feature Interactions
8.1 Conference
The SIP Deskphone can provide conference locally (set ENABLE_3WAY_CALL YES); Avaya Aura®
also provides ad-hoc conference (via FNE). Be aware of the following conference related items:
 The Conf and Join softkeys support the phone’s local 3-way conference capability. They do not
work with the Avaya Aura® ad-hoc conference capability.
 When the local 3-way conference is used and one party that has Music On Hold (MOH) enabled
goes on hold, all remaining conference parties will hear the MOH. Use the Avaya Aura® ad-hoc
conference feature to avoid this.
 When AVAYA_AURA_MODE_ENABLE is YES the phone does not support 3rd party
conference bridges. Thus the CONFERENCE_URI[n] configuration parameters are not
processed.
8.2 Transfer
The SIP Deskphone can initiate both attended and blind transfers. To use attended transfer, set the
Communication Manager (CM) parameter “SIP Endpoint Managed Transfer?” to No.
8.3 Hold
To see “Remote Hold” displayed on a far end phone when an 1100/1200 SIP Deskphone places a call on
hold, the CM “Direct Hold” feature must be active so the CM can forward the hold notification to the far
end. The CM “Direct Hold” feature is enabled by disabling the Music On Hold (MOH) for the user
placing the call on hold (which means when the user places a call on hold, the far end does not hear
MOH).
To disable MOH for a user, set “Hear System Music on Hold?” to No in the IP Deskphone’s COR (Class
of Restriction).
8.4 Call Forward
The Avaya Aura® features Call Forward All Calls and Call Forward Busy/No Answer are
recommended over the phone’s local Call Forward feature (CallFwd softkey) because CM handles call
coverage better with them. The Call Forward All Calls and Call Forward Busy/No Answer features
require FNE access.
If the local CallFwd is used, be aware that it cannot be used when the same extension is logged into
multiple devices (Multiple login).