|
|
|
Review this section if you administer both 4600 and 9600 Series IP Telephones.
Signaling - 46xx Series IP Telephones can use H.323 or SIP for telephony signaling. 96xx Series IP Telephones only use H.323. SIP-related administration of 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.
DHCP & SSON - 46xx telephones use Option 176 as the default DHCP Site Specific Option Number (SSON); 96xx telephones use Option 242.
Upgrade Script - The upgrade script files have different names and content (“46xxupgrade.scr” versus “96xxupgrade.txt”).
File Servers - 46xx telephones can use either TFTP or HTTPS servers as file servers, for example, to download new phone firmware, upgrade script files, or settings files. 96xx telephones only use HTTP or HTTPS.
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. 96xx telephones use HTTP as the protocol to create and access backup files, and users have no options to change backup parameters. 96xx telephones use the settings file parameter BRURI to identify the backup file site.
Backup Filenames - Except for the 9610, 96xx telephones store their backup files with titles that do not include the model number, for example, 1234_96xxdata.txt vs. 1234_4610data.txt or 1234_4620data.txt. While the 9610 never “backs up” data, for consistent terminology with other 9600 Series IP Telephones, we use the term “backup file” to describe the 9610 administration file which uses names like 1234_9610data.txt. The telephone extension number is always included in the backup filenames. In these examples, 1234 denotes the extension.
Backup File Content - Except for the 9610, backup file contents are generally the same, except that the 96xx Contacts data is stored as:
ABKNAMEmmm = label
ABKNUMBERmmm = telephone number
ABKTYPEmmm = entry type
where mmm is 001 to 250. A given Contact entry in the 96xx Backup file must have both name and number to be valid. Type is optional and not applicable for Releases 1.0 and 1.1. ABK stands for “Address Book”, the original Contacts application name. See Special Administration for the 9610 for backup file content information.
Settings File - Although both 46xx and 96xx telephones use the 46xxsettings file, the 96xx uses the following new parameters:
AMADMIN - to get the AvayaMenuAdmin.txt file for A (AVAYA) Menu WML-applications
AUDASYS, AUDIOENV, AUDIOSTHD, and AUDIOSTHS - controls audio alerting, audio environment selection, and headset/handset sidetones
BRURI - to specify a URI to place the backup file; set as the path of the file server where the backup file resides (supported by 46xx telephones as of Release 2.8 in February 2007)
HTTPDIR - to specify a subdirectory path on the HTTP server (supported by 46xx telephones as of Release 2.8 in February 2007)
LANG0STAT, LANGxFILE, and LANGSYS -control language file selection and available language files
LANGLARGEFONT - to specify which of the selected language files can appear in a larger font size
MSGNUM - for voice mail access
WMLHOME - to access the browser on all 9600 Series IP Telephones except the 9610
WMLSMALL - to specify the Home page for the 9610 IP Telephone Web browser
Any 46xx telephone receiving these 96xx-specific parameters ignores them.
IR/SMTP - 96xx telephones do not support Infrared (IR) or Simple Message Transport Protocol (SMTP), so any such 46xx administration is ignored.
Local Administration - The 46xx QOS, CTI, and ALERT Local Procedures are not supported by the 96xx telephones. Also, there is no indication of IR interfaces in the INT Local Procedure.
Language - As of Release 1.1, 96xx IP Telephones allow language administration, which was enhanced in subsequent releases. Note that 4600 Series and 9600 Series IP Telephones might not support the same languages, and the language files differ between the two telephone series.
SNMP & MIBs - Although both 46xx and 96xx telephones support SNMP v2c and have custom Management Information Bases (MIBs), the MIBs are formatted somewhat differently. Note that as of Release 1.1, SNMP is disabled by default in both IP Telephone series. Administrators must initiate SNMP by setting the SNMPADD and SNMPSTRING system values appropriately.
Wideband Codecs - 96xx telephones support G.722 (wide band) codecs, unlike 46xx telephones.
Feature Button Administration - Although 96xx telephones do not require administration of the following feature buttons, the user experience is enhanced if the following is administered: Conference Display, Selective Conference Party Mute, Send All Calls (SAC), Directory, EC500, Call Forward, etc.
|
|
|