Avaya 1600 Series IP Deskphones Administrator Guide Release 1.3.
© 2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. For full legal page information, please see the complete document, Avaya Legal Page for Hardware Documentation, Document number 03-600759.
Contents Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Other Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Chapter 2: Administration Overview and Requirements . . . . . . . . . 11 1600 Series IP Telephones . . . . . . . . . . . . . . . . . . . . . . . .
Contents Chapter 4: Avaya Aura Communication Manager Administration . . . . 31 Call Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch Compatibility and Aliasing IP Telephones . . . . . . . . . . . . . . . . 31 31 Media Server (Switch) Administration IP Interface and Addresses . . . . UDP Port Selection . . . . . . . . RSVP and RTCP . . . . . . . . . . QoS . . . . . . . . . . . . . . . . . IEEE 802.1P and 802.1Q . . . . . . NAT . . . . . . . . . . . . . . . . .
Contents Verifying Your Configuration . . . . . . . . . Windows 2000 DHCP Server . . . . . . . . . . . Verifying the Installation of the DHCP Server Adding DHCP Options . . . . . . . . . . . . . Activating the New Scope . . . . . . . . . . . . . . . . 51 52 52 54 55 HTTP Generic Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 HTTP Configuration for Backup/Restore. . . . . . . . . . . . . . . . . . . . . . . For IIS Web Servers . . . . . . . . . . . . . . . . . . . . . . .
Contents Interface Control . . . . . . . . . . . The View Administrative Option Static Addressing Installation . Disable/Enable Event Logging . Logoff. . . . . . . . . . . . . . . Self-Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1: Introduction About This Guide This guide is for personnel who administer Avaya Aura™ Communication Manager, Avaya Aura Communication Manager Branch (formerly known as Avaya Distributed Office), DHCP, HTTP/ HTTPS servers for Avaya 1600 Series IP Deskphones, a Local Area Network (LAN), or a Web server. The 1600 Series IP Telephones use Internet Protocol (IP) technology with Ethernet line interfaces and support the H.323 protocol only.
Introduction Document Organization The guide contains the following sections: Chapter 1: Introduction Chapter 2: Administration Overview and Requirements Chapter 3: Network Requirements Chapter 4: Avaya Aura Communication Manager Administration Chapter 5: Server Administration Chapter 6: Telephone Software and Application Files Chapter 7: Administering Telephone Options Chapter 8: Administering Applications and Options Appendix A: Glossary of Terms Appendix B: Related Documentation Appendix C: Sample Admin
Other Documentation Other Documentation See the Avaya support site at http://www.avaya.com/support for 1600 Series IP Telephone technical and end user documentation. The following documents are available for the 1600 Series IP Telephones: ● Avaya 1600 Series IP Deskphones Installation and Maintenance Guide, Document Number 16-601438. ● Avaya one-X™ Deskphone Value Edition 1600 Series IP Telephone Pre-Installation Checklist, Document Number 16-601439.
Introduction 10 Avaya 1600 Series IP Deskphones Administrator Guide
Chapter 2: Administration Overview and Requirements 1600 Series IP Telephones The 1600 Series IP Telephones currently support the H.323 signaling protocol. The H.323 standard provides for real time audio, video, and data communications transmission over a packet network. An H.323 telephone protocol stack comprises several protocols: ● H.225 for registration, admission, status (RAS), and call signaling, ● H.
Administration Overview and Requirements Table 1 indicates that you can administer system parameters in a variety of ways and use a variety of delivery mechanisms like: Note: ● Maintaining the information on the call server. ● Manually entering the information by means of the telephone dialpad. ● Administering the DHCP server. ● Editing the configuration file on the applicable HTTP or HTTPS file server. ● User modification of certain parameters, when given administrative permission to do so.
1600 Series IP Telephones Table 1: Administration Alternatives and Options for 1600 Series IP Telephones (continued) Parameter(s) Administrative Mechanisms For More Information See: Manual administration at the telephone “Static Addressing Installation” in the Avaya 1600 Series IP Deskphones Installation and Maintenance Guide. Avaya call server Use the change ip-network-map command to configure the VLAN ID.
Administration Overview and Requirements Table 1: Administration Alternatives and Options for 1600 Series IP Telephones (continued) Parameter(s) Quality of Service Interface Application specific parameters Administrative Mechanisms For More Information See: Avaya call server (strongly recommended) UDP Port Selection on page 34 and Appendix B: Related Documentation. DHCP DHCP and File Servers on page 43, and Chapter 7: Administering Telephone Options.
Parameter Data Precedence Parameter Data Precedence If a given parameter is administered in multiple places, the last server to provide the parameter has precedence. The precedence, from lowest to highest, is: 1. LLDP, 2. Manual administration, with the two exceptions described for the system parameter STATIC on page 72, 3. DHCP, 4. HTTP/HTTPS script file, 5. the Avaya Media Server, and finally, 6. Backup files, if administered and if permitted.
Administration Overview and Requirements Administrative Checklist Use the following checklist as a guide to system and LAN administrator responsibilities. This high-level list helps ensure that all telephone system prerequisites and requirements are met prior to telephone installation. Note: Note: One person might function as both the system administrator and the LAN administrator in some environments.
Telephone Initialization Process Table 2: Administrative Checklist (continued) Task Description For More Information See: Administer telephones locally as applicable As a Group: The GROUP System Value on page 65 and the Avaya 1600 Series IP Deskphones Installation and Maintenance Guide. Individually: The applicable Local Procedures in the Avaya 1600 Series IP Deskphones Installation and Maintenance Guide.
Administration Overview and Requirements Step 2: DHCP Server to Telephone The DHCP file server provides information to the telephone, as described in DHCP and File Servers on page 43. Among other data passed to the telephone is the IP address of the HTTP or HTTPS server. Step 3: Telephone and File Server The 1600 Series IP Telephones can download script files and settings files from either an HTTP or HTTPS server. These telephones can also download the application files from the HTTP server.
Error Conditions The 1600 Series IP Telephones support a feature called Unnamed Registration. Unnamed Registration allows a telephone to register with the Avaya Media Server without an extension, assuming the Avaya Media Server also supports this feature. To invoke Unnamed Registration, take no action. Allow the Extension... prompt to display for 60 seconds without making an entry. The telephone automatically attempts to register by means of Unnamed Registration.
Administration Overview and Requirements 20 Avaya 1600 Series IP Deskphones Administrator Guide
Chapter 3: Network Requirements Network Assessment Perform a network assessment to ensure that the network will have the capacity for the expected data and voice traffic, and that it can support for all applications: ● H.323, ● DHCP, ● HTTP/HTTPS, and ● Jitter buffers Also, QoS support is required to run VoIP on your configuration. For more information, see Appendix B: Related Documentation and UDP Port Selection on page 34.
Network Requirements Server Requirements Two server types can be configured for the 1600 Series IP Telephones: Note: ● DHCP ● HTTP or HTTPS Note: HTTPS does not provide all of the functionality of HTTP. For example, backup/ restore is unavailable via HTTPS, and firmware cannot be downloaded via HTTPS. While the servers listed provide different functions that relate to the 1600 Series IP Telephones, they are not necessarily different boxes.
Required Network Information Required Network Information Before you administer DHCP and HTTP, and TLS, as applicable, complete the information in Table 3. If you have more than one Gateway, HTTP/TLS server, subnetwork mask, and Gatekeeper in your configuration, complete Table 3 for each DHCP server. The 1600 Series IP Telephones support specifying a list of IP addresses for a gateway/router, HTTP/HTTPS server, and Avaya Media Server Gatekeeper(s).
Network Requirements Other Network Considerations SNMP The 1600 Series IP Telephones are fully compatible with SNMPv2c and with Structure of Management Information Version 2 (SMIv2). The telephones respond correctly to queries from entities that comply with earlier versions of SNMP, such as SNMPv1. “Fully compatible” means that the telephones respond to queries directed either at the MIB-II or the read-only Custom MIB.
Other Network Considerations Reliability and Performance All 1600 Series IP Telephones respond to a ping or traceroute message sent from the DEFINITY®, MultiVantage™, Avaya Aura Communication Manager, or Avaya Aura Communication Manager Branch system (formerly known as Avaya Distributed Office) or any other network source. The telephones do not originate a ping or traceroute. The 1600 Series IP Telephones offer and support “remote ping” and “remote traceroute.
Network Requirements Note: Note: Priority 0 is a higher priority than Priority 1. Network Audio Quality Display on 1600 Series IP Telephones All 1600 Series IP Telephones give the user an opportunity to monitor network audio performance while on a call. For more information, see the telephone user guide. While on a call, the telephones display network audio quality parameters in real-time, as shown in Table 4: Table 4: Parameters in Real-Time Parameter Possible Values Received Audio Coding G.711, G.
Other Network Considerations This capability also has the advantage of making station number portability easier. Assume a situation where the company has multiple locations in London and New York, all sharing a corporate IP network. Users want to take their telephones from their offices in London and bring them to New York. When users start up their telephones in the new location, the local DHCP server usually routes them to the local call server.
Network Requirements Figure 1: Signaling, Audio and Management Diagram Signaling, Audio and Management 1600 Series IP Telephone Port: 49300 Port: [1500–6500] randomly selected Port: [4000–10000] randomly selected; range may be changed via Gatekeeper administration; always an even number Port: audio port + 1 (only active during a call if RTCP is enabled) Port: audio port + 2 (only active during a call if RTCP monitoring is enabled) H.323 RAS (UDP/IP) H.
Other Network Considerations Figure 2: Initialization and Address Resolution Diagram Initialization and Address Resolution 1600 Series IP Telephone Port: 68 Port: [1024 - 5000] Operating System –selected (a new port is used for each file requested) Port: [1024 - 5000] Operating System – selected (a new port is used for each file requested) Port: [1024 - 5000] Operating System –selected DHCP (TCP/IP) HTTPS Read Request (TCP/IP) DHCP Server Port: 67 HTTPS Server Port:411 HTTPS Data, ACKs & Errors (TC
Network Requirements Security For information about toll fraud, see the DEFINITY®, Avaya Aura Communication Manager, or Avaya Aura Communication Manager Branch documents on the Avaya support Web site. The 1600 Series IP Telephones cannot guarantee resistance to all Denial of Service attacks. However, there are checks and protections to resist such attacks while maintaining appropriate service to legitimate users.
Chapter 4: Avaya Aura Communication Manager Administration Call Server Requirements Before you perform administration tasks, ensure that the proper hardware is in place, and your call server software is compatible with the 1600 Series IP Telephones. Avaya recommends the latest PBX software and the latest IP telephone firmware. Switch Compatibility and Aliasing IP Telephones As of Release 1.1, 1600 Series IP Telephones were natively supported by Avaya Aura Communication Manager Release 5.2.
Avaya Aura Communication Manager Administration 1600 Series Telephone Model Aliased as... Earliest Avaya Aura Communication Manager Release 1608-I 4610 Avaya Aura Communication Manager 3.0 1616 4620 Avaya Aura Communication Manager 3.0 1616-I 4620 Avaya Aura Communication Manager 3.0 BM32 EU24 Avaya Aura Communication Manager 3.0 The 1603, 1603SW, 1603-I, and 1603SW-I IP Telephones support three administrable call appearances or feature buttons.
Media Server (Switch) Administration Media Server (Switch) Administration If you are using the 1600 Series IP Telephones with Avaya Aura Communication Manager, see the following documents on the Avaya support Web site for information about specific switch administration: ● The Administrator Guide for Avaya Aura™ Communication Manager (Document 03-300509) provides detailed instructions for administering an IP telephone system on Avaya Aura Communication Manager.
Avaya Aura Communication Manager Administration UDP Port Selection The 1600 Series IP Telephones can be administered from the Avaya Aura Communication Manager Network Region form to support UDP port selection. Locate specific port assignment diagrams in the 1600 IP Telephone Installation and Maintenance Guide.
Media Server (Switch) Administration ! Important: Important: Avaya Aura Communication Manager administration always takes precedence over manual administration of IEEE 802.1P/Q data. The four IEEE 802.IP/Q QoS parameters in the telephones that can be administered on the IP Network Region form are L2Q, L2QVLAN, L2QAUD, and L2QSIG.
Avaya Aura Communication Manager Administration Voice Mail Integration 1600 Series IP Telephones with Avaya Aura Communication Manager 5.2 Native Support Release 1.1 provides native support for 1600 Series IP Telephones running on Avaya Aura Communication Manager Release 5.2 or later. When native support applies, pressing the Messages button causes the telephone to first determine if the call server has a dedicated number for retrieving voice mail and when found, to proceed with voice mail retrieval.
Telephone Administration Telephone Administration This section describes how to administer Avaya Aura Communication Manager for 1600 Series IP Telephones. For detailed information about administering Avaya Aura Communication Manager, see the following Avaya documents: ● ● Administrator Guide for Avaya Aura™ Communication Manager (Document 03-300509). Feature Description and Implementation for Avaya Aura™ Communication Manager (Document 555-245-770).
Avaya Aura Communication Manager Administration string, SNMP Source IP addresses, and Craft Access Code (PROCPSWD). Administer these three parameters using Page 3 of the change system-parameters ip-options form. Avaya Aura Communication Manager Feature Administration Feature Administration On-Hook Dialing Set up Avaya Aura Communication Manager so that the phone supports on-hook dialing. Use the System Parameters Features form page 10.
Administering Stations For sample Station Forms, see Appendix C: Sample Administration Forms. Aliasing 1600 Series IP Telephones Avaya Aura Communication Manager releases earlier than 5.2 do not provide native support for 1600 Series IP Telephones.
Avaya Aura Communication Manager Administration Feature Buttons and Call Appearances For the 1603/1603SW/1603-I/1603SW-I and 1608/1608-I IP Telephones You can administer Feature/Call Appearance Buttons 1 – 8 on the Avaya Aura Communication Manager Station form, which the telephone Feature screen then displays in sequence. The telephone does not display any of the Feature Button labels administered on buttons 9 – 24. These telephones do not support the BM32 Button Module.
Shuffling For additional information about administering the call server for 1600 Series IP Telephones, see the following Avaya documents, available on the Avaya Support Web site: ● ● Administrator Guide for Avaya Aura™ Communication Manager (Document Number 03-300509). Feature Description and Implementation for Avaya Aura™ Communication Manager (Document Number 555-245-770).
Avaya Aura Communication Manager Administration Printing Button Labels You can download software from www.desi.com that enables you to print button labels for the 1600 series telephones. To download this software, perform the following steps: 1. Using your web browser, go to www.desi.com. 2. Click DESI downloads. 3. Download the appropriate application.
Chapter 5: Server Administration Software Checklist Ensure that you own licenses to use the DHCP, HTTP, and HTTPS server software. Note: You can install the DHCP and HTTP server software on the same machine. Note: ! CAUTION: The firmware in the 1600 Series IP Telephones reserves IP addresses of the form 192.168.0.24 and 192.168.1.x for internal communications. The telephone(s) improperly use addresses you specify if they are of that form.
Server Administration Avaya recommends that: ● A minimum of two DHCP servers be available for reliability. ● A DHCP server be available when the IP telephone reboots. ● A 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 1600 Series IP Telephone with a script file and, if appropriate, new or updated application software.
DHCP Server Administration Any other DHCP application might work. It is the responsibility of the customer to install and configure the DHCP server correctly. DHCP server setup involves: 1. Installing the DHCP server software according to vendor instructions. 2. Configuring the DHCP server with: ● IP addresses available for the 1600 Series IP Telephones. ● The following DHCP options: - Option 1 - Subnet mask. As described in Table 3, item 3. - Option 3 - Gateway (router) IP address(es).
Server Administration Note: Note: The DHCP standard states that when a DHCP lease expires, the device should immediately cease using its assigned IP address. If the network has problems and the only DHCP server is centralized, the server is not accessible to the given telephone. In this case the telephone is not usable until the server can be reached.
DHCP Server Administration The 1600 Series IP Telephones do not support Regular Expression Matching, and therefore, do not use wildcards. For more information, see Administering Options for the 1600 Series IP Telephones on page 67. In configurations where the upgrade script and application files are in the default directory on the HTTP server, do not use the HTTPDIR=. You do not have to use Option 242.
Server Administration In Table 6, the 1600 Series IP Telephone sets the system values to the DHCPACK message field values shown. Table 6: DHCPACK Setting of System Values System Value Set to IPADD The yiaddr field. NETMASK Option #1 (if received). GIPADD Option #3 (if received, which might be a list of IP addresses). TLSSRVR The siaddr field, if that field is non-zero. HTTPSRVR The siaddr field, if that field is non-zero. DNSSRVR Option #6 (if received, which might be a list of IP addresses).
DHCP Server Administration Creating a DHCP Scope for the IP Telephones Use the following procedure to create a DHCP scope for the IP telephones. 1. Select Start-->Programs-->Admin Tools-->DHCP Manager. 2. Expand Local Machine in the DHCP Servers window by double clicking it until the + sign changes to a - sign. 3. Select Scope-->Create. 4. Using information recorded in Table 3: Required Network Information Before Installation Per DHCP Server: Define the Telephone IP Address Range. Set the Subnet Mask.
Server Administration Editing Custom Options Use the following procedure to edit custom options. 1. Highlight the newly created scope. 2. Select DHCP Options-->Defaults in the menu. 3. Click the New button. 4. In the Add Option Type dialog box, enter an appropriate custom option name, for example, “1600OPTION.” 5. Change the Data Type Byte value to String. 6. Enter 242 in the Identifier field. 7. Click the OK button. The DHCP Options menu displays. 8.
DHCP Server Administration Activating the Leases Use the following procedure to activate the leases. ● Click Activate under the Scope menu. The light-bulb icon for the scope lights. Verifying Your Configuration This section describes how to verify that the 1600OPTION is correctly configured for the Windows NT® 4.0 DHCP server. Note: Note: Although this configuration represents that for 1600 Series IP Telephones, the file remains as 46XXOPTIONS.
Server Administration Verify the Global Option, 242 1600OPTION 1. Select Global under DHCP OPTIONS. 2. In the Active Options: scroll list, click 242 1600OPTION. 3. Click the Value button. 4. Verify that the Value String box contains the correct value from DHCP Generic Setup on page 44. If not, update the string and click the OK button. Windows 2000 DHCP Server Verifying the Installation of the DHCP Server Use the following procedure to verify whether the DHCP server is installed. 1.
DHCP Server Administration 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. 9. Exclude any IP addresses in the range specified in the previous step that you do not want assigned to an IP telephone. a.
Server Administration 16. Under Lease duration for DHCP clients, select Unlimited and then click the OK button. ! CAUTION: CAUTION: IP address leases are kept active for varying periods of time. To avoid having calls terminated suddenly, make the lease duration unlimited. Adding DHCP Options Use the following procedure to add DHCP options to the scope you created in the previous procedure. 1. On the DHCP window, right-click the Scope Options folder under the scope you created in the last procedure.
HTTP Generic Setup Activating the New Scope Use the following procedure to activate the new scope. 1. In the DHCP console tree, click the IP Telephone Scope you just created. 2. From the Action menu, select Activate. The small red down arrow over the scope icon disappears, indicating that the scope was activated. HTTP Generic Setup You can store the same application software, script file, and settings file on an HTTP server as you can on a TFTP server. TFTP is not supported for 1600 Series IP Telephones.
Server Administration ● Download the upgrade script file and application file(s) from the Avaya Web site http://www.avaya.com/support to the HTTP server. For more information, see Contents of the Settings File on page 64. Note: Many LINUX servers distinguish between upper and lower case names. Ensure that you specify the settings file name accurately, as well as the names and values of the data within the file.
HTTP Configuration for Backup/Restore Additional step for IIS 6.0 (Win2003): 1. Use Internet Information Services. Go to Start --> Settings --> Control Panel --> Administrative Tools. 2. Below Default Web Site select Web Services Extension. 3. Make sure the WebDAV option is set to Allowed. For Apache Web servers: 1. Create a “backup” folder under the root directory of your Web server, and make the folder writable by everyone. All backup files will be stored in that directory.
Server Administration Web Configuration Tool Recent call server versions provide all the Web configuration support the 1600 Series IP Telephones require. Also, the media server has an easy to use, PC-based interface for creating script files. Given these resources, you do not need to manually create the text files discussed in 1600 Series IP Telephone Scripts and Application Files.
Web Configuration Tool Table 7: Media Server Field Names & Corresponding Script File Parameter Names (continued) Media Server Field Name Script File Parameter Name CNA Port Number CNAPORT 802.1X Supplicant Mode DOT1X DOT1XSTAT DHCP Lease Violation Flag DHCPSTD Domain Name DOMAIN Domain Name Server DNSSRVR HTTP Server IP Address HTTPSRVR HTTP Directory HTTPDIR Send Destination Unreachable Messages ICMPDU Process Received Redirect Messages ICMPRED Layer 2 Frame Tagging L2Q 802.
Server Administration Table 7: Media Server Field Names & Corresponding Script File Parameter Names (continued) Media Server Field Name Script File Parameter Name National Telephone # Length PHNLDLENGTH Outside Line Access Code PHNOL Ethernet Line Interface Status PHY1STAT Secondary Ethernet Interface Layer 2 Priority Value PHY2PRIO Secondary Ethernet Line Interface Status PHY2STAT Secondary Ethernet Interface VLAN Identifier PHY2VLAN Local (dial pad) Procedure Password PROCPSWD Local Dialp
Chapter 6: Telephone Software and Application Files General Download Process The 1600 Series IP Telephones download script files and settings files from either an HTTP or HTTPS server. These telephones download the application files from the HTTP server. The HTTPS server applies only if the server supports Transport Layer Security (TLS) encryption. Note: Note: The script files, application files, and settings files discussed in this chapter are identical for HTTP and HTTPS servers.
Telephone Software and Application Files 1600 Series IP Telephone Scripts and Application Files Choosing the Right Application File and Upgrade Script File The software releases containing the files needed to operate the 1600 Series IP Telephones are bundled together. You download this self-extracting executable file to your file server from the Avaya support Web site at: http://www.avaya.com/support. The file is available in both zipped and unzipped format.
1600 Series IP Telephone Scripts and Application Files Settings File The settings file contains the option settings you need to customize the Avaya IP Telephones for your enterprise. Note: Note: You can use one settings file for all your Avaya IP Telephones. The settings file includes the 1600 Series IP Telephones covered in this document as well as 9600 Series IP Telephones and 4600 Series IP Telephones.
Telephone Software and Application Files Contents of the Settings File After checking the application software, the 1600 Series IP Telephone looks for a 46xxsettings file. This optional file is where you identify non-default option settings, application-specific parameters, and so on. You can download a template for this file from the Avaya support Web site. An example of what the file might look like follows. Note: Note: The following is intended only as a simple example.
The GROUP System Value The GROUP System Value You might have different communities of users, all of which have the same telephone model, but which require different administered settings. For example, you might want to restrict Call Center agents from being able to Logoff, which might be an essential capability for “hot-desking” associates. We provide examples of the group settings for each of these situations later in this section. Use the GROUP system value for this purpose: 1.
Telephone Software and Application Files 66 Avaya 1600 Series IP Deskphones Administrator Guide
Chapter 7: Administering Telephone Options Administering Options for the 1600 Series IP Telephones This chapter explains how to change parameters by means of the DHCP or HTTP servers. In all cases, you are setting a system parameter in the telephone to a desired value. Table 8 lists: ● the parameter names, ● their default values, ● the valid ranges for those values, and ● a description of each one.
Administering Telephone Options Table 8: 1600 Series IP Telephone Customizable System Parameters Parameter Name AGCHAND Default Value 1 AGCHEAD 1 AGCSPKR 1 APPNAME " " (Null) APPSTAT 1 AUTH 0 BAKLIGHTOFF 120 BRURI " " (Null) DHCPSTD 0 DNSSRVR 0.0.0.0 DOMAIN " " (Null) DOT1X 0 Description and Value Range Automatic Gain Control status for handset (0=disabled, 1=enabled). Automatic Gain Control status for headset (0=disabled, 1=enabled).
Administering Options for the 1600 Series IP Telephones Table 8: 1600 Series IP Telephone Customizable System Parameters (continued) Parameter Name DOT1XSTAT Default Value 0 ENHDIALSTAT 1 FONTFILE " " (Null) HTTPDIR " " (Null) HTTPSRVR " " (Null) ICMPDU 0 ICMPRED 0 L2Q 0 L2QVLAN 0 LANG0STAT 1 LANGxFILE " " (Null) Description and Value Range Determines how the telephone handles Supplicants. Valid values are: 0=Supplicant operation is completely disabled.
Administering Telephone Options Table 8: 1600 Series IP Telephone Customizable System Parameters (continued) Parameter Name LANGSYS Default Value " " (Null) LOGLOCAL 0 LOGSRVR " " (Null) MCIPADD 0.0.0.0 MSGNUM " " (Null) OPSTAT 111 PHNCC 1 Description and Value Range 0 to 32 ASCII characters. The file name of the system default language file, if any. Event Log Severity Level (one 0-8 ASCII numeric digit).
Administering Options for the 1600 Series IP Telephones Table 8: 1600 Series IP Telephone Customizable System Parameters (continued) Parameter Name PHNDPLENGTH Default Value 5 PHNIC 011 PHNLD 1 PHNLDLENGTH 10 PHNOL 9 PHY1STAT 1 PHY2PRIO 0 PHY2STAT 1 PHY2VLAN 0 Description and Value Range Internal extension telephone number length. Specifies the number of digits associated with internal extension numbers by the algorithm that dials calls from the incoming Call Log or from Web pages.
Administering Telephone Options Table 8: 1600 Series IP Telephone Customizable System Parameters (continued) Parameter Name PROCPSWD Default Value " " (Null) PROCSTAT 0 REREGISTER 20 RTCPMON " " (Null) SNMPADD " " (Null) SNMPSTRING " " (Null) STATIC 0 SUBSCRIBELIST " " (Null) Description and Value Range Text string containing the local (dialpad) procedure password (Null or 1-7 ASCII digits).
VLAN Considerations Table 8: 1600 Series IP Telephone Customizable System Parameters (continued) Parameter Name TPSLIST Default Value " " (Null) UNNAMEDSTAT 1 VLANSEP 1 VLANTEST 60 Note: Description and Value Range One or more trusted domain/path strings, separated by commas without any intervening spaces (0-255 ASCII characters, including commas). A URL pushed to a telephone must contain one of these strings if it is to be used to obtain content to be rendered by the telephone.
Administering Telephone Options has absolute authority. Otherwise, you can set VLAN tagging manually, by DHCP, or in the 46xxsettings.txt file. If VLAN tagging is enabled (L2Q=0 or 1), the 1600 Series IP Telephones set the VLAN ID to L2QVLAN, and VLAN priority for packets from the telephone to L2QAUD for audio packets and L2QSIG for signalling packets. The default value (6) for these parameters is the recommended value for voice traffic in IEEE 802.1D.
VLAN Considerations VLAN Separation VLAN separation controls whether or not traffic received on the secondary Ethernet interface can be forwarded on the voice VLAN. VLAN separation also controls whether network traffic received on the data VLAN can be forwarded to the telephone. The following system parameters control VLAN separation: ● VLANSEP - enables (1) or disables (0) VLAN separation. The default is 1 (on), which allows full separation.
Administering Telephone Options Table 9: VLAN Separation Rules (continued) If Then VLANSEP is “1” (On/Enabled) AND the telephone is not tagging frames, OR if the telephone is tagging frames with a VLAN ID equal to PHY2VLAN, The Ethernet switch forwarding logic determines that frames received on the Ethernet line interface are forwarded to the secondary Ethernet interface or to the telephone without regard to specific VLAN IDs or the existence of tags. OR if the PHY2VLAN value is zero.
IEEE 802.1X IEEE 802.1X Certain 1600 Series IP Telephones support the IEEE 802.1X standard for pass-through and Supplicant operation. The system parameter DOT1X determines how the telephones handle 802.1X multicast packets and proxy logoff, as follows: ● When DOT1X = 0, the telephone forwards 802.1X multicast packets from the Authenticator to the PC attached to the telephone and forwards multicast packets from the attached PC to the Authenticator (multicast pass-through). Proxy Logoff is not supported.
Administering Telephone Options Note: If the Ethernet line interface link fails, the 802.1X Supplicant, if enabled, enters the Disconnected state. The 802.1X Supplicant variable userLogoff normally has a value of FALSE. This variable will be set to TRUE before the telephone drops the link on the Ethernet line interface (and back to FALSE after the link has been restored). The userLogoff variable may also be briefly set to TRUE to force the Supplicant into the LOGOFF state when new credentials are entered.
Link Layer Discovery Protocol (LLDP) attempts occur using the stored 802.1X credentials, without prompting the user for ID and password entry. An IP telephone can support several different 802.1X authentication scenarios, depending on the capabilities of the Ethernet data switch to which it is connected. Some switches may authenticate only a single device per switch port. This is known as single-supplicant or port-based operation. These switches typically send multicast 802.
Administering Telephone Options TR-41 Committee - Media Endpoint Discovery (LLDP-MED, ANSI/TIA-1057), and Proprietary elements. LLDP Data Units (LLDPDUs) are sent to the LLDP Multicast MAC address (01:80:c2:00:00:0e). These telephones: ● ● do not support LLDP on the secondary Ethernet interface. will not forward frames received with the 802.1AB LLDP group multicast address as the destination MAC address between the Ethernet line interface and the secondary Ethernet interface.
Link Layer Discovery Protocol (LLDP) Table 10: LLDPDU Transmitted by the 1600 Series IP Telephones (continued) Category TLV Name (Type) TLV Info String (Value) TIA LLDP MED Extended Power-Via-MDI Power Value = 0 if the telephone is not currently powered via PoE, else the maximum power usage of the telephone plus all modules and adjuncts powered by the telephone in tenths of a watt. TIA LLDP MED Network Policy Tagging Yes/No, VLAN ID for voice, L2 Priority, DSCP Value.
Administering Telephone Options Table 10: LLDPDU Transmitted by the 1600 Series IP Telephones (continued) Category TLV Name (Type) TLV Info String (Value) Avaya Proprietary 802.1Q Framing 802.1Q Framing = 1 if tagging or 2 if not. Subtype = 7. Basic Mandatory End-of-LLDPDU Not applicable.
Link Layer Discovery Protocol (LLDP) Table 11: Impact of TLVs Received by 1600 Series IP Telephones on System Parameter Values (continued) System Parameter Name TLV Name L2Q, L2QVLAN, L2QAUD, L2QSIG, DSCPAUD, DSCPSIG MED Network Policy TLV Impact L2Q - set to “2” (off) If T (the Tagged Flag) is set to 0; set to “1” (on) if T is set to 1. L2QVLAN - set to the VLAN ID in the TLV. L2QAUD and L2QSIG - set to the Layer 2 Priority value in the TLV. DSCPAUD and DSCPSIG - set to the DSCP value in the TLV.
Administering Telephone Options Local Administrative Options Using the Telephone Dialpad The local procedures you use most often as an administrator are: ● ● ● ● ● ● CLEAR - Remove all administered values, user-specified data, option settings, etc. and return a telephone to its initial “out of the box” default values. DEBUG - Enable or disable debug mode for the button module serial port. GROUP - Set the group identifier on a per-phone basis.
Local Administrative Options Using the Telephone Dialpad Note: Note: Press the Mute button momentarily. Do not press this button while pressing other keys/buttons. The following text displays left-justified at the top of the display: Clear all values? *=no #=yes 2. If you do not want to clear all values, press * (no) to terminate the procedure and retain the current values. A screen displays the following prompt on the top line: Are you sure? *=no #=yes 3.
Administering Telephone Options 2. After entry of the command sequence, the following displays, based on the current value of the system value NVDEBUG: If NVDEBUG = 1: Debug mode=on 0=off #=OK If NVDEBUG = 0: Debug mode=off 1=on #=OK If a value different from the current NVDEBUG value is entered, the following text displays left-justified at the top of the display: Save new value? *=no #=yes 3. Press the * button to terminate the procedure, or the # button to save the new value.
Local Administrative Options Using the Telephone Dialpad 1. Enter a valid Group value (0-999). If a value different from the current Group value is entered, the following text displays left-justified at the top of the display: Save new value? *=no #=yes 2. Press the * button to terminate the procedure, or the # button to save the new value. If you press the # button, the following text displays: New value being saved The new value is saved and the user interface is restored to its previous state.
Administering Telephone Options 2. If you do not want to reset the system values, press * (no) and proceed to Step 4. The following prompt displays on the top line: Are you sure? *=no #=yes 3. Press the * button to continue without resetting the values and proceed to Step 4. Or, press the # button to reset values to their defaults. All telephones display the following text left-justified at the top of the display while the system values are reset to defaults: Resetting values.
Interface Control 2. Press the # button to reset values to their defaults, or * to continue a restart without resetting the values to their defaults. The telephones display the following text left-justified at the top of the display while the system values are reset to defaults: Resetting values. Once the system values are reset, the following prompt displays on all IP telephones: Restart phone? *=no #=yes 3. Press the * key to terminate the procedure without restarting the telephone.
Administering Telephone Options ● Status is 100Mbps FDX when PHY1STAT = 5 3. To change the PHY1 value, press *. Depending on the current value, the next sequential valid PHY1 value is selected and displayed as the status. For example, if the current value is 10Mbps HDX (2), pressing * changes the value to 3 (10Mbps FDX). 4. Press the * button to terminate the procedure, or the # button to save the new value.
Interface Control ● Status is 100Mbps HDX when PHY2STAT = 4 ● Status is 100Mbps FDX when PHY2STAT = 5 5. To change the PHY2 value, press *. Depending on the current value, the next sequential valid PHY2 value is selected and displayed as the status. For example, if the current value is 10Mbps HDX (2), pressing * changes the value to 3 (10Mbps FDX). The following text displays left-justified at the top of the display: Save new value? *=no #=yes 6.
Administering Telephone Options 1. While the telephone is on-hook and idle, press the following sequence of keys on the faceplate of the telephone: Mute 8 4 3 9 # (Mute V I E W #) Note: Note: Press the Mute button momentarily. Do not press this key while pressing other keys. The following text displays left-justified at the top of the display: View settings *=next #=exit 2. Press the * button at any time during viewing to display the next name and system value pair or filename from Table 12.
Interface Control Table 12: Parameter Values (continued) Name System Value Format L2 tagging ccccccccc Up to 9 ASCII characters: “on” if NVL2Q = 1 “off” if NVL2Q = 2 “auto: on” if NVL2Q = 0 and 802.1Q tagging is on “auto: off” if NVL2Q = 0 and 802.1Q tagging is off VLAN ID cccc Up to 4 ASCII characters. Value is L2QVLAN if 802.1Q tagging is on or “none” of 802.1Q tagging is off. IP address nnn.nnn.nnn.nnn Up to 15 ASCII characters: IPADD value. Subnet mask nnn.nnn.nnn.
Administering Telephone Options Table 12: Parameter Values (continued) Name System Value Format Protocol: cccccccc Up to 8 ASCII characters, currently only “H.323.” 4 to 32 ASCII characters. The name of the primary ("big app") image file currently stored in the telephone (endptAPPINUSE). 2 to 7 ASCII characters, either “100Mbps”, “10Mbps”, or “No” depending on the current speed of the Ethernet line interface. 1 to 32 ASCII characters.
Interface Control a. During normal DHCP processing, press the * key while “* to program“ displays during the DHCP process. or b. While the telephone is on-hook and idle, press the following sequence of keys on the faceplate of the telephone: Mute 2 3 3 7 # (Mute A D D R #) Note: Note: Press the Mute button momentarily. Do not press this button while pressing other keys/buttons. The telephone displays: Phone=nnn.nnn.nnn.nnn New=_ where nnn.nnn.nnn.
Administering Telephone Options 5. Enter the IP netmask followed by the # button. The telephone displays: FileSv=nnn.nnn.nnn.nnn New=_ where nnn.nnn.nnn.nnn is the current system value of the HTTP/HTTPS server IP address. 6. Enter the File server followed by the # button. The telephone displays one of the following texts, depending on the current setting of the system parameter NVL2Q (802.1Q): If NVL2Q is 0: 802.1Q=auto *=change #=OK If NVL2Q is 1: 802.1Q=on *=change #=OK If NVL2Q is 2: 802.
Interface Control 10. Enter a valid value between 0 and 999 for the new value of the DHCPOFFER wait period. The telephone displays: Save new values? *=no #=yes 11. Press the # button to save the new values you entered. The telephone displays: New values being saved Once the new values are stored, the telephone is reset. If a new boot program is downloaded from the HTTP server after you enter static addressing information, you must reenter your static addressing information.
Administering Telephone Options ● Status is notices when NVLOGSTAT = 6 ● Status is information when NVLOGSTAT = 7 ● Status is debug when NVLOGSTAT = 8 3. To change the logging status, press *. Depending on the current value, the next sequential valid NVLOGSTAT value is selected and displayed as the status. For example, if the current value is alerts (2), pressing * changes the value to 3 (critical). If the current value is debug (8), pressing * changes the value to 0 (disabled).
Interface Control Self-Test Procedure Note: Note: Replace variable w/ short product names store two software code images in reprogrammable non-volatile memory. The primary image, called the “big app” must be running to perform a self-test. The backup image, called the “little app” does not support the self-test. For self-testing, use the following procedure: 1.
Administering Telephone Options Language Selection 1600 Series IP Telephones are factory-set to display information in the English language. The languages available depend of the type of telephone you have.
Language Selection ● text string replacements for the built-in English text strings, for example, entry prompts and error messages ● an indication of the font corresponding to the language Table 13: Language Files Available with Software Downloads for 1600 Series Global Telephones Note: Language Character Input Method to be specified in each respective language file Font Dutch Latin-1 Default English Latin-1 Default French (Canadian) French Default French (Parisian) French Default Germa
Administering Telephone Options Use the configuration file and these parameters to customize the settings for up to four languages: ● LANGxFILE - The name of a selected language file, for example, "French". In addition to providing the language name as this value, replace the "x" in this parameter with a "1", "2", "3", or "4" to indicate which of four languages you are specifying. For example, to indicate German and French are the available languages, the setting is: LANG1FILE=mlf_german.
Language Selection Note: ● text string replacements for the built-in English text strings, for example, entry prompts and error messaged ● an indication of the font corresponding to the language Note: The 1600 Series International Telephones also require a font file (*.lzma) that must be paired with the language file. Both the language file and corresponding font file must reside on the HTTP server.
Administering Telephone Options ● FONTFILE - The name of the selected font file for a language to be downloaded. You must specify this parameter for any language except Japanese Katakana. For example, to use Arabic, the setting is: SET FONTFILE Arabic_b004i.rbm.lzma. Note: Arabic and Hebrew share one font file. Note: ● LANGxFILE - The name of a selected language file.
Enhanced Local Dialing Enhanced Local Dialing The 1600 Series IP Telephones have a variety of telephony-related applications that might obtain a telephone number during operation. For example, the Call Log saves a number of an incoming caller. The telephones can evaluate a raw telephone number. Based on administered parameters, the telephone can automatically prepend the correct digits, saving the user time and effort. This is the Enhanced Dialing feature.
Administering Telephone Options Backup/Restore The 1600 Series IP Telephones support the HTTP client to back up and restore the user-specific data indicated in Table 16. For backup, the telephone creates a file with all the user-specific data if a backup file location is specified in system parameter BRURI. The file is sent to the server by an HTTP PUT message, with appropriate success or failure confirmation. For restore, the initiating process must supply only the backup file name.
Backup/Restore Backup When the system parameter BRURI is non-null, user changes are automatically backed up to the file ext_16xxdata.txt (where ext is the value of NVPHONEXT) on the HTTP server to a user-specified directory.
Administering Telephone Options Table 16: Options and Non-Password Parameters Saved During Backup Parameter Name Setting LANGUSER Display Language LOGACTIVE Call Log Active LOGBRIDGED Log Bridged Calls LOGLINEAPPS Log Line Calls LOGOTHERANS Log Calls Answered By Others OPTAGCHAND Handset Automatic Gain Control OPTAGCHEAD Headset Automatic Gain Control OPTAGCSPKR Speaker Automatic Gain Control OPTAUDIOPATH Audio Path OPTCLICKS Button Clicks OPTERRORTONE Error Tone PERSONALRING Perso
Backup/Restore Note: If you administered the APPSTAT parameter to suppress changes to one or more applications, the telephone backs up and restores data as usual, but ignores data for “suppressed” applications. This prevents a user from bypassing your APPSTAT restrictions by editing the backup file. For information about APPSTAT, see The Application Status Flag (APPSTAT) on page 114.
Administering Telephone Options 110 Avaya 1600 Series IP Deskphones Administrator Guide
Chapter 8: Administering Applications and Options Customizing 1600 Series IP Telephone Applications and Options The 1600 Series IP Telephones have some unique and powerful capabilities that take advantage of their display and access to LAN facilities. You need to provide the information called for in relevant sections of Table 17 in a customized script file. For more information, see 1600 Series IP Telephone Scripts and Application Files on page 62.
Administering Applications and Options Table 17: 1600 Series IP Telephone Customizable System Parameters Parameter Name Default Value Status Description and Value Range General User Parameters: APPSTAT 1 Optional Applications status flag. See The Application Status Flag (APPSTAT) on page 114 for a description. See Table 18 for the range of values. OPSTAT 111 Optional Options status flag(s) (1 or 3 ASCII numeric digits) indicate which options are user-selectable.
Customizing 1600 Series IP Telephone Applications and Options Table 17: 1600 Series IP Telephone Customizable System Parameters (continued) Parameter Name Default Value Status Description and Value Range Web Access Application Parameters: SUBSCRIBELIST " " (Null) Optional Subscription list for potential pushed content. List of zero or more fully qualified URLs, separated by commas without intervening spaces, with up to 255 total characters.
Administering Applications and Options The Application Status Flag (APPSTAT) The 1600 Series IP Telephones offer the user numerous applications like Contacts, Call Log, Redial, and so on. Each of these applications allows the user to add, delete, or in some cases, edit entries. You, as the administrator, might not want the user to have that level of functionality. For example, a hotel lobby telephone probably should not allow a user to delete the concierge’s contact number.
Customizing 1600 Series IP Telephone Applications and Options When the relocated telephone resets, it retains its Contact entries, like Concierge, but does not allow the user to create new entries. When you set APPSTAT to any valid value other than 1, the telephone does not accept any Contact button label changes that might have been made directly on a backup file. Only the existing labels of the telephone are used. This restriction prevents circumvention of the APPSTAT restrictions.
Administering Applications and Options Parameter Name Default Value NR_thresh_Hd 0 (6dB noise reduction) for a typical office environment Status 1 (15dB noise reduction) for call center applications Description and Value Range The transmit noise reduction threshold for the headset. These thresholds correspond to the maximum amount of noise reduction that is applied in the transmit path.
Customizing 1600 Series IP Telephone Applications and Options Parameter Name Default Value NR_thresh_Hs 0 (6dB noise reduction) for a typical office environment Status Description and Value Range The transmit noise reduction threshold for the handset. The values are same as the headset noise reduction threshold.
Administering Applications and Options Parameter Name Default Value EXP_slope_Hd 0 for a typical office environment Status 1 for call center applications 2 for other audio environments 3 for disabling the noise reduction algorithm altogether Description and Value Range The expander threshold for the headset. These thresholds correspond to the maximum amount of expansion that is applied in the transmit path. These numbers define the slope of the expander curve.
Customizing 1600 Series IP Telephone Applications and Options Parameter Name Default Value EXP_slope_Hs 0 for a typical office environment 1 for call center applications Status Description and Value Range The expander threshold for the handset. The values are same as the expander threshold for the headset.
Administering Applications and Options Parameter Name Default Value Status Description and Value Range AUDIOSTHD: The value associated with this script file variable controls the side tone for the headset. AUDIOSTHD 0 for default setting 1 for 3 steps below default The system ignores values other the ones specified and retains the default values for Sidetone_Gain_Hd.
Customizing 1600 Series IP Telephone Applications and Options Parameter Name Default Value Status Description and Value Range AUDIOSTHS: The value associated with this script file variable controls the side tone for the handset. AUDIOSTHS 0 for default setting 1 for 3 steps below default The system ignores values other the ones specified and retains the default values for Sidetone_Gain_Hs.
Administering Applications and Options Parameter Name Default Value Status Description and Value Range EXPANENHS If this system variable is 1, then the system changes the default noise-reduction algorithm operating in the transmit path, and uses an actual expander algorithm. If the value is 0 or not specified, then the system takes the normal noise-reduction algorithms.
Appendix A: Glossary of Terms 802.1P 802.1Q 802.1Q defines a layer 2 frame structure that supports VLAN identification and a QoS mechanism usually referred to as 802.1P. 802.1X Authentication method for a protocol requiring a network device to authenticate with a back-end Authentication Server before gaining network access. Applicable 1600 Series IP telephones support IEEE 802.1X for pass-through and for Supplicant operation with the EAP-MD5 authentication method.
Glossary of Terms Media Channel Encryption Encryption of the audio information exchanged between the IP telephone and the call server or far end telephone. NAPT Network Address Port Translation. NAT Network Address Translation. OPS Off-PBX Station. PHP Hypertext Preprocessor, software used to assist in the format and display of Web pages. PSTN Public Switched Telephone Network, the network used for traditional telephony.
Appendix B: Related Documentation IETF Documents The following documents provide standards relevant to IP Telephony and are available for free from the IETF Web site: http://www.ietf.org/rfc.html. ● Requirements for Internet Hosts - Communication Layers, October 1989, by R. Braden (STD 3: RFC 1122) ● Requirements for Internet Hosts - Application and Support, October 1989, by R.
Related Documentation ● Management Information Base for Network Management of TCP/IP Internets: MIB-II, March 1991, edited by K. McCloghrie and M. Rose (RFC 1213) ● 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. Braden, L.
ISO/IEC, ANSI/IEEE Documents The following documents are available for a fee from the ISO/IEC standards Web site: http://www.iec.ch. ● International Standard ISO/IEC 8802-2:1998 ANSI/IEEE Std 802.2, 1998 Edition, Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks- Specific requirements- Part 2: Logical Link Control ● ISO/IEC 15802-3: 1998 ANSI/IEEE Std 802.
Related Documentation 128 Avaya 1600 Series IP Deskphones Administrator Guide
Appendix C: Sample Administration Forms Use the sample screens that follow as guidelines for telephone setup.
Sample Administration Forms Figure 4: Station Form - Feature Options 130 Avaya 1600 Series IP Deskphones Administrator Guide
Figure 5: Station Form - IP Phone Group ID, Bridged Calls, and Enhanced Call Forwarding Issue 5 April 2010 131
Sample Administration Forms Figure 6: Station Form - Site Data, Abbreviated Dial, and Button Assignments 132 Avaya 1600 Series IP Deskphones Administrator Guide
Figure 7: Feature-Related System Parameters Form Issue 5 April 2010 133
Sample Administration Forms Figure 8: IP Address Mapping Form 134 Avaya 1600 Series IP Deskphones Administrator Guide
Figure 9: IP Codec Set Form Issue 5 April 2010 135
Sample Administration Forms Figure 10: Inter-Network Region Connection Management Form The entries on the IP Address network map shown in Figure 8 might redirect endpoints into a particular network region. That region could be different from what is administered on the previous forms.
Figure 11: IP Network Region Form Issue 5 April 2010 137
Sample Administration Forms Figure 12: IP-Options System Parameters Form 138 Avaya 1600 Series IP Deskphones Administrator Guide
Index Index Assessment, of Network . . . . . . . . . . . . . . 21 Auto Hold administration . . . . . . . . . . . . . . 38 Auto select any idle appearance administration . . . . 39 Numerical 1600 Series IP Telephone Restart . . . . . . . . . . . . . . . . 1600 Series IP Telephones Administering Options for . . . . . . . Administration Alternatives and Options Customizable System Parameters . . . Customizing Applications and Options . Initialization Process . . . . . . . . . Network Audio Quality Display .
Index E Enable Event Logging . . . . . . . . . . . . Enhanced Conference Features administration Enhanced Dialing Procedures . . . . . . . . Enhanced Local Dialing . . . . . . . . . . . Error Conditions . . . . . . . . . . . . . . . Event Logging . . . . . . . . . . . . . . . . . . . . . . . . 97 . 38, 39 . . 105 . . 105 . . 19 . . 97 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 128 . 12 129 . 33 132 121 120 L F Far End Mute administration . . . . . . . . . . .
Index P Parameter Data Precedence . . . . . . Parameter Values . . . . . . . . . . . Parameters in Real-Time . . . . . . . . Parameters Saved During Backup . . . Parameters, Customizable . . . . . . . Pass-Through and Proxy Logoff, 802.1X Port Utilization Selection . . . . . . . . . . . . . . TCP/UDP . . . . . . . . . . . . . Proxy Logoff and Pass-Through, 802.1X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 . 92 . 26 . 108 68, 112 . . 78 . . . . . . 34 . . . . . . 27 . . . . . .
Index V VIEW Administrative Option VLAN Considerations . . . VLAN Default Value . . . . VLAN Separation . . . . . VLAN Separation Rules . . VLAN tagging . . . . . . . Voice Mail Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 73 74 75 75 73 36 W Web Configuration Tool . . . . . . . . . . . . . .