Page 3 - Contents
Issue 1 July 2006 3 Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Chapter 2: Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . 9 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Basic Operation . . . . . . . ....
Page 4 - Index
Contents 4 Avaya IP Telephone File Server Application Reference Guide IP Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Overriding Downloads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Scanning IP Telephone Firmware. . . . . . . . . . ...
Page 5 - Chapter 1: Introduction
Issue 1 July 2006 5 Chapter 1: Introduction The Avaya IP Telephone File Server Application provides IP telephone support as well as administrative server support. For the IP telephones, the application provides the following: ● An HTTP server to support: - configuration file and firmware downloads t...
Page 9 - Chapter 2: Modes of Operation; Introduction
Issue 1 July 2006 9 Chapter 2: Modes of Operation Introduction You can configure the IP Telephone File Server Application to operate in any of five ways: ● As a basic HTTP/HTTPS server for 9600 Series IP Telephones, ● As a basic TFTP/FTP/HTTP/HTTPS server for 4600 Series IP Telephones, ● As a basic ...
Page 10 - Basic Operation; Use Case Scenario
Modes of Operation 10 Avaya IP Telephone File Server Application Reference Guide Basic Operation Figure 2: Mode 1 - Basic Operation Mode Use Case Scenario Use the basic operation mode to: ● Download configuration files like the 96xxupgrade.txt and 46xxsettings.txt files to the telephones using HTTPS...
Page 11 - Basic Server + File Server Client
Basic Server + File Server Client Issue 1 July 2006 11 Basic Server + File Server Client Figure 3: Mode 2 - Basic Server plus File Server Client Mode Use Case Scenario Use the basic server plus file server client to: ● Function as a central Linux server delivering/backing up files, ● Provide a mix o...
Page 12 - Central File Server
Modes of Operation 12 Avaya IP Telephone File Server Application Reference Guide Central File Server Figure 4: Mode 3 - Central File Server Mode Use Case Scenario Use the central file server for the client mode to: ● Act as the central server, delivering update files and storing backing up files, ● ...
Page 13 - Both Basic Server and Central File Server
Both Basic Server and Central File Server Issue 1 July 2006 13 Both Basic Server and Central File Server Figure 5: Mode 4 Basic Server and Central File Server Mode Use Case Scenario Use the basic server and central file server combination mode to: ● Incorporate the features of Modes 1, 2, and 3, ● O...
Page 15 - Chapter 3: File Locations; Individual Server Descriptions; TFTP Server with Default Port 69
Issue 1 July 2006 15 Chapter 3: File Locations Individual Server Descriptions The basic central server architecture uses a standard Red Hat Linux or Windows server installation. The sections in this chapter define the default locations for files. Avaya recommends that you use these default locations...
Page 16 - FTP Server Using Default Ports 21/20
File Locations 16 Avaya IP Telephone File Server Application Reference Guide FTP Server Using Default Ports 21/20 The FTP server backs up individual 4600 Series IP Telephone user data such as screen settings and speed dial data. The data is stored in “data” directory by default: For Linux: /opt/ecs/...
Page 17 - Accessing the File Server Application from an FTP Client Program
HTTP/HTTPS Servers with Default Ports 411/81/80 Issue 1 July 2006 17 Avaya recommends using a specialist FTP client program such as Cute FTP or WS_FTP to access the IP Telephone File Server Application FTP server. The more explicit messages provided regarding log in and change of working directory s...
Page 19 - Chapter 4: Installing the Linux Server
Issue 1 July 2006 19 Chapter 4: Installing the Linux Server Use Red Hat Package Manager (RPM) to install the application on Red Hat Linux Enterprise Linux V3.0, Update 4 or 5. Note: Note: The application has also been tested on Red Hat versions 8 and 9, and Fedora Versions 1 and 2. Issues might aris...
Page 20 - Linux Directory Structure
Installing the Linux Server 20 Avaya IP Telephone File Server Application Reference Guide Linux Directory Structure Verify that the installation has created the directory structure shown in Table 1 . Table 1: Linux Directory Structure Directory Application & function /opt/ecs/mvuser/MV_IPTel/bin...
Page 21 - Sample .ini File Format
MV_IPTel .ini Configuration File Issue 1 July 2006 21 MV_IPTel .ini Configuration File Avaya supplies a standard default set of options to run the IP Telephone File Server Application. Very little needs to be configured on the Linux sever for initial operation. A single configuration file /opt/ecs/m...
Page 27 - Chapter 5: Installing the Windows Server
Issue 1 July 2006 27 Chapter 5: Installing the Windows Server Use the Windows installer application to install the IP Telephone File Server Application on Windows NT/2000 or XP servers. Unlike the Linux version, the Windows version of the application includes an SNMP query agent used for secure FTP....
Page 28 - Windows Directory Structure
Installing the Windows Server 28 Avaya IP Telephone File Server Application Reference Guide Windows Directory Structure Verify that the installation has installed the directory structure shown in Table 2 . Table 2: Windows Directory Structure Directory Application & function C:\Program Files\Ava...
Page 35 - Chapter 6: Optimizing the Server; WatchDog Operation
Issue 1 July 2006 35 Chapter 6: Optimizing the Server This chapter describes the options available to improve the robustness of the server. The options are: ● WatchDog Server ● HeartBeat redundant solution for Linux ● Firmware Update service ● IP Access Control List ● FTP File Server Backup ● CDR/BC...
Page 37 - HeartBeat Redundant Server; Updating Firmware
HeartBeat Redundant Server Issue 1 July 2006 37 HeartBeat Redundant Server HeartBeat is a High Availability Linux solution designed to provide servers with hardware redundancy. HeartBeat provides a primary/hot standby server pairing which can share a single IP address to the external world. HeartBea...
Page 38 - FTP File Server Backup Operation
Optimizing the Server 38 Avaya IP Telephone File Server Application Reference Guide Acting as a client, the IP Telephone File Server Application server requests firmware updates from a central file server. When set as the client and optioned for firmware updates, the IP Telephone File Server Applica...
Page 39 - Backup Using Automatic Archive
FTP File Server Backup Operation Issue 1 July 2006 39 Backup Using the IP Telephone File Server Application as a File Server This operation provides periodic back up of FTP data to a primary and/or secondary server running the file server application software. The data can be backed up every month/d...
Page 41 - IP Access Control Lists
IP Access Control Lists Issue 1 July 2006 41 IP Access Control Lists When deploying new IP telephone software, it is likely that you will use a subset of the telephone population for testing. The Avaya IP Telephone File Server Application server offers the Access control list concept to define which...
Page 42 - Overriding Downloads; Scanning IP Telephone Firmware
Optimizing the Server 42 Avaya IP Telephone File Server Application Reference Guide Overriding Downloads IP telephones that are reset unexpectedly might not access the appropriate upgrade and settings files. In this case, the telephones default to a mode which users can find unacceptable, such as ha...
Page 43 - Copying CDR/BCMS Data
Copying CDR/BCMS Data Issue 1 July 2006 43 To scan, press the SCAN button on the Web page. Because the scan might take some time, refresh the page to check for progress or completion. Note: Note: Windows XP scanning might produce an invalid address range. When scanning an invalid network routing add...
Page 45 - Maintaining Operations; Checking Linux Operation
Issue 1 July 2006 45 Chapter 7: Maintaining Operations and Troubleshooting Maintaining Operations Checking Linux Operation The Avaya IP Telephone File Server Application runs as a daemon on a Linux server and is configured to start up automatically on bootup. The MV_Manager daemon provides a service...
Page 46 - Checking Windows Operation; Checking Application Status
Maintaining Operations and Troubleshooting 46 Avaya IP Telephone File Server Application Reference Guide Checking Windows Operation The Avaya IP Telephone File Server Application runs as a service on a Windows server and is configured to automatically start on power up. Therefore, no default adminis...
Page 48 - Troubleshooting
Maintaining Operations and Troubleshooting 48 Avaya IP Telephone File Server Application Reference Guide Troubleshooting Most problems with the Avaya IP Telephone File Server Application tools are usually configuration- or network-related. A comprehensive set of log files residing in the relevant lo...
Page 51 - Chapter 8: DHCP Server Administration
Issue 1 July 2006 51 Chapter 8: DHCP Server Administration Avaya IP Telephones are usually configured remotely to enable downloading the appropriate configuration files. Normal, dynamically assigned IP configurations need a DHCP server to allocate IP addresses to the telephones, as opposed to static...
Page 53 - Chapter 9: HeartBeat; How HeartBeat Works
Issue 1 July 2006 53 Chapter 9: HeartBeat This section describes the high availability Linux application called “HeartBeat” in more detail. The automated installation script creates all the defaults covered in this chapter. How HeartBeat Works You can configure the Avaya IP Telephone File Server App...
Page 54 - MV_IPTelD Considerations; Basic Assumptions for Easy Installation
HeartBeat 54 Avaya IP Telephone File Server Application Reference Guide For additional redundancy, the servers benefit from additional options such as hot swap power supplies and software or hardware based RAID functions. For more information about hardware setup options, see the HeartBeat documenta...
Page 55 - Disabling Auto-Start of the Daemon; HeartBeat Installation and Configuration
HeartBeat Installation and Configuration Issue 1 July 2006 55 Disabling Auto-Start of the Daemon By default, installing MV_IPTelD causes the daemon to start on a restart of Linux. This start and restart are usually desirable since no manual intervention is required if the Linux server is restarted f...
Page 56 - Configuration File: haresources
HeartBeat 56 Avaya IP Telephone File Server Application Reference Guide Configuration File: ha.cf The ha.cf file is the HeartBeat main configuration file consisting of a configuration parameters list. A sample follows: bcast eth1 keepalive 2 warntime 10 deadtime 30 initdead 120 udpport 694 nice_fail...
Page 57 - Configuration File: authkeys; Controlling HeartBeat
Controlling HeartBeat Issue 1 July 2006 57 Configuration File: authkeys This file controls how the two servers in the High Availability cluster control access to each other. The following file shows a simple mechanism. auth 2 2 crc ! Important: Important: If this file does not have suitable permissi...
Page 58 - Installing and Configuring RSYNC; Enabling the RSYNC Server
HeartBeat 58 Avaya IP Telephone File Server Application Reference Guide Installing and Configuring RSYNC RSYNC is a client/server application for synchronization of files across two servers. Standard Red Hat installation usually installs RSYNC, but RSYNC is supplied as an RPM if it is not already in...
Page 59 - Network Time Protocol
Installing and Configuring RSYNC Issue 1 July 2006 59 This file defines the two/three directories to be synchronized between the two servers. Note that this only defines the operation of RSYNC and what symbolic names are available, it does not perform any actual synchronization. RSYNCHOURLY.SH RSYNC...
Page 63 - Symbols
Issue 1 July 2006 63 Index Index Symbols .ini Configuration File . . . . . . . . . . . . . . . 21 , 29 .ini File Format . . . . . . . . . . . . . . . . . . 21 , 29 .ini File Settings for CDR/BCMS . . . . . . . . . . 44 A Application Overview . . . . . . . . . . . . . . . . . 5 Application Status, Ch...