Application Notes for Converting an Avaya 4600 Series IP Telephone to an Avaya VPNremote Phone Issue 1.0

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for Converting an Avaya 4600 Series IP Telephone to an Avaya VPNremote Phone Issue 1.0 Abstract These Application Notes describe the steps to upgrade an Avaya 4600 Series IP Telephone to a firmware version containing an Avaya IPSec VPN client. This firmware upgrade converts the IP Telephone into the Avaya VPNremote Phone. The steps to convert the VPNremote Phone back to a non-vpn phone are also covered. The configuration presented in these Application Notes makes use of the GROUP ID feature of the Avaya IP telephones. This allows a single Phone Configuration File Server to simultaneously support both non-vpn phones and VPN phones avoiding the need to maintain a separate file server for each firmware type. 1 of 12

2 1. Introduction These Application Notes describe the steps to convert an Avaya 4600 Series IP Telephone into an Avaya VPNremote Phone. The steps to convert a VPNremote Phone back to a non-vpn phone are also covered. The Avaya VPNremote Phone is a software based IPSec VPN client integrated into the firmware of an Avaya 4600 Series IP Telephone. This capability allows the Avaya IP Telephone to be used over a secure IPSec VPN from any broadband Internet connection. The end user experiences the same IP telephone features as if the phone was being used in the office. Avaya IP Telephone models supporting the Avaya VPNremote Phone firmware include the 4610SW, 4620SW, 4621SW, 4622SW and 4625SW. The following terms and associated meanings will be used throughout these Application Notes: non-vpn phone, an Avaya IP Telephone running firmware not containing an IPSec VPN client. VPN phone, an Avaya IP Telephone running firmware containing an IPSec VPN client. The configuration presented in these Application Notes uses a single Phone Configuration File Server to simultaneously support both non-vpn phones and VPN phones avoiding the need to maintain a separate file server for each firmware type. The IP telephone script files maintained on the Phone Configuration File Server, combined with the GROUP ID feature of the IP telephones, are used to convert a non-vpn phone to a VPN phone as well as converting a VPN phone to a non-vpn phone. Setup of the script files and assignment of the telephone GROUP ID are covered in the following sections. 2 of 12

3 2. Network Topology The sample network implemented for these Application Notes is shown in Figure 1. The focus of these Application Notes is on the IP telephone script files contained within the Phone Configuration File Server and specific procedures to be executed on the IP telephone itself. The GROUP ID feature of the IP telephone requires an active registration with Avaya Communication Manager to change the ID value; therefore a redundant set of Avaya S8710 Media Servers running Avaya Communication Manager and an Avaya G650 Media Gateway are included in the sample configuration. Figure 1: Network Diagram 3. Equipment and Software Validated The information in these Application Notes is based on the software and hardware versions list in Table 1 below. Equipment Avaya S8710 Media Server Avaya G650 Media Gateway IPSI (TN2312BP) C-LAN (TN799DP) MedPro (TN2302AP) Avaya 4625SW VPNremote Phone (H.323) Avaya 4625SW IP Telephone (H.323) R2.8 Phone Configuration File Server Software Version Avaya Communication Manager 4.0 Load FW 022 (HW6) FW 016 (HW1) FW 108 (HW12) R2.5.2 Release 2 (a25vpn252_1.bin) Microsoft Windows Server 2003 Enterprise Edition Table 1 Software/Hardware Version Information 3 of 12

4 4. Convert From non-vpn Phone to VPN Phone This section provides the steps to convert a non-vpn phone to a VPN phone. The steps fall into the following areas: Edit 46xxupgrade.scr file Download VPNremote Phone Software to File Server Set Telephone GROUP ID 4.1. Edit 46xxupgrade.scr file The 46xxupgrade.scr file residing on the Phone Configuration File Server is the first file to be accessed by the Avaya 4600 Series IP Telephones. This script file instructs the telephone to either upgrade or downgrade the firmware currently running in the phone. To differentiate between non-vpn phones and VPN phones, the GROUP ID feature of the IP telephone is used. IP telephones designated as a VPN phone are assigned a GROUP ID of 876 (VPN) while non-vpn phones use the default GROUP ID of 0. The following lines must be added to the beginning of the 46xxupgrade.scr file to take advantage of the GROUP ID setting of the IP telephone. When an IP telephone with a GROUP ID of 876 downloads and executes the 46xxupgrade.scr script file, the telephone will be instructed to download and execute the 46vpnupgrade.scr script file which will install the VPN phone firmware on the telephone. IF $GROUP SEQ 876 goto DEFVPN goto NOVPN # DEFVPN GET 46vpnupgrade.scr goto END # NOVPN 4 of 12

5 4.2. Download VPNremote Phone Software to File Server The VPNremote Phone software package is downloadable as a zip file from the web site. The files contained within the downloaded software bundle include: 46vpnupgrade.scr - instructs the VPN phone to upgrade or downgrade the firmware currently running in the phone. 46vpnsetting.txt - instructs the VPN phone to set various VPN specific configuration parameters. 46vpnsetting_readme.txt description of all variable options of the 46vpnsetting.txt file. Binary Application Files (firmware) for all supported 4600 Series IP Telephone models. Binary Boot Files for all supported 4600 Series IP Telephone models. Copy the application and script files extracted from the VPN phone software bundle into the download directory of the Phone Configuration File Server Set Telephone GROUP ID Telephones that are to be converted to VPN phones must have the GROUP number set to 876 (VPN) to match the script changes made in Section 4.1. There are two options available to change the telephone GROUP number. The option selected depends on the version of firmware running in the phone as well as the version of Avaya Communication Manager software being used. The following sections present the details for both options. 5 of 12

6 From Avaya Communication Manager With the IP telephone running H.323 firmware version 2.8 or greater and Avaya Communication Manager running version 4.0 or greater, the telephone GROUP number can be set from Avaya Communication Manager using the change station SAT command as shown below. Enter 876 in the IP Phone Group ID field on Page 3 of the Station form. Otherwise the GROUP number must be set locally from each telephone station as describer in Section change station Page 3 of 5 STATION Conf/Trans on Primary Appearance? n Bridged Appearance Origination Restriction? n Call Appearance Display Format: disp-param-default IP Phone Group ID: 876 ENHANCED CALL FORWARDING Forwarded Destination Unconditional For Internal Calls To: External Calls To: Busy For Internal Calls To: External Calls To: No Reply For Internal Calls To: External Calls To: Active n n n n n n From the Phone With the telephone registered to Avaya Communication Manager, modify the phones group number and restart the phone by pressing the following key sequence: <MUTE> # # # <MUTE> # * # OR <MUTE> G R O U P # V P N # # <MUTE> R E S E T # * # When the phone resets, it will access the Phone Configuration File Server, execute the appropriate scripts and be instructed to download the VPN phone firmware then reset. At this point, the phone will be a VPN phone. 6 of 12

7 5. Convert From VPN phone to non-vpn phone This section provides the steps to convert a VPN phone to a non-vpn phone. The steps fall into the following areas: Edit 46vpnupgrade.scr file Download IP Phone Software to File Server Disable VPN Set the Telephone GROUP ID 5.1. Edit 46vpnupgrade.scr file The 46vpnupgrade.scr file residing on the Phone Configuration File Server is the first file to be accessed by the Avaya 4600 Series IP Telephones running VPN firmware. This script file instructs the telephone to either upgrade or downgrade the firmware currently running in the phone. To differentiate between non-vpn phones and VPN phones, the GROUP ID feature of the IP telephone is used. IP telephones designated as a VPN phone are assigned a GROUP ID of 876 (VPN) while phones to be converted to non-vpn phones are assigned a GROUP ID of 678 (NPV). The first several lines of the default 46vpnupgrade.scr script file are shown below. The lines shown in bold text are necessary to support the GROUP ID conversion. Add these lines to the existing 46vpnupgrade.scr script file if they are not present. 46vpnupgrade.scr (abridged): ################################################## # Release Date: October 17, 2006 # # 46XX Software Upgrade Script for VPN Capable H.323 IP Telephone # # This file upgrades the following telephones to the # indicated releases: # 4620, 4610, 4621, 4622 VPN R2 (Build 13) # 4625 VPN R2 (Build 13) # # * This file will uninstall VPNremote firmware if IP Telephone # GROUP is set to 678 ################################################## IF $GROUP SEQ 678 goto DEF46xx goto DEF46vpn # DEF46xx GET 46xxupgrade.scr goto NO46xx # DEF46vpn 7 of 12

8 5.2. Download IP Phone Software to File Server Verify the version of the non-vpn phone firmware on the Phone Configuration File Server. Download the most recent firmware version from the web site. The firmware version used in these Application Notes is H.323 version Disable VPN The conversion of a VPN phone to a non-vpn phone can not be performed while the phone is located in a remote location with a VPN tunnel connection to the enterprise network. The phone must be connected locally to the enterprise network and the VPN functionality must be disabled. To disable the VPN functionality, connect the phone directly to the enterprise network. With the phone directly connected to the corporate network, it will attempt to start a VPN tunnel connection on boot up. The VPN connection status will be shown on the phones display. Press the Edit button on the bottom left of the screen to enter the VPN Options Menu. This will allow the VPN Start Mode to be changed from BOOT to Disable. Press the button to the right of VPN Start Mode to change the value from BOOT to Disable. Press the Done button at the bottom of the screen to save the settings. The following is displayed: VPN Configuration Changed Do you wish to restart? YES NO Select No and the phone continues to boot without any VPN components activated. The phone functions as a non-vpn phone by registering with Avaya Communication Manager. Note: The phone is functioning as a non-vpn phone as a result of the VPN Start Mode being set to disable. However, the firmware loaded in the phone is still the VPN phone firmware Set the Telephone GROUP number Phones that are to be converted from VPN phones to non-vpn phones must be assigned a GROUP ID of 678 (NPV) to match the script settings described in Section 5.1. The VPN phone firmware is based on the H.323 firmware version 2.3. Therefore, the GROUP ID can only be set locally from the telephone. 8 of 12

9 From the Phone With the telephone registered to Avaya Communication Manager, modify the phones group number and restart the phone by pressing following key sequence: <MUTE> # # # <MUTE> # * # OR <MUTE> G R O U P # N P V # # <MUTE> R E S E T # * # When phone resets, the VPN Start Mode will need to be disabled again as described above in Section 5.3. The phone will then proceed to access the Phone Configuration File Server, execute the appropriate scripts and be instructed to download the non-vpn phone firmware then reset. At this point, the phone will no longer be a VPN phone. Note: If the GROUP ID was set in the change station form in Avaya Communication Manager when the telephone was converted to a VPN phone, verify the correct GROUP ID is set after the telephone is converted back to a non-vpn phone. In this scenario, the GROUP ID could still be set to 876 (VPN) and the telephone could revert back to a VPN phone on the next reboot. 6. Verification 6.1. Firmware Version Pressing the following key sequence on the IP telephone displays the firmware version currently loaded on the phone. <Options> <View IP Settings> <Miscellaneous> <right arrow> Non-VPN phone: Application file a25d01a2_8.bin Boot file b25d01a2_8.bin VPN phone: (Note the letters VPN in the Application file name highlighted below) Application file a25vpn252_1.bin Boot file b25d01a2_8.bin 9 of 12

10 6.2. Phone Configuration File Server The files being accessed by the phone on the Phone Configuration File Server are useful to check the status of an active firmware conversion and helpful if troubleshooting is required. The screens below display the TFTP server logs used in the sample configuration showing the script files being accessed during non-vpn phone to VPN phone conversion as well as VPN phone to non-vpn phone conversion. Non-VPN phone to VPN phone: VPN phone to non-vpn phone: 7. Conclusion Avaya 4600 Series IP Telephone models supporting the Avaya VPNremote firmware can be easily converted between non-vpn and VPN firmware loads. The IP telephone GROUP ID feature combined with the phone configuration script files allow for a simple conversion process and enable the use of a single Phone Configuration File Server to support multiple firmware versions. 10 of 12

11 8. References Avaya Application Notes and additional resources can be found at the following web address Avaya Product Support web site can be found at the following web address [1] Administrators Guide for Avaya Communication Manager Release 4.0, Doc ID: Issue: 3.1 [2] 4600 Series IP Telephone Release 2.8 LAN Administrator Guide, Doc ID: Issue: 6 [3] VPNremote for the 4600 Series IP Telephone Release 2.0 Administrator Guide, Doc ID: Issue: 2 [4] VPNremote for 4600 Series IP Telephone Installation and Deployment Guide Doc ID: Issue: 1 11 of 12

12 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. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at 12 of 12