Beruflich Dokumente
Kultur Dokumente
16-603609
Issue 1
June 2010
Third-party Components
Certain software programs or portions thereof included in the Product may
contain software distributed under third party agreements (Third Party
Components), which may contain terms that expand or limit rights to use
certain portions of the Product (Third Party Terms). Information identifying
Third Party Components and the Third Party Terms that apply to them is
available on Avayas Web site at:
http://support.avaya.com/ThirdPartyLicense/
Interference
Using a cell, mobile, or GSM telephone, or a two-way radio in close proximity to
an Avaya IP Telephone might cause interference.
Contents
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intended Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Telephone Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
10
10
Pre-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
13
14
14
16
20
21
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
22
23
24
25
25
27
30
32
Clear Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
Group Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
Interface Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
37
Logoff. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
39
40
41
Contents
Self-Test Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42
43
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43
.
.
.
.
.
43
44
45
45
46
46
47
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DTMF Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Interruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
48
48
48
51
54
59
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
59
59
61
. . . . . . . . . . . . . . . . .
64
. . . . . . . . . . . . . . . . .
66
69
69
71
IETF Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ITU Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ISO/IEC, ANSI/IEEE Documents . . . . . . . . . . . . . . . . . . . . . . . . .
71
71
71
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
Index
Chapter 1: Introduction
Note:
Avaya Aura Communication Manager Release 6.0 or later and Avaya Aura Session
Manager Release 6.0 or later.
Avaya Midsize Business Template Release 5.2.1 and Avaya SIP Enablement Services
Release 5.2.1.
Note:
Any reference to HTTP in this guide applies equally to HTTPS.
When running the 1603SW-I IP Deskphones in an H.323 environment see the
Avaya 1600 Series IP Deskphones Installation and Maintenance Guide for
installation and maintenance information.
This document does not cover installation or administration for Avaya Aura
Session Manager. Find full documentation for Avaya Aura Session Manager on
the Avaya support Web site, www.avaya.com/support, specifically Installing and
Upgrading Avaya Aura Session Manager (Document Number 03-603473) and
Administering Avaya Aura Session Manager (Document Number 03-603324).
For more information about administering Avaya Midsize Business Template
Release 5.2.1 and Avaya SES R5.2.1, go to www.avaya.com/support.
Introduction
Intended Audience
This document is intended for personnel who install and administer the 1603SW-I IP
Deskphones.
! CAUTION:
CAUTION:
Avaya does not provide product support for many of the products mentioned in
this document. Take care to ensure that there is adequate technical support
available for the servers involved, including, but not necessarily limited to, HTTP,
HTTPS, and DHCP servers. If the servers are not functioning correctly, the IP
Deskphones might not be able to operate correctly.
Document Organization
The guide contains the following sections:
Chapter 1: Introduction
Chapter 2: 1603SW-I IP
Deskphone Installation
Chapter 3: Local
Administrative Options
Chapter 4: Maintaining
1603SW-I IP Deskphones
Chapter 5: Troubleshooting
Guidelines
Appendix A: Restart
Scenarios
Appendix B: Glossary of
Terms
Appendix C: Related
Documentation
Other Documentation
Other Documentation
See the Avaya support site at http://www.avaya.com/support for 1603SW-I IP Deskphone
technical and end user documentation.
See Appendix C: Related Documentation for a list of non-Avaya documents, such as those
published by the Internet Engineering Task Force (IETF) and International Telecommunication
Union (ITU).
Customer Support
For 1603SW-I IP Deskphone support, call the Avaya support number provided to you by your
Avaya representative or Avaya reseller.
Information about Avaya products can be obtained at the following URL:
http://www.avaya.com/support
Introduction
Introduction
The 1603SW-I IP Deskphones use Internet Protocol (IP) technology with Ethernet interfaces.
The IP telephones supplement the existing Avaya IP Solutions platform.
The 1603SW-I IP Deskphones support DHCP and HTTP/HTTPS over TCP which enhance the
administration and servicing of the telephones. These telephones use DHCP to obtain dynamic
IP addresses, HTTP or HTTPS to download customized settings for the telephones, and HTTP
only to download the new software version.
The 1603SW-I IP Deskphones provide the ability to have one IP connection on the desktop for
both a telephone set and a PC using an Ethernet switch.
In compliance with Australian law, the following information is provided:
This equipment shall be installed and maintained by trained service personnel. All the input/
output ports are classified as Safety Extra Low Voltage (SELV, in the meaning of IEC
60950). To maintain safety compliance when connecting the equipment electrically to other
equipment, the interconnecting circuits shall be selected to provide continued conformance
of clause 2.3 for SELV circuits (generally, double/reinforced insulation to 240Vac rms to any
primary/mains circuitry and 120Vac rms to any telecommunications network circuitry). To
ensure that these conditions are adhered to, interconnect the equipment only with the
already approved/certified equipment.
IP Telephone Models
The 1603SW-I telephones have:
The 1603SW-I IP Deskphones also have an internal Ethernet switch that allows the telephone
and a PC to share the same LAN connection, if appropriate. Thus, these telephones do not
need, or work with, the 30A switched hub interface.
This document describes the installation of these telephones and post-installation maintenance
issues. For details about using the features provided by the telephones, see the user
documentation for each telephone. For information about desk or wall mounting any of the
1603SW-I IP Deskphones, see the instructions boxed with the telephone. Wall or desk mount
instructions are also available on the Avaya support Web site http://www.avaya.com/support.
Software
The 1603SW-I IP Deskphones ship from the factory set tot he H.323 protocol. To run the
deskphones in a SIP environment, you must convert the deskphones to SIP settings. Further, a
factory-shipped 1603SW-I IP Deskphone will not contain the most up-to-date software for
registration and SIP operation. When the deskphone is first plugged in, a software download
from an HTTP server might be initiated. The software download gives the telephone upgraded
H.323 functionality, however, you must still download the latest SIP software bundle for the
deskphones to be converted to SIP, then convert the deskphones to run SIP software, as
describe in Converting Software on 1603SW-I IP Deskphones on page 13.
For subsequent downloads of software upgrades, Avaya Aura Session Manager and Avaya
SES provide the capability for a remote reboot of the deskphone. As a consequence of
rebooting, the deskphone automatically downloads new software if it is available. Chapter
4: Maintaining 1603SW-I IP Deskphones covers downloading new software releases.
Pre-Installation Checklist
Pre-Installation Checklist
Before plugging in the 1603SW-I IP Deskphones, verify that all the following requirements are
met. Failure to do so prevents the telephone from working properly and can have a negative
impact on the network. Print copies of this checklist for each server and deskphone.
!
Important:
Important:
The above must be configured properly to support SIP. The CM
Outboard Proxy SIP (OPS) Station Form must be completed to
enable SIP prior to plugging in the telephones. For information, see
SIP Support in Avaya Communication Manager Running on Avaya
S8XXX Servers (Document Number 555-245-206).
Note:
All 1603SW-I IP Deskphones must be aliased as a 9620 SIP.
The following circuit packs are installed on the switch:
TN2602 IP Media Processor circuit pack. Sites with a TN2302 IP Media
Processor circuit pack are strongly encouraged to install a TN2602 circuit pack
to benefit from increased capacity.
TN799C V3 or greater Control-LAN (C-LAN) circuit pack.
Note:
3.
!
Important:
Important:
IP telephone firmware requires TN799C V3 or greater C-LAN circuit
pack(s). For more information, see the Communication Manager
Software and Firmware Compatibility Matrix on the Avaya support
Web site http://www.avaya.com/support.
Later versions of the Communication Manager S87XX or S85XX can use Processor
Ethernet in place of the C-LAN.
Sites with H.248 gateways will use the Processor Ethernet (procr) on the S8300 in
place of the C-LAN. The media processor resources are embedded on the gateway.
See the gateway documentation for media processor capacity.
11
Note:
Notes:
- Any or all of the server applications mentioned in items 5-8 can be co-resident on the
same hardware, subject to the specific restrictions of each individual application.
- See the Avaya one-X Deskphone Value Edition for 1603SW-I Deskphones
Administrator Guide for more information about:
administering other network equipment,
administering applications like firewalls, and
information about topics like port utilization.
14.
You have an extension number and an Avaya Communication Manager security code
(password) for each applicable IP telephone.
You have an OPTIM extension number and an Avaya Communication Manager
security code (password) for each telephone, and have configured Avaya Session
Manager or Avaya SES for each telephone.
A Category 5e LAN jack is available at each telephone site.
Electrical power is provided to each telephone by a Telephone Power Module (DC
power jack) (must be ordered separately). If the LAN will supply IEEE-standard power
to the telephone, no power module is required.
1 Category 5e modular line cord is available for the connection between the IP
telephone and the PC, if applicable.
Verify that the 1603SW-I IP Deskphone package includes the following components:
1 telephone set with stand.
1 handset capable of transmitting and receiving 7KHz audio.
1 H4DU 9-foot long (when extended) 4-conductor coiled handset cord, plugged
into the telephone and the handset.
Avaya 1600 Series IP Telephones Safety Instructions.
You will need 1 Category 5e modular line cord for the connection from the IP
telephone to the Ethernet wall jack.
15.
Note:
IP telephones ship from the factory with H.323 software. Existing installations might
also have many IP telephones running H.323 software. For instructions on how to
convert between H.323 and SIP software, see Converting Software on 1603SW-I IP
Deskphones.
Note:
The 1603SW-I IP Deskphone does not support headsets.
13
Be careful to use the correct jack when plugging in the deskphone. The jacks are
located on the back of the deskphone housing and are flanked by icons to
represent their correct use.
Note:
Note:
Note:
The last step in assembling the 1603SW-I IP Deskphones must be applying
power. Apply power either by plugging the power cord into the power source
(local powering) or plugging the modular line cord into the Ethernet wall jack
(IEEE powering). Do not use the 1151 power adapter with these telephones.
Note:
For Brazilian user when using the 5V power adapter:
For the users safety and to avoid electric shock, this equipment must be
connected to a grounded (three pin) electrical network power outlet according to
Standard NBR ABNT 5410.
Este equipamento deve ser conectado obrigatoriamente em tomada de rede de
energia eletrica que possua aterramento (tres pinos), conforme a Norma NBR
ABNT 5410, visando a seguranca dos usuarios contra choques eletricos.
! CAUTION:
CAUTION:
Failure to connect the proper cables with the proper jacks might result in an
outage in part of your network.
Figure 1 provides an illustration that shows how to connect cords to jacks on 1603SW-I IP
Deskphones. Use the illustration and the associated procedure for deskphone assembly.
Figure 1: Connection Jacks on a 1603SW/1603SW-I IP Telephone
15
1. Plug one end of the first Category 5 modular line cord into the Ethernet jack of the PC and
the other end into the secondary Ethernet jack on the 1603SW-I IP Deskphones,
if appropriate.
2. Plug one end of the second Category 5 modular line cord into the Ethernet jack on the
1603SW-I IP Deskphones. Plug the other end of this cord into the Ethernet wall jack. If the
telephone is to be IEEE-powered, you are finished. Do not proceed to Step 3.
3. If the telephone is to be powered locally, plug the power cord into the 1603SW-I IP
Deskphones and the power cord plug into the wall socket.
Note:
Important:
Before starting this process, read Converting Software on 1603SW-I IP
Deskphones on page 13 to understand the requirements for converting
factory-set H.323 telephones to SIP and make any changes necessary to suit
your particular environment. Also, ensure that both Avaya Communication
Manager (CM) and Session Manager (SM) or Avaya Midsize Business Template
and Avaya SES are properly set up for your telephone environment.
Note:
Before starting this process you must have an OPTIM extension number for the
SIP deskphone, the Avaya Aura Communication Manager security code
(password) for that extension, and a login and password on the Session Manager
or SES server.
Any reference to the HTTP server applies equally to an HTTPS server.
The following description of the process of installing the SIP deskphones assumes that the
process is executed successfully. Only an initial out of the box installation is described. For
errors that might be encountered during the process and the messages displayed, see
Chapter 5: Troubleshooting Guidelines.
When you plug the deskphone into the Ethernet wall jack and apply power, if applicable, the
following process takes place.
Note:
Note:
If the application has already been downloaded, the whole process takes
approximately 1 to 2 minutes after the telephone is plugged in. For software
upgrades, including the boot file and application file download, the process might
take 5 - 10 minutes. The duration is based on LAN loading, how many telephones
are being installed at once, and similar factors.
Do not unplug the power cord during the download process.
1. The telephone activates the Ethernet line interface, the PC Ethernet jack, and dial pad input
to allow the invocation of procedures. The activation occurs as soon as possible after
power-up or a reset.
The telephone displays the speed of the Ethernet interface in Mbps, that is,
10 or 100. The message No Ethernet displays until the software determines whether the
interface is 10 Mbps or 100 Mbps.
Note:
Note:
The Ethernet speed indicated is the LAN interface speed for both the telephone
and any attached PC, assuming the administrator has not disabled the latter
interface by a PHY2STAT setting.
2. The IP telephone sends a request to the DHCP server and invokes the DHCP process.
One of the following messages display:
DHCP: s secs
* to program
DHCP: s secs
VLAN ID = n
DHCP: s secs
where s is the number of seconds that have elapsed since DHCP was invoked. The
message on the left appears if 802.1Q tagging is off and access to local programming
procedures is not disabled or restricted. (See Chapter 3: Local Administrative Options for
specifics.) The middle message appears if 802.1Q tagging is on and access to local
programming procedures is disabled or restricted. If the left and middle messages alternate
every two seconds, 802.1Q tagging is on. When both messages alternate, access to local
programming procedures is not disabled or restricted. Finally, the message on the right
appears if 802.1Q tagging is off and access to local programming procedures is disabled or
restricted.
3. The DHCP server provides IP addresses for the following hardware:
The IP telephone
4. Using the list of gateway IP addresses provided by the DHCP server, the telephone
performs a router check and verifies that the router is on the same subnet as the IP
address. The telephone cycles through the gateway IP addresses with ARPs or pings until it
receives a response. When the router is located, the HTTP/HTTPS process starts.
5. While the IP telephone connects to the HTTP/HTTPS server, the telephone displays the
following message:
HTTP:n ipadd
where n is the number of the IP address obtained from the HTTP/HTTPS server and ipadd
is the IP address.
17
where n is the number of the IP address obtained from the HTTP server, sc is the status
code of the HTTP response and etag is the value of the ETag header.
9. While the application file is saved in flash memory, the 1603SW-I IP Deskphones display
the following message:
Saving to flash
1%, 1 secs
with the percentage of the file and the number of elapsed seconds incremented as the
application file is stored in flash memory.
10. Upon successful initialization and power-up, the 1603SW-I IP Deskphones display the
following Login prompts for an extension:
Enter Extension
EXT= #=OK
the MIB object endptVLANLIST will be set to the value of VLANLIST, and then the value
of VLANLIST will be set to null.
15. The telephone contacts PPM, logs in, and downloads the configuration file.
16. Successful completion of this process produces a dial tone when the Speaker button is
pressed or the handset is lifted.
The 1603SW-I IP Deskphone was installed successfully.
19
Introduction
After you have successfully installed a 1603-SWI SIP Deskphone, you might be instructed to
administer one of the options described in this chapter.
Note:
Note:
You can modify the settings file to set parameters for deskphones that download
their upgrade script and application files from the same HTTP server. See
Chapter 4: Maintaining 1603SW-I IP Deskphones and 1603SW-I IP Deskphone
Scripts and Application Files in Chapter 4 of the Avaya 1603-SWI SIP
Deskphones Administrator Guide.
! CAUTION:
CAUTION:
21
2. Attempts to enter invalid data are rejected, and the telephone emits an error beep.
3. If you enter a numeric digit for a value or for an IP address or subnet mask field after
entering only a zero, the new digit replaces the zero.
4. Press the # button to go to the next step.
5. To backspace, press the leftmost softkey. When you press the applicable button or key to
backspace, the most recently entered digit or period is erased from the display. The cursor
remains in the erased characters former position.
6. If PROCPSWD is administered as indicated in Chapter 7 of the Avaya one-X Deskphone
Value Edition SIP for 1603SW-I IP Deskphones Administrator Guide, you must type the
Local Procedure password after pressing Mute and before pressing the code for your
given local programming option.
Note:
Note:
If PROCSTAT has been administered to 1, you will not be able to invoke any
administrative options other than V I E W.
Note:
Note:
Unless otherwise prohibited by administration, the user can view but not change
most of the parameters associated with Local Administrative procedures. For
more information about this option, see the applicable user guides.
Code
See
8 0 2 1 X (8 0 2 1 9)
Static addressing
A D D R (2 3 3 7)
A G C (2 4 2)
C H A D D R (2 4 2 3 3 7)
C L E A R (2 5 3 2 7)
Code
See
Group Identifier
G R O U P (4 7 6 8 7)
Interface Control
I N T (4 6 8)
Event Logging
L O G (5 6 4)
Disable/Enable Event
Logging on page 37.
R E S E T (7 3 7 3 8)
R E S E T (7 3 7 3 8)
S S O N (7 7 6 6)
T E S T (8 3 7 8)
V I E W (8 4 3 9)
Note:
Note:
Unless otherwise prohibited using administration, the user can view but not
change most of the parameters associated with Local Administrative Procedures.
For more information about this option, see the applicable user guide(s).
Note:
Note:
Press the Mute button momentarily. Do not press this button while pressing other
keys/buttons.
After entry of the command sequence, the following text displays:
802.1X=setting
*=change #=OK
where the setting is the current value of the system value DOT1X (802.1X Supplicant
Mode), defined as:
23
If you want to change the DOT1X mode value, go to Change the DOT1X Mode Value on
page 24.
If you want to change the DOT1XSTAT mode value go to Change the DOT1XSTAT
Mode Value on page 25.
Disabled if setting = 0
Unicast/multicast if setting = 2
25
from working. Such errors can also have a negative impact on your network. Print copies of this
checklist for each subnet.
1.
2.
3.
4.
5.
6.
7.
! CAUTION:
CAUTION:
When you configure SIP proxy server manually, the 1603-SWI SIP Deskphone will use TLS (not
UDP or TCP) to access the server.
Use the following procedure to invoke manual address information programming.
1. Start manual address programming by performing one of the following steps:
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.nnn is the current IP address system value of the telephone.
2. Enter the telephones IP address followed by the # button.
The telephone displays:
CallSv=nnn.nnn.nnn.nnn
New=_
where nnn.nnn.nnn.nnn is the current system value of the SIP proxy IP address.
27
802.1Q=auto
*=change #=OK
If NVL2Q is 1:
802.1Q=on
*=change #=OK
If NVL2Q is 2:
802.1Q=off
*=change #=OK
7. Press * to change 802.1Q to the next sequential value. For example, if the current value is 0
(auto) pressing * changes it to 1 (on) and if the current value is 2 (off), pressing * changes it
to 0 (auto).
The display is updated to show the current status of 802.1Q.
8. Press the # button to continue the procedure without changing the displayed status of
802.1Q
The telephone displays the following text:
VLAN ID=dddd
New=_
where dddd is the current system value of the 802.1 VLAN ID.
9. Enter a valid value between 0 and 4094 for the new value of the 802.1 VLAN ID.
The telephone displays the following message:
VLAN test=ddd
New=_
where ddd is the number of seconds to wait for the DHCPOFFER on a non-zero VLAN.
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.
29
Note:
Note:
The user can potentially override the AGC local procedure settings, as described
in the telephone user guide. If overridden, the backup file stores the AGC
value(s) set by the user and ignores any setting established using this local
procedure.
1. While the telephone is on-hook and idle, press the following sequence of keys on the
faceplate of the telephone:
Mute 2 4 2 # (Mute A G C #)
Note:
Note:
Press the Mute button momentarily. Do not press this button while pressing other
keys/buttons.
2. After entry of the command sequence, one of the following displays, based on the current
value of the system value AGCHAND:
If AGCHAND = 1:
Handset AGC=on
0=off #=OK
If AGCHAND = 0:
Handset AGC=off
1=on #=OK
3. To change the AGC Handset value from On to Off, press 0. To change the AGC Handset
value from Off to On, press 1.
If the telephone has a Headset interface one of the following displays, based on the current
value of the system value AGCHEAD:
If AGCHEAD = 1:
Headset AGC=on
0=off #=OK
If AGCHEAD = 0:
Headset AGC=off
1=on #=OK
4. To change the AGC Headset value from On to Off, press 0. To change the AGC Headset
value from Off to On, press 1.
One of the following displays, based on the current value of the system value AGCSPKR:
If AGCSPKR = 1:
Speaker AGC=on
0=off #=OK
If AGCSPKR = 0:
Speaker AGC=off
1=on #=OK
5. To change the AGC Speaker value from On to Off, press 0. To change the AGC Speaker
value from Off to On, press 1.
If a value different from the current AGCHAND value and/or the current AGCHEAD value
and/or the current AGCSPKR value is entered, the following text displays left-justified at the
top of the display:
Save new value?
*=no
#=yes
6. Press the * button to terminate the procedure, or the # button to save the new value(s). If
you press the # button, the telephone displays the following text:
New value being saved
The telephone saves the new value(s).
31
Note:
Note:
Press the Mute button momentarily. Do not press this button while pressing other
keys/buttons.
The telephone displays the following text left-justified at the top of the display:
chaddr=ddd
New=
where ddd is the value of NVCHADDR, the system variable for the DHCP Client Hardware
Address.
2. To change the Client Hardware Address value, enter a valid client hardware address. This
value is usually the MAC address, which DHCP then converts to an integer preceded by
zeroes.
For all IP telephones, if a value different from the current value of NVCHADDR 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. If you
press the # button, the telephone displays the following text:
New value being saved
The telephone saves the new value.
Clear Procedure
Clear Procedure
Sometimes, you might want to remove all administered values, user-specified data, and option
settings. Essentially, you want to return a telephone to its initial clean slate or out of the box
condition. This is usually done when passing a telephone to a new, dedicated user when the
users L O G O F F option is not sufficient. For example, a new user is assigned the same
extension, but requires different permissions than the previous user.
The C L E A R option erases all administered datastatic programming, file server and call
server programming, and user settings including Contact button labels and locally programmed
Feature button labels, and restores all such data to default values. The C L E A R option does
not affect the software load itself. If you have upgraded the telephone, the telephone retains the
latest software. Once you have cleared a telephone, you can administer it normally.
! CAUTION:
CAUTION:
This procedure erases all administered data, without any possibility of recovering
the data.
Use the following procedure to clear the telephone of its administrative, user-assigned and
options values.
1. While the telephone is on-hook and idle, press the following sequence of keys on the
faceplate of the telephone:
Mute 2 5 3 2 7 # (Mute C L E A R #)
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
33
3. Press the * button to terminate the procedure without clearing the values. Press the # button
to clear all values to their initial default values.
A confirmation tone sounds and the following text displays left-justified at the top of the
display:
Clearing values.
The telephone is cleared to its out of the box state.
Group Identifier
Use the following procedure to set or change the Group Identifier.
Note:
Note:
Perform this procedure only if the LAN Administrator instructs you to do so.
For more information about groups, see The GROUP System Value on page 46.
While the telephone is on-hook and idle, press the following sequence of keys on the faceplate
of the telephone:
Mute 4 7 6 8 7 (Mute G R O U P)
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:
Group=ddd
New=_
where ddd is the Group value.
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.
Interface Control
Interface Control
Use the following procedure to set or change the interface control value.
1. While the telephone is on-hook and idle, press the following sequence of keys on the
faceplate of the telephone:
Mute 4 6 8 # (Mute I N T #)
Note:
Note:
Press the Mute button momentarily. Do not press this button while pressing other
keys/buttons.
2. After entry of the command sequence, telephones with an internal Ethernet switch display
the following text, depending on the current interface control value:
PHY1=status
*=change #=OK
where status is the value of PHY1STAT, defined as:
35
4. Press the * button to terminate the procedure, or the # button to save the new value. If you
press the # button, the following text displays:
PHY2=status
*=change #=OK
where status is the value of PHY2STAT, defined as:
Note:
Note:
Press the Mute button momentarily. Do not press this button while pressing other
keys/buttons.
2. After entry of the command sequence, the telephone displays the following text, depending
on the current value of the system parameter NVLOGSTAT:
Log=status
*=change #=OK
where status is the type of logging indicated by the NVLOGSTAT value, defined as:
37
4. Press the * button to terminate the procedure, or the # button to save the new value. If you
press the # button, the telephone displays the following text:
New value being saved
The telephone saves the new value.
Logoff
Use the following procedure to log off a telephone.
! CAUTION:
CAUTION:
Note:
Note:
Press the Mute button momentarily. Do not press this button while pressing other
keys/buttons.
2. After entry of the command sequence, the telephone unregisters from the call server. The
telephone display (and button module display, if applicable) clears, then displays the
following prompt for subsequent login:
Enter Extension
EXT= #=OK
! CAUTION:
CAUTION:
This procedure erases all static information except the extension number and
password, without any possibility of recovering the data.
1. While the telephone is on-hook and idle, press the following sequence of keys on the
faceplate of the telephone:
Mute 7 3 7 3 8 # (Mute R E S E T #)
Note:
Note:
Press the Mute button momentarily. Do not press this button while pressing other
keys/buttons.
The IP telephones display the following text left-justified at the top of the display:
Reset values?
*=no
#=yes
! CAUTION:
CAUTION:
As soon as you press the # button, all static information except the extension
number and password will be erased, without any possibility of recovering the
data.
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.
The telephone resets from the beginning of registration, which takes a few minutes.
39
4. If you do not reset the telephone, the telephone displays the following prompt:
Restart phone?
*=no
#=yes
5. Press the * key to terminate the procedure without restarting the telephone. Otherwise,
press # and perform the following Restart procedure.
Note:
Note:
Press the Mute button momentarily. Do not press this button while pressing other
keys/buttons.
The IP telephones display the following text left-justified at the top of the display:
Reset values?
*=no
#=yes
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 you press the * button to restart without resetting the values, the following prompt
displays on all IP telephones:
Restart phone?
*=no
#=yes
3. Press the * key to terminate the procedure without restarting the telephone.
Press the # key to restart the telephone.
The remainder of the procedure depends on the status of the boot and application files.
See Appendix A: Restart Scenarios.
Do not perform this procedure if you are using static addressing. Perform this
procedure only if you are using DHCP and the LAN administrator instructs you to
do this.
Use the following procedure to set the Site-Specific Option Number (SSON).
1. While the telephone is on-hook and idle, press the following sequence of keys on the
faceplate of the telephone:
Mute 7 7 6 6 # (Mute S S O N #)
Note:
Note:
Press the Mute button momentarily. Do not press this button while pressing other
keys/buttons.
The telephone displays the following text left-justified at the top of the display:
SSON=ddd
New=_
where ddd is the value of SSON.
2. Enter a valid value between 128 and 254 for the SSON.
For all IP telephones, if a value different from the current SSON 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. If you
press the # button, the telephone displays the following text:
New value
being saved
The telephone saves the new value, and restores the user interface to its previous state.
41
Self-Test Procedure
Note:
Note:
1603SW-I IP Deskphones 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.
Note:
Note:
Press the Mute button momentarily. Do not press this button while pressing other
keys/buttons.
All telephones show the following text, left-justified at the top of the display, for 1 second
after self-test is invoked:
Self test
#=end
A block character with all pixels on then displays in all display character locations for
5 seconds. Display of the block character helps to find bad display pixels.
The telephone displays one of the following:
If self-test passes:
If self-test fails:
2. To terminate the self-test, press the # button on the dial pad at any time. Doing so generates
a confirmation tone, and returns the user interface to its previous state.
Introduction
This chapter covers the maintaining the 1603SW-I IP Deskphones, for example, downloading a
new software version from the Avaya support Web site. Note that the recommended
configuration is the latest call server software and the latest IP deskphone firmware.
!
Important:
Important:
You can convert a 1603SW-I IP Deskphone from H.323 to SIP software, or from
SIP to H.323 software. Note that, depending on the telephone model and the
software version you start from, additional steps may be required from those
mentioned in this section.
An upgrade script file, 16xxupgrade.txt, which allows you to upgrade to new software
releases and new functionality without having to replace SIP IP telephones. The upgrade
script tells the telephone whether a software upgrade is needed. All Avaya IP Telephones
attempt to read this file whenever they reset. The upgrade script file is also used to point to
the settings file. An "alternate" upgrade script is also included, designed for environments
that will support both the H323 and SIP modes of operation. For such environments, the
file needs to be edited in those sections having headings of H.323 EDIT
INSTRUCTIONS. Specific instructions are provided in the Readme file that accompanies
each software bundle. Once these changes are made, the alternate file should be
renamed to 16xxupgrade.txt and placed in the HTTP download directory. The HTTP
download directory holds the telephone backup and application binaries the telephone will
download. Renaming the alternate file causes any 16xxupgrade.txt files residing in that
directory to be overwritten.
parameter settings and values that customize the telephones for your enterprise. One
settings file is used for all your Avaya IP Telephones.
43
.Binary files with the latest SIP binary code for 1603SW-I SIP IP Telephones.
All these files are in a self-extracting executable file that comes in both zipped and unzipped
format.
When the majority of your IP telephones are SIP-based, select the software bundle identified as
SIP from the Web site. The application files in this SIP software bundle are the same as in the
H.323 bundle. The difference is a modified upgrade script file that assumes SIP is the default
protocol for your 1603SW-I IP Deskphones, and that H.323 is the exception.
Download Procedure
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:
Remove all the files in the download directory. This ensures that you do not have an
inappropriate binary or configuration file on the server. The only system values that can be
used in the Conditional statement are: BOOTNAME, GROUP, and SIG.
Note:
Note:
You use one settings file for all your Avaya IP Telephones including the 1603SW-I
SIP IP Deskphones covered in this document, 1603SW-I IP Telephones (H.323
protocol, as covered in the Avaya 1600 Series IP Deskphones Administrator
Guide), and 4600 Series IP Telephones, as covered in the 4600 Series IP
Telephone LAN Administrator Guide (Document 555-233-507).
The Avaya-provided upgrade script file includes lines that tell the telephone to GET
46xxsettings.txt. These lines cause the telephone to use HTTP/HTTPS to attempt to download
the file specified in the GET command. If the file is obtained, its contents are interpreted as an
additional script file. That is how your settings are changed from the default settings. If the file
cannot be obtained, the telephone continues processing the upgrade script file. If the settings
file is successfully obtained but does not include any setting changes the telephone stops using
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.
You can change the settings file name, if desired, as long as you also edit the corresponding
GET command in the upgrade script file. However, we encourage you not to alter the
Avaya-provided upgrade script file. If Avaya changes the upgrade script file in the future, any
changes you have made will be lost. We strongly encourage you to use the 46xxsettings file to
customize your settings instead.
For detailed information about modifying the settings file, see Chapter 4 in the Avaya one-X
Deskphone Value Edition SIP for 1603SW-I IP Deskphones Administrator Guide.
See Chapter 7 in the Avaya one-X Deskphone Value Edition SIP for 1603SW-I IP
Deskphones Administrator Guide for details about specific values. You need only
specify settings that vary from defaults, although specifying defaults is harmless.
45
Introduction
This chapter describes problems that might occur during both installation and normal operation
of the 1603SW-I SIP Deskphone and possible ways of resolving these problems.
This chapter contains the following sections:
Error Conditions
There are three 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:
Check LAN connectivity in both directions to all servers - DHCP, HTTP, HTTPS, Avaya
Aura Communication Manager, and/or SIP Proxy server.
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.
Use the View command to find the names of the files being used and verify that these
filenames match those on the HTTP/HTTPS server. See The View Administrative
Option on page 48 for more information. Check the Avaya Web site to verify whether the
correct files are being used.
Use the ADDR command to verify IP addresses. See Static Addressing Installation on
page 27 for information.
3. If the 1603SW-I IP Deskphone is not communicating with the system (DHCP, HTTP, or
Avaya Aura Communication Manager call server), make a note of the last message
displayed, as described in Table 2 and/or Table 3. 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.
47
Troubleshooting Guidelines
DTMF Tones
SIP desjphones send DTMF tones according to the SEND_DTMF_TYPE parameter setting.
The default setting of this parameter sends DTMF tones as telephone event RTP packets
per RFC 2833. Whether a non-SIP telephone hears these DTMF tones depends on whether the
Avaya Communication Manager media resource converts the telephone event RTP packets
into audio RTP packets.
Power Interruption
If power to a 1603SW-I IP Deskphone is interrupted while the telephone is saving the
application file, the HTTP/HTTPS application can stop responding. If this occurs, restart the
HTTP/HTTPS server.
Note:
Note:
Note:
Unless otherwise prevented using administration, the user can view but not
change most of the parameters associated with Local Administrative Procedures.
For more information about this option, see the applicable user guide(s).
Note:
If the View Network Information option is not available due to being disabled by
administration, use the ADDR option to view IP addresses. See Static
Addressing Installation in Chapter 3: Local Administrative Options. The IP
addresses might have been entered incorrectly. Verify whether you were
provided with correct IP addresses.
1. While the deskphone 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 1. The first pair returns after the last pair displays. Values that
cannot display on one line wrap to the next line.
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:
System Value
Format
Model
16ccDccc
Phone SN
cccccccccccccccccc
PWB SN
cccccccccccccccccc
PWB comcode
nnnnnnnnn
MAC address
hh:hh:hh:hh:hh:hh
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
49
Troubleshooting Guidelines
System Value
Format
IP address
nnn.nnn.nnn.nnn
Up to 15 ASCII characters:
IPADD value.
Subnet mask
nnn.nnn.nnn.nnn
Up to 15 ASCII characters:
NETMASK value.
Router
nnn.nnn.nnn.nnn
Up to 15 ASCII characters:
the IP address of the router in use.
File server
nnn.nnn.nnn.nnn.nnnnn
Call server
nnn.nnn.nnn.nnn.nnnnn
802.1X
If DOT1X = 0
If DOT1X = 1
If DOT1X = 2
pass-thru mode.
p-t w/Logoff (pass-thru with Logoff).
Supplicant mode.
Group
nnn
Protocol:
cccccccc
filename.ext
cccccccc Ethernet
bootcodename
2 of 2
Cause/Resolution
802.1X Failure
Address
Conflict
Bad FileSv
Address
Bad Router?
Contacting call
server...
DHCP: CONFLICT
* to program
EEPROM error,
repair required
51
Troubleshooting Guidelines
Cause/Resolution
Finding
router...
Incompatible
Versions
Invalid file
IP Address
Error
License Error
Limit Error
NAPT Error
Network
connectivity
has been lost.
Trying to reestablish...
No Ethernet
Packet Error
Restarting...
Subnet conflict
Cause/Resolution
System busy
System Error
Undefined Error
Updating: DO
NOT UNPLUG THE
TELEPHONE
Wrong Set Type
CAUSE: The call server does not recognize the set type.
RESOLUTION: Ensure the call server is properly administered to
expect the appropriate telephone for the IP address and extension.
3 of 3
53
Troubleshooting Guidelines
Cause/Resolution
Cause/Resolution
AND no lights are lit
on the telephone and
the display is not lit.
AND power to the
telephone is fine, but
there is no dial tone.
The display might
show System Busy.
2 of 5
55
Troubleshooting Guidelines
Cause/Resolution
Cause/Resolution
AND the HTTP/
HTTPS server is a
LINUX or UNIX
system.
AND telephone
administration
recently changed.
57
Troubleshooting Guidelines
Cause/Resolution
Note:
Note:
The file names used in this appendix are examples only. Your particular file
names are likely to be different.
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:
Reset values?
*=no #=yes
2. Press the # button to continue the procedure.
The following text displays left-justified at the top of the display while the system values are
reset to defaults:
Resetting
values.
Once you press the * button to restart without resetting the values, the following prompt
displays:
Restart phone?
*=no #=yes
59
Restart Scenarios
3. Press the * key to terminate the procedure without restarting the telephone.
Press the # key to restart the telephone.
The remainder of the procedure depends on the status of the boot and application files:
If this condition applies:
See:
While either the application file if there is one or the boot code is uncompressed into RAM,
the telephone displays:
Loading: 5 secs
replboot_v3.app
4084KB
This message counts the seconds as the application file (replboot_v3.app in this example)
is being written into RAM.
When control is passed to the software that was just loaded, the following messages
display:
Starting...
61
Restart Scenarios
Note:
Note:
The Ethernet speed indicated is the LAN interface speed for both the telephone
and any attached PC, assuming the administrator has not disabled the latter
interface through the PHY2STAT setting.
The software determines whether sufficient IP address information was downloaded. In this
scenario, it is discovered that sufficient information has not been downloaded. The
following message displays while the DHCP process is invoked:
DHCP: 0 secs
* to program
The number of elapsed seconds is incremented once per second, until DHCP successfully
completes.
While the IP telephone establishes a TCP connection to the HTTP server, the telephone
displays the following message:
HTTP:n ipadd
where n is the number of the IP address obtained from the HTTP server and ipadd is the IP
address.
The following message displays while the HTTP process is invoked:
HTTP: n uri
The number increments once per second, until the HTTP server responds.
While the upgrade script file is being downloaded, all IP telephones display the following
message:
HTTP:n sc etag
where n is the number of the IP address obtained from the HTTP server, sc is the status
code of the HTTP response and etag is the value of the ETag header.
The script file is processed. The software determines that the telephones boot code file
name (BOOTNAME) is not the latest version. APPNAME is set to the name of an
application file to replace the boot code. The following message displays while the
application file is downloaded into RAM:
app_filename
n KB received
where n is the number of KBs downloaded.
The following message displays while the application file is stored in flash memory:
Saving to flash
n%, x secs
where n is the percentage of the file stored, and x is the number of elapsed seconds. This
usually takes longer than the file download.
The following message displays while the telephone is reset so the application file can be
executed:
Restarting...
63
Restart Scenarios
The telephone detects and displays the speed of the Ethernet interface in Mbps, that is, 0,
10, or 100. The message No Ethernet displays until the software determines whether the
interface is 10 Mbps or 100 Mbps.
Note:
Note:
The Ethernet speed indicated is the LAN interface speed for both the telephone
and any attached PC.
The software determines whether sufficient IP address information was downloaded. In this
scenario, it is discovered that sufficient information has not been downloaded. The
following message displays while the DHCP process is invoked:
DHCP: 0 secs
* to program
The number of elapsed seconds is incremented once per second, until DHCP successfully
completes.
While the IP telephone establishes a TCP connection to the HTTP server, the telephone
displays the following message:
HTTP:n ipadd
where n is the number of the IP address obtained from the HTTP server and ipadd is the IP
address.
The following message displays while the HTTP process is invoked:
HTTP: n uri
The number increments once per second, until the HTTP server responds.
While the upgrade script file is being downloaded from the HTTP server, all IP telephones
display the following message:
HTTP:n sc etag
where n is the number of the IP address obtained from the HTTP server, sc is the status
code of the HTTP response and etag is the value of the ETag header.
The script file is processed. The software determines that the name of the boot code file in
the telephone (BOOTNAME) is not the latest version. APPNAME is set to the name of an
65
Restart Scenarios
application file to replace the boot code. The following message displays while the
application file is downloaded into RAM:
app_filename
n KB received
where n is the number of KBs downloaded.
The following message displays while the application file is stored in flash memory:
Saving to flash
n%, x secs
where n is the percentage of the file that was stored, and x is the number of elapsed
seconds. This usually takes longer than the files download.
The telephone is reset so the new system-specific application file can be executed.
Continue with the next procedure.
Note:
Note:
The Ethernet speed indicated is the LAN interface speed for both the telephone
and any attached PC.
The software determines whether sufficient IP address information was downloaded. In this
scenario, it is discovered that sufficient information has not been downloaded. The
following message displays while the DHCP process is invoked:
DHCP: 0 secs
* to program
The number of elapsed seconds is incremented once per second, until DHCP successfully
completes.
While the IP telephone establishes a TCP connection to the HTTP server, the telephone
displays the following message:
HTTP:n ipadd
where n is the number of the IP address obtained from the HTTP server and ipadd is the IP
address.
The following message displays while the HTTP process is invoked:
HTTP: n uri
The number increments once per second, until the HTTP server responds.
While the upgrade script file is being downloaded from the HTTP server, all IP telephones
display the following message:
HTTP:n sc etag
where n is the number of the IP address obtained from the HTTP server, sc is the status
code of the HTTP response and etag is the value of the ETag header.
The script file is processed. The software determines that the name of the boot code file in
the telephone (BOOTNAME) is the latest version, and the name of the application file in the
telephone is the same as APPNAME.
System-specific registration with the Avaya media server is invoked.
When registration finishes, a dial tone is available on the telephone.
67
Restart Scenarios
ARP
CLAN
DHCP
DiffServ
DNS
Gatekeeper
H.323
HTTP
HTTPS
IETF
LAN
MAC
QoS
Unnamed
Registration
TLS
VLAN
VoIP
802.1Q defines a layer 2 frame structure that supports VLAN identification and a QoS
mechanism usually referred to as 802.1P.
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.
Address Resolution Protocol, used, for example, to verify that the IP address
provided by the DHCP server is not in use by another IP telephone.
Control LAN, type of Gatekeeper circuit pack.
Dynamic Host Configuration Protocol, an IETF protocol used to automate IP address
allocation and management.
Differentiated Services, an IP-based QoS mechanism.
Domain Name System, an IETF standard for ASCII strings to represent IP
addresses. The Domain Name System (DNS) is a distributed Internet directory
service. DNS is used mostly to translate between domain names and IP addresses.
Avaya 1600 Series IP Telephones can use DNS to resolve names into IP addresses.
In DHCP, TFTP, and HTTP files, DNS names can be used wherever IP addresses
were available as long as a valid DNS server is identified first.
H.323 application that performs essential control, administrative, and managerial
functions in the media server. Sometimes called CLAN in Avaya documents.
A TCP/IP-based protocol for VoIP signaling.
Hypertext Transfer Protocol, used to request and transmit pages on the World Wide
Web.
A secure version of HTTP.
Internet Engineering Task Force, the organization that produces standards for
communications on the internet.
Local Area Network.
Media Access Control, ID of an endpoint.
Quality of Service, used to refer to several mechanisms intended to improve audio
quality over packet-based networks.
Registration with Avaya Aura Communication Manager by an IP telephone with no
extension. Allows limited outgoing calling.
Transport Layer Security, an enhancement of Secure Sockets Layer (SSL). TLS is
compatible with SSL 3.0 and allows for privacy and data integrity between two
communicating applications.
Virtual LAN.
Voice over IP, a class of technology for sending audio data and signaling over LANs.
69
Glossary of Terms
IETF Documents
IETF documents provide standards relevant to IP Telephony and are available for free from the
IETF Web site: http://www.ietf.org/rfc.html.
ITU Documents
Access the ITU Web site for more information about ITU guidelines and documents, available
for a fee from the ITU Web site: http://www.itu.int.
71
Related Documentation
Index
Index
Numerical
1603SW-I SIP Deskphone
Assembling the . . . . . . . . . .
Installation . . . . . . . . . . . .
Maintenance . . . . . . . . . . .
Models . . . . . . . . . . . . . .
Powering the . . . . . . . . . . .
Restart . . . . . . . . . . . . . .
802.1X Operational Mode, Setting the .
E
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
14
. 9
43
10
14
40
23
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
30
37
21
51
47
37
F
Font Files, Downloading . . . . . . . . . . . . . . 46
from . . . . . . . . . . . . . . . . . . . . . . . . 20
A
About This Guide . . . . . . . . . . . .
ADDR Option . . . . . . . . . . . . . .
Administrative Options
Entering Data for . . . . . . . . . . .
Local. . . . . . . . . . . . . . . . .
AGC . . . . . . . . . . . . . . . . . .
ANSI/IEEE Documents . . . . . . . . . .
Assembling the 1603SW-I SIP Deskphone
Automatic Gain Control, Disable/Enable . .
. . . . . . 5
. . . . . 27
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
21
21
30
71
14
30
B
Boot File, upgrading the . . . . . . . . . . . . . . 61
button labels . . . . . . . . . . . . . . . . . . . . 20
C
Clear Procedure . . . . . . . . . . . . . . . . .
Client Hardware Address . . . . . . . . . . . . .
Contents of the Settings File . . . . . . . . . . .
Converting Software on 1603SW-I IP Deskphones .
Customer Support . . . . . . . . . . . . . . . .
.
.
.
.
.
33
32
45
13
. 7
.
.
.
.
.
.
.
.
.
32
30
37
. 6
44
45
43
48
16
D
DHCP Client Hardware Address . . .
Disable Automatic Gain Control (AGC)
Disable Event Logging . . . . . . . .
Document Organization . . . . . . .
Download Procedure . . . . . . . . .
Downloading Language Files . . . . .
Downloading Software Upgrades . . .
DTMF Tones . . . . . . . . . . . .
Dynamic Addressing Process . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
G
Glossary of Terms . . . . . . . . . . . . . . . . . 69
Group Identifier . . . . . . . . . . . . . . . . . . . 34
GROUP System Value . . . . . . . . . . . . . . . 46
I
IEC/ISO Documents . . . . . . . .
IEEE/ANSI Documents . . . . . . .
IETF Documents . . . . . . . . . .
Installation . . . . . . . . . . . . .
Intended Audience, for this document
Interface Control . . . . . . . . . .
IP Telephone Models . . . . . . . .
ISO/IEC, ANSI/IEEE Documents . .
ITU Documents. . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
71
71
71
.9
.6
35
10
71
71
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
45
21
22
37
38
M
Maintaining 1603SW-I SIP Deskphone . . . . . . . . 43
73
Index
Parameter Values . . . . . . . . . . . . . . . . 49
Power Interruption . . . . . . . . . . . . . . . . 48
VIEW Administrative Option . . . . . . . . . . . 48
O
Operational Errors and Status Messages . . . . . . 54
Other Documentation . . . . . . . . . . . . . . . . 7
P
Parameter Values . . . . . . . . . . . . . .
Power Interruption . . . . . . . . . . . . . .
Powering the 1603SW-I SIP Deskphone. . . .
Pre-Installation Checklist . . . . . . . . . . .
Pre-Installation Checklist for Static Addressing .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
49
48
14
.11
25
U
Upgrade
Application File . . . . . . . . . . . . . . . . . 64
Boot File . . . . . . . . . . . . . . . . . . . . 61
V
VIEW Administrative Option . . . . . . . . . . . . . 48
R
Related Documentation . . . . . . . . . . . . . . 71
Requirements, for each IP Telephone . . . . . . . . 12
Reset
Boot File and System-Specific Application File Already
Loaded . . . . . . . . . . . . . . . . . . . . 66
Boot File Loaded/No Application File or Application File
Needs to be Upgraded . . . . . . . . . . . . . 64
Boot File Needs to be Upgraded . . . . . . . . . 61
Reset System Values . . . . . . . . . . . . . . . 39
Restart Process, Scenarios for the . . . . . . . . . 59
Restart Scenarios . . . . . . . . . . . . . . . . . 59
Restart the Telephone . . . . . . . . . . . . . . . 59
S
Scenarios for the Restart Process . . . . .
Self-Test . . . . . . . . . . . . . . . .
Settings File, Contents . . . . . . . . . .
Site-Specific Option Number Setting . . .
Software . . . . . . . . . . . . . . . .
Software Upgrades, Downloading . . . . .
SSON Procedure . . . . . . . . . . . .
Static Addressing
Installation . . . . . . . . . . . . . .
Pre-Installation Checklist . . . . . . .
System Parameter Values, troubleshooting
System Values, Reset . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
59
42
45
41
10
43
41
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
27
25
49
39
T
Technical Support . . . . . . . . . . . . .
Terms, Glossary of . . . . . . . . . . . . .
TEST Procedure . . . . . . . . . . . . . .
Troubleshooting
DTMF Tones . . . . . . . . . . . . . .
Error Conditions . . . . . . . . . . . .
Guidelines for . . . . . . . . . . . . .
Installation Error and Status Messages . .
Operational Errors and Status Messages .
. . . . . 7
. . . . 69
. . . . 42
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
48
47
47
51
54