Avaya Readme for the 1692 IP Conference Phone R1.0 User Manual
1692 Release R1.00 Readme (November 9, 2009)
1692 H.323 Release R1.00 Readme.
This file is the readme for the Avaya 1692 IP Conference Phone. This file describes the contents of
the November 9, 2009 General Availability (GA) software distribution package.
Product Description:
The Avaya 1692 IP Conference Phone is an H.323 based, telephone that delivers a set of
Avaya Communication Manager features directly to the conference room.
Support for POE (Power Over Ethernet).
It offers “RF hardening” and eliminates interference from mobile phones.
Improved audio quality.
Two optional extended microphones for expanded coverage (same mics used on the 4690).
User display prompts in several languages.
New features introduced as part of R1.00
Usability
HD (High Definition) voice support: provides a voice quality with G.722 codec support, with
following enhancements
• Twice the clarity of ordinary phone calls for life-like, vibrant conversations
• More natural conversations that significantly boost recognition and enhance productivity
• Hear every word without repeating
• Enable remote collaboration with vibrant, life-like voice quality
RF compliance: Receive an uninterrupted voice when there is a mobile buzz, i.e its “RF
hardening” eliminates the interference from mobile phones
Language Support: the phone supports the following languages
a) English (Default)
b) German
c) French (Canadian)
d) French (Parisian)
e) Spanish (Latin American)
f) Italian
SRTP Support: Provides encryption, message authentication, and protection of the RTP Data.
Default SSON value has been changed from 176 to 242.
FTP/HTTPS server support along with the existing HTTP and TFTP support have been added.
Copyright Avaya 2009 All rights reserved
Page 1 of 8
1692 Release R1.00 Readme (November 9, 2009)
Known issues of Release R1.00
Upgrade/Downgrade:
During the first upgrade the phone will show “no Ethernet”, even if Ethernet is present. This
message can be ignored during this first upgrade.
Phone displays navigation indication arrow with single server feature screen.
Remote Trace Issue:
Phone can’t be traced from the remote location.
Gatekeeper Request (GRQ) Issue:
Phone is not sending GRQ request in particular time interval, when it goes into discovery
mode.
Workaround: Wait for some time, the phone will get registered.
TLS Connection Issue:
TLS connection doesn’t fail even when the duration of the server certificate expires.
Workaround: The issue was identified during the negative test scenario. Phone functionality is
not impacted and will work normally.
Changing the TLSPORT parameter in the settings file or DHCP has no effect on the phone.
Phone does not display the file server address in its DNS name format in System information.
If the network parameter value is set via SSON and *to program then the priority is given to
SSON.
Workaround:
1) Boot the phone up in the existing setup. Change the SSON value by using the Mute Key
Sequence MUTE-7-7-6-6-#. This new value could be either an empty scope option in DHCP
server or an option where the second file server is configured. For example, if current SSON
option is 242 with File Server1 being configured, then by setting another SSON option 176 it
could be used to ask the phone to divert to File Server2.
2) Boot the phone up in the existing setup. Do not let the phone take any SSON value by
disabling it on the phone. Now statically program the required file server address and save. The
phone will come with the modified file server address on automatic reboot.
3) When both SSON and “* to program” are used to configure the same parameter, then the
priority is given to SSON. This could be addressed after having the requirements in place
detailing the order of preference of all the local procedures used to set parameters on the phone
and not just SSON vs “* to program” menu.
Copyright Avaya 2009 All rights reserved
Page 2 of 8
1692 Release R1.00 Readme (November 9, 2009)
1692 Release R1.00 package contents
For more information on upgrading or configuring the Avaya 1692 IP telephones, refer
Appendix A. For information on using the 1692 IP telephones, refer the user and quick
reference guides at http://support.avaya.com.
The package contains all the files necessary to upgrade Avaya 1692 IP telephones to H.323 Release
R1.00.The following files are included in each package:
1692_000100.bin (APP. file)
bootrom.id (Boot file)
1692upgrade.txt (Avaya upgrade script file)
000000000000.cfg (XML file required for BootServer Process)
sip_backup.cfg (Required for TLS and Localization)
phone1_vcvr.cfg (Required for TLS and Localization)
1692Localization folder containing all the supported language folders
1692 Localization folder should contain the following supported language folders along with
corresponding “1692-dictionary.xml” files:
French_Canada
French_France
German
Italian
Spanish
System specific parameters should be entered into the 46xxsettings.txt file which is available for
separate download at support.avaya.com
Procedures and information:
The phone consists of two parts: Application image and BootROM image. Upgrade and
downgrade facility for both the images are available.
The required Bootserver menu has been preprogrammed in the phone.
The Bootserver menu and the entire boot process have been demarcated from the application
load by changing the font size.
1692 supports four types of file servers (FTP, TFTP, HTTP, HTTPS). Currently a particular File
server needs to be selected from ‘* to program’ menu during boot-up.
The Avaya upgrade script file name is “1692upgrade.txt”.
Presently, the Bootserver process also expects the “000000000000.cfg” XML file to be
available in file server directory.
Correspondingly, the APPNAME (1692_000xxx.bin) given in the “1692upgrade.txt” file needs
to have the same application name and needs to be updated against APP_FILE_PATH field of
the ‘000000000000.cfg’ file.
CONFIG_FILES field into ‘000000000000.cfg’ should contain phone1_vcvr.cfg, sip_backup.cfg
entries.
Copyright Avaya 2009 All rights reserved
Page 3 of 8
Loading...