Avaya Aura Communication Manager Administration
36 Avaya 1600 Series IP Deskphones Administrator Guide
1600 Series IP Telephones with Avaya Aura Communication
Manager 5.2 Native Support
Release 1.1 provides native support for 1600 Series IP Telephones running on Avaya Aura
Communication Manager Release 5.2 or later. When native support applies, pressing the
Messages button causes the telephone to first determine if the call server has a dedicated
number for retrieving voice mail and when found, to proceed with voice mail retrieval.
1600 Series IP Telephones Aliased as 4600 Series IP Telephones
When native support does not apply, 1600 Series IP Telephones are aliased as 4600 Series IP
Telephones and run under an Avaya Aura Communication Manager Release earlier than 5.2. In
this case, use the settings file to configure the Messages button by setting the system
parameter MSGNUM to any dialable string. MSGNUM examples are:
●a standard telephone number the telephone should dial to access your voice mail system,
such as AUDIX or Octel.
●a Feature Access Code (FAC) that allows users to transfer an active call directly to voice
mail. FACs are supported only for QSIG-integrated voice mail systems like AUDIX or
Octel. QSIG is an enhanced signaling system that allows the voice mail system and Avaya
Aura Communication Manager Automated Call Processing (ACP) to exchange
information.
When the user presses the Messages button on the telephone, that number or FAC is
automatically dialed, giving the user one-touch access to voice mail.
The settings file specifies the telephone number to be dialed automatically when the user
presses this button. The command is:
SET MSGNUM 1234
where 1234 is the Voice Mail extension (Avaya Aura Communication Manager hunt group or
VDN). For more information, see Table8.
MSGNUM is used both in native support and when the telephone is aliased using non-native
support. Messaging must be configured for native support.
A separate Voice Mail extension can be administered for each station.