Product Support Notice © 2013 Avaya Inc. All Rights Reserved.
Original publication date: 17-Jan-13. This is Issue #01, published date:
17-Jan-13.
1692 Conference Phone fails to upgrade to new firmware specified in 1692upgrade.txt file.
1692 Conference Phone: Releases 1.3 and 1.4
Workaround or alternative remediation
Backup before applying the patch
Patch install instructions
Patch uninstall instructions
Avaya Security Vulnerability Classification
When using the 1692 official firmware package, 1692 phone does not have any issue to upgrade/downgrade to a new firmware, but if
you JUST change the APPNAME in 1692upgrade.txt, phone will not upgrade to that firmware.
There is a dependency file (000000000000.cfg) that must also be modified. Please find the text similar to the text below in the file
“000000000000.cfg “:
APPLICATION APP_FILE_PATH="1692_014000.bin"
and change it “1692_014000.bin” to the SAME binary in the 1692upgrade.txt file. Phone will now be able to upgrade to new
firmware.
In other words, the name of the .bin file ( the firmware desired for the 1692) must exist in both the 1692upgrade.txt file and the
000000000000.cfg.
This dependency will be removed in future release 1.5.
You have to change the binary name in file “000000000000.cfg “, and then reboot the phone.
n/a
Patch Notes
The information in this section concerns the patch, if any, recommended in the Resolution above.
Security Notes
The information in this section concerns the security risk, if any, represented by the topic of this PSN.
U.S. Remote Technical Services – Enterprise
U.S. Remote Technical Services – Small Medium Enterprise
U.S. Remote Technical Services – BusinessPartners for Enterprise Product
BusinessPartners for Small Medium Product
Please contact your distributor.
Caribbean and Latin America
Europe, Middle East, and Africa
For additional support, contact your Authorized Service Provider. Depending on your coverage entitlements, additional
support may incur charges. Support is provided per your warranty or service contract terms unless otherwise specified.
Disclaimer: ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED “AS IS”.
AVAYA INC., ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO
AS “AVAYA”), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS
OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS’
SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION
WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL
DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS.
SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA.
All trademarks identified by ® or
All other trademarks are the property of their respective owners.
TM
are registered trademarks or trademarks, respectively, of Avaya Inc.
© 2013 Avaya Inc. All Rights Reserved. Page 2