• Transfer a call to another DN
- To perform a Blind Transfer, place the current call on hold, call the required DN, and
immediately release from the call.
- To perform a Consultative Transfer, place the current call on hold, call the required
DN, wait for the answer, and release the call after the DN answers.
• Press digit keys on the Handset during an established call to transmit DTMF tones to the
other party on the call.
• Initiate a three-way call. Place an active call on hold, call the third party, and wait until the
call is answered. Press the
star (*)
key to start the conference.
• Receive a second incoming call (call waiting): When a second call is waiting, a message
"2nd call from <Directory Number>"
(the text of the message can be configured)
displays on the screen and a beep emits every 3 seconds. The second calling party hears
a ring back tone instead of a busy tone.
You can use the
"*"
to toggle between calls. When you toggle between calls, the on-
screen messages changes from <Directory Number> to "Waiting <Directory Number>".
• Observe SIP DECT user status (OCS interaction); if a SIP DECT user has Multiple
Appearance Directory Numbers (MADN), then you must configure the SIP DECT Handset
as an OCS-controlled device (AST 0, CLS t87a). The presence status is updated based
on the busy status of either DN.
If a SIP DECT user does not have MADNs, then you must configure the SIP Line UEXT
as AST 0, CLS t87a. If a user for the primary DN is configured in OCS, the presence
status is updated based on the SIP DECT Handset use (busy/available).
• Activate FFC features such as Call Forward, Make Set Busy, Ring Again, Call Park, which
are available for SIP Line users from a DECT Handset. For more information, see
Avaya
SIP Line Fundamentals, NN43001-508
Note:
Some of the described features require Call Server configuration.
CallPilot and Message Waiting Indication support
DECT Handsets subscribed on SIP DECT can use CallPilot.
You can configure Call Forward No Answer for the Primary DN of the UEXT so that the
unanswered calls on the corresponding DECT handset or IP Deskphone (in the case of a
twinned configuration) are forwarded to CallPilot. Calls can also be forwarded to CallPilot as
busy treatment for the Primary DN.
Product overview
14 SIP DECT Fundamentals
October 2012
Summary of Contents for CS 1000
Page 6: ...6 SIP DECT Fundamentals October 2012 ...
Page 146: ...System administration 146 SIP DECT Fundamentals October 2012 Comments infodev avaya com ...
Page 174: ...System maintenance 174 SIP DECT Fundamentals October 2012 Comments infodev avaya com ...
Page 204: ...Site survey example 204 SIP DECT Fundamentals October 2012 Comments infodev avaya com ...