You are on page 1of 60

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Installing security and SES service packs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Setting parameters . . . . . . . . . . . . . . . . . 43 Upgrading SES . . . . . 42 Suppressing alarming . . . . . . . . 44 Rebooting the server . . . . . . . . . . . . . . . 40 Resolving alarms . . . 40 Copying files to the server . 36 Setting parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Verifying reboot progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Inserting the SES CD into the server . . . . . . . . . . . . . . . . . . if any . . . . . . . . . . . 50 4 SES Implementation Guide . . . . . . . . 49 Upgrading a Cable Duplicated Server Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Upgrading a Network Duplicated Server Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Installing a new release of SES from the local hard drive . . . . . . . . . . . . . . . 42 Disabling the boot timeout of the SAMP board . . . . . . . . . . . . . . . 41 Backing up recovery system files . . . . . . . . . . . . . . . . . . . 38 Chapter 6: Upgrading SIP Enablement Services . . . . . . . 33 Compatibility Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Verifying the backup. . . . . . . . 31 Other scenarios for using an SES system . . . . . . . . . . . . . . . . . . 47 Making the upgrade permanent on the server . . . . . . . . . . 4610SW and 4620SW/4621SW SIP telephones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Chapter 5: Setting up a SIP Endpoint . . . . . . . . . . . . . . . . . 35 Avaya 4602/4602SW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Setting up Avaya softphone clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Avaya one-X™ Deskphone SIP for 9600 series telephones. . . . . . 39 Connecting to the server . . . . . . . . . . . 39 Accessing the System Management Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Installing the authentication file . . . . . . . . 31 Advanced SIP trunk administration . . . . . . . . . . . . . . . . . . . . . . . . 47 Checking system status. . . . . 42 Upgrade tasks . . . . . . . . . . . . . . . . . . . . .Contents Chapter 4: Establishing SIP trunks in Communication Manager. . . .

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

Contents 6 SES Implementation Guide .

This document is a road map. Using this document Use this document as a reference point for deploying the Avaya SES solution. and installers who are deploying the Avaya SES solution over an IP telephony network. 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. 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 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. services technicians. Document tables At the beginning of each chapter. Intended audience This document is for field technicians. The document is high-level.

and Troubleshooting Avaya Aura™ SIP Enablement Services. refer to this document: Installing. Related sources The following documents are referenced within this document: ● Avaya application notes ● Administering Network Connectivity on Avaya Aura™ Communication Manager. 16-601943 ● Avaya one-X™ Deskphone Edition for 9600 Series SIP IP Telephones Administrator Guide. Administering. 16-601946 ● Avaya one-X™ Deskphone SIP for 9640/9640G IP Telephone User Guide. Maintaining. 16-601944 ● Avaya one-X™ Deskphone SIP for 9620 IP Telephone User Guide. and Troubleshooting Avaya Aura™ SIP Enablement Services. Maintaining. the relevant chapter within the document. The reference point refers to the document that has the information that is needed to complete the task at hand. 03-600768 ● Avaya Toll Fraud and Security Handbook. The sample reference point above refers to the Avaya document. 03-602508 ● Installing. 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. Administering. Avaya white paper. 555-233-504 ● Administering Avaya Aura™ SIP Enablement Services on the Avaya S8300 Server. 555-025-600 ● Security and the Avaya S8700 Media Servers.About this document Reference points A key component of this documentation is the reference point. 16-601945 ● Avaya one-X™ Deskphone SIP for 9630/9630G IP Telephone User Guide. 16-602403 ● Avaya one-X™ Deskphone SIP for 9620 IP Telephone Quick Reference. Chapter 3: "Setup and configuration"—"Configuring a new server". 03-600768. Resource Library ● Avaya one-X™ Deskphone Edition for 9600 Series SIP IP Telephones Installation and Maintenance Guide. and the section heading within the chapter to complete the task. 16-601947 8 SES Implementation Guide .

1 or later. 16-300475 ● Avaya Extension to Cellular User’s Guide. Issue 6 May 2009 9 . 129214 ● Avaya Agent Deskphone 16CC 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-233-128 ● Avaya 4602/4602SW SIP Telephone User’s Guide. 16-602096 ● Avaya 4600 Series IP Telephone LAN Administrator Guide. 16-602097 ● Avaya Agent Deskphone 16CC Administrator Guide. Avaya media servers may be S8300. it means a Linux-based media server running Avaya Communication Manager R3. 16-300035 ● Avaya 4602/4602SW SIP Telephone Quick Reference. 16-602095 ● Avaya Agent Deskphone 16CC User Guide. ● Media server—In the SES solution. 16-300472 ● Avaya 4610SW SIP IP Telephone Quick Reference. or S8710 series. 210-100-500 ● Avaya Server Availability Management Processor User Guide (SAMP). S8400. 555-233-507 ● Avaya 4600 Series IP Telephone Installation Guide. When this document refers to a media server. 03-300322 Conventions used in this document Become familiar with the following terms and conventions. 16-300474 ● Avaya 4620SW/4621SW SIP IP Telephone Quick Reference. 16-300471 ● Avaya 4610SW SIP IP Telephone User’s Guide. 16-602093 ● Avaya Agent Deskphone 16CC Installation and Maintenance Guide. S8500 series. 16-300473 ● Avaya 4620SW/4621SW SIP IP Telephone User’s Guide. 555-245-206 ● Getting Started with Avaya Call Center and Avaya Agent Deskphone 16CC. 210-100-700 ● Avaya Extension to Cellular and Off-PBX Station (OPS) Installation and Administration Guide. 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.

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

See Chapter 5: Setting up a SIP Endpoint on page 33. scalability. or any other communications method. 4. 03-600768. See Chapter 2: Setting up the Communication Manager server on page 21. SIP is a text-based protocol that is designed to set up. 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. 2. modify. and local failover design. See Setting up OPS stations on page 30. instant messaging.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. in these sections: 1. 5. See Chapter 3: Setting up the server(s) running SES on page 27. Issue 6 May 2009 11 . This document outlines how to deploy an SES solution. Chapter 3: "Introduction". See Chapter 4: Establishing SIP trunks in Communication Manager on page 31. and Troubleshooting SIP Enablement Services. Configure supported SIP IP telephones for use with the SES solution. Reference point—System architecture. Once sessions are established. Establish SIP Trunks on the server running Communication Manager. an Internet-centric protocol that provides basic functionality beyond that of H. and the 4600/9600 series SIP IP telephones via Extension to Cellular and Off-PBX Station (OPS) mapping. SIP Enablement Services. Administering. Install and configure Avaya SIP Enablement Services on the SES server(s). 3. Presently. SIP architecture promises increased resiliency.323. server requirements. and local failover ● Installing. Practical necessity requires that some intelligence be in the network. provides details of the SES solution architecture and topography. Set up the server(s) running Avaya Communication Manager. was originally designed to place the intelligence in the endpoints rather than within the network. The tasks required to deploy this solution are described in this document. Maintaining. video. Integrate Communication Manager. the content of these sessions can be voice. and rapid application development. server hardware and software requirements. SIP. and tear down communication sessions between users.

Avaya 4600 Series IP Telephones supporting SIP . 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. and local failover design. and redirection functions associated with SIP applications. DCP or H. Home. as well as SIP-enabled endpoints. 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. such as instant messaging. When the SES home server communicates with one or more servers running Communication Manager. The SES application also supports the Avaya S8300C Server. 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. registration. provides details of the SES solution architecture and topography. In this configuration.323 stations and analog. digital or IP trunks. 03-602508. running co-resident with Avaya Communication Manager 5. The SES edge server is dedicated to performing proxy. Endpoints supported by Communication Manager include analog.1 and later with the IM client 12 SES Implementation Guide . and combination Home/Edge servers. server hardware and software requirements.Avaya one-X™ Deskphone supporting SIP for 9600 Series phones .0 ● Gateways ● SIP endpoints: .0 or later releases. communication between and among the various non-SIP endpoints is supported.SES Solution Overview Reference point—Co-resident system architecture and server requirements ● Administering SIP Enablement Services on the Avaya S8300 Server.Avaya softphones. SIP-enabled endpoints may be any from this list: ● Avaya 9600 Series one-X™ Deskphone. only Home and Home/Edge SES server types are supported.

Administering. For example.Chapter 3: "Introduction to SIP and SIP Enablement Services" ● Installation . They support both bearer and signaling traffic routed between packet-switched and circuit-switched networks. S8500-series.0 Avaya’s SES solution can be deployed with Communication Manager running on Avaya S8300. SIP is also used for communications. depending on your hardware configuration ● Administration . The gateways are optimized for use with enterprise class telephony and provide a variety of flexible deployment options.323 with the server running Avaya Communication Manager. S8400. fax. Although technically an Avaya IP Softphone is not managed by Communication Manager. and fully IP environments.Chapter 22: "Administration web interface" Servers running Avaya Communication Manager 5. installation and administration for standalone SES servers The document Installing.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 . Reference point—System requirements. These hardware elements deliver application-enabling data. it is required to register H. and administrative tasks for S8500 series servers running SES. 03-600768. Although IP softphones use H. such as IP and TDM. installation instructions. and the S8700-series servers. and Troubleshooting SIP Enablement Services.Chapter 4: "Setup and configuration" Chapter 5: "Getting ready to install SES" One or more of chapters 7-21. Maintaining. Overview of Avaya SES solution components SIP-enabled endpoints must register with the SES server.323 for voice. Options include both partial environments. video and messaging capabilities to your network. instant messages on IP softphones use SIP.Chapter 4: "Setup and configuration"—"Installation checklist" Chapter 4: "Setup and configuration"—"Post installation tasks" ● Administration in general . Features for SIP in Avaya Communication Manager 5. provides detailed system requirements. See the respective chapters. ● System requirements . voice.

323 phone to a SIP phone.323 software. refer to the document Avaya one-X™ Deskphone Edition for 9600 Series SIP IP Telephones R2.x Installation and Maintenance Guide. ● This telephone employs standards-based SIP telephony call control. See the latest 9600 Series one-X™ Deskphone SIP telephone documentation for more details.com/support/ Then select the link for Downloads under Most Visited Support Areas. Chapter 2: "9600 Series SIP IP Telephone Installation"—"Converting Software 14 SES Implementation Guide . you must convert the H. 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. allowing integration into multi-vendor telephony environments using SIP. 9640/9640G telephones. Converting Avaya 9600 Series telephones to one-X™ Deskphone SIP SIP can be deployed on the Avaya 9620. To use an H. 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.323 phone with SES.avaya. 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. Avaya ships these phones from the factory and they contain the latest load of H. 9630/9630G. Note: Note: The 9600 Series SIP telephone incorporates a SIP stack. See Other scenarios for using an SES system on page 32 for more information on multi-vendor SIP telephony deployments.323 to SIP firmware upgrade provides a migration path to SIP that maximizes investment protection.SES Solution Overview Gateways The Avaya SIP Enablement Services solution can be deployed with any of the Avaya gateways supporting S8xxx. 16-601943. ● The simple H. The telephone registers with a server running SIP Enablement Services (SES) software and communicates through the server with Communication Manager for call control.

see the next Reference point.8. ● A separate Avaya one-X™ Deskphone SIP for 9600 Series SIP IP Telephones R2. 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. Note: Note: The 4600 Series SIP telephone incorporates a SIP stack. and 9640/9640G IP Telephones provides detailed tasks associated with using the phone. ● A separate Avaya one-X™ Deskphone for 9600 Series SIP IP Telephone Quick Reference for each of the 9620. For the 4602. 9630/9630G.x to 2. you may need to migrate your H. Issue 6 May 2009 15 .x User Guide for each of the 9620. installation and administration for 9600 Series SIP IP telephones ● The Avaya one-X™ Deskphone Edition for 9600 Series SIP IP Telephones R2. 9630/9630G.323 firmware from 1.2 before converting the phone to SIP firmware. 16-601944 provides detailed tasks associated with administering the 9600 Series SIP IP telephone for use.avaya. and 9640/9640G IP Telephones provides installation instructions and initial configuration tasks.x Administrator Guide. See Other scenarios for using an SES system on page 32 for more information on multi-vendor SIP telephony deployments. Overview of Avaya SES solution components on 9600 Series IP Telephones".com/support/ Then select the link for Downloads under Most Visited Support Areas. The telephone registers with a server running SIP Enablement Services (SES) software and communicates through the server with Communication Manager for call control. Reference point—System requirements. ● The simple H. ● This telephone employs standards-based SIP telephony call control and so allows integration into multi-vendor telephony environments using SIP. See the latest 4600 Series IP telephone documentation for more details.323-to-SIP firmware upgrade provides a migration path to SIP that maximizes investment protection. 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. For more information about administering and installing the phones.

323 software. 4610SW or 4620SW/4621SW telephones SIP can be deployed on the Avaya 4602/4602SW. installation and administration for 4602 SIP telephones ● The Avaya 4602/4602SW SIP Telephone User’s Guide.323 IP telephones to SIP telephones ● For detailed instructions on enhancing the software on the Avaya 4600 Series SIP IP telephones. Avaya ships these phones from the factory and they contain the latest load of H. Reference point—System requirements.323 phone to a SIP phone.2 Installation Guide. installation and administration for 4620SW/4621SW SIP telephones ● The Avaya 4620SW/4621SW SIP IP Telephone User’s Guide. Reference point—System requirements. ● The Avaya 4610SW SIP IP Telephone Quick Reference. installation and administration for 4610SW SIP telephones ● The Avaya 4610SW SIP IP Telephone User’s Guide. 4610SW or 4620SW/4621SW telephones. 16-300471 provides installation instructions and initial configuration tasks for the 4602/4602SW SIP telephone. 16-300475 provides installation and initial configuration tasks for the 4620SW or 4621SW SIP telephone. the administrator must convert the H. refer to the document 4600 Series IP Telephone R2. ● The Avaya 4602/4602SW SIP Telephone Quick Reference. To use an H. 555-233-128. Reference Point—Enhancing 4600 Series H. 16-300474 provides detailed tasks associated with using the 4620SW or 4621SW SIP telephone.SES Solution Overview Avaya 4602/4602SW. ● The Avaya 4620SW/4621SW SIP IP Telephone Quick Reference. 16-300035 provides detailed tasks associated with using the 4602 or 4602SW SIP telephone. Chapter 2: "4600 Series IP Telephone Installation"—"Converting Software on Avaya 4600 Series IP Telephones". Reference point—System requirements.323 phone with SES. 16-300473 provides installation instructions and initial configuration tasks for the 4610SW SIP. 16-300472 provides detailed tasks associated with using the 4610SW SIP Telephone. 16 SES Implementation Guide .

Overview of Avaya SES solution components

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
http://support.avaya.com/japple/css/
japple?PAGE=Document&temp.productID=252060&temp.bucketID=159898&temp.documentI
D=252143&temp.selectedRelease=252204

Issue 6 May 2009 17

SES Solution Overview

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.

18 SES Implementation Guide

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

Document Title Document ID

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

SES Solution Overview 20 SES Implementation Guide .

you will need to have these references available: Table 3: Documents required for setting up Communication Manager servers Document Title Document ID 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. IP connectivity must be configured correctly. refer to Administering Network Connectivity on Avaya Aura™ Communication Manager.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. For details. Note: Note: Prior to enabling SIP/SES on the server(s) running Communication Manager. Issue 6 May 2009 21 . with or without Avaya SES running co-resident with it ● Avaya S8400 Server ● Avaya S8500-series Servers ● Avaya S8700-series Servers. 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. Maintaining.

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. fax. The gateways are optimized for use with enterprise class telephony and to provide a variety of flexible deployment options. refer to SIP Support in Avaya Aura™ Communication Manager. and Troubleshooting Avaya Aura™ SIP Enablement Services : ● Chapter 4: "Setup and configuration"—"Pre installation checklist". With Avaya Communication Manager. These hardware elements deliver application-enabling data. Options include partial environments. 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. prior to setting up an Avaya server for SIP. SIP features include these: 22 SES Implementation Guide . if applicable. Setting up SIP support in Avaya Communication Manager Avaya’s SES solution can be deployed with the S8300. refer to Administering Network Connectivity on Avaya Aura™ Communication Manager. Setting up Advanced SIP Telephony on page 25 ● And. Setting up Modular Messaging as an adjunct system on page 26.Setting up the Communication Manager server Setting up the Avaya server As noted above. as well as full IP environments with H. voice. ● For information on setting up Avaya Communication Manager. Maintaining. Many sections in this document discuss this topic. Administering. and the S8700-series servers running Communication Manager. you must configure IP connectivity correctly.323 and SIP endpoints. video and messaging capabilities to your network. refer to Installing. Setting up Click to Conference on page 25 ● If applicable for your SIP endpoints. ● For information on setting up standalone Avaya SES server(s). Chapter 2: "Administering SIP in Avaya Communication Manager". S8500-series. refer to Administering Avaya Aura™ SIP Enablement Services on the Avaya S8300 Server . S8400. Reference point—List of related documents ● For information on correctly configuring IP connectivity on your server. After IP connectivity has been configured. such as both IP and TDM. They support both bearer and signaling traffic routed between packet-switched and circuit-switched networks.

SIP stations Support for SIP stations using SIP trunks allows any fully compliant SIP phone to interoperate with Avaya phones. 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. Setting up the Avaya server ● SIP trunking ● SIP stations ● Call Detail Recording (CDR) ● Profile-based access control ● Call routing ● Enterprise dial plan. 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. 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). see the applicable SES installation and administration guide: Installing. Chapter 22: "Administration Web Interface"—"Adjunct Systems". SIP signaling-group properties in Communication Manager must be administered to match each other in certain. This means any SIP phone. Reference point—OPS ● For more details on OPS installation. Administering. specific ways. or see the document Administering Avaya Aura™ SIP Enablement Services on the Avaya S8300 Server . from Avaya or a third party. Outboard Proxy SIP (OPS) stations support additional features as well. like bridging. ● Put calls on hold and participate in transfers and conference calls. In complex configurations with Avaya S8700-series servers. if desired. Maintaining. 210-100-500 Reference point—Modular Messaging ● For using Modular Messaging as an adjunct system to SES. and Troubleshooting Avaya Aura™ SIP Enablement Services . and through that proxy to an external SIP service provider. refer to these documents: . 210-100-700 .Avaya Extension to Cellular and OPS Installation and Administration Guide. Issue 6 May 2009 23 .Avaya Extension to Cellular User’s Guide.

typically would be required to control access to SIP trunks from SIP endpoints that are outside of the enterprise. such as a network firewall. 24 SES Implementation Guide .Setting up the Communication Manager server 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.

Then select the link for Application Notes under Resource Type. 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. Setting up Click to Conference For information on how to administer the click-to-conference feature of SES. Filter the results for AST. obtain this Avaya document: Getting Started with Avaya SIP Softphone. or the specific product supporting advanced SIP telephony in which you are interested. refer to Chapter 3: "Administering Communication Manager for SIP Enablement Services".com and select Do Your Research: Resource Library in the middle of the page. Issue 6 May 2009 25 . Administration And Provisioning. and Route Pattern screens. Numbering. refer to Chapter 2: "Administering SIP in Avaya Communication Manager"—"Requirements for SIP". 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. Specific topics in this document are as follows: ● For hardware and software requirements. ● For setting up and configuring SIP trunks in Communication Manager. Refer to Chapter 3: "Administering Communication Manager for SIP Enablement Services". go to Avaya’s web site: http://www. available from your Avaya representative.avaya. 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. This involves several screens. Setting up Advanced SIP Telephony For application notes on how to set up SES for use with Advanced SIP Telephony. including for example the Locations.

and Troubleshooting Avaya Aura™ SIP Enablement Services . Configuration Note 88010—This note will be published on the Avaya support web site. refer to the following resources: Installing. Maintaining. Administering. Search the Configuration Notes Master Index.Setting up the Communication Manager server 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. or for PSN #1186U on SIP and MM Adjunct integration. 26 SES Implementation Guide . Chapter 22: "Administration Web Interface"—"Adjunct Systems".

SIP trunking must be administered properly on the server running the Communication Manager software. that is. use the three Server Upgrade screens in the maintenance interface of SES. 555-245-206. or R4.If you are upgrading from SES R3. Trunking For endpoint clients on Avaya Communication Manager to interoperate through the Avaya SES server.x to R5. and configured on.0 to SES X.1.0 to SES R3.0 or later. This administration requires that you specify several values. an enterprise’s IP network. and Troubleshooting 03-600768 Avaya Aura™ SIP Enablement Services 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.0 to 4. must be properly connected to. Note for SES X. Refer to SIP Support in Avaya Communication Manager. 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. These screens may not be used to upgrade and migrate directly from SES R3. the SIP proxy servers.0. Chapter 3: "Administering Communication Manager for SIP Enablement Services" for more details. Additional administration of call routing may be required. 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.1 upgrades: . Issue 6 May 2009 27 . Administering. Maintaining.Chapter 3: Setting up the server(s) running SES When working with the server(s) with SES installed.1. depending on current server values. you might use these references: Table 4: Documents required for setting up an Avaya SES server Document Title Document ID Installing.

SES access is required for phone registration. and on the server by way of a Troubleshooting Avaya Aura™ SIP Point to Point Protocol (PPP) Enablement Services session. refer to Administering Avaya Aura™ SIP Enablement Services on the Avaya S8300 Server . Administering. the same authoritative domain must be specified in the phone’s settings file(s) as on the IP Network Region screen.323 versions of these IP telephones. Administering. ● Chapter 4: "Setup and configuration"—"Installation checklist" ● Chapter 4: "Setup and configuration"—"Post installation checklist" 1 of 2 28 SES Implementation Guide . Also.Setting up the server(s) running SES Note: Note: For 4600 Series and 9600 Series SIP IP Telephones. Maintaining. and Troubleshooting Avaya Aura™ SIP Enablement Services ● Chapters 7-21: "Installation Procedures" Perform administrative tasks Installing. Administering. Note: Note: For greater detail about the tasks necessary to configure a co-resident server running Communication Manager to run SES as well. Installing. and setup. Maintaining. Maintaining. Task list for configuring server(s) for SES Table 5 lists the tasks necessary to configure a standalone server for SES. Troubleshooting Avaya Aura™ SIP Enablement Services ● Chapter 4: "Setup and configuration"—"Configuring a new server" ● Chapter 4: "Setup and Configuration"—"Pre-installation tasks" Install all server software. For greater detail about each task. the SIP versions must have working IP network access to their respective TFTP or HTTP servers upon startup. unlike the H. Table 5: Configuration task list for standalone server(s) running SES Task Reference document ✔ Perform initial assembly and Installing. refer to the documents that correspond with each task listed in the table.

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.avaya. Maintaining. available from the ProVision web site’s Document Center. and by way of the Automatic Troubleshooting Avaya Aura™ SIP Registration Tool (ART). Maintaining. Maintaining.com/support/iProVision/ Issue 6 May 2009 29 . Administering. and Troubleshooting Avaya Aura™ SIP Enablement Services ● For loading users in bulk with ProVision. Maintaining. and Troubleshooting Avaya Aura™ SIP Enablement Services Also refer to ProVision’s help subsystem and also to the Notepad newsletter. Administering. Administering. and way of WebLM. Reference point—Creating users via the user screens in SES ● For creating a new SIP user in your SES solution. 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. Maintaining. Administering. refer to Installing. you must access the web-based user interface and perform the necessary tasks in the following reference point. refer to Installing. Administering. Log in to ProVision at this web site: http://www. and Troubleshooting Avaya Aura™ SIP Enablement Services ● For server administration of users. refer to Installing. Troubleshooting Avaya Aura™ SIP Enablement Services Chapters 7-21: "Installation Procedures"—"Server license installation" Deliver the authentication file Installing.

30 SES Implementation Guide . 210-100-500. Note: Note: Any SIP phone or endpoint must have access to and register with the SIP proxy.1.Setting up the server(s) running SES Setting up OPS stations Table 6: Documents required for setting up Extension to Cellular and OPS Document Title Document ID Avaya Extension to Cellular and OPS Installation and 210-100-500 Administration Guide Outboard Proxy SIP (OPS) Beginning with Avaya Communication Manager Release 2. regardless of whether OPS is administered in Communication Manager. 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. Extension to Cellular/OPS is in fact dealing with a multi-function phone. 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. 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. From a call processing perspective. whereas the previous Extension to Cellular implementation utilized one or two XMOBILE stations that behaved like analog station types.

Chapter 4: Establishing SIP trunks in Communication Manager When you set up the SIP trunks on the server running Communication Manager. For more information on SIP administration and usage. use these references to help you: Table 7: Documents required for establishing SIP trunks in Communication Manager Document Title Document ID SIP Support in Avaya Aura™ Communication Manager 555-245-206 Installing. see the overview and introduction chapters of the documents listed in the preceding table. Maintaining. 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. the server(s) running SES enable(s) these SIP trunks to be connected to SIP endpoints. These trunks are administered as a trunk type and associated with the appropriate type of signaling group on the server running Communication Manager. Issue 6 May 2009 31 . Administering.323 or SIP. and Troubleshooting 03-600768 Avaya Aura™ SIP Enablement Services Session Initiated Protocol (SIP) is an endpoint-oriented messaging standard defined by the Internet Engineering Task Force (IETF). the new 9600 series IP telephones with one-X™ Deskphone SIP). DCP telephones) and SIP-enabled endpoints (for example. Then. Advanced SIP trunk administration Avaya Communication Manager provides the capability to administer IP trunks as either H.

go to the web site: http://www. 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. go to the web site: http://www. The service provider may employ different proxy servers. 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. You may filter results using SIP or the specific product name or model of third-party equipment in which you are interested. 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.htm For application notes on which third-party SIP endpoints are supported. implementation. and then documents them in Application Notes. However.avaya. For detailed information about the Avaya DeveloperConnection Program.Establishing SIP trunks in Communication Manager Reference Point—SIP Trunk Administration ● To administer SIP trunks in Avaya Communication Manager. configuration. or maintenance of any third-party SIP IP equipment.com and select Do Your Research: Resource Library in the middle of the page. Avaya’s Solution and Interoperability Test Lab (SITL) tests other scenarios. Avaya does not provide installation. PSTN gateways and other equipment as part of these scenarios. Chapter 3: "Administering Communication Manager for SIP"—"Administer SIP signaling and trunks".com/gcm/naster-usa/en-us/corporate/alliances/devconnect/index. 32 SES Implementation Guide . see SIP Support in Avaya Aura™ Communication Manager. Then select the link for Application Notes under Resource Type.avaya.

0. one-X™ Deskphone SIP Release 2. use document tables Table 11 and Table 12 in this section to guide you.0. one-X™ Deskphone SIP Release 2.x 4602 IP telephone SIP not supported 4602/4602SW SIP IP telephone Release 2. one-X™ Deskphone SIP Release 2.2 4610SW SIP IP telephone Release 2.Chapter 5: Setting up a SIP Endpoint When you configure the endpoints for your SES system. SIP Version 9620 IP telephone. Issue 6 May 2009 33 . 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.0 software.2 4620SW/4621SW SIP IP telephone Release 2.x 9630/9630G IP telephone.x 9640/9640G IP telephone.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. Table 9: Firmware versions required for using Avaya 9600 Series and 4600 Series SIP IP Telephones Telephone Min.

SIP calls may be placed from the phones.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 Document Title Document ID Avaya one-X™ Deskphone Edition for 9600 Series SIP IP 16-601944 Telephones R2. Reference Point—Enhancing 9600 Series H. Finally.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 Avaya one-X™ Deskphone SIP for 9630/9630G IP Telephone 16-601946 User Guide Avaya one-X™ Deskphone SIP for 9640/9640G IP Telephone 16-602408 Quick Reference Avaya one-X™ Deskphone SIP for 9640/9640G IP Telephone 16-602403 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. their station records/extensions must be administered both in Avaya Communication Manager and as SIP users (with the associated server extension) in SES software. If an SES solution includes 9600 Series IP telephones. the IP phones must be converted from H. refer to the document Avaya one-X™ Deskphone Edition for 9600 Series SIP IP Telephones R2.323 protocol to SIP.x Administrator Guide Avaya one-X™ Deskphone Edition for 9600 Series SIP IP 16-601943 Telephones R2. Then. 34 SES Implementation Guide . Chapter 2: "9600 Series SIP IP Telephone Installation"—"Converting Software on 9600 Series IP Telephones". 16-601943. after parameters for the phones have been set properly.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.x Installation and Maintenance Guide.

Issue 6 May 2009 35 . The 46XX phones obtain the domain setting from the 46XXsettings. manual programming.txt file.com For application notes on configuring specific SIP endpoints. The line in the file(s) for this setting is: SET SIPDOMAIN = yourSIPdomainName. but the SIPDOMAIN setting must be the same for your enterprise.com and select Do Your Research: Resource Library in the middle of the page. the 9600-series. Avaya SIP telephones will not be able to register in an SES system unless they can obtain the correct SIPDOMAIN setting.avaya. and the 16CC. You may filter the results using the term SIP or the specific model number of your Avaya telephone. Setting these parameters establishes the telephone’s operating parameters. go to the web site: http://www. Then select the link for Application Notes under Resource Type. 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.txt file for the 96XX phones. you may set up a separate 96XXsettings. 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) file. Avaya SIP telephones include the 4600-series. and configuration files. 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.txt (or 46XXsettings.

4610SW and 4620SW/4621SW SIP telephones Table 11: Documents required for setting up the Avaya 4600 Series SIP Telephones Document Title Document ID 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.323 protocol to SIP. after parameters for the phones have been set properly."—"Converting Software on Avaya 4600 Series IP Telephones". refer to 4600 Series IP Telephone Installation Guide. If an SES solution includes 4600 Series IP telephones. SIP calls may be placed from the phones. the IP phones must be converted from H. Reference Point—Enhancing 4600 Series H. Finally.Setting up a SIP Endpoint Avaya 4602/4602SW. 36 SES Implementation Guide .323 IP telephones to SIP telephones ● For detailed instructions on enabling the software on the 4600 Series IP Telephones. Then their station records must be administered as OPS in Communication Manager and as SIP users with a server extension in SES software. Chapter 2: "4600 Series IP Telephone Installation. 555-233-128.

Then select the link for Application Notes under Resource Type. Setting these parameters establishes the telephone’s operating parameters. Avaya 4602/4602SW.com and select Do Your Research: Resource Library in the middle of the page. You may filter the results using the term SIP or the specific model number of your Avaya telephone.txt file.avaya. and configuration files. 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. Issue 6 May 2009 37 . manual programming. For application notes on configuring SIP endpoints. 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. go to the web site: http://www.

com SIP Support area one-X ™Desktop Edition R2. Note that these clients manage their presence information by means of the SIP Personal Information Manager running on an SES server.avaya.Setting up a SIP Endpoint Setting up Avaya softphone clients Table 12: Documents required for setting up the Avaya softphones Document Title Document ID one-X™ Desktop Edition R2. then the software must be installed and configured to use.com/support > IP Agent > Avaya IP Agent Installation and User Guide http://support. http://www.com/japple/css/ japple?temp.x (or later) online help with IM client Avaya SIP Softphone Release 2 online help If an SES solution includes Avaya IP Softphone clients.avaya. the version of IP Agent or IP Softphone including the SIP-enabled instant messaging and presence module must be used. You must uninstall SIP softphone clients before installing one-X™ Desktop Edition Release 2. Reference Point—Enhancing H.x Getting Started www. 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.avaya.x Quick Setup Guide www.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.support.productID=107698&temp. refer to IP softphone online help.document ID=252143&temp.bucketID=159898&temp.selectedRelease=252204 38 SES Implementation Guide . refer to SIP softphone online help. Note that these clients manage presence information in a peer-to-peer fashion.com/japple/css/ japple?PAGE=Document&temp.com/support > SIP Softphone > Avaya SIP Softphone Administration http://support.com/support/ > Find Documentation > Avaya one-X™ Desktop Edition http://www.x/IP Softphone R5.releaseID= 235038&temp. or one of these locations: http://www.avaya.avaya.bucketID=160259&PAGE=Document If an SES solution includes Avaya one-X™ Desktop Edition or SIP softphone clients.avaya.productID=252060&temp.avaya.support.documentID=280964&temp.com SIP Support area Avaya IP Agent R6.

! Important: Important: S8500A servers cannot upgrade to SES 5.1. see Installing. You must migrate from the S8500A Server to an S8500B or S8500C Server to run SES 5.0).1.x or later releases. If you are an existing customer with S8500-based deployments of SIP Enablement Services 3.2. Issue 6 May 2009 39 . ! Important: Important: Cable Duplicated Avaya Aura™ SIP Enablement Services server pairs. The Distributed Replicated Block Device (DRBD) is automatically upgraded during the upgrade to SIP Enablement Services Release 5. Administering. before upgrading to SIP Enablement Services 5. connect to the services port.1.1 or later. Please follow the instruction in the Upgrading a Cable Duplicated Server Pair on page 49 section for the correct steps.2. require an upgrade to the Distributed Replicated Block Device (DRBD) when upgrading to Avaya Aura™ SIP Enablement Services Release 5.x.2.1 software from the Avaya SAFE download site.Chapter 6: Upgrading SIP Enablement Services The procedure for upgrades use the Manage Software link on the System Management Interface (SMI). deployed on SIP Enablement Services Releases 5. Connecting to the server Perform one of the following options: ● If you are on site.x and earlier.1. For more information on the latest upgrade procedures. The procedure for upgrading a cable duplicated pair of servers in SIP Enablement Services Release 5. You can download the SES 3. use the IP address of the server to log on to the server. Issue 7. you must upgrade to minimum release 3.2 has changed from previous releases. ● If you are off site. you can directly upgrade to release 5.1.1. and Troubleshooting Avaya Aura™ SIP Enablement Services document (03-600768. Maintaining. But if your software release is earlier than 3.2.1.

Start the Web browser. 2. Select the required option in the Manage Software web page in the System Management Interface and load the software. type 192. Copying files to the server To copy files to the server: Copy the following files. as appropriate. 3. To upgrade remotely: 1. 2. if required) 40 SES Implementation Guide .Upgrading SIP Enablement Services Accessing the System Management Interface To access the server: 1.11. Log in as craft 4.6 and press Enter to open the login Web page. 4. 3. if required ● Security update files (used post-upgrade. from the computer to the server: ● License file and Avaya Authentication file ● Postupgrade service pack files. In the Address field. Follow the steps as required. Click yes to suppress alarms The system displays the System Management Interface Web page. In the Address field.13. Start the Web browser. type the hostname or IP Address of the target SES server. 5. Click the Manage Software link under the Upgrade menu to go to Manage Software web page.

Click Download to copy the files to the server. Note: Note: Do not select the check box. To copy files to the server: 1. 3. Select the SES files. click Backup Now. Note: Note: If you back up to a flashcard. Click Start Backup to start the back up process. or click Clear All. under Alarms. Do not select Full Backup because this option does not save data files. click Download Files. Resolving alarms To clear alarms: 1. 4. Under Data Backup/Restore. On the Server (Maintenance) Web interface. Issue 6 May 2009 41 . 2. Select the backup method. On the Server (Maintenance). Click Browse next to the top field to open the Choose File window on your computer. Backing up recovery system files To back up the system configuration files: 1. 2. click Current Alarms to examine the alarm log. You might need these data files if you need to back out of the upgrade procedure. Repeat steps 1 through 4 for each server that will be upgraded. 4. under Miscellaneous. “Install this file on the local server. The system copies the files automatically to the default file location. Avaya recommends that you use a different flashcard from the one with the prior release data files. 5. Select File(s) to download from the machine used to connect to the server. Select the server alarms that you want to clear and click Clear. Find the files that you need to copy to the server. 2.” 3.

where time is the length of time that the alarms are suppressed up to 120 minutes (2 hours).11. see "Disabling the boot timeout on Release 3.1 using the SAMP Web page" in the Using the Avaya Server Availability Management Processor (SAMP).Upgrading SIP Enablement Services Verifying the backup To verify that the backup was successful: 1. and click Check Status. Verify that Backup Successful appears for each data set in the backup. 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. 4. 42 SES Implementation Guide . The system displays the following message: Alarm is suppressed. Access the command line interface of the server with telnet or an SSH client like PuTTY and an IP address of 192. the system can generate alarms. 3. Log off and close the dialog box. Log in as craft. 120 minutes left. Press Enter to suppress both dial-out and SNMP alarms.13. 3. To suppress alarming: 1. Under Data Backup/Restore. Select the backup that you want to verify. Suppressing alarming ! CAUTION: CAUTION: Ensure that you suppress alarming during the upgrade.6. 2. Type almsuppress -t time. 03-300322. click Backup History. resulting in unnecessary trouble tickets. The system displays the status of the backup. If you do not do so. For more information. 2.

At the SAMP command line. enter sampcmd. Close the tray. The Welcome banner appears. The system responds with the following output: Power On Server Operational Reset Deasserted Boot Time Disabled 4. The system responds with OK. followed by the SAMP command line. skip this step. Upgrading SES To start the upgrade: 1. At the command line on the S8500 Server. the SAMP boot timeout is automatically enabled again. When you have completed the upgrade and the server reboots. Enter Exit to return to the server command line. At the SAMP command line. Note: Note: You can copy SES software from an http or tftp server onto the server. In this case. Issue 6 May 2009 43 . you must delete one release to make room for the new release. Upgrade tasks To disable the boot timeout of the SAMP: 1. 2. enter serverctrl. enter serverctrl boot timer disable. Under Upgrade. 3. ! Important: Important: If three releases already reside on the hard disk. select Manage Software. Upgrade tasks Inserting the SES CD into the server Insert the CD that contains SES into the CD-ROM drive on the server.

When complete. 2. 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. and click Continue. Perform one of the following tasks: ● If three releases already reside on the hard disk 1. Select Copy from this server’s CD-ROM drive: and click Continue. select: 44 SES Implementation Guide .If a super-user login already existed prior to the upgrade. The system displays the Copy in Progress page. the system displays the following message: Deletion Complete 3. Select the software release you want. View the progress screen as the software is copied to the hard drive. Click Continue to view the releases available. Select the release to be copied and click Continue. ● Update authentication information as well as license information. The Choose Software page appears.If a super-user login did not exist prior to the upgrade.Upgrading SIP Enablement Services 2. Click Continue to return to the initial Manage Software page. Select one of the following: ● Copy a release to the local hard drive. If you have copied the license and authentication files to the server. When complete. then follow these steps: 1. 3. select the following options: . 2. 4. Select Delete one of the above releases from the local hard drive. . 2. Select the software release that you want to delete and click Delete. which you use to copy files from the source you selected. select: ● I will supply the license files myself when prompted later in this process. 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. ● If less than 3 releases reside on the hard disk 1. Click Continue to return to the initial Manage Software page. the system displays the following message: Success 5.

or if you previously ran a backup. 1. When complete. If you click Continue before the reboot is finished. the browser displays Expired Page. Note: Note: When you reboot the server. The system refreshes the Install in Progress window every 10 seconds or when you click Refresh. Although the Continue button is visible. The Reboot in Progress Web page displays during the reboot. it can no longer communicate with the Web interface. Click Continue. The system displays the Begin Installation page. The system displays the Review Notices page. If the system displays Page cannot be displayed. you do not need to run a backup at this time. ● Do not update authentication information. The system displays the Reboot in Progress window. The tray of the CD-ROM drive opens automatically. Wait for 3 minutes and then click Continue. 6. If you see the Expired Page message. The system does not automatically report when the reboot is complete. Click Continue. Click Continue. 4. do not click Continue yet. 7. refresh the browser. 2. use the browser Back button to return to the Reboot in progress Issue 6 May 2009 45 . The page summarizes the request you have made. The installation takes approximately 10 to 20 minutes. Click Continue. Remove the CD-ROM from the CD-ROM drive. 3. 3. 5. Upgrade tasks ● I will supply the license files myself when prompted later in this process. the system might try to reboot from the software on the CD-ROM. Click Reboot. the system displays the Reboot Server page. ! CAUTION: CAUTION: If you do not remove the CD-ROM and the tray of the CD-ROM drive closes again. Note: Note: The reboot takes approximately 3 minutes. Rebooting the server To reboot the server. For a new installation.

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

1. Close the MS-DOS window. click Status Summary to verify that the server mode is active. 2.6 and press Enter to clear the ARP cache in the laptop. 6. Click Start > Run to open the Run dialog box. it is recommended that you check the status before proceeding to upgrade the next server (if applicable). Under Server. click Software Version. 4. When you get a response. ● 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. Issue 6 May 2009 47 . The -t causes the ping to repeat until you get a response. Type arp -d 192. Under Server. Upgrade tasks Note: Note: You do not have to perform these activities if you are upgrading from release 5.0 to release 5. 2. 5. Verify the details in the Software Version web page to ensure that the new software is present. This command responds with one of the following responses: ● The command line prompt when the cache is cleared.13. Verifying software operation To verify the software version. in about 3 minutes. Verifying reboot progress To check the reboot process. 1. However. 3. Type command and press Enter to open an MS-DOS window.11.6 to access the server.2. Type ping -t 192. wait an additional 30 seconds before you go back to the Web interface. Checking system status To check the system status: 1.11.13. Type ctrl c to stop the ping.

Select Summary and Display once. To make the upgrade permanent. Wait until the system displays the message Finished unpacking. click Boot Partition to confirm that the new software release is selected for the boot partition and the active partition. Click View to access the View Process Status Results screen. Click Process Status. 3. If a reboot is required. the system automatically reboots.and click Continue. select the update ID and click Activate. 2. the next time when you reboot the server. and you must install the new software again. 9. an alarm is raised. The system displays the Manage Updates screen. 4. Click Continue. select update ID and click Unpack. 4. 7. select Manage Updates. You might lose any new translations you might have made. the server might run the previous version of the software. If the update ID you want to activate shows unpacked in the Status column. Click Yes. Under Server Upgrades. Click Submit to make the partition with the new software version the permanent partition. 5. Wait until the system displays the Continue button. 48 SES Implementation Guide . click Make Upgrade Permanent. If you do not make the upgrade permanent within 2 hours of the upgrade. If an update file you want to activate shows packed in the Status column. Under Server Upgrades. if any 1. 3. Otherwise.. The window shows the status of activating the update.Upgrading SIP Enablement Services 2. Verify that all the processes are UP. The window shows the status of the update. 1.. Installing security and SES service packs. Making the upgrade permanent on the server ! CAUTION: CAUTION: You must make the upgrade permanent. 2. 8. 6. 3. Under Server Upgrades.

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

Upgrading a Network Duplicated Server Pair A redundant pair consists of a primary server and a backup server. In the following steps. Repeat steps 1 to 7 for Server A. Reboot the server when the system displays the reboot instruction. Perform an interchange between the servers. 2. 8. it is assumed that Server A is the primary server and Server B is the backup server. as both servers will be out of service simultaneously. 10. so it is out of service. 5. 7. Release Server B. if applicable. using the Server Status web page.Upgrading SIP Enablement Services Note: Note: When upgrading a cable duplicated server pair to Release 5. 1. 50 SES Implementation Guide . Confirm that both servers are in-service and that Server A is the backup server and Server B is the primary server. After completing the upgrades. Upgrade Server B using the software upgrade process. 6. so it is back in service. 9. Busy-out Server B. 4. using the Server Status web page.2. (Optional) Apply service packs to Server B. make sure to perform the Make Upgrade Permanent step. Confirm that Server B is in-service and that it is the backup server. there will be a downtime in the availability of the system. 3.

323 IP telephones to SIP telephones on page 14 ● Reference point—System requirements. installation and administration for 4610SW SIP telephones on page 16 ● Reference point—System requirements. and local failover on page 11 ● Reference point—Co-resident system architecture and server requirements on page 12 ● Reference point—System requirements.Appendix A: Reference Points This appendix lists all of the reference points contained within this document.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 . 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. installation and administration for 9600 Series SIP IP telephones on page 15 ● Reference Point—Enhancing 4600 Series H. installation and administration for standalone SES servers on page 13 ● Reference Point—Enhancing 9600 Series H.323 IP telephones to SIP telephones on page 16 ● Reference point—System requirements. This appendix can serve as a quick reference for those who need to refer quickly to a document for a specific task. installation and administration for 4602 SIP telephones on page 16 ● Reference point—System requirements. server requirements. installation and administration for 4620SW/ 4621SW SIP telephones on page 16 ● Reference Point—Enhancing H.

323 IP telephones to SIP telephones on page 34 ● Reference Point—Enhancing 4600 Series H.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 ● Reference Point—Enhancing 9600 Series H.323 IP telephones to SIP telephones on 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 52 SES Implementation Guide .

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

SIP endpoints will not Administration web interface. 03-600768. 2 of 2 54 SES Implementation Guide . Administering. See SES 5. and Troubleshooting Avaya Aura™ SIP Enablement Services. 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. many maintenance alarms are generated. Appendix B: SNMP Alerts. Refer to the Installing. register to the backup server when it is Active Primary. It needs to be as Unknown when checking server state. Maintaining.x release notes for details. but then undesired interactions with both PSA and TTI on the Communication Manager server may occur. and Troubleshooting Avaya Aura™ SIP Enablement Services. Maintaining. Administering.Troubleshooting the SES solution Problem/Symptom Suggested Solution Server licensing errors occur. administered as the Master Administrator Takeover and interchanges are successful through the initial_setup and in the for both servers. 03-600768. with X-port specified. Note that OPS is required for any SIP-enabled extension. ensure that the IM client. SIP calls route to the wrong server. If a DCP station type such as 6408D+ or 6424D+ is used. All other routing through SES works. Refer to the Installing. Network Duplicated SES The secondary SES does not know its roll. administered in Communication Manager. Check the host address maps on the server(s) running SES software.2 users cannot be seen in the SES home serving these users. then these maintenance alarms are not generated. Chapter 4: "Installation Procedures"—"Server license installation". Presence information for Avaya IP On the Add Host or Edit Host screen for the Softphone 5. Alerts and events occur. so it The backup server is reporting its SIP Roll will not register SIP endpoints.

if duplicated. Use one worksheet for each server in your SES network. SES Server Type (Home.) SIP Domain Name (do not use special characters.) 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. spaces. and is the physical address. or capital letters.) 1 of 2 Issue 6 May 2009 55 .Appendix C: Worksheet for installation Use copies of this worksheet to answer all the questions asked by the install script. not the logical one. Should only be enabled on one box. or capital letters. spaces. Entered from the Web Interface: SIP License Host IP Address (typically the edge server.Yes or No) This Servers Role if Duplicated (A or B) Entered during 'initial_setup' sequence: Host Name (do not use special characters. Edge or Combo) Communication Manager HOME Communication Manager Edge Is this server duplicated? (High Availability . Table 13: SES Server Planning Form Complete with the customer for each server being installed.

txt File or 96xxsettings.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. Please make sure that this planning form is part of the permanent customer record (Maestro. If lost. and so on.Worksheet for installation Table 13: SES Server Planning Form (continued) Complete with the customer for each server being installed. 2 of 2 56 SES Implementation Guide . 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 .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. it is a Time and Materials (T&M) escalation. Rover. EPROJECT.

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

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

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

Index 60 SES Implementation Guide .