Manager: Key and Lamp Operation
|
|
Call Appearance Buttons |
Call appearance buttons are used to display alerts for incoming calls directed to a user's extension number or to a hunt group of which they are a member. Call appearance buttons are also used to make outgoing calls.
By having several call appearance buttons, a user is able to be alerted about several calls, select which call to answer, switch between calls and take other actions.

When all the user's call appearance buttons are in use or alerting, any further calls to their extension number receive busy treatment. Instead of busy tone, the user's forward on busy is used if enabled or otherwise voicemail if available.
Call appearance buttons are the primary feature of key and lamp operation. None of the other appearance button features can be used until a user has some call appearance button programmed[1].
There are also addition requirements to programming call appearance buttons:
| • | Call appearance buttons must be the first button programmed for the user, followed by any further call appearance buttons in a continuous block. |
| • | For IP Office 5.0+, line appearance buttons can be programmed before call appearance buttons for 1600 Series phone users. |
| • | Programming a single call appearance button for a user is not supported. The normal default is 3 call appearances per user except on phones where only two physical buttons are available. |
| • | [1] For IP Office 4.2+, T3 phones support the use of Line Appearance buttons. These can be programmed against buttons on T3 phones without requiring call appearance buttons. See T3 Phone Line Appearances. |
|
© 2009 AVAYA 15-601011 Issue 23.p.- 07:06, 30 October 2009 (call_appearance_buttons.htm) Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by (R) or TM are registered trademarks or trademarks respectively of Avaya Inc. All other trademarks are the property of their respective owners. Last Modified: 06/04/2009 |