User's Manual

ManualsBrandsAvaya ManualsTelephoneAvaya VPNremote Phone

EMH; Reviewed:

SPOC 10/25/2006

Solution & Interoperability Test Lab Application Notes

1 of 25

weblm_vpnphone.doc

Avaya Solution & Interoperability Test Lab

Application Notes for Configuring Avaya WebLM License

Manager for Avaya VPNremote™ Phone Release 2

– Issue 1.0

Abstract

These Application Notes describe the steps for configuring the Avaya WebLM License

Manager to support Avaya VPNremote™ Phones.

Avaya WebLM is a Web-based license manager application designed to support Avaya

software products that require licensing. The Avaya VPNremote™ Phone is a software based

Virtual Private Network (VPN) client integrated into the firmware of an Avaya IP Telephone.

Release 2 of the Avaya VPNremote Phone utilizes Avaya's WebLM license management

system. The Avaya VPNremote Phone license file must be installed on the WebLM server for

the Avaya VPNremote Phone to be fully functional. A WebLM client integrated into the

Avaya VPNremote Phone communicates with the WebLM sever for license verification during

the phone startup process.

Summary of content (25 pages)

PAGE 1
Avaya Solution & Interoperability Test Lab Application Notes for Configuring Avaya WebLM License Manager for Avaya VPNremote™ Phone Release 2 – Issue 1.0 Abstract These Application Notes describe the steps for configuring the Avaya WebLM License Manager to support Avaya VPNremote™ Phones. Avaya WebLM is a Web-based license manager application designed to support Avaya software products that require licensing.
PAGE 2
TABLE OF CONTENTS 1. INTRODUCTION..............................................................................................................................................3 1.1. VPNREMOTE PHONE STARTUP ....................................................................................................................4 2. NETWORK TOPOLOGY ................................................................................................................................5 3.
PAGE 3
1. Introduction These Application Notes describe the steps for configuring the Avaya WebLM License Manager to support Avaya VPNremote™ Phones. Avaya WebLM is a Web-based license manager that runs on both Microsoft Windows and UNIX systems. It is designed to support Avaya software products that require licensing. The WebLM server provides a Web User Interface (UI) for license administration which can be accessed from a standard web browser over a secure SSL link.
PAGE 4
1.1. Avaya VPNremote Phone Startup The steps shown in Figure 1 below describe the high level events that take place during the VPNremote phone startup process including access to the WebLM server. 1. The VPNremote Phone establishes an IPSec VPN tunnel upon boot up with the designated VPN gateway. 2. The VPNremote Phone initiates a TFTP or HTTP session with the phone configuration server (HTTP/TFTP Server) for configuration file download. 3.
PAGE 5
2. Network Topology The sample network implemented for these Application Notes is shown in Figure 2. The WebLM License Manager supports both Linux and Windows platforms. Microsoft Windows 2000 Server was used in the sample configuration. While separate physical servers are used for the WebLM License Manager and the HTTP/TFTP phone configuration download server in the sample network, they can be installed as co-resident applications on the same physical server.
PAGE 6
3. Equipment and Software Validated Table 1 lists the equipment and software/firmware versions used in the sample configuration provided.
PAGE 7
4.2. Configuring Avaya VPNremote Phone The VPNremote Phone configuration can be administered centrally from an HTTP or TFTP server or locally on the phone. See Section 10 References VPNremote for the 4600 Series IP Telephones Release 2.0 Administrator Guide for details on all the VPNremote Phone configuration parameters. 1. Locally Setting the Avaya VPNremote Phone File Server parameter Most parameters of the VPN Options menu of the VPNremote Phone are VPN specific.
PAGE 8
2. Setting the NVWEBLMURL Variable One of the configuration script files downloaded by the VPNremote Phone from the HTTP/TFTP file server is the 46VPNsetting.txt file. The 46VPNsetting.txt file contains many variables including the variable NVWEBLMURL which identifies all available WebLM servers to the VPNremote Phone. Below are the specifics of the NVWEBLMPURL variable: • • Variable Name: NVWEBLMURL Valid Values: o Comma separated URLs of available WebLM Licensing servers.
PAGE 9
5. Avaya WebLM License Manager Installation and Configuration 5.1. Install the Java Runtime Environment The Avaya WebLM application, when installed on a Microsoft Windows platform, requires both the Java Runtime Environment (JRE) and Apache Tomcat applications be installed on the system to be used for WebLM. See Table 1 for versions used for these Application Notes. The JRE must be installed first followed by Apache Tomcat. Default settings were chosen during installation for both applications. 1.
PAGE 10
5.2. Install Apache Tomcat With the JRE application installed from Section 5.1, download and install the Apache Tomcat for Windows server application. 1. Download Apache Tomcat The following URL is to the Apache Tomcat download web site to access the Tomcat server version 5.5.17 used for these Application Notes. http://tomcat.apache.org/download-55.cgi#5.5.17 From the download web page select ○ Windows Executable (pgp, md5) under Core distribution, as shown below.
PAGE 11
2. Install Apache Tomcat Execute the downloaded Apache Tomcat 5.5.17 installation script and follow the prompts. Below are a few of the screens that appear during the Tomcat installation which require input. The first screen to appear to start the installation is shown below. Note the Destination Folder used for the Tomcat installation. This folder path is needed in Section 5.3 of these Application Notes.
PAGE 12
Note the HTTP Port number Tomcat will run under. This port number is need when accessing the URL for WebLM described in Section 6 of these Application Notes. The Java Runtime Environment application installed in Section 5.1 is shown on the following screen. EMH; Reviewed: SPOC 10/25/2006 Solution & Interoperability Test Lab Application Notes ©2006 Avaya Inc. All Rights Reserved. 12 of 25 weblm_vpnphone.
PAGE 13
3. Verify Apache Tomcat Verify the installation by going to Windows Control Panel Æ Add/Remove Programs. Apache Tomcat 5.5 should be displayed in the Currently Installed Programs list. 4. Set Tomcat Startup Type appears in the bottom right corner of the Windows The Apache Tomcat server icon toolbar. Select this icon for additional Apache Tomcat configuration options. Apache Tomcat runs as a Windows service which defaults to a startup type of manual.
PAGE 14
5.3. Avaya WebLM Configuration The steps below describe the installation and configuration of the Avaya WebLM License Manager running in a Microsoft Windows environment. The installation is a manual process and requires copying, moving and editing files. Refer to the WebLM release notes prior to installation. The following areas are covered: • Download and Extract WebLM files • Copy WebLM Files • Extract Contents of WebLM.war to the WebLM Folder • Enabling HTTPS 1.
PAGE 15
The WebLM software download is in the form of a zip file. Unzip the WebLM_Windows.zip file to the PC where WebLM will be installed. The following files are extracted: • WebLM.war: A .war file, short for Web Archive, is a compressed ZIP file used to distribute a set of Java classes. The WebLM.war file contains core WebLM files providing the primary WebLM functionality and licensing server components. • mail.jar: Required by the WebLM server to send email to the administrator. • activation.
PAGE 16
4. Enable HTTPS It is recommended the Tomcat server be configured for HTTPS to ensure secure communications with the WebLM application. The following steps configure Tomcat for HTTPS when accessing the WebLM application. Note: Refer to the section titled “SSL Config HOW TO” in the Tomcat 5 documentation for more detailed instructions. • Using a text editor such as Windows Notepad, edit the file server.xml located in \conf (i.e. C:\Program Files\Apache Software Foundation\Tomcat\5.
PAGE 17
• The last line of this HTTPS tag contains the following line: clientAuth="false" sslProtocol="TLS" /> Add the following three attributes to the end of the HTTPS tag in front of the />: keystoreFile=”./webapps/WebLM/WEB-INF/weblmserver.p12” keystoreType=”PKCS12” keystorePass=”weblmserver” The text below shows an “after edit” view of the HTTPS . Save the server.xml file when edits are complete. After server.xml edit: