Avaya 1603 Guia Do Utilizador
Introduction
8 Avaya one-X™ Deskphone Value Edition 1600 Series IP Telephones Administrator Guide Release 1.0
Differences Between 1600 Series, 4600 Series, and 9600
Series IP Telephones
Series IP Telephones
Review this section if you administer more than one series (1600, 4600, 9600) of IP
Telephones.
Telephones.
Signaling - 46xx Series IP Telephones can use H.323 or SIP for telephony signaling. 16xx
Series and 96xx Series IP Telephones only use H.323. SIP-related administration of 16xx and
96xx telephones is neither necessary nor relevant.
Series and 96xx Series IP Telephones only use H.323. SIP-related administration of 16xx and
96xx telephones is neither necessary nor relevant.
Avaya Communication Manager Release - 46xx telephones are supported prior to
Communication Manager Release 3.0. The 96xx telephones are not officially supported prior to
Release 3.0. The 16xx telephones are not officially supported prior to Release 3.0.
Communication Manager Release 3.0. The 96xx telephones are not officially supported prior to
Release 3.0. The 16xx telephones are not officially supported prior to Release 3.0.
DHCP & SSON - 46xx telephones use Option 176 as the default DHCP Site Specific Option
Number (SSON); 16xx and 96xx telephones use Option 242.
Number (SSON); 16xx and 96xx telephones use Option 242.
Upgrade Script - The upgrade script files have different names and content (“46xxupgrade.scr”
versus “16xxupgrade.txt” or “96xxupgrade.txt”).
versus “16xxupgrade.txt” or “96xxupgrade.txt”).
File Servers - 46xx telephones can use either TFTP or HTTP servers as file servers, for
example, to download new phone firmware, upgrade script files, or settings files. 16xx and 96xx
telephones can use either HTTP or TLS servers.
example, to download new phone firmware, upgrade script files, or settings files. 16xx and 96xx
telephones can use either HTTP or TLS servers.
Backup - 46xx telephones use FTP as the protocol to create and access backup files. Users
can specify unique backup server addresses, backup directories, FTP User IDs, and FTP User
Passwords. 16xx and 96xx telephones use HTTP as the protocol to create and access backup
files, and users have no options to change backup parameters. 16xx and 96xx telephones use
the settings file parameter BRURI to identify the backup file site.
can specify unique backup server addresses, backup directories, FTP User IDs, and FTP User
Passwords. 16xx and 96xx telephones use HTTP as the protocol to create and access backup
files, and users have no options to change backup parameters. 16xx and 96xx telephones use
the settings file parameter BRURI to identify the backup file site.
Backup Filenames - 16xx and 96xx telephones store their backup files with titles that do not
include the model number, for example, 1234_96xxdata.txt or 1234_16xxdata.txt vs.
1234_4610data.txt or 1234_4620data.txt.
include the model number, for example, 1234_96xxdata.txt or 1234_16xxdata.txt vs.
1234_4610data.txt or 1234_4620data.txt.
Backup File Content - Backup file contents are generally the same, except that the 16xx and
96xx Contacts data is stored as:
96xx Contacts data is stored as:
ABKNAMEmmm = label
ABKNUMBERmmm = telephone number
ABKNUMBERmmm = telephone number
where mmm is 001 to 100 for 16xx Series Telephones and 001 to 250 for 96xx Series
Telephones. A given Contact entry in the 16xx or 96xx Backup file must have both name and
number to be valid. Type is optional and not applicable for the 16xx Series Telephones or the
96xx Series Telephones for Release 1.0 or Release 1.1. ABK stands for “Address Book”, the
original Contacts application name.
Telephones. A given Contact entry in the 16xx or 96xx Backup file must have both name and
number to be valid. Type is optional and not applicable for the 16xx Series Telephones or the
96xx Series Telephones for Release 1.0 or Release 1.1. ABK stands for “Address Book”, the
original Contacts application name.