Setting L2Q Tagging Control (4601 Only)

Use the following procedure to set the layer 2 (802.1Q) framing parameter manually for the 4601 IP Telephone only.

1.While the phone is on-hookand idle, press the following sequence of keys on the faceplate of the telephone:

Mute 8 2 4 # (Mute T A G #)

Note:

Press the Mute button momentarily. Do not press this button while pressing other keys/buttons. Pressing theHold button instead of theMute button also works.

Because it does not have a display, the 4601 IP Telephone’s Call Appearance Line indicators wink out the current NVL2Q value. Valid values are:

●1=ON (enabled)

●2=OFF (disabled)

●3-AUTO(the default)

The single-digitvalue is represented by Call Appearance Linea, which winks the number of times represented by the current L2Q value 600 milliseconds on, 200 milliseconds off. If the current value is zero (AUTO), Call Appearance Linea’s indicator flutters five times 50 milliseconds on, 50 milliseconds off instead of winking.

After “displaying” the current L2Q value, the Message Waiting indicator at the top of the phone and the Message button LED on the faceplate flash 500 milliseconds on, 500 milliseconds off to indicate an entry is expected.

The 4601 provides feedback for the digit as you enter it using Call Appearance Line a. For example, if the L2Q value is “2,” pressing the number2 on the dial pad causes Call Appearance Linea’s indicator to wink two times. Pressing “0” (zero) on the dial pad causes Call Appearance Linea’s indicator to flutter three times 50 milliseconds on, 50 milliseconds off.

Then both Message Waiting indicators flash 500 milliseconds on, 500 milliseconds off to indicate an entry is expected.

3.Press the * button to terminate the procedure, or the# button to save the new value. If you press the# button, the 4601 saves the new value, and resets the telephone to restore the user interface to its previous state.

Issue 2.2 April 2005 61

Local Administrative Options

62 4600 Series IP Telephone Release 2.2 Installation Guide

Chapter 4: Troubleshooting Guidelines

Introduction

This chapter describes problems that might occur during installation of the 4600 Series IP Telephones and possible ways of resolving these problems. For problems that occur during normal operation, see “Troubleshooting Guidelines” in the4600 Series IP Telephone LAN Administrator Guide.

This chapter contains the following sections:

●Descriptions of error conditions and methods for resolving them.

●The use of the V I E W option to view system values.

●Error and status messages, and methods for resolving them.

Error Conditions

There are four areas where installers can troubleshoot problems before seeking assistance from the system or LAN administrator:

1.Check both the power and Ethernet wiring for the following conditions:

●If the telephone is supposed to be powered from the LAN, ensure that the LAN is properly administered and is compliant with IEEE 803.3af.

●Ensure that the Ethernet complies with Category 5e wiring.

2.If you are using static addressing:

●Use the View command) to find the names of the files being used and verify that these filenames match those on the TFTP or HTTP server. SeeThe View Administrative Option on page 65 for more information. Check the Avaya Web site to verify whether the correct files are being used.

3.If the 4600 Series IP Telephone is not communicating with the system (DHCP, TFTP, HTTP or Avaya Media Server), make a note of the last message displayed. Consult the system administrator.

4.If you expect the telephone to be IEEE-powered,verify with the LAN administrator that IEEE power is indeed supported on the LAN.

Note:

Because the 4601 IP Telephone does not have a display, it is limited in its ability to provide visual feedback and error messages. See Troubleshooting the 4601 IP Telephone later in this chapter for more information.

DTMF Tones

The failure to hear DTMF tones sent by a far-end4600 Series IP Telephone does not require any action on the user’s part. The TN2302AP board does not passin-bandDTMF tones.

Power Interruption

If power to a 4600 Series IP Telephone is interrupted while the telephone is saving the application file, the TFTP application can stop responding. If this occurs, restart the TFTP server.

64 4600 Series IP Telephone Release 2.2 Installation Guide

The View Administrative Option

The View Administrative Option

If you are using static addressing and encounter problems, use the following procedure to verify the current values of system parameters and file versions.

Note:

Also use the ADDR option to view IP addresses. SeeStatic Addressing Installation inChapter 3: Local Administrative Options. The IP addresses might have been entered incorrectly. Verify whether you were provided with correct IP addresses.

The 4601 IP Telephone does not support the V I E W option.

1.While the phone is on-hookand idle, press the following sequence of keys on the faceplate of the telephone:

Mute 8 4 3 9 # (Mute V I E W #)

Note:

Press the Mute button momentarily. Do not press this key while pressing other keys. The 4630/4630SW IP Telephones and the 4690 IP Conference Telephone do not have a dedicatedHold button. For all other 4600 Series IP Telephones, pressing theHold button instead of theMute button also works.

The following text displays left-justifiedat 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 fromTable 1. The first pair returns after the last pair displays.

Press the # button at any time during viewing to terminate the procedure and restore the user interface to its previous state. The names and values display in the following order:

Table 1: Parameter Values

Name

System Value

Format

Model

46ccDccc

Up to 8 ASCII graphics characters.

Market

domestic

Only one value displays.

export

Phone SN

cccccccccccc

Phone Serial Number, up to 18 ASCII

cccccccc

graphic characters.

1 of 2

Issue 2.2 April 2005 65

Troubleshooting Guidelines

Table 1: Parameter Values (continued)

Name

System Value

Format

PWB SN

cccccccccccc

Printed Wiring Board (circuit board)

cccccccc

Serial Number, up to 18 ASCII

graphic characters.

PWB

ccccccccc

9 ASCII numbered characters.

comcode

MAC

00:60:1D:hh:hh:hh

Each octet of the MAC address

address

displays as a pair of hexadecimal

numbers.

L2 tagging

ccccccccc

Up to 9 ASCII characters.

VLAN ID

cccc

Up to 4 ASCII characters. Value is ID

number or “none.”

IP address

nnn.nnn.nnn.nnn

Up to 15 ASCII characters.

Subnet mask

nnn.nnn.nnn.nnn

Up to 15 ASCII characters.

Router

nnn.nnn.nnn.nnn

Up to 15 ASCII characters.

File server

nnn.nnn.nnn.nnn.nnnnn

Up to 21 ASCII characters: IP

address and port of last file server

used successfully.

Media server

nnn.nnn.nnn.nnn.nnnnn

Up to 21 ASCII characters: IP

address and port of media server

currently in use.

Group

nnn

Up to 3 ASCII characters.

Protocol

cccccccc

Up to 8 ASCII characters.

filename1.exe

Up to 16 ASCII graphic characters.

filename2.exe

Out of the box, there is only one

filename.exe. After installation, there

should be two filenames. If there is only one filename, installation has failed. Verify the problem and then reinstall the telephone.

2 of 2

66 4600 Series IP Telephone Release 2.2 Installation Guide

Error and Status Messages

Error and Status Messages

Note:

This section describes error and status messages only for those IP telephones having a display. For error and status messages related to installing a 4601 IP Telephone, see Troubleshooting the 4601 IP Telephone on page 71.

The 4600 Series IP Telephones issue messages in English only. The IP telephones also display messages from the switch, which can issue messages in the local language outside the United States.

Most of the messages in Table 2 display only for about 30 seconds, and then the telephone resets. The most common exception isExtension in Use, which requires manual intervention.

System busy CAUSE: Most likely, the number of IP endpoints on the PBX is already at maximum, Less likely, network resource is unavailable.

RESOLUTION: The telephone was attempting to access a network resource (DHCP server, TFTP server, HTTP server, or the PBX) and was not successful. Check the resource being called upon for its availability. If the resource appears operational and properly linked to the network, verify that addressing is accurate and that a communication path exists in both directions between the telephone and the resource.