4610_20_readme_R2_3.txt Driver File Contents (46xxH323_111405.zip)

Copyright Avaya 2005
All rights reserved

This file is the readme for Avaya software, Release 2.3 for
the Avaya 4610SW, 4620, 4620SW, 4621SW and 4622SW IP Telephones.
This release letter describes the major changes and improvements
between the software releases R2.2.3 and R2.3. 

There are a number of files that apply to the Avaya 4610 and 4620 type 
IP Telephones. The actual files required to upgrade depends on which
language version is used, as follows:

1) For single-byte software to support English and Western European fonts on all sets:
a20d01a2_3.bin - The 4620 English/European language R2.3 application.
b20d01a2_3.bin - The 4620 boot application.
a20d01b2_3.bin - The 4620SW/4621SW/4622SW English/European language R2.3 application. 
b20d01b2_3.bin - The 4620SW/4621SW/4622SW boot application. 
a10d01b2_3.bin - The 4610SW English/European language R2.3 application. 
b10d01b2_3.bin - The 4610SW boot application. 
46xxupgrade.scr - The script the IP Telephones will download. 

2) For multi-byte software to support English, Chinese and
Cyrillic fonts on sets as noted:
a20d01a2_3.bin - The 4620 English/European language R2.3 application. 
b20d01a2_3.bin - The 4620 boot application.
a20c01b2_3.bin - The 4620SW/4621SW/4622SW English/Chinese/Russian language R2.3 application.
b20d01b2_3.bin - The 4620SW/4621SW/4622SW boot application. 
a10c01b2_3.bin - The 4610SW English/Chinese/Russian language R2.3 application. 
b10d01b2_3.bin - The 4610SW boot application. 
46xxupgrade.scr - The script the IP Telephones will download. 

3) For multi-byte software to support English, Japanese and
Cyrillic fonts on sets as noted:
a20d01a2_3.bin - The 4620 English/European language R2.3 application. 
b20d01a2_3.bin - The 4620 boot application.
a20j01b2_3.bin - The 4620SW/4621SW/4622SW English/Japanese/Russian language R2.3 application.
b20d01b2_3.bin - The 4620SW/4621SW/4622SW boot application. 
a10j01b2_3.bin - The 4610SW English/Japanese/Russian language R2.3 application. 
b10d01b2_3.bin - The 4610SW boot application. 
46xxupgrade.scr - The script the IP Telephones will download.


Note: This 46xxupgrade.scr file applies to the Avaya 4601, 4602,
	4602SW, 4606, 4612, 4610SW, 4620, 4620SW, 4621SW, 4622SW, 4624,
	4625SW and 4690 IP Telephones, both SIP and H.323, where appropriate.



IMPROVEMENTS IN R2.3

.	Support of Signaling Channel Encryption is enabled.
.	Support of Unnamed Registration is enabled.
.	Support for Extensible Authentication Protocol over the
	Local Area Network (EAPOL) packet forwarding
.	More accurate Network Audio Quality screen & VoIP Monitoring
	Manager (VMM) reporting.


KNOWN ISSUES AND INTERACTIONS IN R2.3


·	IP Softphone will not be able to register with the IP Telephone in the “Control of
	Avaya Telephone (Via the telephone)” configuration if Signaling Channel Encryption
	is set to “ANY AUTH” or “STRONG ONLY”. To resolve, either:
		- Use IP Softphone in the “Control Avaya Telephone (Via the server)” configuration
		[this requires appropriate licenses]. In this case, the IP Network Region should be
		configured for either “ANY AUTH” or “CHALLENGE ONLY”.
		- Provision the IP Network Region for the IP Telephone with Signal Channel
		Encryption as “CHALLENGE ONLY”.
·	If the Avaya circuit pack TN799C (CLAN board) is used, it must be at vintage 3, or greater.
·	If a Cajun 550 or Cajun 880 is being used, a separate Trunk port for each CLAN will be needed.
·	If the Avaya circuit pack TN2602 (IP Media Processor board) is used with CM3.0.1, there may be
	instances where no voice path exists when media encryption is enabled. A workaround
	for this is to disable media encryption.
·	The use of Merge Tests by a Catapult/ANS server is not supported.
·	In some cases, when upgrading software via a TLS server, the phone may reboot.
·	When in Unnamed Registration mode on a 4610SW, after the far end party ends the call,
	the dial pad keys are not disabled and may display dialed digits on top line.
	To clear the display, depress the switch hook twice.
·	When in Unnamed Registration mode on a 4610SW, after a call is made and ringback
	is heard, dialed digits will be accepted and displayed on top line display after the
	called party's number. These digits also are seen on the call appearance. Once the
	4610SW goes on hook to end the call, the digits are cleared from the display.
·	When using a Windows 2003 server with IIS (version 6.0) for HTTP download, the HTTP download
	may fail. The phone will receive an HTTP 404 error when retrieving the "46xxupgrade.scr"
	file. This is a known behavior of the IIS (version 6.0) where the web server does not
	serve files with unknown mime types. In the case of 46xx IP telephones, this includes
	mime types being files with ".scr" extension and binary files with ".bin" extensions.
	A workaround for this requires steps be taken in the administration of the web server to
	enable HTTP download of these file types. These mime types need to be enabled on the
	webserver for the phones to successfully download these files. A complete description
	of the issue can be found on the Microsoft support website.
·	DO NOT downgrade from this release to R2.0 unless specifically
	instructed to do so by an Avaya Tier 4 associate.


DEFECTS RESOLVED IN R2.3


IPT00007211	 Registering on extension with wrong set type	 
IPT00006963	 Local procedures LOGOFF	 
IPT00006961	 Idle Display while connection, after 2nd call	 
IPT00006959	 Idle display while active connection	 
IPT00006957	 ALERTing mode control - Phones without display	 
IPT00006783	 LOGing  
IPT00006602	 When using HTTP, the file server address on the 4610sw 
   		 phone is not displayed .	 	 
IPT00006552	 test plug stops responding under heavy load	 
IPT00006488	 Phone display is locked with error “Web:301 Moved Permanently”.	
IPT00006446	 No sending of switch-hook state change after ceasing local procedure	 
IPT00006291	 PSA associate do not change the display from TTI screen to fully 
    		 registred screen	  
IPT00005035	 Link recovery does not work when phone/CM reuses Session ID	 
IPT00004907	 Trace route command from CM SAT doesnt work	 	 
IPT00004609	 Modify CNA testplug protocol to prevent RTP test incorrectly reporting 
		 100% pkt loss	  
IPT00004436	 File server address been shown different at mute addre# and thr' 
	 	 view ip settings	 
IPT00004206	 Call Log Detail Screens not aligned correctly for Hebrew	 
IPT00004134	 Ring - Blip, Ring - Blip	 
IPT00004126	 Stop spawning of multiple http tasks	 
IPT00004074	 Multiple HTTP processes spawned (frozen on boot!)	 	 
IPT00003585	 501ms One-way network delay	

___________________________________________________________________________
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.
________________________________________________________________________

Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: ftp, load: 5.45