4601_02_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 4601 and 4602 type IP Telephones.
This release letter describes the major changes and improvements
between the software releases R1.8.2 and R2.3. 

There are a number of files that apply to the
Avaya 4601, 4602 and 4602SW IP Telephones.

For single-byte software to support English and Western European fonts on all sets:
cvt01_2_3.bin - The 4601 conversion boot application
cvt02_2_3.bin - The 4602 conversion boot application
cvt02sw_2_3.bin - The 4602SW conversion boot application
b01d01b2_3.bin - The 4601 boot application. 
a01d01b2_3.bin - The 4601 English/European language R2.3 application.
b02d01b2_3.bin - The 4602/02SW boot application. 
a02d01b2_3.bin - The 4602/02SW English/European language R2.3 application.
46xxupgrade.scr - The script the IP Telephones will download. 


Note: This 46xxupgrade.scr file applies to the Avaya 4601, 4602,
	4602SW, 4606, 4610SW, 4612, 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 of DHCP Option 12. The telephones will send a unique Host
	Name in DHCP Option 12.  The name will be AV[ALEX]ffffff.  The letters AV,
	followed by one of A, L, E, or X, followed by 6 hexadecimal digits.
	The name is unique and based on the MAC address of the telephone.
·	Layer 2 tagging controlled by DHCP.
·	Keypad procedures like <hold>VIEW# can now be accessed during periods
	when the initialization can be interrupted.  This can aid in debugging.
·	Automatic Gain Control (AGC) on headset and handset.
·	Support forwarding of Bridge Protocol Data Units (BPDUs)

·	Ability to disable all local/hidden procedures except 
	Mute VIEW# via PROCSTAT
·	Enhanced security measures to prevent users from accessing certain
	IP telephone applications. Administrable through TFTP or DHCP
	via APPSTAT.
	- 1 = default; full functionality
	- 0 = Redial and Call Log suppressed; no Speed Dial changes allowed
	- 2 = Call Log suppressed; no Speed Dial changes allowed,
	      1-number Redial allowed
	- 3 = No Speed Dial changes allowed
·	New local/hidden procedures:
	- Mute 47687# (Mute GROUP#), to select group identifier
	- Mute 25327# (Mute CLEAR#), to erase all system values; back to factory defaults
	- Mute 564633# (Mute LOGOFF#), to logoff from the current extenstion
·	Ability to set parameter values in script files for individual phones
	(via MACADDR) or group of phones (via GROUP)
·	Code image file validation before programming FLASH.
·	Voice stream media encryption using AES (Requires CM2.0)
	Note: It is highly recommended that if media encryption is used,
	either AES or AEA2, the TN2302AP circuit pack should be running
	firmware release 72 or later. This release can be obtained
	from the support.avaya.com web site.
·	Enhanced Alternate Gatekeeper and Link Recovery (Requires CM2.0)
		- Improves detection of and recovery time from failure
		  of call signaling link
		- Differentiates between IP Addresses on same Gatekeeper 
		  versus others (e.g., LSP or alternate Call Server)
·	Enhanced speakerphone performance
·	RTCP was enhanced to remove large spikes in One-way network delay
	Network audio quality metric.
·	User can set PC Ethernet interface speed (10/100),
	duplex (half/full); can also turn-off auto-negotiation
·	Ability to change SNMP community string
·	Ability to designate source IP address(es) for SNMP queries


PRE-REQUIREMENTS FOR USING THE H323 R2.3 APPLICATION

·	Any 4601, 4602 or 4602SW phone must be running R1.8.2 code before
	upgrading to R2.3.
·	The 4601 telephone can only be administered via DHCP.


KNOWN ISSUES AND INTERACTIONS IN R2.3

·	When upgrading from R1.8.2, HTTP and HTTPS are not supported.
·	If Signaling Channel Encryption is set to "STRONG ONLY", IP Softphone will not register. The
	work around for this is to set Signaling Channel Encryption to "AUTH-ANY and CHALLENGE".
·	Use of Avaya IP Softphone in Control of Avaya IP Telephone (via the telephone) mode can 
	only be used if Signaling Channel Encryption is set to "CHALLENGE ONLY".
·	Operation of this release requires that the CLAN board (Avaya circuit pack TN799C) be at
	version 3, or greater.
·	In some cases, when upgrading to software via a TLS server, the phone may reboot.
·	In some cases, rapid (2-3 times per second) switching between call appearances may cause the
	phone to reboot.
·	When using a Windows 2003 server with IIS (ver 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 (ver 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.


DEFECTS RESOLVED IN R2.3

IPT00000463	L2Q Feature Control from Script/DHCP Options	
IPT00001910	Add PTI to H.323 and SIP for 2.2	
IPT00002572	Include IPT4601 and IPT4602 audio changes	
IPT00003574	One way audio path in 4601	
IPT00003808	4601/02: PHONESN, PWBCC and PWBSN values not populated correctly ("?bad?")	
IPT00003809	4601: Line "b" LED flashes continually until user selects line B	
IPT00003822	4602 Reboot when put  extension	
IPT00003891	GAB: 4601 and 4602 do not resort to Unnamed registration without user
		intervention after boot	
IPT00003900	4601/4602: Local Procedure's backspace does not work (key mapping incorrect)	
IPT00003903	4601/4602: Phones continue to display as if still logged in after ext being taken over	
IPT00004074	GAB: ST_Failed (ipt1006471/IPT00003606) Multiple HTTP processes spawned(frozen on boot!)	
IPT00004082	GAB: 4601/02 Implement downgrade from R2.2 to R1.8.2	
IPT00004083	4601/02 Add support for the 5601/02/02SW	
IPT00004330	4601/4602 upgrade by HTTP download not work	
IPT00005342	Re-merge 4602 with 4620 code	
IPT00005660	HTTP Download: Filename validation Unit test fails... launches request	
IPT00005877	4602 is not able to convert from Avaya to Elite code through HTTP	
IPT00005957	4602 Phones take more time for upgrade-downgrade in 2.172g using DHCP & TFTP	
IPT00006291	PSA associate do not change the display from TTI screen to fully registred screen	
IPT00006310	blank display, 4602	
IPT00006349	4602/4601: SNMP entptRASGKLIST not 0.0.0.0 after logoff	
IPT00006446	No sending of switch-hook state change after ceasing local procedure	
IPT00006696	HTTP Download fails on Windows 2003 machine without these additional server
		administration steps.	
IPT00007211	Registering on extension with wrong set type	
IPT00007386	GAB: After Login for unnamed registration the display of 4602/4602SW is totally blank	
IPT00007528	4602: Icon of volume control remains in unnamed registration	
IPT00008058	CONFERENCE button not  working as BACKSPACE key while local programming	
IPT00008105	calls not initiated properly on the feture buttons available (while testing HOLD)
		and display screen displays garbage values	
IPT00008436	4602 phone display not recovered from MuteTEST#	



___________________________________________________________________________
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: web3, load: 2.44