Copyright Avaya 2006
All rights reserved


This file is the readme for the Avaya one-X™ Deskphone Edition 
9620 and 9630 model IP Telephones.
This file describes the contents of the August 25, 2006 
software distribution package.


The reason for the August 25, 2006 release of this software is:
 - Mutli Language capability with 13 predefined languages and
support of custom languages.
 - Support for the 9600 Gigabit Ethernet Adapter.
 - Language Localization Tool Release 1.0 for the creation
of downloadable custom languages.


For more information on upgrading or configuring the Avaya 9600
IP telephones, see the Avaya one-X™ Deskphone Edition for 9600 Series
IP Telephones Read This First and Administrator Guide for details.
For information on using the 9600 IP telephones, see the user and quick
reference guides for each model.
All documents are available at support.avaya.com  
________________________________________________________________________

This package is available in two formats - zip and exe,
The tar format will no longer be supported.
The package contains all the files necessary to upgrade
Avaya 9600 IP telephones to H.323 Release 1.1.

________________________________________________________________________

The following files are included in each package:

ha96xxd110.bin - The 9600 R1.1 H.323 phone application

hb96xxd110.bin - The 9600 R1.1 H.323 boot application

Thirteen predefined language files:
	mlf_chinese.txt
	mlf_korean.txt
	mlf_japanese.txt
	mlf_hebrew.txt
	mlf_russian.txt
	mlf_dutch.txt
	mlf_german.txt
	mlf_french_paris.txt
	mlf_portuguese.txt
	mlf_spanish_latin.txt
	mlf_italian.txt
	mlf_french_can.txt
	mlf_spanish.txt

96xxupgrade.txt - This file is downloaded by the Avaya 9600 IP telephones 
and instructs the telephones how to upgrade. DO NOT EDIT this file.
You MUST USE the 96xxupgrade.txt file included in this package to
upgrade to R1.1.

96xxreadmeR110.txt - This readme file.

System specific parameters should be entered into the
46xxsettings.txt file which is available for separate download at
support.avaya.com

________________________________________________________________________

To upgrade your Avaya 9600 IP Telephones:

 - Unzip the zip or executable file in the root directory of the 
   outbound file directory of your HTTP server.
 - Make any adjustments to your 46xxsettings.txt file.
 - Reset your Avaya 9600 IP telephones.

________________________________________________________________________

HIGH LEVEL DESCRIPTION OF R1.1
The Avaya one-X™ Deskphone Edition family of next-generation IP telephones
delivers a unique communications experience that drives increased employee
productivity. 

KEY FEATURES:
 - Intuitive User Interface
 - Superior Audio Quality, support of G.722 wide band codec.
 - New design and display
 - Modules and Adapters
 - Phone models designed for user profiles
For more information, see the one-X Edition Family Brochure
or the user guides available on support.avaya.com.

DIFFERENCES BETWEEN THE 9600 AND 4600 IP PHONES - WHAT IS NEW:

 - Multi-Language support using downloadable language files and a single
application file. Up to 4 languages can be downloaded via HTTP/HTTPS.
13 language files are delivered with the distribution package and 
with the Language Localization Tool, custom language files can be created.

 - The configuration files and firmware files are downloaded via HTTP only.

 - A new 96xxupgrade.txt configuration file is provided with each 9600 IP
telephone software distribution, but a 46xxsettings.txt configuration file
continues to be used for customer settings so that only a single file needs
to be maintained to support both 4600 and 9600 IP telephones.

 - Backup and restore of user data is also done via HTTP only
(requires Apache R2.0.55 or greater or Microsoft IIS 5.5 or greater).
You may also use the Avaya File Server Application available on
support.avaya.com.
Digest authentication is supported for improved security.

 - DHCP uses site-specific option 242 as a default instead of option 176
(the IETF is reclassifying option numbers 128-223 for standard use; see RFC 3942).

 - After a configurable period of inactivity, the display backlight will
turn off to conserve power (the default period is 2 hours).

 - After a configurable period of inactivity, a screen saver will be
displayed (the default period is 4 hours). 

 - A new HIS cord must be used to connect a headset to a 9600 telephone.

 - The Phone Application Suite 2.2 (formerly known as the "AG250 Application Gateway")
will provide support for the 9600 IP telephones. Previous releases of the Phone
Applications Suite, including Release 2.1, do not support 9600 IP telephones.

 - The 9600 IP telephones support AES audio encryption for enhanced security, AEA
is no longer supported. For proper operation with 4600 IP telephones, AEA should be
removed from the list of supported Media Encryption types, or at a minimum, AEA
must be listed after AES. The Media Encryption parameters can be found on page 1
of the IP Codec Settings form.

DIFFERENCES BETWEEN THE 9600 AND 4600 IP PHONES - WHAT IS NO LONGER SUPPORTED:

 - Existing HIP and HIC headset cords are not supported by 96xx telephones.

 - The CTI protocol is no longer supported for use with IP Softphone.

 - DHCP options 43 and 66 are not supported by 96xx telephones.
Option 176 may be used as the site-specific option, but it would
have to be manually programmed into each telephone.

 - Only a subset of parameters may be set in the DHCP site-specific option,
others must be set in a 46xxsettings.txt configuration file.

For more information on differences between 9600 Series and 4600 Series
IP Telephones, see the Avaya one-X™ Deskphone Edition for 9600 Series
IP Telephones Administrator Guide.

________________________________________________________________________

KNOWN ISSUES AND INTERACTIONS IN R1.1

 - When logging out a 9600 IP telephone, the display will show 
"Logging out ..." in English regardless of the language selected.

 - RTCPMON can only be set with dotted decimal IP addresses. 
DNS names are not accepted. 

 - It is recommended that WML pages intended for display through
the 9600 IP Telephone Browser be limited to 3.5 Mbytes.

 - When an SBM24 expansion module is used with a 9600 IP telephone,
the button labels on the SBM24 may not be displayed in the selected
language. Button labels generated from CM will always be displayed
in English, regardless of the selected language. Personalized
labels that are localized by editing the backup file will be displayed
properly in all languages except for Japanese, Chinese and Korean.
Personalized SBM24 button labels should not be localized to Japanese,
Chinese or Korean as these will not display properly.

 - Note to 802.1X users without PoE (Power over Ethernet):
Changing the phone LAN connection on the Layer 2 switch
may require a phone reboot. For guaranteed proper operation,
the phone should be reset after the new connection is made.

 - In order to prevent a cached version of the backup file from
being sent to the IP Telephones during a restore, the address of
the HTTP server used for backup should be added to the WMLEXCEPT
list in the 46xxsettings.txt file.
See the Avaya one-X™ Deskphone Edition for 9600 Series IP Telephones
Read This First and Administrator Guide for more information on
using the WMLEXCEPT parameter.

________________________________________________________________________

COMMUNICATION MANAGER (CM) COMPATABILITY:

 - Although the 9600 IP phones are supported on Communication
Manager 3.0 and higher, we recommend using the latest
Communication Manager release with 9600 IP telephones.
 
See the “Communication Manager Software & Firmware Compatibility Matrix”
at support.avaya.com for the supported software/firmware versions of
the Media Server, Media Gateway, and circuit packs.

 - CM 3.1 is required to enable G.722 wide band audio.

 - CM 3.1.2 is required for personalization of button labels. Using
an earlier release of CM may result in corrupted button labels.
 
 - Currently Communication Manager does not provide native support for
the 9600 IP Telephones; we recommend that the 9620 IP Telephone be
administered as a 4610 IP Telephone and that the 9630 IP Telephone
be administered as a 4620/4621 IP Telephone

 - TN799C (C-LAN) circuit pack Versions 1 & 2 do not work correctly with
9600 IP telephones since they do not support the long UDP packet lengths required
for signaling encryption. Versions 3 and higher of the TN799C and all versions of
the TN799DP do support the longer packets and work correctly with the 9600 IP
telephones. TN799C version 3 and higher or TN799DP circuit packs should
be used with the 9600 IP telephones.

 - There is an MTU size incompatibility with the Cajun P882 and P550
enterprise switches. This may prevent large packets from either the 9600
IP telephones or CM from being forwarded correctly when 802.1Q tagging is
enabled. To work around this problem, 802.1Q tagging must be enabled
on the Cajun ports to which the telephones and C-LANs are connected.
If you are connecting a PC to the second Ethernet jack on the phone
in this configuration, the NIC on the PC needs to be set to support
802.1Q tagging.

 - For information on which system and station features
should be administrated for proper operation of the Avaya 9600
IP telephones, see the Avaya one-X™ Deskphone Edition for 9600 Series
IP Telephones Read This First, available on support.avaya.com.

________________________________________________________________________
OpenSSL License Agreement
This program includes software developed by the OpenSSL Project which was used
by Avaya pursuant to the following license.
Copyright (c) 1998-2003 The OpenSSL Project.  All rights reserved.
Redistribution and use of the software developed by the OpenSLL  Project,
in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must
display the following acknowledgment: "This product includes software developed
by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse
or promote products derived from this software without prior written permission.
For written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL"
appear in their names without prior written  permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the
OpenSSL Toolkit (http://www.openssl.org/)"
________________________________________________________________________
W3C(r) SOFTWARE NOTICE AND LICENSE
Copyright (c) 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, 
Institut National de Recherche en Informatique et en Automatique, Keio University). 
All Rights Reserved. http://www.w3.org/Consortium/Legal/
This W3C work (including software, documents, or other related items) is being provided
by the copyright holders under the following license. By obtaining, using and/or copying
this work, you (the licensee) agree that you have read, understood, and will comply with
the following terms and conditions:
Permission to use, copy, modify, and distribute this software and its documentation,
with or without modification,  for any purpose and without fee or royalty is hereby
granted, provided that you include the following on ALL copies of the software and
documentation or portions thereof, including modifications, that you make:
The full text of this NOTICE in a location viewable to users of the redistributed or 
derivative work. 
Any pre-existing intellectual property disclaimers, notices, or terms and conditions. 
If none exist, a short notice of the following form (hypertext is preferred, text is
permitted) should be used within the body of any redistributed or derivative code: 
"Copyright (c) 2004 World Wide Web Consortium, (Massachusetts Institute
of Technology, Institut National de Recherche en Informatique et en Automatique,
Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/" 
Notice of any changes or modifications to the W3C files, including the date changes
were made. (We recommend you provide URIs to the location from which the code is derived.) 
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE
USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS,
COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
The name and trademarks of copyright holders may NOT be used in advertising or
publicity pertaining to the software without specific, written prior permission.
Title to copyright in this software and any associated documentation will at all 
times remain with copyright holders.
________________________________________________________________________
Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
________________________________________________________________________

HTTP Server functionality is provided by the GoAhead WebServer 2.1,
Copyright (c) 2004 GoAhead Software, Inc. All Rights Reserved.
________________________________________________________________________

© 2006 Avaya Inc.  All Rights Reserved.
Notice
While reasonable efforts were made to ensure that the information in this 
document was complete and accurate at the time of printing, Avaya Inc. can 
assume no liability for any errors. Changes and corrections to the information
in this document may be incorporated in future releases.
Documentation disclaimer.
 
Avaya Inc. is not responsible for any modifications, 
additions, or deletions to the original published version of this documentation 
unless such modifications, additions, or deletions were performed by Avaya. 
Link disclaimer

Avaya Inc. is not responsible for the contents or reliability of any linked 
Web sites referenced elsewhere within this Documentation, and Avaya does not 
necessarily endorse the products, services, or information described or offered 
within them. We cannot guarantee that these links will work all of the time and 
we have no control over the availability of the linked pages.

License
USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER’S ACCEPTANCE OF THE 
TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA 
WEBSITE AT http://support.avaya.com/LicenseInfo/  (“GENERAL LICENSE TERMS”).  
IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) 
TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT.
Avaya grants End User a license within the scope of the license types described below. 
The applicable number of licenses and units of capacity for which the license is 
granted will be one (1), unless a different number of licenses or units of capacity 
is specified in the Documentation or other materials available to End User. 
“Designated Processor” means a single stand-alone computing device. “Server” means 
a Designated Processor that hosts a software application to be accessed by multiple 
users. “Software” means the computer programs in object code, originally licensed by 
Avaya and ultimately utilized by End User, whether as stand-alone Products or 
pre-installed on Hardware. “Hardware” means the standard hardware Products, originally 
sold by Avaya and ultimately utilized by End User. 

License Type(s):  
Designated System(s) License (DS). End User may install and use each copy of the 
Software on only one Designated Processor, unless a different number of Designated 
Processors is indicated in the Documentation or other materials available to End User. 
Avaya may require the Designated Processor(s) to be identified by type, serial number, 
feature key, location or other specific designation, or to be provided by End User to 
Avaya through electronic means established by Avaya specifically for this purpose.

Copyright 
Except where expressly stated otherwise, the Product is protected by copyright 
and other laws respecting proprietary rights. Unauthorized reproduction, transfer, 
and or use can be a criminal, as well as a civil, offense under the applicable law.
Third-party Components
Certain software programs or portions thereof included in the Product may contain 
software distributed under third party agreements (“Third Party Components”), which 
may contain terms that expand or limit rights to use certain portions of the 
Product (“Third Party Terms”). Information identifying Third Party Components and 
the Third Party Terms that apply to them is available on Avaya’s web site 
at: http://support.avaya.com/ThirdPartyLicense/

Avaya fraud intervention
If you suspect that you are being victimized by toll fraud and you need technical 
assistance or support, call Technical Service Center Toll Fraud Intervention 
Hotline at +1-800-643-2353 for the United States and Canada.  Suspected security 
vulnerabilities with Avaya Products should be reported to Avaya by sending mail
to: securityalerts@avaya.com.  
For additional support telephone numbers, see the Avaya Web site:  
http://www.avaya.com/support
 
Trademarks
Avaya, AUDIX, DEFINITY, and COMMUNICATIONS MANAGER  and the Avaya logo are 
registered trademarks and/or service marks of Avaya Inc. in the U.S. and certain 
other jurisdictions.
 
All other trademarks are the property of their respective owners.
Document ordering information:
Avaya Publications Center
Voice:		+1-207-866-6701
		1-800-457-1764 (Toll-free, U.S. and Canada only)
Fax:		+1-207-626-7269
		1-800-457-1764 (Toll-free, U.S. and Canada only)
Write:		Globalware Solutions
		200 Ward Hill Avenue
		Haverhill, MA 01835 USA
		Attention: Avaya Account Manager
Web:		http://www.avaya.com/support 
E-mail:		totalware@gwsmail.com 
Order:		Document No. 07-300334 , Issue 1.0 	
		May 2005
 
For the most current versions of documentation, go to the Avaya support Web site:
http://www.avaya.com/support 

Avaya support
Avaya provides a telephone number for you to use to report problems or to ask 
questions about your contact center. The support telephone number is 
1  800  242  2121 in the United States. For additional support telephone numbers, 
see the Avaya Web site:  http://www.avaya.com/support
___________________________________________________________________________________

~~END OF FILE~~
