16-300140 6

Avaya Aura™ SIP Enablement
Services (SES) Implementation Guide
16-300140
Issue 6
May 2009
© 2010 Avaya Inc. Software that permits one user to interface with the Software. Units
All Rights Reserved. may be linked to a specific, identified Server.
• Named User License (NU):
Notice End User may: (i) install and use the Software on a single
While reasonable efforts have been made to ensure that the information in this Designated Processor or Server per authorized Named User
document is complete and accurate at the time of printing, Avaya assumes no (defined below); or (ii) install and use the Software on a Server so
liability for any errors. Avaya reserves the right to make changes and long as only authorized Named Users access and use the
corrections to the information in this document without the obligation to notify Software. “Named User” means a user or device that has been
any person or organization of such changes. expressly authorized by Avaya to access and use the Software. At
Avaya's sole discretion, a “Named User” may be, without limitation,
Documentation disclaimer designated by name, corporate function (for example, webmaster
Avaya shall not be responsible for any modifications, additions, or deletions to or helpdesk), an e-mail or voice mail account in the name of a
the original published version of this documentation unless such modifications, person or corporate function, or a directory entry in the
additions, or deletions were performed by Avaya. administrative database utilized by the Software that permits one
End User agree to indemnify and hold harmless Avaya, Avaya's agents, user to interface with the Software.
servants and employees against all claims, lawsuits, demands and judgments • Shrinkwrap License (SR):
arising out of, or in connection with, subsequent modifications, additions or Customer may install and use the Software in accordance with the
deletions to this documentation, to the extent made by End User. terms and conditions of the applicable license agreements, such as
“shrinkwrap” or “clickthrough” license accompanying or applicable
Link disclaimer to the Software (“Shrinkwrap License”). (See Third-party
Avaya is not responsible for the contents or reliability of any linked Websites Components for more information).
referenced within this site or documentation(s) provided by Avaya. Avaya is not
Copyright
responsible for the accuracy of any information, statement or content provided
on these sites and does not necessarily endorse the products, services, or Except where expressly stated otherwise, no use should be made of materials
information described or offered within them. Avaya does not guarantee that on this site, the Documentation(s) and Product(s) provided by Avaya. All
these links will work all the time and has no control over the availability of the content on this site, the documentation(s) and the product(s) provided by
linked pages. Avaya including the selection, arrangement and design of the content is owned
either by Avaya or its licensors and is protected by copyright and other
Warranty intellectual property laws including the sui generis rights relating to the
Avaya provides a limited warranty on this product. Refer to your sales protection of databases. You may not modify, copy, reproduce, republish,
agreement to establish the terms of the limited warranty. In addition, Avaya’s upload, post, transmit or distribute in any way any content, in whole or in part,
standard warranty language, as well as information regarding support for this including any code and software. Unauthorized reproduction, transmission,
product, while under warranty, is available to Avaya customers and other dissemination, storage, and or use without the express written consent of
parties through the Avaya Support Website: http://www.avaya.com/support. Avaya can be a criminal, as well as a civil, offense under the applicable law.
Please note that if you acquired the product from an authorized Avaya reseller
Third Party Components
outside of the United States and Canada, the warranty is provided to you by the
said Avaya reseller and not by Avaya. Certain software programs or portions thereof included in the Product may
contain software distributed under third party agreements (“Third Party
Licenses Components”), which may contain terms that expand or limit rights to use
The software license terms available on the Avaya Website, certain portions of the Product (“Third Party Terms”). Information regarding
http://support.avaya.com/licenseinfo/ are applicable to anyone who downloads, distributed Linux OS source code (for those Products that have distributed the
uses and/or installs Avaya software, purchased from Avaya Inc., any Avaya Linux OS source code), and identifying the copyright holders of the Third Party
affiliate, or an authorized Avaya reseller (as applicable) under a commercial Components and the Third Party Terms that apply to them is available on the
agreement with Avaya or an authorized Avaya reseller. Unless otherwise Avaya Support Website: http://support.avaya.com/Copyright.
agreed to by Avaya in writing, Avaya does not extend this license if the
Preventing toll fraud
software was obtained from anyone other than Avaya, an Avaya affiliate or an
Avaya authorized reseller, and Avaya reserves the right to take legal action “Toll fraud” is the unauthorized use of your telecommunications system by an
against you and anyone else using or selling the software without a license. By unauthorized party (for example, a person who is not a corporate employee,
installing, downloading or using the software, or authorizing others to do so, agent, subcontractor, or is not working on your company's behalf). Be aware
you, on behalf of yourself and the entity for whom you are installing, that there can be a risk of toll fraud associated with your system and that, if toll
downloading or using the software (hereinafter referred to interchangeably as fraud occurs, it can result in substantial additional charges for your
“you” and “end user”), agree to these terms and conditions and create a telecommunications services.
binding contract between you and Avaya Inc. Or the applicable Avaya affiliate
Avaya fraud intervention
(“Avaya”).
If you suspect that you are being victimized by toll fraud and you need technical
Avaya grants End User a license within the scope of the license types
assistance or support, call Technical Service Center Toll Fraud Intervention
described below. The applicable number of licenses and units of capacity for
Hotline at +1-800-643-2353 for the United States and Canada. For additional
which the license is granted will be one (1), unless a different number of
support telephone numbers, see the Avaya Support Website:
licenses or units of capacity is specified in the Documentation or other
materials available to End User. “Designated Processor” means a single http://www.support.avaya.com/.
stand-alone computing device. “Server” means a Designated Processor that Suspected security vulnerabilities with Avaya products should be reported to
hosts a software application to be accessed by multiple users. “Software” Avaya by sending mail to:securityalerts@avaya.com.
means the computer programs in object code, originally licensed by Avaya and
ultimately utilized by End User, whether as stand-alone products or Trademarks
pre-installed on Hardware. “Hardware” means the standard hardware originally Avaya® and Avaya Aura™ are trademarks of Avaya Inc.
sold by Avaya and ultimately utilized by End User. The trademarks, logos and service marks (“Marks”) displayed in this site, the
documentation(s) and product(s) provided by Avaya are the registered or
License types
unregistered Marks of Avaya, its affiliates, or other third parties. Users are not
• Designated System(s) License (DS):
permitted to use such Marks without prior written consent from Avaya or such
End User may install and use each copy of the Software on only
third party which may own the Mark. Nothing contained in this site, the
one Designated Processor, unless a different number of
documentation(s) and product(s) should be construed as granting, by
Designated Processors is indicated in the Documentation or other
implication, estoppel, or otherwise, any license or right in and to the Marks
materials available to End User. Avaya may require the Designated
without the express written permission of Avaya or the applicable third party.
Processor(s) to be identified by type, serial number, feature key,
location or other specific designation, or to be provided by End All non-Avaya trademarks are the property of their respective owners.
User to Avaya through electronic means established by Avaya
Downloading documents
specifically for this purpose.
• Concurrent User License (CU): For the most current versions of documentation, see the Avaya Support
End User may install and use the Software on multiple Designated Website: http://www.avaya.com/support.
Processors or one or more Servers, so long as only the licensed
Contact Avaya Support
number of Units are accessing and using the Software at any given
time. A “Unit” means the unit on which Avaya, at its sole discretion, Avaya provides a telephone number for you to use to report problems or to ask
bases the pricing of its licenses and can be, without limitation, an questions about your product. The support telephone number is
agent, port or user, an e-mail or voice mail account in the name of a 1-800-242-2121 in the United States. For additional support telephone
person or corporate function (e.g., webmaster or helpdesk), or a numbers, see the Avaya Website: http://www.avaya.com/support.
directory entry in the administrative database utilized by the
Contents
About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Using this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Document tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Reference points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Related sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 1: SES Solution Overview . . . . . . . . . . . . . . . . . . . . 11

Overview of Avaya SES solution components. . . . . . . . . . . . . . . . . . . . 12
Avaya SIP Enablement Services server . . . . . . . . . . . . . . . . . . . . . 12
Servers running Avaya Communication Manager 5.0 . . . . . . . . . . . . . . 13
Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Avaya one-X™ Deskphone supporting SIP for 9600 Series phones . . . . . . 14
Avaya 4600 Series IP Telephones supporting SIP. . . . . . . . . . . . . . . . 15
Avaya softphones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Third-party SIP clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Security in general. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Security and SES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 2: Setting up the Communication Manager server . . . . . . . 21

Setting up the Avaya server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Setting up SIP support in Avaya Communication Manager . . . . . . . . . . 22
Setting up Click to Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Setting up Advanced SIP Telephony . . . . . . . . . . . . . . . . . . . . . . . . . 25
Setting up Modular Messaging as an adjunct system . . . . . . . . . . . . . . . 26
Chapter 3: Setting up the server(s) running SES . . . . . . . . . . . . . 27

Configuring the server running SES . . . . . . . . . . . . . . . . . . . . . . . . . 27
Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Task list for configuring server(s) for SES . . . . . . . . . . . . . . . . . . . . 28
Creating SIP users in the SES system . . . . . . . . . . . . . . . . . . . . . . . . 29
Setting up OPS stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Outboard Proxy SIP (OPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Issue 6 May 2009 3

Contents
Chapter 4: Establishing SIP trunks in Communication Manager. . . . . 31

Advanced SIP trunk administration . . . . . . . . . . . . . . . . . . . . . . . . . 31
Other scenarios for using an SES system . . . . . . . . . . . . . . . . . . . . . . 32
Chapter 5: Setting up a SIP Endpoint . . . . . . . . . . . . . . . . . . . 33

Compatibility Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Avaya one-X™ Deskphone SIP for 9600 series telephones. . . . . . . . . . . . . 34
Setting parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Avaya 4602/4602SW, 4610SW and 4620SW/4621SW SIP telephones . . . . . . . 36
Setting parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Setting up Avaya softphone clients . . . . . . . . . . . . . . . . . . . . . . . . . 38
Chapter 6: Upgrading SIP Enablement Services . . . . . . . . . . . . . 39

Connecting to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Accessing the System Management Interface . . . . . . . . . . . . . . . . . . 40
Copying files to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Backing up recovery system files . . . . . . . . . . . . . . . . . . . . . . . . 41
Verifying the backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Disabling the boot timeout of the SAMP board . . . . . . . . . . . . . . . . . 42
Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Inserting the SES CD into the server . . . . . . . . . . . . . . . . . . . . . . . 43
Upgrading SES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Installing a new release of SES from the local hard drive . . . . . . . . . . . 44
Rebooting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Verifying reboot progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Checking system status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Making the upgrade permanent on the server . . . . . . . . . . . . . . . . . 48
Installing security and SES service packs, if any . . . . . . . . . . . . . . . . 48
Installing the authentication file . . . . . . . . . . . . . . . . . . . . . . . . . 49
Upgrading a Cable Duplicated Server Pair . . . . . . . . . . . . . . . . . . . . 49
Upgrading a Network Duplicated Server Pair . . . . . . . . . . . . . . . . . . 50
4 SES Implementation Guide

Contents
Appendix A: Reference Points . . . . . . . . . . . . . . . . . . . . . . . 51
Appendix B: Troubleshooting the SES solution. . . . . . . . . . . . . . 53
Appendix C: Worksheet for installation . . . . . . . . . . . . . . . . . . 55
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Issue 6 May 2009 5

Contents

About this document
Overview
This Avaya Aura™ SIP Enablement Services (SES) Implementation Guide provides references
to the documentation needed to deploy the Avaya SES solution with Avaya SIP IP telephony
products.
This document is a road map.
Intended audience
This document is for field technicians, services technicians, and installers who are deploying the
Avaya SES solution over an IP telephony network.
Using this document

Use this document as a reference point for deploying the Avaya SES solution. The document is
high-level, task-oriented and guides you through the documentation that contains installation,
administration, and deployment instructions for all of the components of the Avaya SES
solution.
Document tables
At the beginning of each chapter, related documents are listed in a table as follows:
Table 1: Related documents
Document Title Document ID
4600 Series IP Telephone LAN Administrator Guide 555-233-507

4610SW SIP Telephone User's Guide 16-300472
4610SW SIP Telephone Quick Reference 16-300473
Issue 6 May 2009 7

About this document
Reference points
A key component of this documentation is the reference point. The reference point refers to the
document that has the information that is needed to complete the task at hand.
Reference point—Setting up SES server(s)

● For detailed instructions on the initial setup of Avaya SIP Enablement Services on a
standalone S8500-series server, refer to this document:
Installing, Administering, Maintaining, and Troubleshooting Avaya Aura™ SIP Enablement
Services, 03-600768, Chapter 3: "Setup and configuration"—"Configuring a new server".
The sample reference point above refers to the Avaya document, the relevant chapter within the
document, and the section heading within the chapter to complete the task.
Related sources
The following documents are referenced within this document:
● Avaya application notes
● Administering Network Connectivity on Avaya Aura™ Communication Manager,
555-233-504
● Administering Avaya Aura™ SIP Enablement Services on the Avaya S8300 Server,
03-602508
● Installing, Administering, Maintaining, and Troubleshooting Avaya Aura™ SIP Enablement
Services, 03-600768
● Avaya Toll Fraud and Security Handbook, 555-025-600
● Security and the Avaya S8700 Media Servers, Avaya white paper, Resource Library
● Avaya one-X™ Deskphone Edition for 9600 Series SIP IP Telephones Installation and
Maintenance Guide, 16-601943
● Avaya one-X™ Deskphone Edition for 9600 Series SIP IP Telephones Administrator
Guide, 16-601944
● Avaya one-X™ Deskphone SIP for 9620 IP Telephone User Guide, 16-601945
● Avaya one-X™ Deskphone SIP for 9630/9630G IP Telephone User Guide, 16-601946
● Avaya one-X™ Deskphone SIP for 9640/9640G IP Telephone User Guide, 16-602403
● Avaya one-X™ Deskphone SIP for 9620 IP Telephone Quick Reference, 16-601947

Conventions used in this document
● Avaya one-X™ Deskphone SIP for 9630/9630G IP Telephone Quick Reference,

16-601948
● Avaya one-X™ Deskphone SIP for 9640/9640G IP Telephone Quick Reference,
16-602408
● Avaya one-X™ Desktop Edition Quick Setup Guide
● Avaya one-X™ Desktop Edition Getting Started
● SIP Support in Avaya Aura™ Communication Manager, 555-245-206
● Getting Started with Avaya Call Center and Avaya Agent Deskphone 16CC, 129214
● Avaya Agent Deskphone 16CC Quick Reference, 16-602097
● Avaya Agent Deskphone 16CC Administrator Guide, 16-602093
● Avaya Agent Deskphone 16CC Installation and Maintenance Guide, 16-602095
● Avaya Agent Deskphone 16CC User Guide, 16-602096
● Avaya 4600 Series IP Telephone LAN Administrator Guide, 555-233-507
● Avaya 4600 Series IP Telephone Installation Guide, 555-233-128
● Avaya 4602/4602SW SIP Telephone User’s Guide, 16-300035
● Avaya 4602/4602SW SIP Telephone Quick Reference, 16-300471
● Avaya 4610SW SIP IP Telephone User’s Guide, 16-300472
● Avaya 4610SW SIP IP Telephone Quick Reference, 16-300473
● Avaya 4620SW/4621SW SIP IP Telephone User’s Guide, 16-300474
● Avaya 4620SW/4621SW SIP IP Telephone Quick Reference, 16-300475
● Avaya Extension to Cellular User’s Guide, 210-100-700
● Avaya Extension to Cellular and Off-PBX Station (OPS) Installation and Administration
Guide, 210-100-500
● Avaya Server Availability Management Processor User Guide (SAMP), 03-300322
Conventions used in this document

Become familiar with the following terms and conventions.
● Media server—In the SES solution, Avaya media servers may be S8300, S8400, S8500
series, or S8710 series. When this document refers to a media server, it means a
Linux-based media server running Avaya Communication Manager R3.1 or later.
Issue 6 May 2009 9

About this document
● Commands are printed in bold face as follows: command.

We show complete commands in this book, but you can usually type an abbreviated version
of the command. For example, list configuration station can be typed as list
config sta.
● Screen displays and names of fields are printed in constant width as follows: screen
display.
A screen is any form displayed on your computer or terminal monitor.
● Variables are printed in constant width, bold, italic: variable.
● Keys and buttons are printed as follows: KEY.
To move to a certain field, you can use the TAB key, arrows, or the ENTER key (the ENTER
key may appear as the RETURN key on your keyboard).
● In this book we use the terms “telephone” and “voice terminal” to refer to phones.
● Reference point—Defined
The reference point refers to any related documentation that details the tasks at hand.
● Tips look like this:
Tip:
Tip: Draws attention to information that you may find helpful.
● Notes look like this:
Note:
Note: A general note calls attention to neutral information or positive information that
supplements the main text.
● Cautions look like this:
! CAUTION:
CAUTION: Denotes possible harm to software, possible loss of data, or possible service
interruptions.

Chapter 1: SES Solution Overview
This chapter provides an overview of the process and components needed to deploy an Avaya
IP convergence solution using Session Initiation Protocol (SIP) as its enabling technology.
SIP is a text-based protocol that is designed to set up, modify, and tear down communication
sessions between users. Once sessions are established, the content of these sessions can be
voice, video, instant messaging, or any other communications method.
SIP, an Internet-centric protocol that provides basic functionality beyond that of H.323, was
originally designed to place the intelligence in the endpoints rather than within the network.
Practical necessity requires that some intelligence be in the network. SIP architecture promises
increased resiliency, scalability, and rapid application development.
Presently, Avaya’s SIP Enablement Services (SES) solution offers these advantages:
● The ability to make and receive SIP telephone calls
● Many advanced features and services
● Secure instant messaging
● To subscribe to and receive presence notifications.
This document outlines how to deploy an SES solution.
Reference point—System architecture, server requirements, and local failover

● Installing, Administering, Maintaining, and Troubleshooting SIP Enablement Services,
03-600768, Chapter 3: "Introduction", provides details of the SES solution architecture and
topography, server hardware and software requirements, and local failover design.
The tasks required to deploy this solution are described in this document, in these sections:
1. Set up the server(s) running Avaya Communication Manager.
See Chapter 2: Setting up the Communication Manager server on page 21.
2. Install and configure Avaya SIP Enablement Services on the SES server(s).
See Chapter 3: Setting up the server(s) running SES on page 27.
3. Integrate Communication Manager, SIP Enablement Services, and the 4600/9600 series
SIP IP telephones via Extension to Cellular and Off-PBX Station (OPS) mapping.
See Setting up OPS stations on page 30.
4. Establish SIP Trunks on the server running Communication Manager.
See Chapter 4: Establishing SIP trunks in Communication Manager on page 31.
5. Configure supported SIP IP telephones for use with the SES solution.
See Chapter 5: Setting up a SIP Endpoint on page 33.
Issue 6 May 2009 11

SES Solution Overview
Reference point—Co-resident system architecture and server requirements

● Administering SIP Enablement Services on the Avaya S8300 Server, 03-602508, provides
details of the SES solution architecture and topography, server hardware and software
requirements, and local failover design.
Overview of Avaya SES solution components

The Avaya SIP Enablement Services (SES) solution consists of the following components:
● Avaya SIP Enablement Services server or servers
● One (or more) Servers running Avaya Communication Manager 5.0
● Gateways
● SIP endpoints:
- Avaya one-X™ Deskphone supporting SIP for 9600 Series phones
- Avaya 4600 Series IP Telephones supporting SIP
- Avaya softphones, including one-X™ Desktop Edition
● Third-party SIP clients
Avaya SIP Enablement Services server

The SES application runs standalone on Avaya’s S8500-series hardware platform. This
platform supports Edge, Home, and combination Home/Edge servers. The SES application also
supports the Avaya S8300C Server, running co-resident with Avaya Communication Manager
5.0 or later releases. In this configuration, only Home and Home/Edge SES server types are
supported.
The SES edge server is dedicated to performing proxy, registration, and redirection functions
associated with SIP applications, such as instant messaging. When the SES home server
communicates with one or more servers running Communication Manager, communication
between and among the various non-SIP endpoints is supported. Endpoints supported by
Communication Manager include analog, DCP or H.323 stations and analog, digital or IP
trunks, as well as SIP-enabled endpoints. SIP-enabled endpoints may be any from this list:
● Avaya 9600 Series one-X™ Deskphone, Avaya 4600 Series SIP IP telephones or Avaya
Agent Deskphone 16CC
● Avaya one-X™ Desktop Edition Release 2 or later (or Avaya SIP Softphone)
● Avaya IP Softphone Release 5.1 and later with the IM client

SIP-enabled endpoints must register with the SES server. Although technically an Avaya IP
Softphone is not managed by Communication Manager, it is required to register H.323 with the
server running Avaya Communication Manager. Although IP softphones use H.323 for voice,
SIP is also used for communications. For example, instant messages on IP softphones use SIP.
Reference point—System requirements, installation and administration for

standalone SES servers
The document Installing, Administering, Maintaining, and Troubleshooting SIP Enablement
Services, 03-600768, provides detailed system requirements, installation instructions, and
administrative tasks for S8500 series servers running SES. See the respective chapters.
● System requirements - Chapter 3: "Introduction to SIP and SIP Enablement Services"
● Installation - Chapter 4: "Setup and configuration"
Chapter 5: "Getting ready to install SES"
One or more of chapters 7-21, depending on your hardware configuration
● Administration - Chapter 4: "Setup and configuration"—"Installation checklist"
Chapter 4: "Setup and configuration"—"Post installation tasks"
● Administration in general - Chapter 22: "Administration web interface"
Servers running Avaya Communication Manager 5.0

Avaya’s SES solution can be deployed with Communication Manager running on Avaya S8300,
S8400, S8500-series, and the S8700-series servers. These hardware elements deliver
application-enabling data, voice, fax, video and messaging capabilities to your network. They
support both bearer and signaling traffic routed between packet-switched and circuit-switched
networks. The gateways are optimized for use with enterprise class telephony and provide a
variety of flexible deployment options. Options include both partial environments, such as IP
and TDM, and fully IP environments.
Features for SIP in Avaya Communication Manager 5.0 running on an Avaya media server
include these:
● SIP trunking
● SIP stations
● Call Detail Record (CDR) support
● Access control
● Routing and dial plan
Issue 6 May 2009 13

Gateways
The Avaya SIP Enablement Services solution can be deployed with any of the Avaya gateways
supporting S8xxx.
Avaya one-X™ Deskphone supporting SIP for 9600 Series phones

Verify that you have up-to-date firmware for your supported SIP endpoints by going to this web
site:
http://www.avaya.com/support/
Then select the link for Downloads under Most Visited Support Areas. See the latest 9600
Series one-X™ Deskphone SIP telephone documentation for more details.
Key benefits of an Avaya 9600 Series one-X™ Deskphone SIP telephone

● The 9600 Series SIP telephone is a fully featured SIP device also utilizing the features of
Communication Manager through SIP Enablement Services.
● This telephone employs standards-based SIP telephony call control, allowing integration
into multi-vendor telephony environments using SIP.
● The simple H.323 to SIP firmware upgrade provides a migration path to SIP that
maximizes investment protection.
Note:
Note: The 9600 Series SIP telephone incorporates a SIP stack. The telephone
registers with a server running SIP Enablement Services (SES) software and
communicates through the server with Communication Manager for call control.
See Other scenarios for using an SES system on page 32 for more information on multi-vendor
SIP telephony deployments.
Converting Avaya 9600 Series telephones to one-X™ Deskphone SIP

SIP can be deployed on the Avaya 9620, 9630/9630G, 9640/9640G telephones. Avaya ships
these phones from the factory and they contain the latest load of H.323 software. To use an
H.323 phone with SES, you must convert the H.323 phone to a SIP phone.
Reference Point—Enhancing 9600 Series H.323 IP telephones to SIP telephones

● For detailed instructions on enhancing the software on the Avaya 9600 Series IP
telephones to one-X™ Deskphone SIP, refer to the document Avaya one-X™ Deskphone
Edition for 9600 Series SIP IP Telephones R2.x Installation and Maintenance Guide,
16-601943, Chapter 2: "9600 Series SIP IP Telephone Installation"—"Converting Software

on 9600 Series IP Telephones".

For more information about administering and installing the phones, see the next
Reference point.
Reference point—System requirements, installation and administration for 9600

Series SIP IP telephones
● The Avaya one-X™ Deskphone Edition for 9600 Series SIP IP Telephones R2.x
Administrator Guide, 16-601944 provides detailed tasks associated with administering the
9600 Series SIP IP telephone for use.
● A separate Avaya one-X™ Deskphone for 9600 Series SIP IP Telephone Quick Reference
for each of the 9620, 9630/9630G, and 9640/9640G IP Telephones provides installation
instructions and initial configuration tasks.
● A separate Avaya one-X™ Deskphone SIP for 9600 Series SIP IP Telephones R2.x User
Guide for each of the 9620, 9630/9630G, and 9640/9640G IP Telephones provides
detailed tasks associated with using the phone.
Avaya 4600 Series IP Telephones supporting SIP

Verify that you have up-to-date firmware for your supported SIP endpoints by going to this web
site:
http://www.avaya.com/support/
Then select the link for Downloads under Most Visited Support Areas. For the 4602, you may
need to migrate your H.323 firmware from 1.8.x to 2.2 before converting the phone to
SIP firmware. See the latest 4600 Series IP telephone documentation for more details.
Key benefits of an Avaya 4600 Series SIP telephone

● The 4600 Series SIP telephone is economical and can utilize the features of
Communication Manager through SIP Enablement Services.
● This telephone employs standards-based SIP telephony call control and so allows
integration into multi-vendor telephony environments using SIP.
● The simple H.323-to-SIP firmware upgrade provides a migration path to SIP that
maximizes investment protection.
Note:
Note: The 4600 Series SIP telephone incorporates a SIP stack. The telephone
registers with a server running SIP Enablement Services (SES) software and
communicates through the server with Communication Manager for call control.
See Other scenarios for using an SES system on page 32 for more information on multi-vendor
SIP telephony deployments.
Issue 6 May 2009 15

Avaya 4602/4602SW, 4610SW or 4620SW/4621SW telephones

SIP can be deployed on the Avaya 4602/4602SW, 4610SW or 4620SW/4621SW telephones.
Avaya ships these phones from the factory and they contain the latest load of H.323 software.
To use an H.323 phone with SES, the administrator must convert the H.323 phone to a
SIP phone.

● For detailed instructions on enhancing the software on the Avaya 4600 Series SIP IP
telephones, refer to the document 4600 Series IP Telephone R2.2 Installation Guide,
555-233-128, Chapter 2: "4600 Series IP Telephone Installation"—"Converting Software
on Avaya 4600 Series IP Telephones".
Reference point—System requirements, installation and administration for 4602

SIP telephones
● The Avaya 4602/4602SW SIP Telephone User’s Guide, 16-300035 provides detailed
tasks associated with using the 4602 or 4602SW SIP telephone.
● The Avaya 4602/4602SW SIP Telephone Quick Reference, 16-300471 provides
installation instructions and initial configuration tasks for the 4602/4602SW SIP telephone.

4610SW SIP telephones
● The Avaya 4610SW SIP IP Telephone User’s Guide, 16-300472 provides detailed tasks
associated with using the 4610SW SIP Telephone.
● The Avaya 4610SW SIP IP Telephone Quick Reference, 16-300473 provides installation
instructions and initial configuration tasks for the 4610SW SIP.

4620SW/4621SW SIP telephones
● The Avaya 4620SW/4621SW SIP IP Telephone User’s Guide, 16-300474 provides
detailed tasks associated with using the 4620SW or 4621SW SIP telephone.
● The Avaya 4620SW/4621SW SIP IP Telephone Quick Reference, 16-300475 provides
installation and initial configuration tasks for the 4620SW or 4621SW SIP telephone.

Avaya softphones
Avaya IP Agent R6.x and IP Softphone R5.x with IM client

SIP can be deployed with either the Avaya IP or SIP softphone clients. To deploy the SES
solution, you must add the IM client module software to the IP softphone or the IP Agent
software. The SIP softphone client software is SIP-enabled with IM capability.
Reference Point—Enhancing H.323 IP softphones to IM-enabled softphones

For detailed instructions on enabling the Avaya IP Softphone client software to include the
SIP-enabled instant messaging with presence application, refer to IP softphone online help:
http://www.support.avaya.com > IP Agent > Avaya IP Agent Installation and User Guide
http://support.avaya.com/japple/css/
japple?temp.documentID=280964&temp.productID=107698&temp.releaseID=235038&temp.b
ucketID=160259&PAGE=Document
Avaya one-X™ Desktop Edition and SIP Softphone R2.x

SIP can be deployed with either the Avaya IP Softphone 5.x or one-X™ Desktop Edition
SIP softphone 2.x clients. To deploy the one-X™ Desktop Edition SIP Softphone solution, the
client software must be installed on the SIP user’s PC by an administrator of that PC.
The deskphone must have the current version of SIP firmware for the Avaya telephone.
Reference Point—Installing and configuring the Avaya SIP Softphone

For detailed instructions on installing the Avaya one-X™ Desktop Edition SIP Softphone client
software, refer to the SIP softphone application’s online help:
http://www.support.avaya.com > SIP Softphone > Avaya SIP Softphone Administration
japple?PAGE=Document&temp.productID=252060&temp.bucketID=159898&temp.documentI
D=252143&temp.selectedRelease=252204
Issue 6 May 2009 17

Third-party SIP clients

The Toshiba SIP Business Phone, model SP-1020A, is fully supported within the Avaya SES
solution. See the documentation for your TSP phone for more information.
Avaya supports and troubleshoots other third-party SIP clients that have been chosen and
completed testing by Avaya’s Solution and Interoperability Test Lab (SITL), and is documented
in Application Notes. However, Avaya does not provide installation, implementation,
configuration, or maintenance of any third-party SIP endpoints.
The SIP-enabled products of third parties must be submitted through Avaya’s DevConnect to be
tested and ultimately designated as supported applications/devices.
For detailed information about the Avaya DeveloperConnection Program, go to the web site:
http://www.avaya.com/gcm/master-usa/en-us/corporate/alliances/devconnect/index.htm
For application notes on which third-party SIP endpoints are supported, go to the web site:
http://www.avaya.com and select Do Your Research: Resource Library in the middle of the
page.
Then select Application Notes under Resource Type. You may filter your results by the term
SIP, or by the specific product name or model of your third-party software or equipment.

Security
Security
Because SES is an Avaya product, and because it operates in conjunction with Avaya
Communication Manager, SES is designed and implemented with security as a prime
consideration.
Security in general
Avaya provides two documents about security that directly affect SES.
Table 2: Documents that relate to security
Avaya Toll Fraud and Security Handbook 555-025-600
Security and the Avaya Communication Manager Media Technical Support

Servers white paper for Avaya
Communication
Manager software
Security and SES

These points are part of the SES security strategy and design:
● SES administration is done securely over HTTPS, a secure extension to HTTP that
encrypts all messages between the web server and a browser. Unique server certificates
can be generated and installed on the SES server.
● The SES firewall is configurable to permit only the necessary network services and
applications.
● SES runs an intrusion detection system to prevent unauthorized modification of files.
Passwords are stored securely.
● SES supports SSH for secure remote login. User logins are denied after successive failed
logins. In addition, ASG is used for secure technician login.
● SNMPv3 trap destinations can be configured for secure SNMP.
● SIP signaling can be protected using TLS, depending on endpoint support for TLS. SIP
signaling to and from Communication Manager is protected using TLS.
● Telephony end users are authenticated using SIP digest authentication.
Issue 6 May 2009 19


Chapter 2: Setting up the Communication Manager
server
When setting up one or more server(s) running Communication Manager to accommodate and
support the Avaya SES solution, you will need to have these references available:
Table 3: Documents required for setting up Communication Manager servers
Administering Network Connectivity on Avaya Aura™ 555-233-504

Communication Manager
Getting Started with Avaya Aura™ SIP Softphone, Available from

Administration and Provisioning your Avaya
representative
Installing, Administering, Maintaining, and Troubleshooting 03-600768
Avaya Aura™ SIP Enablement Services
Administering Avaya Aura™ SIP Enablement Services on the 03-602508
Avaya S8300 Server
SIP Support in Avaya Aura™ Communication Manager 555-245-206
Avaya Communication Manager runs on the following servers:

● Avaya S8300 Server, with or without Avaya SES running co-resident with it
● Avaya S8400 Server
● Avaya S8500-series Servers
● Avaya S8700-series Servers.
Note:
Note: Prior to enabling SIP/SES on the server(s) running Communication Manager, IP
connectivity must be configured correctly. For details, refer to Administering
Network Connectivity on Avaya Aura™ Communication Manager.
Issue 6 May 2009 21

Setting up the Communication Manager server
Setting up the Avaya server

As noted above, prior to setting up an Avaya server for SIP, you must configure IP connectivity
correctly. After IP connectivity has been configured, complete the following tasks:
● Setting up SIP support in Avaya Communication Manager on page 22
● Setting up the server(s) running SES on page 27
● If applicable for your SIP clients, Setting up Click to Conference on page 25
● If applicable for your SIP endpoints, Setting up Advanced SIP Telephony on page 25
● And, if applicable, Setting up Modular Messaging as an adjunct system on page 26.
Reference point—List of related documents

● For information on correctly configuring IP connectivity on your server, refer to
Administering Network Connectivity on Avaya Aura™ Communication Manager. Many
sections in this document discuss this topic.
● For information on setting up standalone Avaya SES server(s), refer to Installing,
Administering, Maintaining, and Troubleshooting Avaya Aura™ SIP Enablement Services
:
● Chapter 4: "Setup and configuration"—"Pre installation checklist", and "Post installation
tasks"
● One or more of chapters 7-22: "Installation procedures"—"Administer Communication
Manager and endpoints"
● For information on setting up co-resident Avaya S8300C server(s) for SES, refer to
Administering Avaya Aura™ SIP Enablement Services on the Avaya S8300 Server .
● For information on setting up Avaya Communication Manager, refer to SIP Support in
Avaya Aura™ Communication Manager, Chapter 2: "Administering SIP in Avaya
Communication Manager".
Setting up SIP support in Avaya Communication Manager

Avaya’s SES solution can be deployed with the S8300, S8400, S8500-series, and the
S8700-series servers running Communication Manager. These hardware elements deliver
application-enabling data, voice, fax, video and messaging capabilities to your network. They
support both bearer and signaling traffic routed between packet-switched and circuit-switched
networks. The gateways are optimized for use with enterprise class telephony and to provide a
variety of flexible deployment options. Options include partial environments, such as both IP
and TDM, as well as full IP environments with H.323 and SIP endpoints.
With Avaya Communication Manager, SIP features include these:

Setting up the Avaya server
● SIP trunking
● SIP stations
● Call Detail Recording (CDR)
● Profile-based access control
● Call routing
● Enterprise dial plan.
SIP trunking
Support for SIP trunks allows an enterprise to connect its Avaya Communication Manager
servers to a SIP-enabled proxy server running Avaya SIP Enablement Services (SES), and
through that proxy to an external SIP service provider, if desired. The trunk support in Avaya
Communication Manager complies with SIP standards IETF RFC 3261 and interoperates with
any SIP-enabled endpoint that also complies with the standard.
In complex configurations with Avaya S8700-series servers, SIP signaling-group properties in
Communication Manager must be administered to match each other in certain, specific ways.
SIP stations
Support for SIP stations using SIP trunks allows any fully compliant SIP phone to interoperate
with Avaya phones. This means any SIP phone, from Avaya or a third party, that complies with
the appropriate RFC or draft service standards can do the following:
● Dial and be dialed as an extension in the enterprise dial plan. Outboard Proxy SIP (OPS)
stations support additional features as well, like bridging.
● Put calls on hold and participate in transfers and conference calls.
Reference point—OPS
● For more details on OPS installation, refer to these documents:
- Avaya Extension to Cellular User’s Guide, 210-100-700
- Avaya Extension to Cellular and OPS Installation and Administration Guide, 210-100-500
Reference point—Modular Messaging

● For using Modular Messaging as an adjunct system to SES, see the applicable SES
installation and administration guide: Installing, Administering, Maintaining, and
Troubleshooting Avaya Aura™ SIP Enablement Services , Chapter 22: "Administration
Web Interface"—"Adjunct Systems", or see the document Administering Avaya Aura™
SIP Enablement Services on the Avaya S8300 Server .
Issue 6 May 2009 23

Access control
Support is provided for the full control of access to external trunks from any phone. Note that
some other means of access control, such as a network firewall, typically would be required to
control access to SIP trunks from SIP endpoints that are outside of the enterprise.

Setting up Click to Conference
Reference point—Setting up Communication Manager servers

All necessary information for setting up the servers with Avaya Communication Manager is
detailed in SIP Support in Avaya Aura™ Communication Manager. Specific topics in this
document are as follows:
● For hardware and software requirements, refer to Chapter 2: "Administering SIP in Avaya
Communication Manager"—"Requirements for SIP".
● For setting up and configuring SIP trunks in Communication Manager, refer to Chapter 3:
"Administering Communication Manager for SIP Enablement Services".
Routing and Dial Plan

The final step before you make SIP calls from endpoints connected to Communication Manager
is to administer call routing properly on the Avaya Communication Manager servers. This
involves several screens, including for example the Locations, Numbering, and Route
Pattern screens.
Reference point—Administering SIP call routing in Communication Manager

Information for administering call routing on the servers with Communication Manager is
detailed in SIP Support in Avaya Aura™ Communication Manager. Refer to Chapter 3:
"Administering Communication Manager for SIP Enablement Services".
Setting up Click to Conference

For information on how to administer the click-to-conference feature of SES, obtain this Avaya
document:
Getting Started with Avaya SIP Softphone, Administration And Provisioning, available from your
Avaya representative.
Setting up Advanced SIP Telephony

For application notes on how to set up SES for use with Advanced SIP Telephony, go to Avaya’s
web site:
page.
Then select the link for Application Notes under Resource Type. Filter the results for AST, or
the specific product supporting advanced SIP telephony in which you are interested.
Issue 6 May 2009 25

Setting up Modular Messaging as an adjunct system

For administration guidance on how to implement Avaya’s Modular Messaging product as an
adjunct system in an SES solution, refer to the following resources:
Installing, Administering, Maintaining, and Troubleshooting Avaya Aura™ SIP Enablement
Services , Chapter 22: "Administration Web Interface"—"Adjunct Systems".
Configuration Note 88010—This note will be published on the Avaya support web site. Search
the Configuration Notes Master Index, or for PSN #1186U on SIP and MM Adjunct integration.

Chapter 3: Setting up the server(s) running SES
When working with the server(s) with SES installed, you might use these references:
Table 4: Documents required for setting up an Avaya SES server

Administering Avaya Aura™ SIP Enablement Services on the 03-602508
Avaya S8300 Server
Avaya Extension to Cellular and OPS Installation and 210-100-500
Administration Guide
Configuring the server running SES

All servers running SIP Enablement Services, that is, the SIP proxy servers, must be properly
connected to, and configured on, an enterprise’s IP network. Appendix C: Worksheet for
installation on page 55 provides a complete list of the information you need to answer questions
when prompted by the install script.
Note for SES X.0 to SES X.1 upgrades: - If you are upgrading from SES R3.0 to SES R3.1,
or R4.0 to 4.0.1, use the three Server Upgrade screens in the maintenance interface of SES.
These screens may not be used to upgrade and migrate directly from SES R3.x to R5.0 or later.
Trunking
For endpoint clients on Avaya Communication Manager to interoperate through the Avaya SES
server, SIP trunking must be administered properly on the server running the Communication
Manager software. Refer to SIP Support in Avaya Communication Manager, 555-245-206,
Chapter 3: "Administering Communication Manager for SIP Enablement Services" for more
details. This administration requires that you specify several values, including:
● Network names of the SES hosts on the IP Node Names screen
● Authoritative domain assigned to server(s) on the IP Network Region screen.
Additional administration of call routing may be required, depending on current server values.
Issue 6 May 2009 27

Setting up the server(s) running SES
Note:
Note: For 4600 Series and 9600 Series SIP IP Telephones, the same authoritative
domain must be specified in the phone’s settings file(s) as on the IP Network
Region screen. Also, unlike the H.323 versions of these IP telephones, the
SIP versions must have working IP network access to their respective TFTP or
HTTP servers upon startup. SES access is required for phone registration.
Task list for configuring server(s) for SES

Table 5 lists the tasks necessary to configure a standalone server for SES. For greater detail
about each task, refer to the documents that correspond with each task listed in the table.
Note:
Note: For greater detail about the tasks necessary to configure a co-resident server
running Communication Manager to run SES as well, refer to Administering
Avaya Aura™ SIP Enablement Services on the Avaya S8300 Server .
Table 5: Configuration task list for standalone server(s) running SES
Task Reference document

✔
Perform initial assembly and Installing, Administering, Maintaining, and

setup. Troubleshooting Avaya Aura™ SIP
Enablement Services
● Chapter 4: "Setup and
configuration"—"Configuring a new
server"
Configuration"—"Pre-installation tasks"
Install all server software. Installing, Administering, Maintaining, and
Troubleshooting Avaya Aura™ SIP
Enablement Services
● Chapters 7-21: "Installation Procedures"
Perform administrative tasks Installing, Administering, Maintaining, and

on the server by way of a Troubleshooting Avaya Aura™ SIP
Point to Point Protocol (PPP) Enablement Services
session. ● Chapter 4: "Setup and
configuration"—"Installation checklist"
configuration"—"Post installation
checklist"
1 of 2

Creating SIP users in the SES system
Table 5: Configuration task list for standalone server(s) running SES (continued)
Task Reference document

✔
Install the server license by Installing, Administering, Maintaining, and

way of WebLM. Troubleshooting Avaya Aura™ SIP
Enablement Services
Chapters 7-21: "Installation
Procedures"—"Server license installation"
Deliver the authentication file Installing, Administering, Maintaining, and
by way of the Automatic Troubleshooting Avaya Aura™ SIP
Registration Tool (ART). Enablement Services
Chapter 4: "Setup and Configuration"—"Load
the authentication file"
2 of 2
Creating SIP users in the SES system

To create users in the SES system, you must access the web-based user interface and perform
the necessary tasks in the following reference point.
Reference point—Creating users via the user screens in SES

● For creating a new SIP user in your SES solution, refer to Installing, Administering,
Maintaining, and Troubleshooting Avaya Aura™ SIP Enablement Services
● For server administration of users, refer to Installing, Administering, Maintaining, and
Troubleshooting Avaya Aura™ SIP Enablement Services
● For loading users in bulk with ProVision, refer to Installing, Administering, Maintaining, and
Troubleshooting Avaya Aura™ SIP Enablement Services
Also refer to ProVision’s help subsystem and also to the Notepad newsletter, available from the
ProVision web site’s Document Center. Log in to ProVision at this web site:
http://www.avaya.com/support/iProVision/
Issue 6 May 2009 29

Setting up the server(s) running SES
Setting up OPS stations

Table 6: Documents required for setting up Extension to Cellular and OPS
Avaya Extension to Cellular and OPS Installation and 210-100-500

Administration Guide
Outboard Proxy SIP (OPS)

Beginning with Avaya Communication Manager Release 2.1, the Outboard Proxy SIP (OPS)
application type is used to administer a SIP phone. OPS cannot be disabled using the
Extension to Cellular enable/disable feature button.
Note:
Note: Any SIP phone or endpoint must have access to and register with the SIP proxy,
regardless of whether OPS is administered in Communication Manager.
The Extension to Cellular/OPS application allows for many of the parameters used for the
original Extension to Cellular application to be ported onto one of several DCP and IP station
types. From a call processing perspective, Extension to Cellular/OPS is in fact dealing with a
multi-function phone, whereas the previous Extension to Cellular implementation utilized one or
two XMOBILE stations that behaved like analog station types.
Extension to Cellular/OPS supports these features:
● Support for Session Initiation Protocol (SIP) phones
● Administrative ability to map certain Communication Manager features to phone
extensions
Reference Point—Configuring Extension to Cellular and OPS for SIP

● Configuring Extension to Cellular and OPS for SIP is detailed in the Avaya Extension to
Cellular and Off-PBX Station (OPS) Installation and Administration Guide, 210-100-500.

Chapter 4: Establishing SIP trunks in
Communication Manager
When you set up the SIP trunks on the server running Communication Manager, use these
references to help you:
Table 7: Documents required for establishing SIP trunks in Communication

Manager
SIP Support in Avaya Aura™ Communication Manager 555-245-206

Session Initiated Protocol (SIP) is an endpoint-oriented messaging standard defined by the

Internet Engineering Task Force (IETF). SIP trunking enables the Avaya servers running
Communication Manager to function as a POTS gateway and to support the delivery of name
and number data between legacy endpoints (for example, DCP telephones) and SIP-enabled
endpoints (for example, the new 9600 series IP telephones with one-X™ Deskphone SIP).
For more information on SIP administration and usage, see the overview and introduction
chapters of the documents listed in the preceding table.
Advanced SIP trunk administration

Avaya Communication Manager provides the capability to administer IP trunks as either H.323
or SIP. These trunks are administered as a trunk type and associated with the appropriate type
of signaling group on the server running Communication Manager. Then, the server(s) running
SES enable(s) these SIP trunks to be connected to SIP endpoints.
Issue 6 May 2009 31

Establishing SIP trunks in Communication Manager
Reference Point—SIP Trunk Administration

● To administer SIP trunks in Avaya Communication Manager, see SIP Support in Avaya
Aura™ Communication Manager, Chapter 3: "Administering Communication Manager for
SIP"—"Administer SIP signaling and trunks". Capacities are as follows:
Table 8: SIP Trunk capacity
Server Maximum Administered

SIP Trunks
S8700 series 7000

S8500 series 800
S8400 400
S8300 450
Note:
Note: There is a maximum of 255 SIP trunks in a SIP signaling group.
Other scenarios for using an SES system

There are other scenarios in which SIP trunking can link an enterprise’s Avaya IP telephony
network with a third-party SIP service provider’s network. The service provider may employ
different proxy servers, PSTN gateways and other equipment as part of these scenarios.
Avaya’s Solution and Interoperability Test Lab (SITL) tests other scenarios, and then documents
them in Application Notes. However, Avaya does not provide installation, implementation,
configuration, or maintenance of any third-party SIP IP equipment.
The SIP-enabled products of third parties must be submitted through the Avaya DevConnect
program in order to be tested and ultimately designated as supported applications or devices.
For detailed information about the Avaya DeveloperConnection Program, go to the web site:
http://www.avaya.com/gcm/naster-usa/en-us/corporate/alliances/devconnect/index.htm
For application notes on which third-party SIP endpoints are supported, go to the web site:
page.
Then select the link for Application Notes under Resource Type. You may filter results using
SIP or the specific product name or model of third-party equipment in which you are interested.

Chapter 5: Setting up a SIP Endpoint
When you configure the endpoints for your SES system, use document tables Table 11 and
Table 12 in this section to guide you.
Compatibility Matrix
The following table summarizes the minimum version of SIP-enabled firmware required for each
of the supported Avaya telephones to operate properly with SES Release 5.0 software.
Table 9: Firmware versions required for using Avaya 9600 Series and 4600 Series
SIP IP Telephones
Telephone Min. SIP Version
9620 IP telephone, one-X™ Deskphone SIP Release 2.0.x

9630/9630G IP telephone, one-X™ Deskphone SIP Release 2.0.x
9640/9640G IP telephone, one-X™ Deskphone SIP Release 2.0.x
4602 IP telephone SIP not supported
4602/4602SW SIP IP telephone Release 2.2
4610SW SIP IP telephone Release 2.2
4620SW/4621SW SIP IP telephone Release 2.2
Confer with your Avaya representative and check the software downloads section of the Avaya
Support web site to see if compatible versions other than the ones listed here are released.
Issue 6 May 2009 33

Setting up a SIP Endpoint
Avaya one-X™ Deskphone SIP for 9600 series telephones

Table 10: Documents required for setting up the Avaya 9600 Series SIP Telephones
Avaya one-X™ Deskphone Edition for 9600 Series SIP IP 16-601944

Telephones R2.x Administrator Guide
Avaya one-X™ Deskphone Edition for 9600 Series SIP IP 16-601943
Telephones R2.x Installation and Maintenance Guide
Avaya one-X™ Deskphone SIP for 9620 IP Telephone Quick 16-601947
Reference
Avaya one-X™ Deskphone SIP for 9620 IP Telephone User 16-601945
Guide
Avaya one-X™ Deskphone SIP for 9630/9630G IP Telephone 16-601948
Quick Reference
User Guide
Quick Reference
User Guide
The 9600 Series SIP IP telephones cannot boot and then register with the SES server and in
the appropriate SIP domain unless they have network access to the TFTP or HTTP server.
If an SES solution includes 9600 Series IP telephones, the IP phones must be converted from
H.323 protocol to SIP. Then, their station records/extensions must be administered both in
Avaya Communication Manager and as SIP users (with the associated server extension) in
SES software. Finally, after parameters for the phones have been set properly, SIP calls may be
placed from the phones.

● For detailed instructions on enhancing the software on the Avaya 9600 Series IP
telephones to one-X™ Deskphone SIP, refer to the document Avaya one-X™ Deskphone
Edition for 9600 Series SIP IP Telephones R2.x Installation and Maintenance Guide,
16-601943, Chapter 2: "9600 Series SIP IP Telephone Installation"—"Converting Software
on 9600 Series IP Telephones".

Avaya one-X™ Deskphone SIP for 9600 series telephones
Setting parameters
The 9600 Series SIP telephone has these basic tools and capabilities to assist administrators
with managing its settings and features:
● The 96XXsettings.txt (or 46XXsettings.txt) file, annotated with information for
setting most parameters
● DHCP for setting some parameters
● Downloadable configuration files for setting telephone parameters on startup
● Manual programming of critical parameters from the telephone’s dial pad
● Downloadable firmware updates (manual and automatic)
You can set a common set of parameters using DHCP, manual programming, and configuration
files. Setting these parameters establishes the telephone’s operating parameters.
Avaya SIP telephones will not be able to register in an SES system unless they can obtain the
correct SIPDOMAIN setting. Avaya SIP telephones include the 4600-series, the 9600-series,
and the 16CC. The 46XX phones obtain the domain setting from the 46XXsettings.txt file; you
may set up a separate 96XXsettings.txt file for the 96XX phones, but the SIPDOMAIN setting
must be the same for your enterprise.
Always configure the SIPDOMAIN setting for the phones in the appropriate text file(s) and then
ensure that the phones transfer settings from the file(s) via TFTP or HTTP during boot up.
The line in the file(s) for this setting is:
SET SIPDOMAIN = yourSIPdomainName.com
For application notes on configuring specific SIP endpoints, go to the web site:
page.
Then select the link for Application Notes under Resource Type. You may filter the results
using the term SIP or the specific model number of your Avaya telephone.
Issue 6 May 2009 35

Avaya 4602/4602SW, 4610SW and 4620SW/4621SW

SIP telephones
Table 11: Documents required for setting up the Avaya 4600 Series SIP Telephones
4600 Series IP Telephone LAN Administrator Guide 555-233-507

4600 Series IP Telephone Installation Guide 555-233-128
4602/4602SW SIP Telephone Quick Reference 16-300471
4602/4602SW SIP Telephone User’s Guide 16-300035
4610SW SIP IP Telephone Quick Reference 16-300473
4610SW SIP IP Telephone User Guide 16-300472
4620SW/4621SW SIP IP Telephone Quick Reference 16-300475
4620SW/4621SW SIP IP Telephone User Guide 16-300474
The 4600 Series SIP IP telephones cannot boot and then register with the SES server and in
the appropriate SIP domain unless they have network access to the TFTP or HTTP server.
If an SES solution includes 4600 Series IP telephones, the IP phones must be converted from
H.323 protocol to SIP. Then their station records must be administered as OPS in
Communication Manager and as SIP users with a server extension in SES software. Finally,
after parameters for the phones have been set properly, SIP calls may be placed from the
phones.

● For detailed instructions on enabling the software on the 4600 Series IP Telephones, refer
to 4600 Series IP Telephone Installation Guide, 555-233-128, Chapter 2: "4600 Series IP
Telephone Installation,"—"Converting Software on Avaya 4600 Series IP Telephones".

Avaya 4602/4602SW, 4610SW and 4620SW/4621SW SIP telephones
Setting parameters
The 4600 Series SIP telephone has these basic tools and capabilities to assist administrators
with managing its settings and features:
● The 46XXsettings.txt file, annotated with information for setting most parameters
● DHCP for setting some parameters
● Downloadable configuration files for setting telephone parameters on startup
● Manual programming of critical parameters from the telephone’s dial pad
● Downloadable firmware updates (manual and automatic)
You can set a common set of parameters using DHCP, manual programming, and configuration
files. Setting these parameters establishes the telephone’s operating parameters.
For application notes on configuring SIP endpoints, go to the web site:
page.
Then select the link for Application Notes under Resource Type. You may filter the results
using the term SIP or the specific model number of your Avaya telephone.
Issue 6 May 2009 37

Setting up Avaya softphone clients

Table 12: Documents required for setting up the Avaya softphones
one-X™ Desktop Edition R2.x Quick Setup Guide www.support.avaya.com

SIP Support area
one-X ™Desktop Edition R2.x Getting Started www.support.avaya.com
SIP Support area
Avaya IP Agent R6.x/IP Softphone R5.x (or later) online help
with IM client
Avaya SIP Softphone Release 2 online help
If an SES solution includes Avaya IP Softphone clients, the version of IP Agent or IP Softphone
including the SIP-enabled instant messaging and presence module must be used. Note that
these clients manage presence information in a peer-to-peer fashion.
You must uninstall SIP softphone clients before installing one-X™ Desktop Edition Release 2.
Reference Point—Enhancing H.323 IP softphones to IM-enabled softphones

For detailed instructions on how to include and enable the SIP-based instant messaging (with
presence) application in Avaya softphone client software, refer to IP softphone online help.
http://www.avaya.com/support > IP Agent > Avaya IP Agent Installation and User Guide
japple?temp.documentID=280964&temp.productID=107698&temp.releaseID=
235038&temp.bucketID=160259&PAGE=Document
If an SES solution includes Avaya one-X™ Desktop Edition or SIP softphone clients, then the
software must be installed and configured to use. Note that these clients manage their presence
information by means of the SIP Personal Information Manager running on an SES server.
Reference Point—Installing and configuring the Avaya one-X™ Desktop Edition

For detailed instructions on installing one-X™ Desktop Edition or uninstalling the Avaya
SIP softphone client software, refer to SIP softphone online help, or one of these locations:
http://www.avaya.com/support/ > Find Documentation > Avaya one-X™ Desktop Edition
http://www.avaya.com/support > SIP Softphone > Avaya SIP Softphone Administration
japple?PAGE=Document&temp.productID=252060&temp.bucketID=159898&temp.document
ID=252143&temp.selectedRelease=252204

Chapter 6: Upgrading SIP Enablement Services
The procedure for upgrades use the Manage Software link on the System Management
Interface (SMI).
! Important:
Important: Cable Duplicated Avaya Aura™ SIP Enablement Services server pairs, deployed
on SIP Enablement Services Releases 5.1.x and earlier, require an upgrade to
the Distributed Replicated Block Device (DRBD) when upgrading to Avaya
Aura™ SIP Enablement Services Release 5.2. The Distributed Replicated Block
Device (DRBD) is automatically upgraded during the upgrade to SIP Enablement
Services Release 5.2. The procedure for upgrading a cable duplicated pair of
servers in SIP Enablement Services Release 5.2 has changed from previous
releases. Please follow the instruction in the Upgrading a Cable Duplicated
Server Pair on page 49 section for the correct steps.
! Important:
Important: S8500A servers cannot upgrade to SES 5.x or later releases. You must migrate
from the S8500A Server to an S8500B or S8500C Server to run SES 5.x.
If you are an existing customer with S8500-based deployments of SIP

Enablement Services 3.1.1 or later, you can directly upgrade to release 5.2. But if
your software release is earlier than 3.1.1, you must upgrade to minimum release
3.1.1, before upgrading to SIP Enablement Services 5.2. You can download the
SES 3.1.1 software from the Avaya SAFE download site.
For more information on the latest upgrade procedures, see Installing, Administering,
Maintaining, and Troubleshooting Avaya Aura™ SIP Enablement Services document
(03-600768, Issue 7.0).
Connecting to the server

Perform one of the following options:
● If you are on site, connect to the services port.
● If you are off site, use the IP address of the server to log on to the server.
Issue 6 May 2009 39

Upgrading SIP Enablement Services
Accessing the System Management Interface

To access the server:
1. Start the Web browser.
2. In the Address field, type 192.11.13.6 and press Enter to open the login Web page.
3. Log in as craft
4. Click yes to suppress alarms
The system displays the System Management Interface Web page.
5. Click the Manage Software link under the Upgrade menu to go to Manage Software web
page.
To upgrade remotely:
1. Start the Web browser.
2. In the Address field, type the hostname or IP Address of the target SES server.
3. Select the required option in the Manage Software web page in the System Management
Interface and load the software.
4. Follow the steps as required.
Copying files to the server

To copy files to the server:
Copy the following files, as appropriate, from the computer to the server:
● License file and Avaya Authentication file
● Postupgrade service pack files, if required
● Security update files (used post-upgrade, if required)

To copy files to the server:
1. On the Server (Maintenance), under Miscellaneous, click Download Files.
2. Select File(s) to download from the machine used to connect to the server.
Note:
Note: Do not select the check box, “Install this file on the local server.”
3. Click Browse next to the top field to open the Choose File window on your computer. Find
the files that you need to copy to the server.
4. Click Download to copy the files to the server.
The system copies the files automatically to the default file location.
5. Repeat steps 1 through 4 for each server that will be upgraded.
Resolving alarms
To clear alarms:
1. On the Server (Maintenance) Web interface, under Alarms, click Current Alarms to
examine the alarm log.
2. Select the server alarms that you want to clear and click Clear, or click Clear All.
Backing up recovery system files

To back up the system configuration files:
1. Under Data Backup/Restore, click Backup Now.
2. Select the SES files. Do not select Full Backup because this option does not save data
files.
Note:
Note: If you back up to a flashcard, Avaya recommends that you use a different
flashcard from the one with the prior release data files. You might need these
data files if you need to back out of the upgrade procedure.
3. Select the backup method.
4. Click Start Backup to start the back up process.
Issue 6 May 2009 41

Verifying the backup

To verify that the backup was successful:
1. Under Data Backup/Restore, click Backup History.
2. Select the backup that you want to verify, and click Check Status.
The system displays the status of the backup.
3. Verify that Backup Successful appears for each data set in the backup.
Suppressing alarming
! CAUTION:
CAUTION: Ensure that you suppress alarming during the upgrade. If you do not do so, the
system can generate alarms, resulting in unnecessary trouble tickets.
To suppress alarming:
1. Access the command line interface of the server with telnet or an SSH client like PuTTY and
an IP address of 192.11.13.6.
2. Log in as craft.
3. Type almsuppress -t time, where time is the length of time that the alarms are
suppressed up to 120 minutes (2 hours). Press Enter to suppress both dial-out and SNMP
alarms.
The system displays the following message:
Alarm is suppressed. 120 minutes left.

4. Log off and close the dialog box.
Disabling the boot timeout of the SAMP board

Note:
Note: You can also disable the boot timeout of the SAMP board by connecting to the
SAMP services port and using the SAMP’s Web pages. For more information,
see "Disabling the boot timeout on Release 3.1 using the SAMP Web page" in
the Using the Avaya Server Availability Management Processor (SAMP),
03-300322.

Upgrade tasks
To disable the boot timeout of the SAMP:

1. At the command line on the S8500 Server, enter sampcmd.
The Welcome banner appears, followed by the SAMP command line.
2. At the SAMP command line, enter serverctrl boot timer disable.
The system responds with OK.
3. At the SAMP command line, enter serverctrl.
The system responds with the following output:
Power On
Server Operational
Reset Deasserted
Boot Time Disabled
4. Enter Exit to return to the server command line.

When you have completed the upgrade and the server reboots, the SAMP boot timeout is
automatically enabled again.
Upgrade tasks
Inserting the SES CD into the server

Insert the CD that contains SES into the CD-ROM drive on the server. Close the tray.
Note:
Note: You can copy SES software from an http or tftp server onto the server. In this
case, skip this step.
Upgrading SES
To start the upgrade:
1. Under Upgrade, select Manage Software.
! Important:
Important: If three releases already reside on the hard disk, you must delete one release to
make room for the new release.
Issue 6 May 2009 43

2. Perform one of the following tasks:

● If three releases already reside on the hard disk
1. Select Delete one of the above releases from the local hard drive. Click Continue to
view the releases available.
2. Select the software release that you want to delete and click Delete.
When complete, the system displays the following message:
Deletion Complete
3. Click Continue to return to the initial Manage Software page.
● If less than 3 releases reside on the hard disk
1. Select one of the following:
● Copy a release to the local hard drive, but do not install it
● Copy from TFTP server at this IP address
● Copy from URL
and click Continue to view the options for copying the software to the hard drive.
2. Select Copy from this server’s CD-ROM drive: and click Continue.
The Choose Software page appears, which you use to copy files from the source you
selected.
3. Select the release to be copied and click Continue.
The system displays the Copy in Progress page.
4. View the progress screen as the software is copied to the hard drive.
When complete, the system displays the following message:
Success
5. Click Continue to return to the initial Manage Software page.
Installing a new release of SES from the local hard drive

If you selected Install one of the following releases currently resident on the local hard
drive in the previous step, then follow these steps:
1. Select the software release you want, and click Continue.
2. If you have copied the license and authentication files to the server, select the following
options:
- If a super-user login already existed prior to the upgrade, select:
● I will supply the license files myself when prompted later in this process.
● Update authentication information as well as license information.
- If a super-user login did not exist prior to the upgrade, select:

Upgrade tasks
● I will supply the license files myself when prompted later in this process.
● Do not update authentication information.
3. Click Continue.
4. For a new installation, or if you previously ran a backup, you do not need to run a backup at
this time.
5. Click Continue.
The system displays the Review Notices page.
6. Click Continue.
The system displays the Begin Installation page. The page summarizes the request you
have made.
7. Click Continue.
The installation takes approximately 10 to 20 minutes.
The system refreshes the Install in Progress window every 10 seconds or when you click
Refresh. When complete, the system displays the Reboot Server page.
Rebooting the server

To reboot the server.
Note:
Note: When you reboot the server, it can no longer communicate with the Web
interface. The Reboot in Progress Web page displays during the reboot.
Although the Continue button is visible, do not click Continue yet.
1. Click Reboot.
The system displays the Reboot in Progress window. The tray of the CD-ROM drive opens
automatically.
2. Remove the CD-ROM from the CD-ROM drive.
! CAUTION:
CAUTION: If you do not remove the CD-ROM and the tray of the CD-ROM drive closes
again, the system might try to reboot from the software on the CD-ROM.
Note:
Note: The reboot takes approximately 3 minutes. The system does not automatically
report when the reboot is complete.
3. Wait for 3 minutes and then click Continue.
If you click Continue before the reboot is finished, the browser displays Expired Page. If
you see the Expired Page message, refresh the browser. If the system displays Page
cannot be displayed, use the browser Back button to return to the Reboot in progress
Issue 6 May 2009 45

screen. If the Session Timeout screen appears, close the screen, logoff, and log on again.
Select Manage Software, select the option Join this upgrade session in progress and
monitor its activity. Click Pickup.
! CAUTION:
CAUTION: Do not click Cancel after this point. Be patient. If the installation fails, a message
displays on the Reboot in Progress window.
Note:
Note: This Web session will be interrupted by the reboot which occurs during the
upgrade of the server. After the reboot, you can continue to use the Manage
Software window without logging in.
4. When the reboot is complete, click Continue.
The system displays the Update Tripwire Database Web page. If your planning documents
instruct you to enable Tripwire, follow the instructions to reset the signature database.
If your planning documents instruct you to enable Tripwire, follow the instructions to reset
the signature database.
You can also Verifying reboot progress at this stage.
5. Click Continue.
The system displays the Install License Files Web page.
6. Click Continue.
The system installs the license file and authentication file if you selected this action in step 5
on Rebooting the server.
The system displays the Installation Complete screen.
7. Click Close.
The Manage Software window closes and returns you to the main menu.
Note:
Note: This Web session will be interrupted by the reboot that occurs during the server
upgrade. After the reboot, the links in the main menu of the Web interface will not
function. Therefore, you must close and reopen the Web browser to continue with
the upgrade procedure.
8. Close the Web browser.
9. Reopen the Web browser and log in.
10. Use the Status Summary web page to monitor the progress and wait until initial replication
is completed before proceeding to the next home server.
If the server is part of a duplicated pair, you cannot start the upgrade of the backup server in
the duplicated pair until the Status Summary web page indicates that the initial replication
is completed.

Upgrade tasks
Note:
Note: You do not have to perform these activities if you are upgrading from release 5.0
to release 5.2. However, it is recommended that you check the status before
proceeding to upgrade the next server (if applicable).
Verifying reboot progress

To check the reboot process.
1. Click Start > Run to open the Run dialog box.
2. Type command and press Enter to open an MS-DOS window.
3. Type arp -d 192.11.13.6 and press Enter to clear the ARP cache in the laptop. This
command responds with one of the following responses:
● The command line prompt when the cache is cleared.
● The following message is when the specified IP address does not currently contain an
entry in the ARP cache:
The specified entry was not found.

4. Type ping -t 192.11.13.6 to access the server. The -t causes the ping to repeat until
you get a response. When you get a response, in about 3 minutes, wait an additional 30
seconds before you go back to the Web interface.
5. Type ctrl c to stop the ping.
6. Close the MS-DOS window.
Verifying software operation

To verify the software version.
1. Under Server, click Software Version.
2. Verify the details in the Software Version web page to ensure that the new software is
present.
Checking system status

To check the system status:
1. Under Server, click Status Summary to verify that the server mode is active.
Issue 6 May 2009 47

2. Click Process Status.

3. Select Summary and Display once. Click View to access the View Process Status Results
screen.
4. Verify that all the processes are UP.
Making the upgrade permanent on the server

! CAUTION:
CAUTION: You must make the upgrade permanent. Otherwise, the next time when you
reboot the server, the server might run the previous version of the software. You
might lose any new translations you might have made, and you must install the
new software again. If you do not make the upgrade permanent within 2 hours of
the upgrade, an alarm is raised.
To make the upgrade permanent.
1. Under Server Upgrades, click Make Upgrade Permanent.
2. Click Submit to make the partition with the new software version the permanent partition.
3. Under Server Upgrades, click Boot Partition to confirm that the new software release is
selected for the boot partition and the active partition.
Installing security and SES service packs, if any

1. Under Server Upgrades, select Manage Updates.
2. If an update file you want to activate shows packed in the Status column, select update ID
and click Unpack.
3. The window shows the status of the update.
4. Wait until the system displays the message Finished unpacking...and click Continue.
5. The system displays the Manage Updates screen.
6. If the update ID you want to activate shows unpacked in the Status column, select the
update ID and click Activate.
7. The window shows the status of activating the update. If a reboot is required, the system
automatically reboots.
8. Click Yes.
Wait until the system displays the Continue button.
9. Click Continue.

Upgrade tasks
Installing the authentication file

To install the authentication file on the server:
1. Under Security, click License File.
2. Select Install the license I previously downloaded and click Submit to install the license
file.
3. Under Security, click Authentication File.
4. Click Install the Authentication file I previously downloaded and click Install.
Upgrading a Cable Duplicated Server Pair

A redundant pair consists of a primary server and a backup server. In the following steps, it is
assumed that Server A is the primary server and Server B is the backup server.
1. Busy-out Server B, so that it is out of service.
2. Wait for one minute and then Busy-out Server A.
3. Upgrade both Server A and Server B in the redundant pair using the software upgrade
process. Start by upgrading Server B first, and then upgrade Server A.
4. Reboot each server when the system displays the reboot instruction.
5. After completing the upgrades, make sure to perform the Make Upgrade Permanent step
on both the servers.
6. (Optional) Apply service packs to both servers, if applicable.
7. Release Server A, so that it is back in service.
8. As a result, Server B can reboot. If Server B reboots, wait for the rebooting to be complete
before continuing.
9. Wait for 5 minutes and then Release Server B.
Note:
Note: Avaya recommends the wait time, as there could be a full replication of the
database partition from Server A to Server B in progress in the background. You
cannot place Server B into service until the replication is completed.
10. Confirm that both servers are in-service and that Server A is the primary server and Server
B is the backup server, using the Server Status web page.
11. If Server A is either a home server or a combined home/edge server, then make a test call
to verify that Server A is working properly. If Server A is an edge server, access master
admin to verify operation.
Issue 6 May 2009 49

Note:
Note: When upgrading a cable duplicated server pair to Release 5.2, there will be a
downtime in the availability of the system, as both servers will be out of service
simultaneously.
Upgrading a Network Duplicated Server Pair

A redundant pair consists of a primary server and a backup server. In the following steps, it is
assumed that Server A is the primary server and Server B is the backup server.
1. Busy-out Server B, so it is out of service.
2. Upgrade Server B using the software upgrade process.
3. Reboot the server when the system displays the reboot instruction.
4. After completing the upgrades, make sure to perform the Make Upgrade Permanent step.
5. (Optional) Apply service packs to Server B, if applicable.
6. Release Server B, so it is back in service.
7. Confirm that Server B is in-service and that it is the backup server, using the Server Status
web page.
8. Perform an interchange between the servers.
9. Confirm that both servers are in-service and that Server A is the backup server and Server
B is the primary server, using the Server Status web page.
10. Repeat steps 1 to 7 for Server A.

Appendix A: Reference Points
This appendix lists all of the reference points contained within this document. This appendix can
serve as a quick reference for those who need to refer quickly to a document for a specific task.
About this document
● Reference point—Setting up SES server(s) on page 8
● Reference point—Defined on page 10
Chapter 1: SES Solution Overview
● Reference point—System architecture, server requirements, and local failover on page 11
● Reference point—Co-resident system architecture and server requirements on page 12
● Reference point—System requirements, installation and administration for standalone
SES servers on page 13
● Reference Point—Enhancing 9600 Series H.323 IP telephones to SIP telephones on
page 14
● Reference point—System requirements, installation and administration for 9600 Series
SIP IP telephones on page 15
page 16
● Reference point—System requirements, installation and administration for 4602
SIP telephones on page 16
● Reference point—System requirements, installation and administration for 4610SW
SIP telephones on page 16
● Reference point—System requirements, installation and administration for 4620SW/
4621SW SIP telephones on page 16
● Reference Point—Enhancing H.323 IP softphones to IM-enabled softphones on page 17
● Reference Point—Installing and configuring the Avaya SIP Softphone on page 17
Chapter 2: Setting up the Communication Manager server
● Reference point—List of related documents on page 22
● Reference point—OPS on page 23
● Reference point—Modular Messaging on page 23
● Reference point—Setting up Communication Manager servers on page 25
● Reference point—Administering SIP call routing in Communication Manager on page 25
Chapter 3: Setting up the server(s) running SES
● Reference point—Creating users via the user screens in SES on page 29
Issue 6 May 2009 51

Reference Points
● Reference Point—Configuring Extension to Cellular and OPS for SIP on page 30

Chapter 4: Establishing SIP trunks in Communication Manager
● Reference Point—SIP Trunk Administration on page 32
Chapter 5: Setting up a SIP Endpoint
page 34
page 36
● Reference Point—Enhancing H.323 IP softphones to IM-enabled softphones on page 38
● Reference Point—Installing and configuring the Avaya one-X™ Desktop Edition on
page 38

Appendix B: Troubleshooting the SES solution
This Appendix lists common problems or symptoms and some suggested solutions to them.
Problem/Symptom Suggested Solution
Phantom calls If there is an active, ringing call to a SIP

softphone, and there is a network outage, a
phantom call to that extension occurs after
network connectivity is restored. That is, when
the network comes back up, the phone will ring
and no one will be there. The customer
receiving the call should simply hang up.
The server does not respond after a laptop Use a serially connected keyboard and monitor
is connected to the services port. to disable console redirection in the server
BIOS, save, reboot and begin again.
The server cannot find files needed to boot. Ensure that the boot order specified in the
server BIOS indicates CD as first before
attempting to boot from the Avaya CD.
An S8500 server keeps rebooting before the Disable the loader watchdog timer and begin
Installer script completes. installation again. (The default timer interval of 5
minutes for the RSA loader watchdog is
insufficient to allow for complete installation.)
Link bounces, CRC errors, collisions, and Verify the network interface cards (NICs) in all
other aberrations Avaya servers (SES, servers, etc.) and in
enterprise LAN/WAN data equipment have
been set to the 100Mbps full-duplex mode.
DNS errors occur and SIP calls cannot be Do not use capital letters, spaces, underscores,
made or received within the enterprise or special characters (a hyphen is OK) in the
domain. names of domains.
External SIP calls via third-party servers are Refer to instructions in SES 5.x Release Notes
automatically dropped after a period of time. for using the trustedhost command.
Server authentication errors occur. Refer to Installing, Administering, Maintaining,
and Troubleshooting Avaya Aura™ SIP
Enablement Services, 03-600768, Chapter 3:
"Setup and Configuration"—"Load the
authentication file".
1 of 2
Issue 6 May 2009 53

Troubleshooting the SES solution
Problem/Symptom Suggested Solution
Server licensing errors occur. Refer to the Installing, Administering,

Maintaining, and Troubleshooting Avaya Aura™
SIP Enablement Services, 03-600768, Chapter
4: "Installation Procedures"—"Server license
installation".
Alerts and events occur. Refer to the Installing, Administering,
Maintaining, and Troubleshooting Avaya Aura™
SIP Enablement Services, 03-600768,
Appendix B: SNMP Alerts.
SIP calls route to the wrong server. Check the host address maps on the server(s)
running SES software.
Presence information for Avaya IP On the Add Host or Edit Host screen for the
Softphone 5.2 users cannot be seen in the SES home serving these users, ensure that the
IM client. Presence Access Policy (Default) field has been
set to “Allow All”
4600 Series SIP IP telephones produce If a 46XX or another IP-based station type is
many alarms in the alarm log on the server. administered in Communication Manager, many
maintenance alarms are generated. If a DCP
station type such as 6408D+ or 6424D+ is used,
with X-port specified, then these maintenance
alarms are not generated, but then undesired
interactions with both PSA and TTI on the
Communication Manager server may occur.
See SES 5.x release notes for details. Note that
OPS is required for any SIP-enabled extension.
Network Duplicated SES The secondary SES does not know its roll, so it
The backup server is reporting its SIP Roll will not register SIP endpoints. It needs to be
as Unknown when checking server state. administered as the Master Administrator
Takeover and interchanges are successful through the initial_setup and in the
for both servers. SIP endpoints will not Administration web interface.
register to the backup server when it is
Active Primary. All other routing through
SES works.
2 of 2

Appendix C: Worksheet for installation
Use copies of this worksheet to answer all the questions asked by the install script. Use one
worksheet for each server in your SES network.
Table 13: SES Server Planning Form

Complete with the customer for each server being installed.
SES Server Type (Home, Edge or Combo)

Communication Manager HOME Communication
Manager Edge
Is this server duplicated? (High Availability - Yes or No)
This Servers Role if Duplicated (A or B)
Entered during 'initial_setup' sequence:
Host Name
(do not use special characters, spaces, or capital letters.)
SIP Domain Name

(do not use special characters, spaces, or capital letters.)
IP Address
Netmask
Gateway
Primary DNS IP Address
Secondary DNS IP Address
Tertiary DNS IP Address
Logical name of Redundant system
(only required on a duplex server pair)
Logical IP address of redundant system
Is this a Master Administrator? Note: You may not be prompted
(not prompted on B Server in Redundant configuration) with this yes or no question.
Entered from the Web Interface:

SIP License Host IP Address
(typically the edge server, and is the physical address,
not the logical one, if duplicated. Should only be enabled
on one box.)
1 of 2
Issue 6 May 2009 55

Worksheet for installation
Table 13: SES Server Planning Form (continued)

Complete with the customer for each server being installed.
Profile-Service Password
(must be unique for each configured host)
Username WebLM Login (entered on the license host)
Password WebLM Login (customer owned)
SIP Trunk - IP Address and Node Name (IP address of
the CLAN or procr that the SIP trunk uses on
Communication Manager)
Server Admin Login (new customer level super-user
login that also needs adding on Communication
Manager)
Server Admin Password
(must be a minimum of 7 digits)
Server Admin Address (IP address of the
Communication Manager Active server or procr for SAT
access)
NTP Server IP Address (for time synchronization)
Entered in DHCP/46xxsettings.txt File or 96xxsettings.txt file:
FTP Server IP Address
(for backup of station profiles)
TFTP/HTTP Server IP Address
(for station firmware and 46xx or 96xx settings file)
SIP Stations Dial Plan
(dial string pattern as entered in 46xx or 96xx settings
file to allow station dialing without using the 'send' key)
DHCP Option 176 or 242 Option
(see LAN Admin Guide for more details)
Important Notes
INADS Line for remote connectivity required
Passwords must be maintained by the customer. If lost,
it is a Time and Materials (T&M) escalation.
Please make sure that this planning form is part of the
permanent customer record (Maestro, EPROJECT,
Rover, and so on.
2 of 2

Index
Index
Numerical C
4600 SIP IP phones . . . . . . . . . . . 14, 15, 34, 36 call detail records . . . . . . . . . . . . . . . . . . 13
home domain . . . . . . . . . . . . . . . . . . 28 clearing alarms, See Resolving alarms
interactions with click to conference . . . . . . . . . . . . . . . . . 25
PSA . . . . . . . . . . . . . . . . . . . . 54 Communication Manager
TTI . . . . . . . . . . . . . . . . . . . . . 54 configuring for SIP . . . . . . . . . . . . . . . . 31
parameters . . . . . . . . . . . . . . . . . . . 37 copying . . . . . . . . . . . . . . . . . . . . . 43
version required . . . . . . . . . . . . . . . . 33 other SIP scenarios . . . . . . . . . . . . . . . 32
4602 SIP phone . . . . . . . . . . . . . . . . . 15, 16 SIP trunking . . . . . . . . . . . . . . . . . . . 31
4602SW SIP phone . . . . . . . . . . . . . . . . 16 trunk administration . . . . . . . . . . . . . . . 31
4610SW phone . . . . . . . . . . . . . . . . . . 16 Communication Manager servers, Avaya
4620 phone . . . . . . . . . . . . . . . . . . . . 33 setup and configuration . . . . . . . . . . . . . 22
4620SW phone . . . . . . . . . . . . . . . . . . 16 configuring
4621SW phone . . . . . . . . . . . . . . . . . . 16 advanced SIP telephony . . . . . . . . . . . . . 25
46xxsettings.txt file . . . . . . . . . . . . . . . . 35, 37 click to conference. . . . . . . . . . . . . . . . 25
9600 SIP IP phones . . . . . . . . . . . . . . . 14, 34 endpoints . . . . . . . . . . . . . . . . . . 33, 39
firmware version required . . . . . . . . . . . . 33 media servers . . . . . . . . . . . . . . . . . . 22
home domain . . . . . . . . . . . . . . . . . . 28 Modular Messaging . . . . . . . . . . . . . . . 26
parameters . . . . . . . . . . . . . . . . . . . 35 OPS stations . . . . . . . . . . . . . . . . . . 30
9620/9620G phone . . . . . . . . . . . . . . . . 14 SES servers . . . . . . . . . . . . . . . . 27, 28
9630/9630G phone . . . . . . . . . . . . . . . . 14 SIP trunks in Communication Manager . . . . . . 31
9640/9640G phone . . . . . . . . . . . . . . . . 14 softphone clients . . . . . . . . . . . . . . . . 38
96xxsettings.txt file . . . . . . . . . . . . . . . . . 35 CRC errors . . . . . . . . . . . . . . . . . . . . . 53
creating users . . . . . . . . . . . . . . . . . . . 29
A
access control . . . . . . . . . . . . . . . . . . . 13 D
adjunct systems . . . . . . . . . . . . . . . . . . 26 DCP . . . . . . . . . . . . . . . . . . . . . . . . 31
advanced SIP telephony . . . . . . . . . . . . . . 25 dial plan . . . . . . . . . . . . . . . . . . . . 13, 25
alarms DNS errors . . . . . . . . . . . . . . . . . . . . . 53
resolving . . . . . . . . . . . . . . . . . . . . 41 downloading Communication Manager software, see
suppressing . . . . . . . . . . . . . . . . . . 42 Communication Manager, copying
alerts and events . . . . . . . . . . . . . . . . . 54
AST . . . . . . . . . . . . . . . . . . . . . . . . 25
authentication errors . . . . . . . . . . . . . . . . 53 E
authentication file Extension to Cellular . . . . . . . . . . . . . . . . 30
copying to server . . . . . . . . . . . . . . . . 40
F
B firmware
backing up phones . . . . . . . . . . . . . . . . . . . . . 33
recovery system files . . . . . . . . . . . . . . 41
backup
verifying . . . . . . . . . . . . . . . . . . . . 42 I
boot timeout for SAMP . . . . . . . . . . . . . . . 42 IM client . . . . . . . . . . . . . . . . . . . . . . 17
IP Agent R6 . . . . . . . . . . . . . . . . . . . . 17
IP softphone R5 . . . . . . . . . . . . . . . . . . 17
Issue 6 May 2009 57

Index
SES server
configuring . . . . . . . . . . . . . . . . . 27, 28
L user creation . . . . . . . . . . . . . . . . . . 29
license and authentication files SES solution
copying to server . . . . . . . . . . . . . . . . 40 components . . . . . . . . . . . . . . . . . . . 12
installing on server . . . . . . . . . . . . . . . 49 deployment tasks . . . . . . . . . . . . . . . . 11
licensing errors . . . . . . . . . . . . . . . . . . 54 overview . . . . . . . . . . . . . . . . . . . . 11
server for . . . . . . . . . . . . . . . . . . . . 12
SIP client
M third-party . . . . . . . . . . . . . . . . . . . . 18
Make Upgrade Permanent Web page . . . . . . . . 48 SIP endpoints
media servers 4602SIP phone . . . . . . . . . . . . . . . . . 36
making the upgrade permanent . . . . . . . . . 48 4602SW SIP phone . . . . . . . . . . . . . . . 36
Media servers, Avaya 4610SW SIP phones . . . . . . . . . . . . . . 36
access control . . . . . . . . . . . . . . . . . 24 4620SWSIP phones . . . . . . . . . . . . . . . 36
routing and dial plan . . . . . . . . . . . . . . 25 4621SW SIP phones . . . . . . . . . . . . . . 36
SIP stations . . . . . . . . . . . . . . . . . . 23 Avaya 4600 series . . . . . . . . . . . . . . 15, 34
SIP trunking . . . . . . . . . . . . . . . . . . 23 Avaya 9600 series . . . . . . . . . . . . . . . . 14
Modular Messaging . . . . . . . . . . . . . . . . 26 setup . . . . . . . . . . . . . . . . . . . . 33, 39
softphone clients . . . . . . . . . . . . . . . . 38
third-party . . . . . . . . . . . . . . . . . . . . 18
N SIP home domain . . . . . . . . . . . . . . . . . 53
SIP IP Telephones
network interface cards (NICs) . . . . . . . . . . . 53
firmware versions . . . . . . . . . . . . . . . . 33
SIP service provider, Third-party . . . . . . . . . . . 32
O SIP Softphone R2 . . . . . . . . . . . . . . . . . 17
SIP stations . . . . . . . . . . . . . . . . . . 13, 23
Off-PBX Stations SIP trunks . . . . . . . . . . . . . . . . . . . . . 23
see OPS stations . . . . . . . . . . . . . . . . 30 SNMP alerts and events . . . . . . . . . . . . . . 54
one-X™ Deskphone SIP . . . . . . . . . . . . . 14, 34 softphones, Avaya . . . . . . . . . . . . . . . . . 17
one-X™ Desktop Edition . . . . . . . . . . . . . 12, 38 software upgrade
OPS rebooting the server . . . . . . . . . . . . . . . 45
Outboard Proxy SIP. . . . . . . . . . . . . . . 30 verify software operation after . . . . . . . . . . 47
stations, setting up . . . . . . . . . . . . . . . 30 stations . . . . . . . . . . . . . . . . . . . . . . 23
overview . . . . . . . . . . . . . . . . . . . . . .11 system files
backing up . . . . . . . . . . . . . . . . . . . 41
P
phone . . . . . . . . . . . . . . . . . . . . . . . 14 T
telephone firmware versions . . . . . . . . . . . . . 33
telephones, SIP . . . . . . . . . . . . . . . . 14, 16
R third-party SIP client . . . . . . . . . . . . . . . . 18
rebooting the server, software upgrade . . . . . . . 45 Toshiba SIP Business Phone . . . . . . . . . . . . 18
resolving troubles . . . . . . . . . . . . . . . . . . . . . . 53
alarms . . . . . . . . . . . . . . . . . . . . . 41 4600 phones produce excessive alarms . . . . . 54
routing . . . . . . . . . . . . . . . . . . . . . 13, 25 alerts or events . . . . . . . . . . . . . . . . . 54
cannot find boot files . . . . . . . . . . . . . . . 53
collisions . . . . . . . . . . . . . . . . . . . . 53
S CRC errors . . . . . . . . . . . . . . . . . . . 53
SAMP DNS errors . . . . . . . . . . . . . . . . . . . 53
disabling the boot timeout . . . . . . . . . . . . 42 IM presence errors . . . . . . . . . . . . . . . 54
scenarios, other SES . . . . . . . . . . . . . . . . 32 link bounce . . . . . . . . . . . . . . . . . . . 53
servers no server response . . . . . . . . . . . . . . . 53
license and authentication files . . . . . . . . . 49 no SIP call within domain . . . . . . . . . . . . 53
starting Maintenance Web pages . . . . . . . . 40 phantom calls . . . . . . . . . . . . . . . . . . 53

Index
rolling reboot at install . . . . . . . . . . . . . . 53

server authentication error. . . . . . . . . . . . 53
server licensing error . . . . . . . . . . . . . . 54
SIP calls route to wrong server . . . . . . . . . 54
third-party calls dropped . . . . . . . . . . . . . 53
trunk administration in Communication manager . . . 31
trunk capacities . . . . . . . . . . . . . . . . . . 32
trunking . . . . . . . . . . . . . . . . . . . . . . 23
administering SIP . . . . . . . . . . . . . . . . 31
external . . . . . . . . . . . . . . . . . . . . 24
SIP . . . . . . . . . . . . . . . . . . . 13, 23, 31
SIP, capacity . . . . . . . . . . . . . . . . . . 32
SIP, maximum . . . . . . . . . . . . . . . . . 32
SIP, on media server . . . . . . . . . . . . . . 27
SIP, other scenarios . . . . . . . . . . . . . . 32
third-party . . . . . . . . . . . . . . . . . . . 32
trustedhost command . . . . . . . . . . . . . . . 53
U
upgrades
3.0 to 3.1 . . . . . . . . . . . . . . . . . . . . 27
upgrading
making the upgrade permanent . . . . . . . . . 48
users
creating . . . . . . . . . . . . . . . . . . . . 29
V
version
telephone firmware . . . . . . . . . . . . . . . 33
W
Web pages
Make Upgrade Permanent . . . . . . . . . . . 48
X
XMOBILE stations . . . . . . . . . . . . . . . . . 30
X-port . . . . . . . . . . . . . . . . . . . . . . . 54
Issue 6 May 2009 59

Index

16-300140 6

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

16-300140 6

Hochgeladen von

Copyright:

Verfügbare Formate

Avaya Aura™ SIP Enablement

Services (SES) Implementation Guide

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 1: SES Solution Overview . . . . . . . . . . . . . . . . . . . . 11

Chapter 2: Setting up the Communication Manager server . . . . . . . 21

Chapter 3: Setting up the server(s) running SES . . . . . . . . . . . . . 27

Issue 6 May 2009 3

Chapter 4: Establishing SIP trunks in Communication Manager. . . . . 31

Chapter 5: Setting up a SIP Endpoint . . . . . . . . . . . . . . . . . . . 33

Chapter 6: Upgrading SIP Enablement Services . . . . . . . . . . . . . 39

4 SES Implementation Guide

Appendix A: Reference Points . . . . . . . . . . . . . . . . . . . . . . . 51

Appendix B: Troubleshooting the SES solution. . . . . . . . . . . . . . 53

Appendix C: Worksheet for installation . . . . . . . . . . . . . . . . . . 55

Issue 6 May 2009 5

6 SES Implementation Guide

Using this document

Table 1: Related documents

Document Title Document ID

4600 Series IP Telephone LAN Administrator Guide 555-233-507

Issue 6 May 2009 7

Reference point—Setting up SES server(s)

8 SES Implementation Guide

● Avaya one-X™ Deskphone SIP for 9630/9630G IP Telephone Quick Reference,

Conventions used in this document

Issue 6 May 2009 9

● Commands are printed in bold face as follows: command.

10 SES Implementation Guide

Reference point—System architecture, server requirements, and local failover

Issue 6 May 2009 11

Reference point—Co-resident system architecture and server requirements

Overview of Avaya SES solution components

Avaya SIP Enablement Services server

12 SES Implementation Guide

Reference point—System requirements, installation and administration for

Servers running Avaya Communication Manager 5.0

Issue 6 May 2009 13

Avaya one-X™ Deskphone supporting SIP for 9600 Series phones

Key benefits of an Avaya 9600 Series one-X™ Deskphone SIP telephone

Converting Avaya 9600 Series telephones to one-X™ Deskphone SIP

Reference Point—Enhancing 9600 Series H.323 IP telephones to SIP telephones

14 SES Implementation Guide

on 9600 Series IP Telephones".

Reference point—System requirements, installation and administration for 9600

Avaya 4600 Series IP Telephones supporting SIP

Key benefits of an Avaya 4600 Series SIP telephone

Issue 6 May 2009 15

Avaya 4602/4602SW, 4610SW or 4620SW/4621SW telephones

Reference Point—Enhancing 4600 Series H.323 IP telephones to SIP telephones

Reference point—System requirements, installation and administration for 4602

Reference point—System requirements, installation and administration for

Reference point—System requirements, installation and administration for

16 SES Implementation Guide

Avaya IP Agent R6.x and IP Softphone R5.x with IM client

Reference Point—Enhancing H.323 IP softphones to IM-enabled softphones

Avaya one-X™ Desktop Edition and SIP Softphone R2.x

Reference Point—Installing and configuring the Avaya SIP Softphone

Issue 6 May 2009 17

Third-party SIP clients

18 SES Implementation Guide

Table 2: Documents that relate to security

Document Title Document ID