Table of Contents
Advertisement
Network design
Sequence of operation
The following are key boot-up events, listed in order, that can help to verify proper operation of
the IP Telephone. This list includes only key events, and might not be comprehensive. Note also
that the telephone may go blank between events. In such cases, wait a few seconds or more for
an indication from the telephone as to what event is taking place.
1. Initial startup. At power-up or manual reset, the telephone goes through a short initial
startup procedure. The display shows Restarting... (if the telephone was intentionally
restarted with Hold RESET#), and then Loading... and Starting...
2. DHCP. The telephone queries the DHCP server for an IP address and other needed
information. The following packets are transmitted: DHCP Discover from telephone to
broadcast; DHCP Offer from server to broadcast, or relay agent to telephone; DHCP
Request from telephone to broadcast; and DHCP ACK from server to broadcast, or relay
agent to telephone. Note that this step is bypassed if the telephone is manually configured
with all the necessary information.
Also note that a protocol analyzer that is attached to the PC port of an Avaya IP Telephone
with a:
Switch (4602SW, 4620), sees only broadcast packets.
Hub (4606, 4612, 4624, 4630), sees all packets.
3. TFTP ping. The telephone pings the TFTP server for verification purposes.
4. Request file "46XXUPGRADE.SCR" (all caps) and others from TFTP server. This text script
file tells the telephone what boot code ("bbla0_##.bin") and application code
("def##r#_##.bin") are needed. If the telephone does not have the current codes, it requests
them from the TFTP server. A brand new telephone makes all three requests, because
telephones come from the factory with no code, or outdated code. When captured using a
protocol analyzer, all three requests show up as intuitive TFTP messages that reveal the file
name that is being requested or transferred. Note that there is a loading period after each
code is received for the first time. Note also that the file names are case sensitive on some
servers (Unix), and not on others (Microsoft).
5. Ext and Password prompts. The telephone prompts for the extension and the password if
there are no previously stored values.
6. Registration. The telephone registers with a media controller after the codes are
successfully loaded. This registration happens very quickly, and does not show up on the
display. However, the following packets can be captured using a protocol analyzer:
RAS-Gatekeeper Request (GRQ) from the telephone to the media controller;
RAS-Gatekeeper Confirm (GCF) from the media controller to the telephone;
RAS-Registration Request (RRQ) from the telephone to the media controller (not
necessarily the same one that the GRQ was sent to); and RAS-Registration Confirm (RCF)
from the media controller to the telephone.
7. Telephone is operational. The administered display shows up on the telephone, and the
extension LED illuminates.
294 Avaya Application Solutions IP Telephony Deployment Guide
Advertisement
Table of Contents
