Manager:
|
|
Button Programming |
This section covers the IP Office actions that can be assigned to programmable buttons on Avaya phones. This assignment can be done through the IP Office configuration using Manager and for some functions using the phone itself.
| • | Appearance Functions The functions Call Appearance, Bridged Appearance, Coverage and Line Appearance are collectively known as "appearance functions". For full details of their operation and usage refer to the Key and Lamp Operation section. The following restrictions must be observed for the correct operation of phones. |
IP Office Software |
|
||||
IP Office 2.1 or 3.0DT |
On systems running IP Office 2.1 or 3.0DT software, the first programmable button must be set as a call appearance button. This requirement is necessary for the correct operation of phone functions such as call log. |
||||
IP Office 3.0+ |
For systems running IP Office 3.0 or higher (excluding 3.0DT), the first 3 programmable buttons must be set as call appearance buttons. This requirement is necessary for the correct operation of functions such as transfer, conference and call log.
|
||||
IP Office 4.2+ |
T3 phones support Line Appearance buttons only and are exempt from the above rules. |
||||
IP Office 5.0+ |
IP Office 5.0+ allows users have line appearances programmed before call appearances. This option is only supported by users using 1600 Series phones. |
| • | Phone Support Note that not all functions are supported on all phones with programmable buttons. Where possible exceptions have been indicated. |
| • | Actions that use status feedback are only supported on buttons that provide that feedback through lamps or icons. |
|
© 2009 AVAYA 15-601011 Issue 23.p.- 07:06, 30 October 2009 (button_programming_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: 24/08/2008 |