Copyright Avaya 2003, 2004 All rights reserved This is the readme file for the Release 1.8.3 of the Avaya IP Telephone Software for 4624/4612/4606 IP Telephones. There are four files that apply to the Avaya 4624/4612/4606 IP Telephones: def24r1_8_3.bin - The 4624/4612 release 1.8.3 application. def06r1_8_3.bin - The 4606 release 1.8.3 application. bbla0_83.bin - The boot application. 46xxupgrade.scr - The upgrade script the IP Telephones will download. This is not the customer administered script file, 46xxsettings.scr. (Note: 46xxupgrade.scr also applies to the Avaya 4601, 4602, 4602SW, 4610SW, 4620, 4620SW and 4690 IP Telephones.) IMPROVEMENTS IN R1.8.3 FROM R1.8.2: · This release delays the CTI registration until requested. · Audio performance improvements (including one-way audio talk paths). IMPROVEMENTS IN R1.8.2 FROM R1.8.1: Enhancements: · ICMP and ARP filters have been enhanced. · If the signaling channel between the phone and the Avaya call server is disrupted or disconnected, the phone will attempt to maintain an active call until the user goes on-hook regardless of the state of the far-end. This will allow some calls to continue during a network disruption. Fixes: · R1.8.2 will now reboot on receiving DHCP NAK packet from the DHCP server. Previously a DHCP NAK could hang the telephone. · Setting VLANTEST=0 allows the telephone to continue seeking a DHCP server on the initial VLAN indefinitely. Previously VLANTEST=0 was treated as if VLANTEST had not been set and the default value, 60 seconds, was used. · L2QVLAN can now be set in DHCP or TFTP. Previously L2QVLAN must be set in DHCP. IMPROVEMENTS IN R1.8.1 FROM R1.8: · With 802.1Q VLAN tagging enabled all phones can accept Ethernet frame sizes of up to 1522 bytes in length. With this regard all phones conform to IEEE Ethernet standards. · Local administrable options for the Avaya call server (MCIPADD) and the TFTP file server (TFTPSRVR) can be used in conjunction with other DHCP programmed options. These two local options will be used if no other values are assigned for them in the following DHCP options, as defined in RFC 2131 & RFC 2132: siaddr, Option 66, and the Site Specific Option string (Option 176). KNOWN ISSUES IN R1.8.1 (in addition to R1.8): · In the DHCP Site Specific Options string, if a TFTP file server sub-directory (TFTPDIR) is defined, it must be defined prior to the TFTP file server (TFTPSRVR) within the same options string. For example: ...,TFTPDIR=phone\,TFTPSRVR=AvayaTFTPserver,... NEW FEATURES IN 1.8: · Voice stream media encryption. · Out of order packet resynchronization for the voice stream. · Automatic VLAN tagging · IrDA Email - see infrared file for additional information. · Can administer with the TFTP server to disable the local user from manually configuring the telephone. The new variable is PROCPSWD. IMPROVEMENTS IN R1.8 FROM R1.73: · Speakerphone performance enhancements. · Permit global setting of Automatic Gain Control for headset (AGCHEAD) and handset (AGCHAND) via a TFTP script file or DHCP Site Specific Option setting. Default values are enabled for both values. The user may also set values locally when using the <mute>AGC# dial sequence. · Improved NetBios filtering. · Improved headset performance. · Improved support for mobile workers who use Avaya IP Softphone including automatic re-registration after Avaya IP Softphone unregisters. · Improved IrDA interface. · Improved denial of service attack prevention. · Added layer 2 and 3 QOS tagging to RAS messages. · Removed SNMP vulnerability that occurred when a hacker attempted to write to standard MIB. · RTCP was enhanced to remove large spikes in reported jitter buffer at the completion of a call. · Automated recovery from "# to reset" events that previously required user intervention. · Faster recovery from Gatekeeper failures. · The phone ignores unused DHCP options. · Preserve case sensitivity for TFTP script filenames. Resolves Linux compatibility issue. KNOWN ISSUES IN R1.8: · With VLANTEST=0 set shows VLANTEST=60 · Option 66 not setting TFTPSRVR address on the Microsoft 2000 Server. Use DHCP Site Specific Option to specify the TFTP server addresses. · Disabled the display of the Network Audio Quality Assessment. · The Computer Telephony Interface (CTI): When a PC that cannot handle VLAN tagged packets is trying to use CTI to control a phone that has VLAN tagging turned on, the PC will drop the tagged data packets. To resolve this, set up network equipment such that it strips the tags from the packets that are destined for the PC. Alternatively, don't use VLAN tagging on the phone. · 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 you must set the option "Direct IP-IP Audio Connections" to No on the ACP station form for the IP Telephone behind the NAT device prior to CM 1.3. 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. · A statically programmed phone won't detect IP address conflicts when spanning tree is enabled on a phone's port. Disable spanning tree or enable portfast. · Media encryption should be enabled on the switch as preferred when there are R1.73 and R1.8 phones in your network. You may enable media encryption to always if all phones have R1.8 software installed. KNOWN ISSUES IN R1.8 SNMP MIB: General: · Lists of comma separated IP addresses may contain repeated entries. Multiple entries of the same IP address are not consolidated. · IP addresses may sometimes be listed in dotted-decimal format even if the values were specified in DNS format. Group 1: · endptTFTPSRVR: value contains a single IP address of the current TFTP file server. endptTFTPSRVR does not show a complete list of all available TFTP file servers. The value is "0.0.0.0" if the first specified entry is invalid · endptSMTPSRVR: the SMTP server value will appear as it was specified, as an IP address or server name (DNS). The value is "0.0.0.0" if the first specified entry is invalid. Group 3: · endptAPPINUSE: value represents the name of the upgrade script file. Reference endptAPPNAME (Group 1) for the name of the current phone application. · endptUPGRADESCRIPT & endptAPPSTAT: error values are only reported for phone malfunction or network errors. Error codes are not reported for the attempted use of invalid file names. Group 4: · endptDSCPBBE: value does not reflect the setting selected by the Avaya Site Administration terminal for the respective network region. R1.8 NOTES: · While the recommended DHCP lease time is infinite, the lease time should never be less than 5 minutes. · The phone will try finding an available router in the user-provided list, if the first one listed has not responded to an ARP. It will repeat ARPing the router up to 30 times, to accommodate short outages. The phone notifies the user if can't find a reachable router address. It also notifies the user about conflicts between the router address with the phone's IP address and subnet mask. · The phone will install the first three DNS servers without pinging. · R1.8 requires 9.5 or later Communication Manager switch Release. · 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 for more information on DHCP and DNS enhancements: http://support.avaya.com/elmodocs2/avayaip/common/instadmin.htm · 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 number 555-233-504 http://www.avayadocs.com/. · The following features require Avaya Communication Manager 1.3 (CM 1.3): Remote Traceroute Cancel AEA Media Encryption NAT shuffling UPGRADING FROM R1.8.2/R1.8.1/R1.8/R1.73/R1.72/R1.71/R1.7/R1.61/R1.6/R1.51/R1.5 The upgrade script will upgrade your IP Phone to R1.8.3 Release.Download Driver Pack
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.