4601readme_R1_8_2.txt Driver File Contents (46xxH323_101005.exe)

Copyright Avaya 2004
All rights reserved

This file is the readme for software Release 1.8.2 for 
the Avaya 4601 IP Telephone.

There are three files that apply to the Avaya 4601 IP Telephone:

4601ape1_8_2.bin - The 4601 R1.8.2 DEFINITY application.
4601bte1_8_2.bin - The 4601 boot application.
46xxupgrade.scr - The script the IP Telephones will download.
(Note: This file also applies to the Avaya 4602, 4602SW, 4610SW, 4620, 
4620SW, 4624, 4612 and 4606 IP Telephones.)

NEW FEATURES IN 4601:

. 	No New features	

IMPROVEMENTS in R1.8.2:

·	This release is to support manufacturability of the product. Once this 
	firmware is installed, downgrades to prior releases will be blocked. 
	Phones shipping from the factory will begin to utilize this firmware 
	as of 7/04.

KNOWN ISSUES in R1.8.2:

.	Must use TN230AP Media Processor(Prowler) V35, V46 or later, 
	otherwise one way talk paths will occur.
 
·	This release supports Network Address Translation (NAT) on 
	Communication Manager 1.0 or later. Direct IP Telephone to
	IP Telephone calls behind NAT	(aka NAT shuffling) requires
	Avaya Communication Manager 1.3 (CM 1.3). If you use NAT on 
	a version of CM prior to 1.3, you must set the option 
	"Direct IP-IP Audio Connections" to No on the ACM station 
	form for the IP Telephone behind the NAT device. If you 
	upgrade to CM1.3 make sure this option is set to Yes so you
	can take advantage of direct IP-IP Audio connections behind
	the NAT device. See Communication Manager documentation, 
	available for download at support.avaya.com for more details.

·	Undefined DHCP/TFTP variables are not initialized with 
	manually defined values.

.	If a parameter set via a script file contains a comma, the 
	parameter value will be truncated in the phone at the comma.  
	For example, if the command SET TFTPDIR "Testb,19" is issued, 
	TFTPDIR will be set to "Testb" in the phone.  Note however 
	that comma separated lists of IP addresses are processed 
	correctly.

.	If an IP Address of 0.0.0.0 appears in a list of IP 
	addresses, this zero address will be treated as a 
	list terminator and addresses following 0.0.0.0 in the 
	list will be ignored.

·	Media encryption is supported only on R1.8 and later releases.
	
KNOWN ISSUES IN R1.8.2 SNMP MIB:

General:

·	IP addresses may sometimes be listed in dotted-decimal format 
	even if the values were specified in DNS format.

Group 4:
·	endptDSCPBBE: value does not reflect the setting selected by 
	the Avaya Site Administration terminal for the respective 
	network	region.

R1.8.2 NOTES:

·	R1.8 for the 4601 IP Telephone requires Communication 
	Manager R1.0 or later.

·	The default DNS names used are:
	AvayaCallServer - Address of Gatekeeper
	AvayaTFTPServer - Address of TFTP Server

·	Other DNS names can be used in DHCP Option #176 or in TFTP 
	scripts	anywhere an IP address was required for R1.7.

·	DNS names are limited to 32 characters.

·	See the LAN Administrator's Guide (document no. 555-233-507) for more 
	information on DHCP and DNS enhancements: www.avaya.com/support

·	G.711 Silence Suppression is administered on the PBX.  There
	is no option to turn it on (or off) at the telephone.  Turning
	on Silence Suppression reduces the bandwidth needed for most
	calls by more than 50%.  Music-on-hold and other low volume
	audio sources will be significantly worse with Silence
	Suppression than without.  Communication Manager network 
	administration details are covered in document 
	no. 555-233-504 at: www.avaya.com/support

·	The following features require Avaya Communication 
	Manager 1.3 (CM1.3):
	Remote Traceroute Cancel
	AEA Media Encryption
	NAT shuffling

4601 SPECIFIC NOTES:
·	The 4601 requires DHCP setting of the IP address (static programming 
	is not available)

·	The Speaker option on the Avaya Communication Manager must be set 
	to "none"

·	Flashing LED's provide feedback on the phones actions and status. 
	See User and Install guide for description of LED feeback. 

.	Downloading of updated software into your 4601 phone may take up to 
	10 minutes.  You should allow this process to complete; do not disconnect
	the phone from the Ethernet cable supplying power to the phone until all 
	updating operations have been completed.

.	Under some conditions, after the 4601 registers, the "B" LED is left 
	in a flashing state. To clear, pick up the handset, and select the "B" 
	line appearance, and then go on hook.


See the LAN Administrators Guide Addendum (document no. 555-233-507ADD) for more information on installing 
and configuring your 4601 IP Telephone at: www.avaya.com/support

For details on phone features of your 4601 IP Telephone,
see the 4601 IP Telephone Users Guide (document 
no. 16-300043) at: www.avaya.com/support
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.30