Downloading Avaya 46xx IP Telephone Software Using Avaya Media Servers Abstract This paper provides information on using HTTP/HTTPS or TFTP file transfer protocols to transfer Avaya 46xx IP telephone software from Avaya Media Servers to Avaya 46xx IP telephones. BDH Editor; Reviewed: RJS, JWS,CLB,ML,RS,RKP,TGS,BH, PMS, RGF, NHK 4/20/06 Application Notes ©2006 Avaya Inc. All Rights Reserved.
Table of Contents 1. 2. 3. Introduction............................................................................................................................. 3 Overview................................................................................................................................. 3 IP Telephone Software File Transfers Using TFTP ............................................................... 4 3.1. TFTP Protocol Support ...............................................................
1. Introduction This paper provides information regarding the use of Avaya Media Servers to transfer configuration and software files to Avaya 46xx IP telephones. Avaya S8300B or later S8300 Media Servers can be used as TFTP file servers for Avaya 46xx IP telephones as long as the Media Server is running Communication Manager 2.1.1 or later releases.
support software file transfers via HTTP/HTTPS and many configurations might have a mixture of telephones that support HTTP/HTTPS downloads and telephones that only support TFTP downloads. See section Configuring IP Telephones to use HTTP/HTTPS for further details. 3. IP Telephone Software File Transfers Using TFTP 3.1. TFTP Protocol Support Existing 46xx IP telephones support software downloads using TFTP. downloads can be found on the Avaya support website.
Figure 1: Enabling TFTP Service Figure 2: Enabling Firewall for TFTP BDH Editor; Reviewed: RJS, JWS,CLB,ML,RS,RKP,TGS,BH, PMS, RGF, NHK 4/20/06 Application Notes ©2006 Avaya Inc. All Rights Reserved.
3.2.2. Putting Software RPMs on the Media Server The method used to download 46xx IP telephone software RPMS onto a Media Server is the same whether TFTP or HTTP/HTTPS is being used. This information is covered in the Downloading Software RPMs onto Media Servers section of this document. 3.3. Configuring IP Telephones to use TFTP 3.3.1.
Figure 3: IP Telephones Supporting TFTP & HTTP/HTTPS Downloads IP Telephone IP Telephone Software Releases TFTP HTTP/HTTPS 4606 / 4612 / 4624 4630 / 4630SW 4625SW 4610SW 4620 / 4620SW / 4621SW / 4622SW 4602SW / 4602 4601 All Releases All Releases All Releases All Releases All Releases All Releases (except SIP R1.x) All Releases Not Supported Not Supported Not Supported R2.1.3 or later R2.1.3 or later R2.2 or later (and SIP R1.x) R2.
Figure 4: Displaying HTTP/HTTPS Network Service 4.2.2. Putting Software RPMs on the Media Server The method used to download software RPMs on the Media Server is the same whether TFTP or HTTP/HTTPS is being used. This information is covered in the Downloading Software RPMs onto Media Servers section of this document. 4.3. Configuring IP Telephones to use HTTP/HTTPS 4.3.1.
Figure 3: IP Telephones Supporting TFTP & HTTP/HTTPS Downloads for a list of minimum telephone software releases that support HTTP/HTTPS downloads. In some situations it is necessary to support 46xx IP telephone software file transfers via HTTP/HTTPS on a Media Server and other telephone software file transfers using TFTP or HTTP on a separate external server.
All 46xx IP telephones supported by a specific DHCP server can be configured to use HTTP and an external server to obtain software updates by adding the string “HTTPSRVR=nnn.nnn.nnn.nnn” to the current DHCP option string (option 176 in most cases). In this example nnn.nnn.nnn.nnn is the IP address of the desired external server. Again, only 46xx IP telephones that are running software releases that support HTTP/HTTPS will acquire software updates from the external server via HTTP.
Figure 5: Launch Maintenance Web Pages 4. Click Download Files under the Miscellaneous heading. 5. Enter or browse to the 46xx IP telephone tar file containing the telephone software RPM file to be downloaded in the first File(s) to download field. Make sure to check the Install this file on the local server check box. Then click the Download button. See Figure 6: Maintenance Web Page Downloads. BDH Editor; Reviewed: RJS, JWS,CLB,ML,RS,RKP,TGS,BH, PMS, RGF, NHK 4/20/06 Application Notes ©2006 Avaya Inc.
Figure 6: Maintenance Web Page Downloads 6. Verify the 46xx IP telephone software files successfully downloaded to the Media Server. See Figure 7: Software RPM Downloaded Successfully. BDH Editor; Reviewed: RJS, JWS,CLB,ML,RS,RKP,TGS,BH, PMS, RGF, NHK 4/20/06 Application Notes ©2006 Avaya Inc. All Rights Reserved.
Figure 7: Software RPM Downloaded Successfully 7. It is possible that telephone software RPMs fail to download because previously downloaded RPMs cannot be overwritten. In this case the following error message might be encountered and the existing RPM(s) must be removed: Package .rpm FAILED to install. Package is already installed.
Figure 8: IP Telephone Settings Unavailable Figure 9: IP Telephone Settings Page 3. Click on the Phone Settings… button. This displays Figure 10: IP Telephone Configuration Page. This page is used to configure 46xx IP telephones. If a phone BDH Editor; Reviewed: RJS, JWS,CLB,ML,RS,RKP,TGS,BH, PMS, RGF, NHK 4/20/06 Application Notes ©2006 Avaya Inc. All Rights Reserved.
settings file 46xxsettings.txt is placed in the tftpboot directory the fields on the Figure 10: IP Telephone Configuration Page are populated with the information in the 46xxsettings.txt file. The 46xxsettings.txt file is not part of the 46xx IP telephone software RPM and is not placed in the tftpboot directory when the telephone software RPM is downloaded onto the Media Server.
8. Security HTTP/HTTPS is recommended for 46xx IP telephone software file transfers because it provides better performance and security than TFTP and is supported on all S8xx0 series Media Servers running Communication Manager 2.1.1 or later releases. Transport Layer Security (TLS) is a protocol that enables authentication and data encryption over insecure networks. TLS runs on top of TCP and adds security to any protocol that uses reliable connections. It is most commonly used with HTTP to form HTTPS.
back into service before updated software could be downloaded. Processor occupancy increased 7 to 10% consistently throughout the 8 minute download interval. Due to these test results, it is not recommended to use the Avaya Media Server to download 46xx IP telephone software to more than 300 telephones when using HTTP/HTTPS.
©2006 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice.
