- Nortel Communication Server 1000 IP Softphone 2050 User Guide
Table Of Contents
- Revision history
- Contents
- IP Softphone 2050 overview
- IP Softphone 2050 Call Control window
- IP Softphone 2050 Directories
- Installing and setting up the IP Softphone 2050
- Managing contacts from the Local Directory
- Adding contacts to a Local Directory
- Editing contacts in the Local Directory
- Deleting contacts from the Local Directory
- Finding contacts in the Local Directory
- Filtering a Local Directory
- Dialing from the Local Directory
- Managing Groups in the Shortcut Bar
- Using the Properties dialog box
- Linking to external directories
- Managing contacts from the CS 1000 Directory
- Managing IP Softphone 2050 calls
- IP Softphone 2050 Expansion Module
- IP Softphone 2050 Graphical External Application Server
- IP Softphone 2050 USB Headset Adapter
- IP Softphone 2050 macros
- IP Softphone 2050 menu commands
- IP Softphone 2050 Settings
- Opening the Settings window
- Using the Settings window
- Profiles
- Server
- License Servers
- Theme
- Features
- Macros
- Audio
- Sound Devices
- Hardware ID
- Advanced Audio
- Listener IP
- Notifications
- Hot Keys
- Text Replacements
- Lamp Sounds
- Key Type
- Language
- Expansion Module
- Personal Call Recording
- Plantronics USB Bluetooth Headset
- USB Headset
- About
- Accessibility Interface
- Configuring CS 1000 Directory user preferences
- IP Softphone 2050 Diagnostics
- Troubleshooting the IP Softphone 2050
- Index

Accessibility Interface
104
Using hot keys
You can assign keyboard hot keys to access the full range of Call Control
window functions and menu options—necessary for using all of the
IP Softphone 2050 features from the Accessibility Interface.
For information about available hot keys, and for adding or removing hot
keys, see “Hot keys” on page 27.
Limitations of Accessibility Interface
The following limitations apply to the IP Softphone 2050 for Windows
Release 3.3 Accessibility Interface.
• The Graphical External Application Server (GXAS) interface (added
in Release 3.1) is not compliant with the accessibility feature.
• Key Expansion Module (KEM) is not supported for accessibility mode.










