Avaya 4600 Series Administrator's Manual
Avaya 4600 Series Administrator's Manual

Avaya 4600 Series Administrator's Manual

Hide thumbs Also See for 4600 Series:
Table of Contents

Advertisement

4600 Series IP Telephone
Release 2.2
LAN Administrator Guide
555-233-507
Issue 2.2
April 2005

Advertisement

Table of Contents
loading

Summary of Contents for Avaya 4600 Series

  • Page 1 4600 Series IP Telephone Release 2.2 LAN Administrator Guide 555-233-507 Issue 2.2 April 2005...
  • Page 2 Warranty The final responsibility for securing both this system and its networked Avaya Inc. provides a limited warranty on this product. Refer to your equipment rests with you - Avaya’s customer system administrator, your sales agreement to establish the terms of the limited warranty. In telecommunications peers, and your managers.
  • Page 3: Table Of Contents

    Contents Chapter 1: Introduction ......About This Guide ........Intended Audience .
  • Page 4 Contents 4600 Series IP Telephones ......Dual Connection Architecture ......
  • Page 5 TFTP Generic Setup ....... . Avaya TFTP (Suite Pro) ......
  • Page 6 Appendix A: Avaya - 46xx IP Telephone MIB ....123 Downloading the Avaya - 46xx IP Telephone MIB ....
  • Page 7 Contents Fonts ........Maintaining Context .
  • Page 8 Contents 8 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 9: Chapter 1: Introduction

    4602/4602SW SIP Telephones. Intended Audience This document is intended for personnel who administer the DHCP and TFTP servers to support the 4600 Series IP Telephone. This guide is also intended for those who administer the Local Area Network (LAN) itself. CAUTION: Avaya does not support many of the products mentioned in this document.
  • Page 10: Document Organization

    Directories LDAP directory for the 4610SW, 4620/ 4620SW, 4621SW, 4622SW, and 4625SW IP Telephones. Appendix E: The Push Feature Provides information about the Push feature available as of Release 2.1. 10 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 11: Change History

    This version of the document was revised to support DEFINITY Release 10 and the 4630 IP Telephone. Issue 1.7 This version of the document was revised in July, 2002 to support Avaya Communication Manager Release 1.1 and the 4602 and 4620 IP Telephones. Issue 1.8 This version of this document was revised in June, 2003 to support Avaya Communication Manager Releases 1.2 and 1.3.
  • Page 12: What's New In Release 2.2

    Code-excited linear-predictive. Voice compression requiring only 16 kbps of bandwidth. CLAN Control LAN, type of Gatekeeper circuit pack. Converged Network Analyzer, an Avaya product to test and analyze network performance. DHCP Dynamic Host Configuration Protocol, an IETF protocol used to automate IP Address allocation and management.
  • Page 13 Document Organization IETF Internet Engineering Task Force, the organization that produces standards for communications on the internet. Local Area Network. LDAP Lightweight Directory Access Protocol, an IETF standard for database organization and query exchange. Media Access Control, ID of an endpoint. NAPT Network Address Port Translation.
  • Page 14: Conventions Used In This Guide

    Bold type also provides general emphasis for words or concepts. italics Italic type indicates a document that contains additional information about a topic. 14 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 15: Online Documentation

    Online Documentation Online Documentation The online documentation for the 4600 Series IP Telephones is located at the following URL: http://www.avaya.com/support Related Documents ® DEFINITY Documentation Release 8.4 This CD contains documentation that describes, among other things, how to administer a DEFINITY switch with Release 8.4 software.
  • Page 16 This document contains important safety and installation information for the 30A Switched Hub. 4600 Series IP Telephone Installation Guide This document describes how to install 4600 Series IP Telephones. It also provides troubleshooting guidelines for the 4600 Series IP Telephones. 4600 Series IP Telephones Application Programmer Interface (API) Guide This document provides information on developing Web applications for 4610SW, 4620/ 4620SW, 4621SW, 4622SW, and 4625SW IP Telephones.
  • Page 17 This document provides detailed information about using the 4625SW IP Telephone. 4630/4630SW IP Telephone User Guide This document provides detailed information about using the 4630/4630SW IP Telephones. Avaya 4690 IP Conference Telephone User Guide This document provides detailed information about using the 4690 IP Conference Telephones. Issue 2.2 April 2005...
  • Page 18: Ietf Documents

    (SNMPv2), April 1993, by J. Case, K. McCloghrie, M. Rose, and S. Waldbusser (RFC 1441) Management Information Base for Network Management of TCP/IP Internets: MIB-II, March 1991, edited by K. McCloghrie and M. Rose (RFC 1213) 18 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 19: Itu Documents

    Related Documents SNMPv2 Management Information Base for the Internet Protocol using SMIv2, November 1996, edited by K. McCloghrie (RFC 2011) Structure of Management Information Version 2 (SMIv2), April 1999, edited by K. McCloghrie, D. Perkins, and J. Schoenwaelder (RFC 2578) Resource ReSerVation Protocol VI, September 1997, by R.
  • Page 20: Iso/Iec, Ansi/Ieee Documents

    Equipment (DTE) Power via Media Dependent Interface (MDI) Customer Support Call the Avaya support number provided to you by your Avaya representative or Avaya reseller for 4600 Series IP Telephone support. Information about Avaya products can be obtained at the following URL: http://www.avaya.com/support...
  • Page 21: Chapter 2: Overview Of Voice Over Ip (Voip) And Network Protocols

    Overview of Voice over IP (VoIP) The 4600 Series IP Telephones allow enterprises to use Voice over IP (VoIP). VoIP uses packet-switched networks over the Public Switched Telephone Network (PSTN) instead of telephony. However, using data networks to transmit voice packets poses a problem. Data networks were not designed for the specific qualities required by voice traffic.
  • Page 22: Delay And Jitter

    However, data requirements tend to not be as strict as most voice requirements. Starting with Release 1.1, the 4600 Series IP Telephones include a dynamic jitter buffer. This feature automatically smooths jitter to improve audio quality.
  • Page 23: Voice Coding Standards

    Dynamic Host Configuration Protocol (DHCP) allows a server to assign IP Addresses and other parameters to devices like the 4600 Series IP Telephones on an as-needed basis. DHCP eliminates the need to configure each end station with a static IP Address. The DHCP application also passes information to the 4600 Series IP Telephone.
  • Page 24: Http

    However, the 4600 Series IP Telephone must already be running Release 2.2 software to be able to access and use HTTP servers. As with TFTP, some functionality might be lost by a reset if the HTTP server is not available.
  • Page 25: Qos

    SNMPv1. “Fully compatible” means that the telephones respond to queries directed either at the MIB-II or the Custom MIB. The 4600 Series IP Telephone Custom MIB is read-only. Read-only means that the values therein cannot be changed externally by means of network management tools.
  • Page 26: Network Assessment

    To find more information about SNMP and MIBs, see the IETF references listed in Related Documents on page 15. The Avaya Custom MIB for the 4600 Series IP Telephones is available for download in *.txt format on the Avaya support Web site. Network Assessment The current technology allows optimum network configurations to deliver VoIP with perceived voice quality close to that of the Public Switched Telephone Network (PSTN).
  • Page 27: Tcp/Udp Port Utilization

    ) represent the direction(s) of data transfer. The text the arrows point to identifies the port or ports that the 4600 Series IP Telephones support for the specific situation. Brackets identify ranges when more than one port applies. In addition, the text indicates any additional qualifications or clarifications. In many cases, the ports used are the ones called for by IETF or other standards bodies.
  • Page 28 SNMP MIB Viewer Port depends on SNMP (UDP/IP) Port:161 MIB viewer admin Far end of audio channel Port: [33435 – 33524] Remote Traceroute (UDP) Port Determined Operating System locally selected 28 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 29 TCP/UDP Port Utilization Figure 2: Initialization and Address Resolution Diagram Initialization and Address Resolution DHCP Server 4600 Series IP Telephone DHCP (UDP/IP) Port: 68 Port: 67 TFTP Server TFTP Read Request (UDP/IP) Port: [1024 - 5000] Port: 69 Operating System –...
  • Page 30 CTI Data (TCP/IP) Port: 49722 Port: [1024 – 5000] (only active if CTI (4606, 4610SW, 4612, 4620, randomly selected discovery is successful) 4620SW, 4621SW, 4622SW, 4624, 4625SW, 4630, and 4630SW only) 30 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 31: Suggestions For Installation And Configuration

    Telephones introduced “remote ping” and “remote traceroute” support. The switch can instruct such a 4600 Series IP Telephone to initiate a ping or a traceroute to a specified IP Address. The telephone carries out that instruction and sends a message to the switch indicating the results.
  • Page 32: Ip Address Lists And Station Number Portability

    Overview of Voice over IP (VoIP) and Network Protocols IP Address Lists and Station Number Portability Release 1.5 of the 4600 Series IP Telephones provided the capability to specify IP Address lists in either dotted decimal or DNS format. Release 1.5 allowed key network elements to have multiple IP Addresses, rather than being restricted to just one address for each element.
  • Page 33: Security

    Related Documents on page 15. Any equipment on a data network, including a 4600 Series IP Telephone, can be the target of a Denial of Service attack. Usually, such an attack consists of flooding the network with so many messages that the equipment either: spends so much time processing the messages that legitimate tasks are not processed, or the equipment overloads and fails.
  • Page 34: 4600 Series Ip Telephones

    Overview of Voice over IP (VoIP) and Network Protocols 4600 Series IP Telephones Dual Connection Architecture Releases 1.0 and 1.1 of the 4600 Series IP Telephones use dual connection architecture to ® communicate with the DEFINITY switch. In the dual connection architecture, two station extensions must be administered for each telephone.
  • Page 35: Wan Considerations

    DHCP server be available at remote sites if WAN failures isolate IP telephones from the central site DHCP server(s). The file server provides the 4600 Series IP Telephone with a script file and, if appropriate, new or updated application software. See...
  • Page 36: Initialization Process

    These steps offer a high-level description of the information exchanged when the telephone initializes and registers. This description assumes that all equipment is properly administered ahead of time. This description can help you understand how the 4600 Series IP Telephones relate to the routers and servers in your network.
  • Page 37: Step 4: Telephone And The Avaya Media Server

    The settings file can contain options you have administered for any or all of the 4600 Series IP Telephones in your network. For more information about this settings file, see...
  • Page 38 Overview of Voice over IP (VoIP) and Network Protocols 38 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 39: Chapter 3: Requirements

    The 4600 Series IP Telephones use Internet Protocol (IP) technology with Ethernet line interfaces. The IP telephones supplement the existing Avaya IP Solutions platform. This feature provides the user with the capability to natively administer and maintain the new 4600 Series IP Telephones.
  • Page 40: Additional Hardware Requirements

    LAN powering will not be used for that particular telephone model. - IEEE 802.3af-2003, if the LAN supports this powering scheme. Note that the 4630 and 4690 cannot be powered this way, but the 4630SW can be powered this way. 40 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 41: Software Requirements

    - Power Interface Module for the 4690 IP Conference Telephone only. - Power Brick for 4630 IP Telephones only. - Stylus for 4630/4630SW IP Telephones only. You might need a Category 5e modular line cord for the connection from the 4600 Series IP Telephone to the PC. Note: See the 4600 Series IP Telephone Installation Guide.
  • Page 42 HTTP on page 66. CAUTION: A file server does not need to be available for the Avaya IP Telephones to CAUTION: operate. The Avaya IP Telephones obtain important information from the script files on the file server and depend on the application file for software upgrades. If the file server is not available when the Avaya IP Telephones reset, the telephones will register with the media server and operate.
  • Page 43: Chapter 4: Server Administration

    Chapter 4: Server Administration Introduction When a 4600 Series IP Telephone is plugged in and powered, it automatically negotiates with its associated LAN to determine the Ethernet speed. From that point on, the telephone’s actions depend largely on network administration prior to phone installation, and on any actions the installer takes.
  • Page 44 These parameters can be administered in a variety of ways, as indicated in Table 1. Note that not all parameters can be administered on all delivery mechanisms. Table 1: Administration Alternatives and Options for 4600 Series IP Telephones Administrative Parameter(s)
  • Page 45 Introduction Table 1: Administration Alternatives and Options for 4600 Series IP Telephones (continued) Administrative Parameter(s) Mechanisms For More Information See: Interface DHCP DHCP and File Servers on page 47, and Administering Options for the 4600 Series IP Telephones on page 80.
  • Page 46: Administering 4600 Series Ip Telephones On Avaya Media Servers

    ® DEFINITY Release 10 adds support for the 4630 and 4630SW IP Telephones. Avaya Communication Manager Software Release 1.1 adds support for the 4602/4602SW and 4620/4620SW IP Telephones. Administration of a 4612 and 4624 IP Telephone is identical to a 6424 IP softphone.
  • Page 47: Definity Release 8.4

    It is possible to install the DHCP, TFTP, and HTTP server software on the same Note: machine. CAUTION: The circuitry in the 4600 Series IP Telephones reserves IP Addresses of the form CAUTION: 192.168.2.x for internal communications. The telephone(s) will not properly use addresses you specify if they are of that form.
  • Page 48: Required Network Information

    Table 2 for each DHCP server. Release 1.5 of the 4600 Series Telephones supported specifying a list of IP Addresses for a gateway/router, TFTP server, and Avaya media server Gatekeeper(s). We explain this specification in Overview of Voice over IP (VoIP) on page 21.
  • Page 49: Dhcp

    This section provides basic information on DHCP servers and generic information on DHCP server administration. Choosing a DHCP Configuration A discussion on how to best set up your network to work with the 4600 Series IP Telephones is beyond the scope of this document. See Network Assessment on page 26.
  • Page 50: Dhcp Generic Setup

    - Option 51 - DHCP lease time, if desired. We recommend six weeks or greater. Expired leases cause Avaya IP Telephones to reboot. It is highly desirable to provide enough leases so an IP telephone’s IP Address does not change if it is briefly taken offline.
  • Page 51 TFTP. If you use both Option 66 and Option 176 to identify TFTP servers, the value(s) in Option 176 overrides the value(s) in Option 66. - A 4600 Series IP Telephone-specific DHCP option specifying information such as TFTP server and Avaya Media Server Gatekeeper IP Addresses. Use the Site-Specific Option Number (SSON) at #176.
  • Page 52 Server Administration The 4600 Series IP Telephones do not support Regular Expression Matching, and therefore, do not use wildcards. See Administering Options for the 4600 Series IP Telephones on page 80. In configurations where the upgrade script and application files are in the default directory, do not use the TFTPDIR=<path>.
  • Page 53: Windows Nt 4.0 Dhcp Server

    DHCP Table 3, the 4600 Series IP Telephone sets the system values to the DHCPACK message field values shown. Table 3: DHCPACK Setting of System Values System Value Set to IPADD The yiaddr field. NETMASK Option #1 (if received). GIPADD The first four octets of Option #3 (if received).
  • Page 54: Initial Configuration

    In the Exclusion Range Start Address field, enter the first IP Address in the range that you want to exclude. b. In the Exclusion Range End Address field, enter the last IP Address in the range that you want to exclude. 54 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 55: Editing Custom Options

    We recommend that you provision the 4600 Series IP Telephones with sequential Note: IP Addresses. We recommend not mixing 4600 Series IP Telephones and PCs in the same scope. 5. Under Lease Duration, select the Limited To option and set the lease duration to the maximum.
  • Page 56: Adding The Dhcp Option

    11. Click the OK button. Activating the Leases Use the following procedure to activate the leases. 1. Click Activate under the Scope menu. The light-bulb icon for the scope lights. 56 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 57: Verifying Your Configuration

    DHCP Verifying Your Configuration This section describes how to verify that the 46XXOPTIONs are correctly configured for the ® Windows NT 4.0 DHCP server. Verify the Default Option, 176 46XXOPTION Use the following procedure to verify the default option. 1. Select Start Programs Admin Tools DHCP Manager.
  • Page 58: Windows 2000 Dhcp Server

    IP Address available to the IP telephones. The End IP Address is the last IP Address available to the IP telephones. Note: We recommend not mixing 4600 Series IP Telephones and PCs in the same Note: scope. 58 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 59 DHCP 8. Define the subnet mask in one of two ways: The number of bits of an IP Address to use for the network/subnet IDs. The subnet mask IP Address. Enter only one of these values. When you finish, click the Next button. The Add Exclusions dialog box displays.
  • Page 60: Adding Dhcp Options

    5. In the left pane of the DHCP, right click the DHCP Server name, then click Set Predefined Options..6. Under Predefined Options and Values, click Add. 7. In the Option Type Name field, enter any appropriate name, for example, “Avaya IP Telephones”. 60 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 61: Activating The New Scope

    DHCP 8. Change the Data Type to String. 9. In the Code field, enter 176, then click the OK button twice. The Predefined Options and Values dialog box closes, leaving the DHCP dialog box enabled. 10. Expand the newly created scope to reveal its Scope Options. 11.
  • Page 62: Tftp

    Note that this option might not be available to all TFTP servers. Download the upgrade script file and application file from the Avaya Web site (http://www.avaya.com/support) to the directory as specified by the file path.
  • Page 63: Avaya Tftp (Suite Pro)

    71. TFTP Server on S8300 Media Server The S8300 Media Server provides all the TFTP support required for the 4600 Series IP Telephones. In addition, the media server has an easy to use, PC-based interface for creating script files. Thus, you do not need to manually create the text files discussed in...
  • Page 64 Management Complex IP Addresses MCIPADD Management Complex Transport Layer Port MCPORT Network Audio Quality Assessment Display NTWKAUDIO Wait Time for DHCP Offer VLANTEST Ethernet Line Interface Status PHY1STAT 1 of 2 64 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 65 TFTP Table 4: Media Server Field Names & Corresponding Script File Parameter Names (continued) Media Server Field Name Script File Parameter Name Secondary Ethernet Line Interface Status PHY2STAT Local (dial pad) Procedure Password PROCPSWD RTCP Monitor IP Address RTCPMON Voicemail Home Page VMLHOME LDAP Directory Server DIRSRVR...
  • Page 66: Http

    Administer the system parameters HTTPSRVR and CODESRVR to the address(es) of the HTTP server. Include these parameters in DHCP Option 176, or the appropriate SSON Option. Download the upgrade script file and application file(s) from the Avaya Web site http://www.avaya.com/support to the HTTP server.
  • Page 67: 4600 Series Ip Telephone Scripts And Application Files

    The Avaya-provided upgrade script files, and the binaries included in the zip files, upgrade the Avaya IP Telephones. You should not need to modify them. It is essential that all the binary files be together on the file server. When downloading a new release onto a file server with an existing release already on it, we recommend that you: Stop the file server.
  • Page 68 However, you might want to open the default file and administer the options to add useful functionality to your Avaya IP Telephones. This file must reside in the same directory as the upgrade script file, and must be called 46xxsettings.scr or 46xxsettings.txt.
  • Page 69: Choosing The Right Application File And Upgrade Script File

    TFTP or HTTP. This happens when you initially download the script file template from the Avaya support Web site, before you make any changes. When the settings file contains no setting changes, the telephone does not go back to the upgrade script file.
  • Page 70 SIGnaling Protocol Identifier procedure in Chapter 3 of the 4600 Series IP Telephone Installation Guide. For example, if yours is a largely H.323 environment, when SIP phones are installed the SIG system value should be set to “2”. If yours is a largely SIP environment, when H.323 phones are installed the SIG system value...
  • Page 71: Contents Of The Upgrade Script

    4600 Series IP Telephone Scripts and Application Files Contents of the Upgrade Script This is a sample upgrade script file: Note: The filenames following the SET APPNAME command in this sample are Note: examples only and may not match those used in production.
  • Page 72 END #definity bigApp for 4612 & 4624 model # DEF4624 SET APPNAME def24r1_73.bin goto END # END ##################################### #download the 46xx Settings script # ##################################### GET 46xxsettings.scr GET 46xxsettings.txt 72 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 73: Contents Of The Settings File

    Check the last lines of the Upgrade Script file example in the previous section. They show that after checking the application software, the 4600 Series IP Telephone looks for a 46xx settings file. This optional file is under your control and is where you can identify non-default option settings, application-specific parameters, etc.
  • Page 74: Qos

    # END {specify settings common to all Groups} The 4600 Series IP Telephones support both IEEE 802.1D/Q and DiffServ. In the future, the 4600 Series IP Telephones might support other, possibly proprietary, procedures for implementing Quality of Service. In addition, other network-based QoS initiatives such as UDP port selection do not require support by the telephones.
  • Page 75: Diffserv

    To support IEEE 802.1D/Q, the 4600 Series IP Telephones can be administered either of two ways: from the network by appropriate administration of the DHCP or TFTP/HTTP servers, or at the telephone itself using dialpad input. Specific implementation details for local administration are in the Installation Guide. This...
  • Page 76: Udp Port Selection

    To support UDP port selection, the 4600 Series IP Telephones can be administered from the Avaya Communication Manager Network Region form. Locate specific implementation details for local administration of MCPORT in the 4600 Series IP Telephone Installation Guide.
  • Page 77: Network Audio Quality Display On 4600 Series Ip Telephones

    Network Audio Quality Display on 4600 Series IP Telephones With the exceptions of the 4601, 4606, 4612, 4624, and 4690 IP Telephones, all Series 4600 IP Telephones are by default administered to allow the end user an opportunity to monitor network audio performance while on a call.
  • Page 78: Rsvp And Rtcp

    Avaya IP Telephones implement the Resource ReSerVation Protocol (RSVP) to support WAN bandwidth management. RSVP is administered from the media server. Avaya IP Telephones implement the RTP Control Protocol (RTCP) so Avaya’s Voice over IP (VoIP) Monitoring Manager (VMON) software can provide real-time monitoring and historical data of audio quality for VoIP calls.
  • Page 79: Vlan Considerations

    VLAN Considerations If your LAN environment does not include Virtual LANs (VLANs), ignore this section. Otherwise, this section contains information on how to administer 4600 Series IP Telephones to minimize registration time and maximize performance in a VLAN environment. The system value L2QVLAN is initially set to “0” and identifies the 802.1Q VLAN IDentifier. This default value indicates “priority tagging”...
  • Page 80: Administering Options For The 4600 Series Ip Telephones

    4600 Series IP Telephones. This section explains how to change parameters by means of the DHCP or TFTP/HTTP servers. In all cases, you are setting a system parameter in the telephone to a desired value.
  • Page 81 Administering Options for the 4600 Series IP Telephones Table 6: 4600 Series IP Telephone Customizable System Parameters (continued) Parameter Default Name Value Description and Value Range AUTH Script file authentication value (0=HTTP is acceptable, 1=HTTPS is required). CNAPORT 8888 Avaya Converged Network Analyzer (CNA) server registration transport-layer port number (0-65535).
  • Page 82 Server Administration Table 6: 4600 Series IP Telephone Customizable System Parameters (continued) Parameter Default Name Value Description and Value Range OPSTAT Options status flags. Consists of 3 “bits” of the form abc, where each letter represents a 0 (disabled/off) or 1 (enabled/on). The first bit, a, controls the setting for all options not controlled by the second or third bits.
  • Page 83 Administering Options for the 4600 Series IP Telephones Table 6: 4600 Series IP Telephone Customizable System Parameters (continued) Parameter Default Name Value Description and Value Range PROCPSWD " " (Null) Text string containing the local (dialpad) procedure password (Null or 1-7 ASCII digits).
  • Page 84: Dns Addressing

    DHCP server. Entering Options Using the Telephone Dialpad The 4600 Series IP Telephone Installation Guide’s Chapter 3 details how to use the local administrative options. To customize any or all of the QoS parameters locally, follow the “QoS Option Setting”...
  • Page 85: Enhanced Local Dialing

    Japan, but its media server is in the United States, set the PHNCC value to “1" for the United States. In all cases, the digits the phones insert and dial are subject to standard Avaya media server features and administration. This includes Class of Service (COS), Class of Restriction (COR), Automatic Route Selection (ARS), etc.
  • Page 86 WML Web sites. This is indicated by preceding that type of number with a plus (+) sign, and a space or some non-digit character following the country code. 86 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 87: Customizing The 4630/4630Sw Ip Telephone

    46xxsettings file, the 4630/4630SW uses default settings only. The 46xxsettings file is no longer part of the *.zip file on the Avaya software download Web site, but is available as a stand-alone download. If you already have such a file because you downloaded it for a previous 4630 release, installing the stand-alone file overwrites the original file.
  • Page 88 The default is LDAP-standard for “unlimited duration.” DIRLDAPPORT Optional Directory LDAP Port. The port that exchanges LDAP messages with the server. 1 of 2 88 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 89 Customizing the 4630/4630SW IP Telephone Table 7: 4630/4630SW IP Telephone Customizable System Parameters by Application (continued) Parameter Name Default Value Status Description and Value Range Stock Ticker Application Parameters: STKSTAT Optional Text string identifying whether the phones are allowed to have the Stock Ticker Application.
  • Page 90: 4630/4630Sw Backup/Restore

    Parameter FTP User ID Parameter Stock Ticker Active? Option STK.mm Parameter Stock Index DJIA Option Stock Index S&P 500 Option Stock Index Nasdaq Option Stock Change Option Stock Volume Option 90 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 91: Call Log Archive

    Customizing the 4630/4630SW IP Telephone If the Automatic Backup option is set to No, Speed Dial data, Options and Parameter settings are not saved. However, the user can force a one-time backup via the appropriate option. See Chapter 8 of the 4630 IP Telephone User Guide for information. Restoring backed-up data is a separate user option, also covered in Chapter 8 of the 4630 IP Telephone User Guide.
  • Page 92: Customizing 4610Sw, 4620/4620Sw, 4621Sw, 4622Sw, And 4625Sw Ip Telephones

    46xxsettings.txt file, those telephones use default settings only. The 46xxsettings file is no longer part of the *zip file on the Avaya software download Web site, but is available as a stand-alone download. If you already have such a file because...
  • Page 93 Customizing 4610SW, 4620/4620SW, 4621SW, 4622SW, and 4625SW IP Telephones Table 8: 4610SW, 4620/4620SW, 4621SW, 4622SW, and 4625SW IP Telephone Customizable System Parameters Parameter Name Default Value Status Description and Value Range General User Parameters: APPSTAT Optional Applications status flag. See Application Status Flag (APPSTAT) page 95 for a description.
  • Page 94 HTTP. This parameter is optional if the Web pages to be accessed by the user are all on your organization’s intranet. If WMLPROXY is null, the value of this parameter is ignored. 2 of 3 94 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 95: The Application Status Flag (Appstat)

    Number of idle minutes after which the backlight turns off (1-3 ASCII digits, from 0-999). 3 of 3 Note: Appendix C: Creating Web Sites for Other 4600 Series IP Telephones provides Note: assistance in developing local Web sites tailored to the 4610SW/4620/4620SW IP Telephone’s display.
  • Page 96 APPSTAT has no effect on telephones having no user-selectable applications such as the 4602. Also, to “suppress” the WML applications, all you have to do is not administer the appropriate parameters. In essence, these applications are suppressed by default. 96 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 97: Backup/Restore For 4610Sw, 4620/4620Sw, 4621Sw, 4622Sw And 4625Sw Ip Telephones

    Backup/Restore for 4610SW, 4620/4620SW, 4621SW, 4622SW and 4625SW IP Telephones Backup/Restore for 4610SW, 4620/4620SW, 4621SW, 4622SW and 4625SW IP Telephones Backup/Restore automatically saves a phone’s Speed Dial button labels and options/parameter settings, including local Feature button labels. When the Automatic Backup option on a 4610SW, 4620/4620SW, 4621SW, 4622SW, or 4625SW IP Telephone is set to Yes and FTPSRVR is specified, the FTPSTOR command attempts to save all Speed Dial contents, all system options, and non-password parameters to the FTP server specified by FTPSRVR.
  • Page 98 When the Options Status Flag, OPSTAT, is set to 0, retrieving backed up data Note: has no effect. This prevents a user from bypassing the administration of OPSTAT and changing options settings in the backup file. Table 8 includes OPSTAT values. 98 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 99: Chapter 5: Troubleshooting Guidelines

    4625SW IP Telephone User Guide, and 4630/4630SW IP Telephone User Guide Note: Most of the problems reported by 4600 Series IP Telephone users are not likely Note: to be problems with the telephone itself. Problems are more likely LAN-based, where Quality of Service, server administration, and other issues can impact end-user perception of IP telephone performance.
  • Page 100 Troubleshooting Guidelines Table 10: Some Error Conditions in Operation of 4600 Series IP Telephones Condition Cause/Resolution The telephone continually reboots, or reboots CAUSE: The telephone cannot find the call continuously about every 15 minutes. server. RESOLUTION: Ensure that MCIPADD is administered either manually or through DHCP, TFTP, or HTTP, as appropriate.
  • Page 101 Error Conditions Table 10: Some Error Conditions in Operation of 4600 Series IP Telephones (continued) Condition Cause/Resolution The telephone was AND no lights are lit on CAUSE: Loss of power. working, but does the phone and the RESOLUTION: Check the connections not work now, display is not lit.
  • Page 102 Troubleshooting Guidelines Table 10: Some Error Conditions in Operation of 4600 Series IP Telephones (continued) Condition Cause/Resolution The telephone works, but the audio quality is poor, specifically: the user hears echo CAUSE: Echo from digital-to-analog when speaking on a conversion on your Avaya media server handset.
  • Page 103 Error Conditions Table 10: Some Error Conditions in Operation of 4600 Series IP Telephones (continued) Condition Cause/Resolution The telephone works properly except for the CAUSE: The Speaker was turned off on the Speaker. PBX. RESOLUTION: Administer the PBX to allow that station’s Speaker to operate.
  • Page 104 Troubleshooting Guidelines Table 10: Some Error Conditions in Operation of 4600 Series IP Telephones (continued) Condition Cause/Resolution The TFTP or HTTP AND the TFTP or CAUSE: The telephone expects lines of the script file is ignored HTTP server is a script file to terminate with a <Carriage...
  • Page 105 Error Conditions Table 10: Some Error Conditions in Operation of 4600 Series IP Telephones (continued) Condition Cause/Resolution The user indicates a 4610SW/4620/4620SW/ CAUSE: The 46xxsettings script file is not 4621SW/4622SW/4625SW-specific or pointed to accurately, or is not properly 4630/4630SW-specific application is not administered to allow the application.
  • Page 106: The Clear Administrative Option

    See Chapter 3 of the 4600 Series IP Telephone Installation Guide. 3. If the 4600 Series IP Telephone is not communicating with the DHCP, TFTP, HTTP, or media server, make a note of the last message displayed. Consult the system administrator.
  • Page 107 Note: keys/buttons. The 4630/4630SW IP Telephones and the 4690 IP Conference Telephone do not have a dedicated Hold button. For all other 4600 Series IP Telephones, pressing the Hold button instead of the Mute button also works. The following text displays left-justified at the top of the display:...
  • Page 108: The Reset Administrative Option

    Series IP Telephone. Procedures on how to do so are printed in this section. You can also find reset procedures in Chapter 3 of the 4600 Series IP Telephone Installation Guide. These parameters and settings are reset to default values, including “null” as applicable, when the Reset procedure finishes: Registration extension and password.
  • Page 109 The Reset Administrative Option The 4601 IP Telephone flashes both Message Waiting indicators 500 milliseconds on, 500 milliseconds off to indicate user input is expected. All other IP telephones display the following text left-justified at the top of the display: Reset values? *=no #=yes...
  • Page 110: Restart The Telephone

    Note: keys/buttons. The 4630/4630SW IP Telephones and the 4690 IP Conference Telephone do not have a dedicated Hold button. For all other 4600 Series IP Telephones, pressing the Hold button instead of the Mute button also works. The 4601 IP Telephone flashes both Message Waiting Indicators 500 milliseconds on, 500 milliseconds off to indicate user input is expected.
  • Page 111: The View Administration Option

    Note: keys. The 4630 IP Telephone does not have a dedicated Hold button. For all other 4600 Series IP Telephones, pressing the Hold button instead of the Mute button also works. The following text displays left-justified at the top of the display:...
  • Page 112 Up to 21 ASCII characters, IP Address and port of media server currently in use. Group Up to 3 ASCII characters. Protocol cccccccc Up to 8 ASCII characters. filename1.exe Up to 16 ASCII graphic characters. filename2.exe 112 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 113: Error Messages

    Error Messages Error Messages The 4600 Series IP Telephones issue messages in English only. The IP telephones also display messages from the switch, which outside the United States might issue messages in the local language. Note: Because the 4601 IP Telephone does not have a display, it is limited in its ability Note: to provide visual feedback and error messages.
  • Page 114 Troubleshooting Guidelines Table 12: Possible Error Messages During Installation or Operation of 4600 Series IP Telephones (continued) Error Message Cause/Resolution CAUSE: The telephone is seeking a gatekeeper on the Discovering... media server, using its administered gatekeeper list. RESOLUTION: Wait for a valid registration to occur, or press # to interrupt the search and re-initialize manual or DHCP/script files procedures.
  • Page 115 Error Messages Table 12: Possible Error Messages During Installation or Operation of 4600 Series IP Telephones (continued) Error Message Cause/Resolution CAUSE: The file server IP Address in the IP telephone’s No file server address memory is all zeroes. RESOLUTION: Depending on the specific requirements of your network, this may not be an error.
  • Page 116 Troubleshooting Guidelines Table 12: Possible Error Messages During Installation or Operation of 4600 Series IP Telephones (continued) Error Message Cause/Resolution CAUSE: The specified extension is already in use, Extension in use according to the Avaya media server. RESOLUTION: Wait a few minutes, and try again. Waiting...
  • Page 117 Error Messages Table 12: Possible Error Messages During Installation or Operation of 4600 Series IP Telephones (continued) Error Message Cause/Resolution CAUSE: The Avaya media server rejects the registration Resource Error request. RESOLUTION: Verify your Avaya media server administration to ensure the telephone’s proper IP Address, extension, and password are being used.
  • Page 118: Troubleshooting The 4601 Ip Telephone

    14, the Error Messages shown in the first column correspond to the equivalent conditions described in “Chapter 4" of the 4600 Series IP Telephone Installation Guide and Table 12: Possible Error Messages During Installation or Operation of 4600 Series IP Telephones.
  • Page 119 Softphone. RESOLUTION: You can force the current telephone to register, and thereby disconnect the other user, by pressing #. The 4600 Series IP Telephone prompts you again for the Extension and Password. If you enter the same Extension and Password, you must confirm that you want to unregister the original user.
  • Page 120 RESOLUTION: Press * to retry the process using the same values or # to restart and re-enter the Extension and Password. Consult your Avaya media server administration and troubleshooting documentation. 2 of 3 120 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 121 Troubleshooting the 4601 IP Telephone Table 14: Possible Error Messages During 4601 IP Telephone Installation or Operation (continued) Error Message 4601 Visual Indication/Cause/Resolution VISUAL INDICATION: Message Waiting indicators at top of phone and left Wrong Set middle of faceplate display a broken flutter continuously (alternating 50 Type.
  • Page 122 Troubleshooting Guidelines 122 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 123: Appendix A: Avaya - 46Xx Ip Telephone Mib

    Appendix A: Avaya - 46xx IP Telephone MIB Downloading the Avaya - 46xx IP Telephone MIB The custom Management Information Base (MIB) is available in *.txt format for free download at http://www.avaya.com/support. Follow these links: Under Technical Database, select Telephone Devices & User Agents.
  • Page 124 Avaya - 46xx IP Telephone MIB 124 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 125: Appendix B: Creating Web Sites For The 4630/4630Sw Ip Telephone

    Web server technologies. Finally, this document is not intended to provide an introduction to Web browser protocols or technologies. Note: See the Avaya Web site for a link to sites where HTML templates are available Note: for customizing.
  • Page 126: General Background

    Note: The sections in this appendix show comments specific to the 4630 IP Telephone Note: and its browser in italics. 126 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 127: Document Skeleton

    Browser Features and Behavior Document Skeleton Certain tags define the basic framework of an HTML document. Most browsers are usually good at dealing with missing tags. However, when you apply style sheets it is essential that you follow the tag structures. Even ignoring style sheets, it is considered good style to follow the HTML rules.
  • Page 128: Logical Style

    <span> indicates a spanned section of text is placed immediately after the text that precedes the tag with a newline. No physical changes are noticeable, except those implemented in style sheets. 128 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 129: Physical Style

    Browser Features and Behavior Physical Style Physical tags are effectively the opposite of content-based tags. The text in a physical tag might have no meaning whatsoever, outside what the designer intended. These tags show text in a distinct style. Physical tags usually affect font style. Each physical style tag is shown with a brief description and any physical effects the browser imposes.
  • Page 130: Lists And Tables

    <caption> adds a caption to a table. The align attribute allows a caption to be placed above or below the table. This attribute has no effect in the phone. <tr> adds a new table row to a table. 130 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 131: Images

    Browser Features and Behavior <th> adds a header for some column(s) of a table. <td> adds a piece of data for some row(s) and column(s) of a table. <thead> defines a set of table header rows. The intent of this tag is to provide a set of header rows for each printed page.
  • Page 132: Links

    “table of contents” frame with images for links. In general, however, use of frames is strongly discouraged. <frameset> defines an area for a set of frames. <frame> defines a single frame in a frameset. <iframe> defines an in-line frame. 132 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 133: Forms

    Browser Features and Behavior <noframes> provides a fallback for browsers that don’t handle frames. If the designer intends to use frames and make these pages available to the phone, this tag should certainly be employed. See the Design Guidelines on page 135 for information on displaying frames. Forms HTML forms provide the user the ability to enter data into a Web browser.
  • Page 134: Character Entities

    Although we found some problems with font specifications, fonts behave reasonably well given the screen’s size and resolution. The only major problem found is the inability to specify font families. See the Design Guidelines on page 135 for information on displaying images. 134 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 135: Cookies

    Design Guidelines Cookies Cookies can be a useful feature in maintaining the state of a user when interacting with a Web site. HTTP provides no state information, such as when or how often a user visits a site. Cookies allow Web sites to track this information by storing a simple set of values on the browser for the current session.
  • Page 136: Images

    Data is likely to be in frames that can never be seen. Minimal screen real estate and scrolling issues make frames something to avoid. 136 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 137: Fonts

    Design Guidelines Fonts Font size is a major concern in the browser. Without designer intervention, the browser displays text as if it were running on a PC in a normal width and height display. This means that the fonts shown appear huge relative to the screen size. As a result, only seven lines of text can be viewed in the browser when no font sizing is applied.
  • Page 138: User Interaction

    <table border="0" width="100%"> <tr> <td> <b>Call IT Technical Support:</b><br> <a href="javascript:dial('1-555-555-5151')"> <img border="0" src="call.gif">1-555-555-5151 </a> </td> <tr> <td> <b>Call Bill Pay:</b><br> <a href="javascript:dial('1-555-555-5152')"> <img border="0" src="call.gif">1-555-555-5152 </a> <td> <tr> </table> </body></html> 138 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 139 Design Guidelines The generated code is rendered as this Web page: Issue 2.2 April 2005...
  • Page 140 Creating Web Sites for the 4630/4630SW IP Telephone 140 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 141: Appendix C: Creating Web Sites For Other 4600 Series Ip Telephones

    Appendix C: Creating Web Sites for Other 4600 Series IP Telephones Introduction A Web browser is available for Web application development in these 4600 Series IP Telephones: 4610SW 4620/4620SW 4621SW 4622SW 4625SW See the 4600 Series IP Telephones Application Programmer Interface (API) Guide, available on the Avaya support Web site ( http://www.avaya.com/support...
  • Page 142 Creating Web Sites for Other 4600 Series IP Telephones 142 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 143: Appendix D: Administering Thin Client Directories

    4610SW 4620/4620SW 4621SW 4622SW 4625SW See the 4600 Series IP Telephones Application Programmer Interface (API) Guide, available on the Avaya support Web site ( http://www.avaya.com/support ) for detailed information about installing and administering Avaya’s Thin Client Directory application. Issue 2.2 April 2005...
  • Page 144 Administering Thin Client Directories 144 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 145: Appendix E: The Push Feature

    Appendix E: The Push Feature Introduction Release 2.1 of the 4600 Series IP Telephones provides support for a feature called “Push,” which applies to the 4610SW, 4620, and 4620SW Telephones. Release 2.2 introduces additional IP telephones, the 4621SW, the 4622SW, and the 4625SW, to which the Push feature also applies.
  • Page 146: Push Content

    Push content and administering the Push feature. Find the API on the Avaya support Web site, http://www.avaya.com/support. Further information, including sample applications, is also available in a Software Developer Toolkit on the Avaya support Web site.
  • Page 147: Index

    ... Conventions Used in This Guide 4630/4630SW IP Telephone Creating Web Sites for Other 4600 Series IP ....Backup/Restore .
  • Page 148 ..... . . IP Address Lists and Station Number Portability Software 148 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...
  • Page 149 ... . Media Server Field Names Scripts and Application Files, for 4600 Series IP ....
  • Page 150 Index 150 4600 Series IP Telephone Release 2.2 LAN Administrator Guide...

Table of Contents