Avaya 4602 SIP Quick Setup Guide

4602 SIP Telephone Release 1.1 Quick Setup Gui de

This Quick Setup guide is intended for technicians installing Avaya
4602 SIP telephones.

Before performing the procedures in this guide, make sure the
following conditions exist:

● An Avaya Communication Manager (CM ) Release 2. 1.1

with field load 415 is installed and running.

● An Avaya Converged Communications Server (CCS)

Release 2.1 is installed and running.

● DNS is administered properly (if being used by the

customer).

● DHCP scope 172 has been created on the DHCP server.

Under DHCP Scope Options, set Option 172 to
ConfigHttpSrvr=a.b.c.d, where a.b.c.d is the address of
the HTTP server.

● You are familiar with administering Avaya Communication

Manager and Avaya Converged Communica tio ns Se rv er.

When setting up SIP trunks, you will need to know the following
information:

● number of off-PBX stations

● maximum number of SIP trunks

● node name of the Avaya Converged Communications

Server

● IP address of the Avaya Converged Communica tion s

Server

● TAC for the SIP trunk group

● number of members for the SIP trunk group

Release 1.0 to Release 1.1 Migration Notes

In Release 1.0 of the 4602 SIP Telephone, the extension name of
the 4602 SIP telephone had to be different from the extension
name used in Avaya Communication Manager. In Release 1.1
(which is supported by Avaya Communication Manager Release

2.1.1 and Avaya Converged Communications Server Release 2.1),
the extension name of the 4602 SIP telephone must be identical to
the extension name used in Avaya Communication Manager.

● Changes on Avaya Communication Manager

- Only OPS administered SIP endpoints are supported in
Avaya Communication Manager Release 2.1.1. “Pure
SIP” or standalone configurations are not supported.

- Hotline is not supported.

- Assign an AWOH station number for the SIP/OPS
endpoints (if not done already). (Only AWOH is supported
in Avaya Communications Manager Release 2.1.1.)

- Update the off-pbx-telephone station mapping so that the
station names of the AWOH and the 4602 SIP telephone
match.

● Changes on Avaya Converged Communications Server

- Update existing Avaya Converged Communications
Server user records to include a Media Server Extension.
The Media Server Extension should match the AWOH
station assigned in Avaya Communication Manager.

- If the user handle is an extension, it must match the
AWOH station assigned.

● Changes on the 4602 SIP Telephone

- Change the extension name so that it matches the AWOH
station name on Avaya Communication Manager.

- Remove the Hotline option and Extension in the Call
Handling page.

- Enter the registration domain name in the configuration
files so that the 4602 SIP Telephone can register with
Avaya Converged Communications Server Release 2.1.

16-300158, Issue 1.1 October 2004 1

Configure the Avaya Communication Manager.

1

1. Use the change system-parameters customer options
command to set the following parameters:

- the maximum number of off-PBX telephones - OPS (page
1 of form)

- the maximum number of SIP trunks (page 2 of form)

- Enhanced EC500 to “y” (page 4 of form)

- IP trunks to “y” (page 4 of form)

!

Important:

Important: These parameters are determined by the license

file. Only an A vaya- autho rized repr esent ati ve can
modify these parameters.

2. Use the change node-names ip command to set the
following parameters:

- host name of the Avaya Converged Communications
Server

- IP address of the Avaya Converged Communi ca tion s
Server

3. Use the change system-parameters features command to
set Trunk-to-Trunk transfer to “all.”

4. Use the change ip-network-region command to set the
home domain (domain.com) of the Avaya Converged
Communications Server on all applicable regions.

Set up a SIP trunk between the Avaya Communication Manager

2

and the Avaya Converged Communications Server.

1. Use the add signaling-group # command to add a SIP
signaling group. Set the following parameters:

- Group Type to “sip”

- Transport Method to “tls”. (This is the default setting.)

- Depending on the type of system, perform one of the
following steps:

● For an S8500 system or an S8700 system, set

Near-end Node Name to a designated CLAN.

● For an S8300 system, set Near-end Node Name to

“procr.”

- Far-end Node Name. Enter the node name of the Avaya
Converged Communications Server you entered in Step 2
of Procedure 1.

- Near-end Listen Port to “5061”. (This is the default
setting.)

- Far-end Listen Port to “5061”

- Far-end Domain Name. Enter either the local Avaya
Converged Communications Server domain name or the
far-end SIP server domain name to be reached.

- DTMF over IP to “rtp-payload”. (This is the default
setting.)

2. Use the add trunk-group # command to add a SIP trunk
group. Set the following parameters:

- Group Type to “sip”

- Group Name

- TAC. (You must enter a TAC even though the TAC is not
used for accessing a SIP trunk.)

- Service Type to “tie”

- Signaling Group to the number of the signaling group you
created in Step 1 of this procedure.

- Number of Members (up to 255). (This is the number of
concurrent users who will be using the trunk.)

- Administer fields on page 2 as appropriate for the
customer.

2 16-300158, Issue 1.1 October 2004