16-300140_6

8/8/2019 16-300140_6

1/60

Avaya Aura SIP Enablement

Services (SES) Implementation Guide

16-300140Issue 6

May 2009

8/8/2019 16-300140_6

2/60

2010 Avaya Inc.All Rights Reserved.

Notice

While reasonable efforts have been made to ensure that the information in thisdocument is complete and accurate at the time of printing, Avaya assumes noliability for any errors. Avaya reserves the right to make changes andcorrections to the information in this document without the obligation to notifyany person or organization of such changes.

Documentation disclaimer

Avaya shall not be responsible for any modifications, additions, or deletions tothe original published version of this documentation unless such modifications,additions, or deletions were performed by Avaya.

End User agree to indemnify and hold harmless Avaya, Avaya's agents,servants and employees against all claims, lawsuits, demands and judgmentsarising out of, or in connection with, subsequent modifications, additions ordeletions to this documentation, to the extent made by End User.

Link disclaimer

Avaya is not responsible for the contents or reliability of any linked Websitesreferenced within this site or documentation(s) provided by Avaya. Avaya is notresponsible for the accuracy of any information, statement or content providedon these sites and does not necessarily endorse the products, services, orinformation described or offered within them. Avaya does not guarantee thatthese links will work all the time and has no control over the availability of thelinked pages.

Warranty

Avaya provides a limited warranty on this product. Refer to your salesagreement to establish the terms of the limited warranty. In addition, Avayasstandard warranty language, as well as information regarding support for thisproduct, while under warranty, is available to Avaya customers and other

parties through the Avaya Support Website:http://www.avaya.com/support.Please note that if you acquired the product from an authorized Avaya reselleroutside of the United States and Canada, the warranty is provided to you by thesaid Avaya reseller and not by Avaya.

Licenses

The software license terms available on the Avaya Website,http://support.avaya.com/licenseinfo/are applicable to anyone who downloads,uses and/or installs Avaya software, purchased from Avaya Inc., any Avayaaffiliate, or an authorized Avaya reseller (as applicable) under a commercialagreement with Avaya or an authorized Avaya reseller. Unless otherwiseagreed to by Avaya in writing, Avaya does not extend this license if thesoftware was obtained from anyone other than Avaya, an Avaya affiliate or anAvaya authorized reseller, and Avaya reserves the right to take legal actionagainst you and anyone else using or selling the software without a license. Byinstalling, downloading or using the software, or authorizing others to do so,you, on behalf of yourself and the entity for whom you are installing,downloading or using the software (hereinafter referred to interchangeably asyou and end user), agree to these terms and conditions and create a

binding contract between you and Avaya Inc. Or the applicable Avaya affiliate(Avaya).

Avaya grants End User a license within the scope of the license typesdescribed below. The applicable number of licenses and units of capacity forwhich the license is granted will be one (1), unless a different number oflicenses or units of capacity is specified in the Documentation or othermaterials available to End User. Designated Processor means a singlestand-alone computing device. Server means a Designated Processor thathosts a software application to be accessed by multiple users. Softwaremeans the computer programs in object code, originally licensed by Avaya andultimately utilized by End User, whether as stand-alone products orpre-installed on Hardware. Hardware means the standard hardware originallysold by Avaya and ultimately utilized by End User.

License types Designated System(s) License (DS):

End User may install and use each copy of the Software on onlyone Designated Processor, unless a different number ofDesignated Processors is indicated in the Documentation or other

materials available to End User. Avaya may require the DesignatedProcessor(s) to be identified by type, serial number, feature key,location or other specific designation, or to be provided by EndUser to Avaya through electronic means established by Avayaspecifically for this purpose.

Concurrent User License (CU):End User may install and use the Software on multiple DesignatedProcessors or one or more Servers, so long as only the licensednumber of Units are accessing and using the Software at any giventime. A Unit means the unit on which Avaya, at its sole discretion,bases the pricing of its licenses and can be, without limitation, anagent, port or user, an e-mail or voice mail account in the name of aperson or corporate function (e.g., webmaster or helpdesk), or adirectory entry in the administrative database utilized by the

Software that permits one user to interface with the Software. Unitsmay be linked to a specific, identified Server.

Named User License (NU):End User may: (i) install and use the Software on a singleDesignated Processor or Server per authorized Named User(defined below); or (ii) install and use the Software on a Server solong as only authorized Named Users access and use theSoftware. Named User means a user or device that has beenexpressly authorized by Avaya to access and use the Software. AtAvaya's sole discretion, a Named User may be, without limitation,designated by name, corporate function (for example, webmasteror helpdesk), an e-mail or voice mail account in the name of aperson or corporate function, or a directory entry in theadministrative database utilized by the Software that permits one

user to interface with the Software. Shrinkwrap License (SR):Customer may install and use the Software in accordance with theterms and conditions of the applicable license agreements, such asshrinkwrap or clickthrough license accompanying or applicableto the Software (Shrinkwrap License). (See Third-partyComponents for more information).

Copyright

Except where expressly stated otherwise, no use should be made of materialson this site, the Documentation(s) and Product(s) provided by Avaya. Allcontent on this site, the documentation(s) and the product(s) provided byAvaya including the selection, arrangement and design of the content is ownedeither by Avaya or its licensors and is protected by copyright and otherintellectual property laws including the sui generis rights relating to theprotection of databases. You may not modify, copy, reproduce, republish,upload, post, transmit or distribute in any way any content, in whole or in part,including any code and software. Unauthorized reproduction, transmission,dissemination, storage, and or use without the express written consent of

Avaya can be a criminal, as well as a civil, offense under the applicable law.Third Party Components

Certain software programs or portions thereof included in the Product maycontain software distributed under third party agreements (Third PartyComponents), which may contain terms that expand or limit rights to usecertain portions of the Product (Third Party Terms). Information regardingdistributed Linux OS source code (for those Products that have distributed theLinux OS source code), and identifying the copyright holders of the Third PartyComponents and the Third Party Terms that apply to them is available on theAvaya Support Website: http://support.avaya.com/Copyright.

Preventing toll fraud

Toll fraud is the unauthorized use of your telecommunications system by anunauthorized party (for example, a person who is not a corporate employee,agent, subcontractor, or is not working on your company's behalf). Be awarethat there can be a risk of toll fraud associated with your system and that, if tollfraud occurs, it can result in substantial additional charges for yourtelecommunications services.

Avaya fraud intervention

If you suspect that you are being victimized by toll fraud and you need technicalassistance or support, call Technical Service Center Toll Fraud InterventionHotline at +1-800-643-2353 for the United States and Canada. For additionalsupport telephone numbers, see the Avaya Support Website:

http://www.support.avaya.com/.

Suspected security vulnerabilities with Avaya products should be reported toAvaya by sending mail to:[email protected].

Trademarks

Avaya and Avaya Aura are trademarks of Avaya Inc.

The trademarks, logos and service marks (Marks) displayed in this site, thedocumentation(s) and product(s) provided by Avaya are the registered orunregistered Marks of Avaya, its affiliates, or other third parties. Users are notpermitted to use such Marks without prior written consent from Avaya or suchthird party which may own the Mark. Nothing contained in this site, thedocumentation(s) and product(s) should be construed as granting, byimplication, estoppel, or otherwise, any license or right in and to the Marks

without the express written permission of Avaya or the applicable third party.All non-Avaya trademarks are the property of their respective owners.

Downloading documents

For the most current versions of documentation, see the Avaya SupportWebsite: http://www.avaya.com/support.

Contact Avaya Support

Avaya provides a telephone number for you to use to report problems or to askquestions about your product. The support telephone number is1-800-242-2121 in the United States. For additional support telephonenumbers, see the Avaya Website:http://www.avaya.com/support.
http://www.avaya.com/supporthttp://support.avaya.com/licenseinfo/http://support.avaya.com/Copyrighthttp://www.support.avaya.com/mailto:[email protected]://www.avaya.com/supporthttp://www.avaya.com/support/mailto:[email protected]://www.support.avaya.com/http://support.avaya.com/Copyrighthttp://support.avaya.com/licenseinfo/http://www.avaya.com/supporthttp://www.avaya.com/support/http://www.avaya.com/support

8/8/2019 16-300140_6

3/60

Issue 6 May 2009 3

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 . . . . . . 14Avaya 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 . . . . . . . . . . 22Setting 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

Contents

8/8/2019 16-300140_6

4/60

Contents

4 SES Implementation Guide

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

Advanced SIP trunk administration . . . . . . . . . . . . . . . . . . . . . . . . . 31

Other scenarios for using an SES system . . . . . . . . . . . . . . . . . . . . . . 32

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

Compatibility Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Avaya one-X Deskphone SIP for 9600 series telephones. . . . . . . . . . . . . 34

Setting parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Avaya 4602/4602SW, 4610SW and 4620SW/4621SW SIP telephones . . . . . . . 36

Setting parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Setting up Avaya softphone clients . . . . . . . . . . . . . . . . . . . . . . . . . 38

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

Connecting to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Accessing the System Management Interface. . . . . . . . . . . . . . . . . . 40Copying files to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Resolving alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Backing up recovery system files . . . . . . . . . . . . . . . . . . . . . . . . 41

Verifying the backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Suppressing alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Disabling the boot timeout of the SAMP board . . . . . . . . . . . . . . . . . 42

Upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Inserting the SES CD into the server . . . . . . . . . . . . . . . . . . . . . . . 43

Upgrading SES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Installing a new release of SES from the local hard drive . . . . . . . . . . . 44Rebooting the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Verifying reboot progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Verifying software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Checking system status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Making the upgrade permanent on the server . . . . . . . . . . . . . . . . . 48

Installing security and SES service packs, if any . . . . . . . . . . . . . . . . 48

Installing the authentication file . . . . . . . . . . . . . . . . . . . . . . . . . 49

Upgrading a Cable Duplicated Server Pair. . . . . . . . . . . . . . . . . . . . 49

Upgrading a Network Duplicated Server Pair . . . . . . . . . . . . . . . . . . 50

8/8/2019 16-300140_6

5/60

Contents

Issue 6 May 2009 5

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

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

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

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

8/8/2019 16-300140_6

6/60

Contents


8/8/2019 16-300140_6

7/60

Issue 6 May 2009 7

About this document

Overview

ThisAvaya Aura SIP Enablement Services (SES) Implementation Guide provides referencesto the documentation needed to deploy the Avaya SES solution with Avaya SIP IP telephonyproducts.

This document is a road map.

Intended audienceThis document is for field technicians, services technicians, and installers who are deploying theAvaya SES solution over an IP telephony network.

Using this document

Use this document as a reference point for deploying the Avaya SES solution. The document ishigh-level, task-oriented and guides you through the documentation that contains installation,

administration, and deployment instructions for all of the components of the Avaya SESsolution.

Document tables

At the beginning of each chapter, related documents are listed in a table as follows:

Table 1: Related documents

Document Title Document ID

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

4610SW SIP Telephone User's Guide 16-300472

4610SW SIP Telephone Quick Reference 16-300473

8/8/2019 16-300140_6

8/60

About this document


Reference points

A key component of this documentation is the reference point. The reference point refers to thedocument that has the information that is needed to complete the task at hand.

Reference pointSetting up SES server(s)

For detailed instructions on the initial setup of Avaya SIP Enablement Services on astandalone S8500-series server, refer to this document:

Installing, Administering, Maintaining, and Troubleshooting Avaya Aura SIP EnablementServices, 03-600768, Chapter 3: "Setup and configuration""Configuring a new server".

The sample reference point above refers to the Avaya document, the relevant chapter within thedocument, and the section heading within the chapter to complete the task.

Related sources

The following documents are referenced within this document:

Avaya application notes

Administering Network Connectivity on Avaya Aura Communication Manager,555-233-504

Administering Avaya Aura SIP Enablement Services on the Avaya S8300 Server,

03-602508 Installing, Administering, Maintaining, and Troubleshooting Avaya Aura SIP Enablement

Services, 03-600768

Avaya Toll Fraud and Security Handbook, 555-025-600

Security and the Avaya S8700 Media Servers, Avayawhite paper, Resource Library

Avaya one-X Deskphone Edition for 9600 Series SIP IP Telephones Installation andMaintenance Guide, 16-601943

Avaya one-X Deskphone Edition for 9600 Series SIP IP Telephones AdministratorGuide, 16-601944

Avaya one-X Deskphone SIP for 9620 IP Telephone User Guide, 16-601945 Avaya one-X Deskphone SIP for 9630/9630G IP Telephone User Guide, 16-601946

Avaya one-X Deskphone SIP for 9640/9640G IP Telephone User Guide, 16-602403

Avaya one-X Deskphone SIP for 9620 IP Telephone Quick Reference, 16-601947

8/8/2019 16-300140_6

9/60

Conventions used in this document

Issue 6 May 2009 9

Avaya one-X Deskphone SIP for 9630/9630G IP Telephone Quick Reference,16-601948

Avaya one-X Deskphone SIP for 9640/9640G IP Telephone Quick Reference,16-602408

Avaya one-X Desktop Edition Quick Setup Guide

Avaya one-X Desktop Edition Getting Started

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

Getting Started with Avaya Call Center and Avaya Agent Deskphone 16CC, 129214

Avaya Agent Deskphone 16CC Quick Reference, 16-602097

Avaya Agent Deskphone 16CC Administrator Guide, 16-602093

Avaya Agent Deskphone 16CC Installation and Maintenance Guide, 16-602095

Avaya Agent Deskphone 16CC User Guide, 16-602096

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

Avaya 4600 Series IP Telephone Installation Guide, 555-233-128

Avaya 4602/4602SW SIP Telephone Users Guide, 16-300035

Avaya 4602/4602SW SIP Telephone Quick Reference, 16-300471

Avaya 4610SW SIP IP Telephone Users Guide, 16-300472

Avaya 4610SW SIP IP Telephone Quick Reference, 16-300473

Avaya 4620SW/4621SW SIP IP Telephone Users Guide, 16-300474

Avaya 4620SW/4621SW SIP IP Telephone Quick Reference, 16-300475

Avaya Extension to Cellular Users Guide, 210-100-700

Avaya Extension to Cellular and Off-PBX Station (OPS) Installation and AdministrationGuide, 210-100-500

Avaya Server Availability Management Processor User Guide (SAMP), 03-300322

Conventions used in this document

Become familiar with the following terms and conventions.

Media serverIn the SES solution, Avaya media servers may be S8300, S8400, S8500series, or S8710 series. When this document refers to a media server, it means aLinux-based media server running Avaya Communication Manager R3.1 or later.

8/8/2019 16-300140_6

10/60

About this document


Commands are printed in bold face as follows: command.

We show complete commands in this book, but you can usually type an abbreviated versionof the command. For example, list configuration station can be typed as listconfig sta.

Screen displays and names of fields are printed in constant width as follows: screen

display.

A screen is any form displayed on your computer or terminal monitor.

Variables are printed in constant width, bold, italic: variable.

Keys and buttons are printed as follows: KEY.

To move to a certain field, you can use the TAB key, arrows, or the ENTER key (the ENTERkey may appear as the RETURN key on your keyboard).

In this book we use the terms telephone and voice terminal to refer to phones.

Reference pointDefined

The reference point refers to any related documentation that details the tasks at hand.

Tips look like this:

Tip:

Tip: Draws attention to information that you may find helpful.

Notes look like this:

Note:

Note: A general note calls attention to neutral information or positive information thatsupplements the main text.

Cautions look like this:

! CAUTION:

CAUTION: Denotes possible harm to software, possible loss of data, or possible serviceinterruptions.

8/8/2019 16-300140_6

11/60

Issue 6 May 2009 11

Chapter 1: SES Solution Overview

This chapter provides an overview of the process and components needed to deploy an Avaya

IP convergence solution using Session Initiation Protocol (SIP) as its enabling technology.SIP is a text-based protocol that is designed to set up, modify, and tear down communicationsessions between users. Once sessions are established, the content of these sessions can bevoice, video, instant messaging, or any other communications method.

SIP, an Internet-centric protocol that provides basic functionality beyond that of H.323, wasoriginally designed to place the intelligence in the endpoints rather than within the network.Practical necessity requires that some intelligence be in the network. SIP architecture promisesincreased resiliency, scalability, and rapid application development.

Presently, Avayas SIP Enablement Services (SES) solution offers these advantages:

The ability to make and receive SIP telephone calls

Many advanced features and services Secure instant messaging

To subscribe to and receive presence notifications.

This document outlines how to deploy an SES solution.

Reference pointSystem architecture, server requirements, and local failover

Installing, Administering, Maintaining, and Troubleshooting SIP Enablement Services,03-600768, Chapter 3: "Introduction",provides details of the SES solution architecture andtopography, server hardware and software requirements, and local failover design.

The tasks required to deploy this solution are described in this document, in these sections:

1. Set up the server(s) running Avaya Communication Manager.

See Chapter 2: Setting up the Communication Manager serveron page 21.

2. Install and configure Avaya SIP Enablement Services on the SES server(s).

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

3. Integrate Communication Manager, SIP Enablement Services, and the 4600/9600 seriesSIP IP telephones via Extension to Cellular and Off-PBX Station (OPS) mapping.

See Setting up OPS stations on page 30.

4. Establish SIP Trunks on the server running Communication Manager.

See Chapter 4: Establishing SIP trunks in Communication Manageron page 31.

5. Configure supported SIP IP telephones for use with the SES solution.

See Chapter 5: Setting up a SIP Endpoint on page 33.

8/8/2019 16-300140_6

12/60

SES Solution Overview


Reference pointCo-resident system architecture and server requirements

Administering SIP Enablement Services on the Avaya S8300 Server, 03-602508, providesdetails of the SES solution architecture and topography, server hardware and softwarerequirements, and local failover design.

Overview of Avaya SES solution components

The Avaya SIP Enablement Services (SES) solution consists of the following components:

Avaya SIP Enablement Services serveror servers

One (or more) Servers running Avaya Communication Manager 5.0

Gateways

SIP endpoints:

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

- Avaya 4600 Series IP Telephones supporting SIP

- Avaya softphones, including one-X Desktop Edition

Third-party SIP clients

Avaya SIP Enablement Services server

The SES application runs standalone on Avayas S8500-series hardware platform. This

platform supports Edge, Home, and combination Home/Edge servers. The SES application alsosupports the Avaya S8300C Server, running co-resident with Avaya Communication Manager5.0 or later releases. In this configuration, only Home and Home/Edge SES server types aresupported.

The SES edge server is dedicated to performing proxy, registration, and redirection functionsassociated with SIP applications, such as instant messaging. When the SES home servercommunicates with one or more servers running Communication Manager, communicationbetween and among the various non-SIP endpoints is supported. Endpoints supported byCommunication Manager include analog, DCP or H.323 stations and analog, digital or IPtrunks, as well as SIP-enabled endpoints. SIP-enabled endpoints may be any from this list:

Avaya 9600 Series one-X Deskphone, Avaya 4600 Series SIP IP telephones or Avaya

Agent Deskphone 16CC

Avaya one-X Desktop Edition Release 2 or later (or Avaya SIP Softphone)

Avaya IP Softphone Release 5.1 and later with the IM client

8/8/2019 16-300140_6

13/60


Issue 6 May 2009 13

SIP-enabled endpoints must register with the SES server. Although technically an Avaya IPSoftphone is not managed by Communication Manager, it is required to register H.323 with theserver running Avaya Communication Manager. Although IP softphones use H.323 for voice,SIP is also used for communications. For example, instant messages on IP softphones use SIP.

Reference pointSystem requirements, installation and administration for

standalone SES servers

The document Installing, Administering, Maintaining, and Troubleshooting SIP EnablementServices, 03-600768, provides detailed system requirements, installation instructions, andadministrative tasks for S8500 series servers running SES. See the respective chapters.

System requirements - Chapter 3: "Introduction to SIP and SIP Enablement Services"

Installation - Chapter 4: "Setup and configuration"Chapter 5: "Getting ready to install SES"One or more of chapters 7-21, depending on your hardware configuration

Administration - Chapter 4: "Setup and configuration""Installation checklist"Chapter 4: "Setup and configuration""Post installation tasks"

Administration in general - Chapter 22: "Administration web interface"

Servers running Avaya Communication Manager 5.0

Avayas SES solution can be deployed with Communication Manager running on Avaya S8300,S8400, S8500-series, and the S8700-series servers. These hardware elements deliverapplication-enabling data, voice, fax, video and messaging capabilities to your network. Theysupport both bearer and signaling traffic routed between packet-switched and circuit-switchednetworks. The gateways are optimized for use with enterprise class telephony and provide a

variety of flexible deployment options. Options include both partial environments, such as IPand TDM, and fully IP environments.

Features for SIP in Avaya Communication Manager 5.0 running on an Avaya media serverinclude these:

SIP trunking

SIP stations

Call Detail Record (CDR) support

Access control

Routing and dial plan

8/8/2019 16-300140_6

14/60



Gateways

The Avaya SIP Enablement Services solution can be deployed with any of the Avaya gatewayssupporting S8xxx.

Avaya one-X Deskphone supporting SIP for 9600 Series phones

Verify that you have up-to-date firmware for your supported SIP endpoints by going to this website:

http://www.avaya.com/support/

Then select the link forDownloads underMost Visited Support Areas. See the latest 9600Series one-X Deskphone SIP telephone documentation for more details.

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

The 9600 Series SIP telephone is a fully featured SIP device also utilizing the features ofCommunication Manager through SIP Enablement Services.

This telephone employs standards-based SIP telephony call control, allowing integrationinto multi-vendor telephony environments using SIP.

The simple H.323 to SIP firmware upgrade provides a migration path to SIP thatmaximizes investment protection.

Note:

Note: The 9600 Series SIP telephone incorporates a SIP stack. The telephone

registers with a server running SIP Enablement Services (SES) software andcommunicates through the server with Communication Manager for call control.

See Other scenarios for using an SES system on page 32 for more information on multi-vendorSIP telephony deployments.

Converting Avaya 9600 Series telephones to one-X Deskphone SIP

SIP can be deployed on the Avaya 9620, 9630/9630G, 9640/9640G telephones. Avaya shipsthese phones from the factory and they contain the latest load of H.323 software. To use anH.323 phone with SES, you must convert the H.323 phone to a SIP phone.

Reference PointEnhancing 9600 Series H.323 IP telephones to SIP telephones

For detailed instructions on enhancing the software on the Avaya 9600 Series IPtelephones to one-X Deskphone SIP, refer to the documentAvaya one-X DeskphoneEdition for 9600 Series SIP IP Telephones R2.x Installation and Maintenance Guide,16-601943, Chapter 2: "9600 Series SIP IP Telephone Installation""Converting Software
http://www.avaya.com/support/http://www.avaya.com/support/

8/8/2019 16-300140_6

15/60


Issue 6 May 2009 15

on 9600 Series IP Telephones".For more information about administering and installing the phones, see the nextReference point.

Reference pointSystem requirements, installation and administration for 9600Series SIP IP telephones

TheAvaya one-X Deskphone Edition for 9600 Series SIP IP Telephones R2.xAdministrator Guide, 16-601944 provides detailed tasks associated with administering the9600 Series SIP IP telephone for use.

A separateAvaya one-X Deskphone for 9600 Series SIP IP Telephone Quick Referencefor each of the 9620, 9630/9630G, and 9640/9640G IP Telephones provides installationinstructions and initial configuration tasks.

A separateAvaya one-X Deskphone SIP for 9600 Series SIP IP Telephones R2.x UserGuide for each of the 9620, 9630/9630G, and 9640/9640G IP Telephones providesdetailed tasks associated with using the phone.

Avaya 4600 Series IP Telephones supporting SIP

Verify that you have up-to-date firmware for your supported SIP endpoints by going to this website:

http://www.avaya.com/support/

Then select the link forDownloads underMost Visited Support Areas. For the 4602, you mayneed to migrate your H.323 firmware from 1.8.x to 2.2 before converting the phone toSIP firmware. See the latest 4600 Series IP telephone documentation for more details.

Key benefits of an Avaya 4600 Series SIP telephone

The 4600 Series SIP telephone is economical and can utilize the features ofCommunication Manager through SIP Enablement Services.

This telephone employs standards-based SIP telephony call control and so allowsintegration into multi-vendor telephony environments using SIP.

The simple H.323-to-SIP firmware upgrade provides a migration path to SIP thatmaximizes investment protection.

Note:

Note: The 4600 Series SIP telephone incorporates a SIP stack. The telephoneregisters with a server running SIP Enablement Services (SES) software andcommunicates through the server with Communication Manager for call control.

See Other scenarios for using an SES system on page 32 for more information on multi-vendorSIP telephony deployments.
http://www.avaya.com/support/http://www.avaya.com/support/

8/8/2019 16-300140_6

16/60



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

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


For detailed instructions on enhancing the software on the Avaya 4600 Series SIP IPtelephones, refer to the document 4600 Series IP Telephone R2.2 Installation Guide,555-233-128, Chapter 2: "4600 Series IP Telephone Installation""Converting Softwareon Avaya 4600 Series IP Telephones".

Reference pointSystem requirements, installation and administration for 4602SIP telephones

TheAvaya 4602/4602SW SIP Telephone Users Guide, 16-300035provides detailed

tasks associated with using the 4602 or 4602SW SIP telephone. TheAvaya 4602/4602SW SIP Telephone Quick Reference, 16-300471 provides

installation instructions and initial configuration tasks for the 4602/4602SW SIP telephone.

Reference pointSystem requirements, installation and administration for4610SW SIP telephones

TheAvaya 4610SW SIP IP Telephone Users Guide, 16-300472provides detailed tasksassociated with using the 4610SW SIP Telephone.

TheAvaya 4610SW SIP IP Telephone Quick Reference, 16-300473 provides installationinstructions and initial configuration tasks for the 4610SW SIP.

Reference pointSystem requirements, installation and administration for4620SW/4621SW SIP telephones

TheAvaya 4620SW/4621SW SIP IP Telephone Users Guide, 16-300474 providesdetailed tasks associated with using the 4620SW or 4621SW SIP telephone.

TheAvaya 4620SW/4621SW SIP IP Telephone Quick Reference, 16-300475providesinstallation and initial configuration tasks for the 4620SW or 4621SW SIP telephone.

8/8/2019 16-300140_6

17/60


Issue 6 May 2009 17

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 SESsolution, you must add the IM client module software to the IP softphone or the IP Agentsoftware. The SIP softphone client software is SIP-enabled with IM capability.

Reference PointEnhancing H.323 IP softphones to IM-enabled softphones

For detailed instructions on enabling the Avaya IP Softphone client software to include theSIP-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 EditionSIP softphone 2.x clients. To deploy the one-X Desktop Edition SIP Softphone solution, theclient software must be installed on the SIP users PC by an administrator of that PC.

The deskphone must have the current version of SIP firmware for the Avaya telephone.

Reference PointInstalling and configuring the Avaya SIP Softphone

For detailed instructions on installing the Avaya one-X Desktop Edition SIP Softphone clientsoftware, refer to the SIP softphone applications 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.documentID=252143&temp.selectedRelease=252204

8/8/2019 16-300140_6

18/60



Third-party SIP clients

The Toshiba SIP Business Phone, model SP-1020A, is fully supported within the Avaya SESsolution. See the documentation for your TSP phone for more information.

Avaya supports and troubleshoots other third-party SIP clients that have been chosen andcompleted testing by Avayas Solution and Interoperability Test Lab (SITL), and is documentedin 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 Avayas DevConnect to betested 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 thepage.

Then select Application Notes underResource Type. You may filter your results by the termSIP, or by the specific product name or model of your third-party software or equipment.
http://www.avaya.com/gcm/master-usa/en-us/corporate/alliances/devconnect/index.htmhttp://www.avaya.com/http://www.avaya.com/http://www.avaya.com/gcm/master-usa/en-us/corporate/alliances/devconnect/index.htm

8/8/2019 16-300140_6

19/60

Security

Issue 6 May 2009 19

Security

Because SES is an Avaya product, and because it operates in conjunction with AvayaCommunication 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.

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 thatencrypts all messages between the web server and a browser. Unique server certificatescan be generated and installed on the SES server.

The SES firewall is configurable to permit only the necessary network services andapplications.

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 failedlogins. 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. SIPsignaling to and from Communication Manager is protected using TLS.

Telephony end users are authenticated using SIP digest authentication.

Table 2: Documents that relate to security


Avaya Toll Fraud and Security Handbook 555-025-600

Security and the Avaya Communication Manager MediaServers

Technical Supportwhite paper for AvayaCommunicationManager software

8/8/2019 16-300140_6

20/60



8/8/2019 16-300140_6

21/60

Issue 6 May 2009 21

Chapter 2: Setting up the Communication Manager

server

When setting up one or more server(s) running Communication Manager to accommodate andsupport the Avaya SES solution, you will need to have these references available:

Avaya Communication Manager runs on the following servers:

Avaya S8300 Server, with or without Avaya SES running co-resident with it

Avaya S8400 Server

Avaya S8500-series Servers

Avaya S8700-series Servers.

Note:

Note: Prior to enabling SIP/SES on the server(s) running Communication Manager, IPconnectivity must be configured correctly. For details, refer toAdministeringNetwork Connectivity on Avaya Aura Communication Manager.

Table 3: Documents required for setting up Communication Manager servers


Administering Network Connectivity on Avaya AuraCommunication Manager

555-233-504

Getting Started with Avaya Aura SIP Softphone,Administration and Provisioning

Available fromyour Avaya

representativeInstalling, Administering, Maintaining, and Troubleshooting

Avaya Aura SIP Enablement Services03-600768

Administering Avaya Aura SIP Enablement Services on theAvaya S8300 Server

03-602508

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

8/8/2019 16-300140_6

22/60

Setting up the Communication Manager server


Setting up the Avaya server

As noted above, prior to setting up an Avaya server for SIP, you must configure IP connectivitycorrectly. After IP connectivity has been configured, complete the following tasks:

Setting up SIP support in Avaya Communication Manageron page 22

Setting up the server(s) running SES on page 27

If applicable for your SIP clients, Setting up Click to Conference on page 25

If applicable for your SIP endpoints, Setting up Advanced SIP Telephony on page 25

And, if applicable, Setting up Modular Messaging as an adjunct system on page 26.

Reference pointList of related documents

For information on correctly configuring IP connectivity on your server, refer toAdministering Network Connectivity on Avaya Aura Communication Manager. Many

sections in this document discuss this topic.

For information on setting up standalone Avaya SES server(s), refer to Installing,Administering, Maintaining, and Troubleshooting Avaya Aura SIP Enablement Services:

Chapter 4: "Setup and configuration""Pre installation checklist", and "Post installationtasks"

One or more of chapters 7-22: "Installation procedures""Administer CommunicationManager and endpoints"

For information on setting up co-resident Avaya S8300C server(s) for SES, refer toAdministering Avaya Aura SIP Enablement Services on the Avaya S8300 Server.

For information on setting up Avaya Communication Manager, refer to SIP Support inAvaya Aura Communication Manager, Chapter 2: "Administering SIP in AvayaCommunication Manager".

Setting up SIP support in Avaya Communication Manager

Avayas SES solution can be deployed with the S8300, S8400, S8500-series, and theS8700-series servers running Communication Manager. These hardware elements deliverapplication-enabling data, voice, fax, video and messaging capabilities to your network. They

support both bearer and signaling traffic routed between packet-switched and circuit-switchednetworks. The gateways are optimized for use with enterprise class telephony and to provide avariety of flexible deployment options. Options include partial environments, such as both IPand TDM, as well as full IP environments with H.323 and SIP endpoints.

With Avaya Communication Manager, SIP features include these:

8/8/2019 16-300140_6

23/60

Setting up the Avaya server

Issue 6 May 2009 23

SIP trunking

SIP stations

Call Detail Recording (CDR)

Profile-based access control

Call routing

Enterprise dial plan.

SIP trunking

Support for SIP trunks allows an enterprise to connect its Avaya Communication Managerservers to a SIP-enabled proxy server running Avaya SIP Enablement Services (SES), andthrough that proxy to an external SIP service provider, if desired. The trunk support in AvayaCommunication Manager complies with SIP standards IETF RFC 3261 and interoperates withany SIP-enabled endpoint that also complies with the standard.

In complex configurations with Avaya S8700-series servers, SIP signaling-group properties inCommunication Manager must be administered to match each other in certain, specific ways.

SIP stations

Support for SIP stations using SIP trunks allows any fully compliant SIP phone to interoperatewith Avaya phones. This means any SIP phone, from Avaya or a third party, that complies withthe appropriate RFC or draft service standards can do the following:

Dial and be dialed as an extension in the enterprise dial plan. Outboard Proxy SIP (OPS)stations support additional features as well, like bridging.

Put calls on hold and participate in transfers and conference calls.

Reference pointOPS

For more details on OPS installation, refer to these documents:

- Avaya Extension to Cellular Users Guide, 210-100-700

- Avaya Extension to Cellular and OPS Installation and Administration Guide, 210-100-500

Reference pointModular Messaging

For using Modular Messaging as an adjunct system to SES, see the applicable SESinstallation and administration guide: Installing, Administering, Maintaining, and

Troubleshooting Avaya Aura SIP Enablement Services , Chapter 22: "AdministrationWeb Interface""Adjunct Systems", or see the documentAdministering Avaya AuraSIP Enablement Services on the Avaya S8300 Server.

8/8/2019 16-300140_6

24/60



Access control

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

8/8/2019 16-300140_6

25/60

Setting up Click to Conference

Issue 6 May 2009 25

Reference pointSetting up Communication Manager servers

All necessary information for setting up the servers with Avaya Communication Manager isdetailed in SIP Support in Avaya Aura Communication Manager. Specific topics in thisdocument are as follows:

For hardware and software requirements, refer to Chapter 2: "Administering SIP in Avaya

Communication Manager""Requirements for SIP".

For setting up and configuring SIP trunks in Communication Manager, refer to Chapter 3:"Administering Communication Manager for SIP Enablement Services".

Routing and Dial Plan

The final step before you make SIP calls from endpoints connected to Communication Manageris to administer call routing properly on the Avaya Communication Manager servers. Thisinvolves several screens, including for example the Locations, Numbering, and RoutePattern screens.

Reference pointAdministering SIP call routing in Communication Manager

Information for administering call routing on the servers with Communication Manager isdetailed in SIP Support in Avaya Aura Communication Manager. Refer to Chapter 3:"Administering Communication Manager for SIP Enablement Services".

Setting up Click to Conference

For information on how to administer the click-to-conference feature of SES, obtain this Avayadocument:

Getting Started with Avaya SIP Softphone, Administration And Provisioning, available from yourAvaya representative.

Setting up Advanced SIP Telephony

For application notes on how to set up SES for use with Advanced SIP Telephony, go to Avayas

web site:http://www.avaya.com and select Do Your Research: Resource Library in the middle of thepage.

Then select the link forApplication Notes underResource Type. Filter the results for AST, orthe specific product supporting advanced SIP telephony in which you are interested.
http://www.avaya.com/http://www.avaya.com/

8/8/2019 16-300140_6

26/60



Setting up Modular Messaging as an adjunct system

For administration guidance on how to implement Avayas Modular Messaging product as anadjunct system in an SES solution, refer to the following resources:

Installing, Administering, Maintaining, and Troubleshooting Avaya Aura SIP EnablementServices , Chapter 22: "Administration Web Interface""Adjunct Systems".

Configuration Note 88010This note will be published on the Avaya support web site. Searchthe Configuration Notes Master Index, or for PSN #1186U on SIP and MM Adjunct integration.

8/8/2019 16-300140_6

27/60

Issue 6 May 2009 27

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

When working with the server(s) with SES installed, you might use these references:

Configuring the server running SES

All servers running SIP Enablement Services, that is, the SIP proxy servers, must be properlyconnected to, and configured on, an enterprises IP network. Appendix C: Worksheet forinstallation on page 55 provides a complete list of the information you need to answer questionswhen prompted by the install script.

Note for SES X.0 to SES X.1 upgrades: - If you are upgrading from SES R3.0 to SES R3.1,or R4.0 to 4.0.1, use the three Server Upgrade screens in the maintenance interface of SES.These screens may not be used to upgrade and migrate directly from SES R3.x to R5.0 or later.

Trunking

For endpoint clients on Avaya Communication Manager to interoperate through the Avaya SESserver, SIP trunking must be administered properly on the server running the CommunicationManager software. Refer to SIP Support in Avaya Communication Manager, 555-245-206,Chapter 3: "Administering Communication Manager for SIP Enablement Services" for more

details. This administration requires that you specify several values, including: Network names of the SES hosts on the IP Node Names screen

Authoritative domain assigned to server(s) on the IP Network Region screen.

Additional administration of call routing may be required, depending on current server values.

Table 4: Documents required for setting up an Avaya SES server


Installing, Administering, Maintaining, and TroubleshootingAvaya Aura SIP Enablement Services

03-600768

Administering Avaya Aura SIP Enablement Services on theAvaya S8300 Server

03-602508

Avaya Extension to Cellular and OPS Installation andAdministration Guide

210-100-500

8/8/2019 16-300140_6

28/60

Setting up the server(s) running SES


Note:

Note: For 4600 Series and 9600 Series SIP IP Telephones, the same authoritativedomain must be specified in the phones settings file(s) as on the IP NetworkRegion screen. Also, unlike the H.323 versions of these IP telephones, theSIP versions must have working IP network access to their respective TFTP orHTTP servers upon startup. SES access is required for phone registration.

Task list for configuring server(s) for SES

Table 5 lists the tasks necessary to configure a standalone server for SES. For greater detailabout each task, refer to the documents that correspond with each task listed in the table.

Note:

Note: For greater detail about the tasks necessary to configure a co-resident serverrunning Communication Manager to run SES as well, refer toAdministering

Avaya Aura SIP Enablement Services on the Avaya S8300 Server.

Table 5: Configuration task list for standalone server(s) running SES

Task Reference document

Perform initial assembly andsetup.

Installing, Administering, Maintaining, andTroubleshooting Avaya Aura SIPEnablement Services

Chapter 4: "Setup andconfiguration""Configuring a newserver"

Chapter 4: "Setup and

Configuration""Pre-installation tasks"Install all server software. Installing, Administering, Maintaining, and

Troubleshooting Avaya Aura SIPEnablement Services

Chapters 7-21: "Installation Procedures"

Perform administrative taskson the server by way of aPoint to Point Protocol (PPP)session.

Installing, Administering, Maintaining, andTroubleshooting Avaya Aura SIPEnablement Services

Chapter 4: "Setup andconfiguration""Installation checklist"

Chapter 4: "Setup andconfiguration""Post installation

checklist"

1 of 2

8/8/2019 16-300140_6

29/60

Creating SIP users in the SES system

Issue 6 May 2009 29

Creating SIP users in the SES system

To create users in the SES system, you must access the web-based user interface and performthe necessary tasks in the following reference point.

Reference pointCreating users via the user screens in SES

For creating a new SIP user in your SES solution, refer to Installing, Administering,Maintaining, and Troubleshooting Avaya Aura SIP Enablement Services

For server administration of users, refer to Installing, Administering, Maintaining, andTroubleshooting Avaya Aura SIP Enablement Services

For loading users in bulk with ProVision, refer to Installing, Administering, Maintaining, andTroubleshooting Avaya Aura SIP Enablement Services

Also refer to ProVisions help subsystem and also to the Notepad newsletter, available from theProVision web sites Document Center. Log in to ProVision at this web site:

http://www.avaya.com/support/iProVision/

Install the server license byway of WebLM.

Installing, Administering, Maintaining, andTroubleshooting Avaya Aura SIPEnablement ServicesChapters 7-21: "InstallationProcedures""Server license installation"

Deliver the authentication fileby way of the AutomaticRegistration Tool (ART).

Installing, Administering, Maintaining, andTroubleshooting Avaya Aura SIPEnablement ServicesChapter 4: "Setup and Configuration""Loadthe authentication file"

Table 5: Configuration task list for standalone server(s) running SES (continued)

Task Reference document

2 of 2
http://www.avaya.com/support/iProVision/http://www.avaya.com/support/iProVision/

8/8/2019 16-300140_6

30/60

Setting up the server(s) running SES


Setting up OPS stations

Outboard Proxy SIP (OPS)

Beginning with Avaya Communication Manager Release 2.1, the Outboard Proxy SIP (OPS)application type is used to administer a SIP phone. OPS cannot be disabled using the

Extension to Cellular enable/disable feature button.Note:

Note: Any SIP phone or endpoint must have access to and register with the SIP proxy,regardless of whether OPS is administered in Communication Manager.

The Extension to Cellular/OPS application allows for many of the parameters used for theoriginal Extension to Cellular application to be ported onto one of several DCP and IP stationtypes. From a call processing perspective, Extension to Cellular/OPS is in fact dealing with amulti-function phone, whereas the previous Extension to Cellular implementation utilized one ortwo XMOBILE stations that behaved like analog station types.

Extension to Cellular/OPS supports these features:

Support for Session Initiation Protocol (SIP) phones

Administrative ability to map certain Communication Manager features to phoneextensions

Reference PointConfiguring Extension to Cellular and OPS for SIP

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

Table 6: Documents required for setting up Extension to Cellular and OPS


Avaya Extension to Cellular and OPS Installation andAdministration Guide

210-100-500

8/8/2019 16-300140_6

31/60

Issue 6 May 2009 31

Chapter 4: Establishing SIP trunks in

Communication Manager

When you set up the SIP trunks on the server running Communication Manager, use thesereferences to help you:

Session Initiated Protocol (SIP) is an endpoint-oriented messaging standard defined by theInternet Engineering Task Force (IETF). SIP trunking enables the Avaya servers runningCommunication Manager to function as a POTS gateway and to support the delivery of nameand number data between legacy endpoints (for example, DCP telephones) and SIP-enabledendpoints (for example, the new 9600 series IP telephones with one-X Deskphone SIP).

For more information on SIP administration and usage, see the overview and introductionchapters of the documents listed in the preceding table.

Advanced SIP trunk administration

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

Table 7: Documents required for establishing SIP trunks in CommunicationManager


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

Installing, Administering, Maintaining, and TroubleshootingAvaya Aura SIP Enablement Services

03-600768

8/8/2019 16-300140_6

32/60

Establishing SIP trunks in Communication Manager


Reference PointSIP Trunk Administration

To administer SIP trunks in Avaya Communication Manager, see SIP Support in AvayaAura Communication Manager, Chapter 3: "Administering Communication Manager forSIP""Administer SIP signaling and trunks". Capacities are as follows:

Note:Note: There is a maximum of 255 SIP trunks in a SIP signaling group.

Other scenarios for using an SES system

There are other scenarios in which SIP trunking can link an enterprises Avaya IP telephonynetwork with a third-party SIP service providers network. The service provider may employdifferent proxy servers, PSTN gateways and other equipment as part of these scenarios.

Avayas Solution and Interoperability Test Lab (SITL) tests other scenarios, and then documentsthem in Application Notes. However, Avaya does not provide installation, implementation,configuration, or maintenance of any third-party SIP IP equipment.

The SIP-enabled products of third parties must be submitted through the Avaya DevConnectprogram in order to be tested and ultimately designated as supported applications or devices.

For detailed information about the Avaya DeveloperConnection Program, go to the web site:

http://www.avaya.com/gcm/naster-usa/en-us/corporate/alliances/devconnect/index.htm

For application notes on which third-party SIP endpoints are supported, go to the web site:

http://www.avaya.com and select Do Your Research: Resource Library in the middle of the

page.

Then select the link forApplication Notes underResource Type. You may filter results usingSIP or the specific product name or model of third-party equipment in which you are interested.

Table 8: SIP Trunk capacity

Server Maximum AdministeredSIP Trunks

S8700 series 7000

S8500 series 800

S8400 400

S8300 450
http://www.avaya.com/gcm/master-usa/en-us/corporate/alliances/devconnect/index.htmhttp://www.avaya.com/http://www.avaya.com/gcm/master-usa/en-us/corporate/alliances/devconnect/index.htmhttp://www.avaya.com/

8/8/2019 16-300140_6

33/60

Issue 6 May 2009 33

Chapter 5: Setting up a SIP Endpoint

When you configure the endpoints for your SES system, use document tables Table 11 and

Table 12 in this section to guide you.

Compatibility Matrix

The following table summarizes the minimum version of SIP-enabled firmware required for eachof the supported Avaya telephones to operate properly with SES Release 5.0 software.

Confer with your Avaya representative and check the software downloads section of the AvayaSupport 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 SeriesSIP IP Telephones

Telephone Min. SIP Version

9620 IP telephone, one-X Deskphone SIP Release 2.0.x

9630/9630G IP telephone, one-X Deskphone SIP Release 2.0.x

9640/9640G IP telephone, one-X Deskphone SIP Release 2.0.x

4602 IP telephone SIP not supported

4602/4602SW SIP IP telephone Release 2.2

4610SW SIP IP telephone Release 2.2

4620SW/4621SW SIP IP telephone Release 2.2

8/8/2019 16-300140_6

34/60

Setting up a SIP Endpoint


Avaya one-X Deskphone SIP for 9600 series telephones

The 9600 Series SIP IP telephones cannot boot and then register with the SES server and in

the appropriate SIP domain unless they have network access to the TFTP or HTTP server.

If an SES solution includes 9600 Series IP telephones, the IP phones must be converted fromH.323 protocol to SIP. Then, their station records/extensions must be administered both inAvaya Communication Manager and as SIP users (with the associated server extension) inSES software. Finally, after parameters for the phones have been set properly, SIP calls may beplaced from the phones.


For detailed instructions on enhancing the software on the Avaya 9600 Series IPtelephones to one-X Deskphone SIP, refer to the documentAvaya one-X DeskphoneEdition for 9600 Series SIP IP Telephones R2.x Installation and Maintenance Guide,

16-601943, Chapter 2: "9600 Series SIP IP Telephone Installation""Converting Softwareon 9600 Series IP Telephones".

Table 10: Documents required for setting up the Avaya 9600 Series SIP Telephones


Avaya one-X Deskphone Edition for 9600 Series SIP IPTelephones R2.x Administrator Guide

16-601944

Avaya one-X Deskphone Edition for 9600 Series SIP IPTelephones R2.x Installation and Maintenance Guide

16-601943

Avaya one-X Deskphone SIP for 9620 IP Telephone QuickReference

16-601947

Avaya one-X Deskphone SIP for 9620 IP Telephone UserGuide

16-601945

Avaya one-X Deskphone SIP for 9630/9630G IP TelephoneQuick Reference

16-601948

Avaya one-X Deskphone SIP for 9630/9630G IP TelephoneUser Guide

16-601946

Avaya one-X Deskphone SIP for 9640/9640G IP TelephoneQuick Reference

16-602408

Avaya one-X Deskphone SIP for 9640/9640G IP TelephoneUser Guide

16-602403

8/8/2019 16-300140_6

35/60

Avaya one-X Deskphone SIP for 9600 series telephones

Issue 6 May 2009 35

Setting parameters

The 9600 Series SIP telephone has these basic tools and capabilities to assist administratorswith managing its settings and features:

The 96XXsettings.txt (or46XXsettings.txt) file, annotated with information forsetting most parameters

DHCP for setting some parameters

Downloadable configuration files for setting telephone parameters on startup

Manual programming of critical parameters from the telephones dial pad

Downloadable firmware updates (manual and automatic)

You can set a common set of parameters using DHCP, manual programming, and configurationfiles. Setting these parameters establishes the telephones operating parameters.

Avaya SIP telephones will not be able to register in an SES system unless they can obtain thecorrect SIPDOMAIN setting. Avaya SIP telephones include the 4600-series, the 9600-series,and the 16CC. The 46XX phones obtain the domain setting from the 46XXsettings.txtfile; youmay set up a separate 96XXsettings.txtfile for the 96XX phones, but the SIPDOMAIN settingmust be the same for your enterprise.

Always configure the SIPDOMAIN setting for the phones in the appropriate text file(s) and thenensure that the phones transfer settings from the file(s) via TFTP or HTTP during boot up.

The line in the file(s) for this setting is:

SET SIPDOMAIN = yourSIPdomainName.com

For application notes on configuring specific SIP endpoints, go to the web site:


Then select the link forApplication Notes underResource Type. You may filter the resultsusing the term SIP or the specific model number of your Avaya telephone.

8/8/2019 16-300140_6

36/60



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

SIP telephones

The 4600 Series SIP IP telephones cannot boot and then register with the SES server and inthe appropriate SIP domain unless they have network access to the TFTP or HTTP server.

If an SES solution includes 4600 Series IP telephones, the IP phones must be converted fromH.323 protocol to SIP. Then their station records must be administered as OPS inCommunication Manager and as SIP users with a server extension in SES software. Finally,after parameters for the phones have been set properly, SIP calls may be placed from the

phones.


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

Table 11: Documents required for setting up the Avaya 4600 Series SIP Telephones


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

4600 Series IP Telephone Installation Guide 555-233-128

4602/4602SW SIP Telephone Quick Reference 16-300471

4602/4602SW SIP Telephone Users 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

8/8/2019 16-300140_6

37/60

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

Issue 6 May 2009 37

Setting parameters

The 4600 Series SIP telephone has these basic tools and capabilities to assist administratorswith managing its settings and features:

The 46XXsettings.txt file, annotated with information for setting most parameters

DHCP for setting some parameters

Downloadable configuration files for setting telephone parameters on startup

Manual programming of critical parameters from the telephones dial pad

Downloadable firmware updates (manual and automatic)

You can set a common set of parameters using DHCP, manual programming, and configurationfiles. Setting these parameters establishes the telephones operating parameters.

For application notes on configuring SIP endpoints, go to the web site:


Then select the link forApplication Notes underResource Type. You may filter the resultsusing the term SIP or the specific model number of your Avaya telephone.

8/8/2019 16-300140_6

38/60



Setting up Avaya softphone clients

If an SES solution includes Avaya IP Softphone clients, the version of IP Agent or IP Softphoneincluding the SIP-enabled instant messaging and presence module must be used. Note thatthese clients manage presence information in a peer-to-peer fashion.

You must uninstall SIP softphone clients before installing one-X Desktop Edition Release 2.

Reference PointEnhancing H.323 IP softphones to IM-enabled softphones

For detailed instructions on how to include and enable the SIP-based instant messaging (withpresence) application in Avaya softphone client software, refer to IP softphone online help.

http://www.avaya.com/support > IP Agent > Avaya IP Agent Installation and User Guide

http://support.avaya.com/japple/css/japple?temp.documentID=280964&temp.productID=107698&temp.releaseID=235038&temp.bucketID=160259&PAGE=Document

If an SES solution includes Avaya one-X Desktop Edition or SIP softphone clients, then thesoftware must be installed and configured to use. Note that these clients manage their presenceinformation by means of the SIP Personal Information Manager running on an SES server.

Reference PointInstalling and configuring the Avaya one-X Desktop Edition

For detailed instructions on installing one-X Desktop Edition or uninstalling the AvayaSIP softphone client software, refer to SIP softphone online help, or one of these locations:

http://www.avaya.com/support/ > Find Documentation > Avaya one-X Desktop Edition

http://www.avaya.com/support > SIP Softphone > Avaya SIP Softphone Administration

http://support.avaya.com/japple/css/japple?PAGE=Document&temp.productID=252060&temp.bucketID=159898&temp.documentID=252143&temp.selectedRelease=252204

Table 12: Documents required for setting up the Avaya softphones


one-X Desktop Edition R2.x Quick Setup Guide www.support.avaya.comSIP Support area

one-X Desktop Edition R2.x Getting Started www.support.avaya.comSIP Support area

Avaya IP Agent R6.x/IP Softphone R5.x (or later)with IM client

online help

Avaya SIP Softphone Release 2 online help

8/8/2019 16-300140_6

39/60

Issue 6 May 2009 39

Chapter 6: Upgrading SIP Enablement Services

The procedure for upgrades use the Manage Software link on the System Management

Interface (SMI).

! Important:

Important: Cable Duplicated Avaya Aura SIP Enablement Services server pairs, deployedon SIP Enablement Services Releases 5.1.x and earlier, require an upgrade tothe Distributed Replicated Block Device (DRBD) when upgrading to AvayaAura SIP Enablement Services Release 5.2. The Distributed Replicated BlockDevice (DRBD) is automatically upgraded during the upgrade to SIP EnablementServices Release 5.2. The procedure for upgrading a cable duplicated pair ofservers in SIP Enablement Services Release 5.2 has changed from previousreleases. Please follow the instruction in the Upgrading a Cable DuplicatedServer Pairon page 49 section for the correct steps.

! Important:

Important: S8500A servers cannot upgrade to SES 5.x or later releases. You must migratefrom the S8500A Server to an S8500B or S8500C Server to run SES 5.x.

If you are an existing customer with S8500-based deployments of SIPEnablement Services 3.1.1 or later, you can directly upgrade to release 5.2. But ifyour software release is earlier than 3.1.1, you must upgrade to minimum release3.1.1, before upgrading to SIP Enablement Services 5.2. You can download theSES 3.1.1 software from the Avaya SAFE download site.

For more information on the latest upgrade procedures, see Installing, Administering,

Maintaining, and Troubleshooting Avaya Aura SIP Enablement Services document(03-600768, Issue 7.0).

Connecting to the server

Perform one of the following options:

If you are on site, connect to the services port.

If you are off site, use the IP address of the server to log on to the server.

8/8/2019 16-300140_6

40/60

Upgrading SIP Enablement Services


Accessing the System Management Interface

To access the server:

1. Start the Web browser.

2. In the Address field, type 192.11.13.6 and press Enterto open the login Web page.

3. Log in as craft

4. Click yes to suppress alarms

The system displays the System Management Interface Web page.

5. Click the Manage Software link under the Upgrade menu to go to Manage Software webpage.

To upgrade remotely:

1. Start the Web browser.

2. In the Address field, type the hostname or IP Address of the target SES server.

3. Select the required option in the Manage Software web page in the System ManagementInterface and load the software.

4. Follow the steps as required.

Copying files to the server

To copy files to the server:

Copy the following files, as appropriate, from the computer to the server:

License file and Avaya Authentication file

Postupgrade service pack files, if required

Security update files (used post-upgrade, if required)

8/8/2019 16-300140_6

41/60

Issue 6 May 2009 41

To copy files to the server:

1. On the Server (Maintenance), under Miscellaneous, click Download Files.

2. Select File(s) to download from the machine used to connect to the server.

Note:

Note:

Do notselect the check box, Install this file on the local server.3. Click Browse next to the top field to open the Choose File window on your computer. Find

the files that you need to copy to the server.

4. Click Download to copy the files to the server.

The system copies the files automatically to the default file location.

5. Repeat steps 1 through 4 for each server that will be upgraded.

Resolving alarms

To clear alarms:

1. On the Server (Maintenance) Web interface, underAlarms, click Current Alarms toexamine the alarm log.

2. Select the server alarms that you want to clear and click Clear, or click Clear All.

Backing up recovery system files

To back up the system configuration files:

1. UnderData Backup/Restore, click Backup Now.

2. Select the SES files. Do notselect Full Backup because this option does not save datafiles.

Note:

Note: If you back up to a flashcard, Avaya recommends that you use a differentflashcard from the one with the prior release data files. You might need thesedata files if you need to back out of the upgrade procedure.

3. Select the backup method.

4. Click Start Backup to start the back up process.
http://-/?-http://-/?-http://-/?-http://-/?-

8/8/2019 16-300140_6

42/60



Verifying the backup

To verify that the backup was successful:

1. UnderData Backup/Restore, click Backup History.

2. Select the backup that you want to verify, and click Check Status.

The system displays the status of the backup.

3. Verify that Backup Successful appears for each data set in the backup.

Suppressing alarming

! CAUTION:

CAUTION: Ensure that you suppress alarming during the upgrade. If you do not do so, the

system can generate alarms, resulting in unnecessary trouble tickets.

To suppress alarming:

1. Access the command line interface of the server with telnet or an SSH client like PuTTY andan IP address of192.11.13.6.

2. Log in as craft.

3. Type almsuppress -ttime, where time is the length of time that the alarms aresuppressed up to 120 minutes (2 hours). Press Enterto suppress both dial-out and SNMPalarms.

The system displays the following message:

Alarm is suppressed. 120 minutes left.

4. Log off and close the dialog box.

Disabling the boot timeout of the SAMP board

Note:

Note: You can also disable the boot timeout of the SAMP board by connecting to theSAMP services port and using the SAMPs Web pages. For more information,

see "Disabling the boot timeout on Release 3.1 using the SAMP Web page" inthe Using the Avaya Server Availability Management Processor (SAMP),03-300322.

8/8/2019 16-300140_6

43/60

Upgrade tasks

Issue 6 May 2009 43

To disable the boot timeout of the SAMP:

1. At the command line on the S8500 Server, entersampcmd.

The Welcome banner appears, followed by the SAMP command line.

2. At the SAMP command line, enterserverctrl boot timer disable.

The system responds with OK.

3. At the SAMP command line, enterserverctrl.

The system responds with the following output:

4. EnterExit to return to the server command line.

When you have completed the upgrade and the server reboots, the SAMP boot timeout isautomatically enabled again.

Upgrade tasks

Inserting the SES CD into the server

Insert the CD that contains SES into the CD-ROM drive on the server. Close the tray.

Note:

Note: You can copy SES software from an http or tftp server onto the server. In thiscase, skip this step.

Upgrading SES

To start the upgrade:

1. UnderUpgrade, select Manage Software.

! Important:

Important: If three releases already reside on the hard disk, you must delete one release tomake room for the new release.

Power On

Server Operational

Reset Deasserted

Boot Time Disabled

8/8/2019 16-300140_6

44/60



2. Perform one of the following tasks:

If three releases already reside on the hard disk

1. Select Delete one of the above releases from the local hard drive. Click Continue toview the releases available.

2. Select the software release that you want to delete and click Delete.

When complete, the system displays the following message:

Deletion Complete

3. Click Continue to return to the initial Manage Software page.

If less than 3 releases reside on the hard disk

1. Select one of the following:

Copy a release to the local hard drive, but do not install it

Copy from TFTP server at this IP address

Copy from URLand click Continue to view the options for copying the software to the hard drive.

2. Select Copy from this servers CD-ROM drive: and click Continue.The Choose Software page appears, which you use to copy files from the source youselected.

3. Select the release to be copied and click Continue.The system displays the Copy in Progress page.

4. View the progress screen as the software is copied to the hard drive.When complete, the system displays the following message:Success

5. Click Continue to return to the initial Manage Software page.

Installing a new release of SES from the local hard drive

If you selected Install one of the following releases currently resident on the local hard

drive in the previous step, then follow these steps:

1. Select the software release you want, and click Continue.

2. If you have copied the license and authentication files to the server, select the followingoptions:

- If a super-user login already existed prior to the upgrade, select:

I will supply the license files myself when prompted later in this process.

Update authentication information as well as license information.

- If a super-user login did not exist prior to the upgrade, select:

8/8/2019 16-300140_6

45/60

Upgrade tasks

Issue 6 May 2009 45

I will supply the license files myself when prompted later in this process.

Do not update authentication information.

3. Click Continue.

4. For a new installation, or if you previously ran a backup, you do not need to run a backup atthis time.

5. Click Continue.The system displays the Review Notices page.

6. Click Continue.

The system displays the Begin Installation page. The page summarizes the request youhave made.

7. Click Continue.

The installation takes approximately 10 to 20 minutes.

The system refreshes the Install in Progress window every 10 seconds or when you clickRefresh. When complete, the system displays the Reboot Serverpage.

Rebooting the server

To reboot the server.

Note:

Note: When you reboot the server, it can no longer communicate with the Webinterface. The Reboot in Progress Web page displays during the reboot.Although the Continue button is visible, do not click Continue yet.

1. Click Reboot.

The system displays the Reboot in Progress window. The tray of the CD-ROM drive opensautomatically.

2. Remove the CD-ROM from the CD-ROM drive.

! CAUTION:

CAUTION: If you do not remove the CD-ROM and the tray of the CD-ROM drive closesagain, the system might try to reboot from the software on the CD-ROM.

Note:

Note: The reboot takes approximately 3 minutes. The system does not automatically

report when the reboot is complete.

3. Wait for 3 minutes and then click Continue.

If you click Continue before the reboot is finished, the browser displays Expired Page. Ifyou see the Expired Page message, refresh the browser. If the system displays Pagecannot be displayed, use the browser Back button to return to the Reboot in progress

8/8/2019 16-300140_6

46/60



screen. If the Session Timeout screen appears, close the screen, logoff, and log on again.Select Manage Software, select the option Join this upgrade session in progress andmonitor its activity. Click Pickup.

! CAUTION:

CAUTION: Do not click Cancel after this point. Be patient. If the installation fails, a message

displays on the Reboot in Progress window.

Note:

Note: This Web session will be interrupted by the reboot which occurs during theupgrade of the server. After the reboot, you can continue to use the ManageSoftware window without logging in.

4. When the reboot is complete, click Continue.

The system displays the Update Tripwire Database Web page. If your planning documentsinstruct you to enable Tripwire, follow the instructions to reset the signature database.

If your planning documents instruct you to enable Tripwire, follow the instructions to reset

the signature database.You can also Verifying reboot progress at this stage.

5. Click Continue.

The system displays the Install License Files Web page.

6. Click Continue.

The system installs the license file and authentication file if you selected this action in step 5on Rebooting the server.

The system displays the Installation Complete screen.

7. Click Close.

The Manage Software window closes and returns you to the main menu.

Note:

Note: This Web session will be interrupted by the reboot that occurs during the serverupgrade. After the reboot, the links in the main menu of the Web interface will notfunction. Therefore, you must close and reopen the Web browser to continue withthe upgrade procedure.

8. Close the Web browser.

9. Reopen the Web browser and log in.

10. Use the Status Summary web page to monitor the progress and wait until initial replication

is completed before proceeding to the next home server.If the server is part of a duplicated pair, you cannot start the upgrade of the backup server inthe duplicated pair until the Status Summary web page indicates that the initial replicationis completed.
http://-/?-http://-/?-

8/8/2019 16-300140_6

47/60

Upgrade tasks

Issue 6 May 2009 47

Note:

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

Verifying reboot progress

To check the reboot process.

1. Click Start > Run to open the Run dialog box.

2. Type commandand press Enterto open an MS-DOS window.

3. Type arp -d 192.11.13.6 and press Enterto clear the ARP cache in the laptop. Thiscommand responds with one of the following responses:

The command line prompt when the cache is cleared.

The following message is when the specified IP address does not currently contain anentry in the ARP cache:

The specified entry was not found.

4. Typeping -t 192.11.13.6 to access the server. The -t causes the ping to repeat untilyou get a response. When you get a response, in about 3 minutes, wait an additional 30seconds before you go back to the Web interface.

5. Type ctrl c to stop the ping.

6. Close the MS-DOS window.

Verifying software operation

To verify the software version.

1. Under Server, click Software Version.

2. Verify the details in the Software Version web page to ensure that the new software ispresent.

Checking system status

To check the system status:

1. UnderServer, click Status Summary to verify that the server mode is active.

8/8/2019 16-300140_6

48/60



2. Click Process Status.

3. Select Summary and Display once. Click View to access the View Process Status Resultsscreen.

4. Verify that all the processes are UP.

Making the upgrade permanent on the server

! CAUTION:

CAUTION: You must make the upgrade permanent. Otherwise, the next time when youreboot the server, the server might run the previous version of the software. Youmight lose any new translations you might have made, and you must install thenew software again. If you do not make the upgrade permanent within 2 hours ofthe upgrade, an alarm is raised.

To make the upgrade permanent.

1. UnderServer Upgrades, click Make Upgrade Permanent.

2. Click Submit to make the partition with the new software version the permanent partition.

3. Under Server Upgrades, click Boot Partition to confirm that the new software release isselected for the boot partition and the active partition.

Installing security and SES service packs, if any

1. Under Server Upgrades, select Manage Updates.

2. If an update file you want to activate shows packed in the Status column, select update IDand click Unpack.

3. The window shows the status of the update.

4. Wait until the system displays the message Finished unpacking...and click Continue.

5. The system displays the Manage Updates screen.

6. If the update ID you want to activate shows unpacked in the Status column, select theupdate ID and click Activate.

7. The window shows the status of activating the update. If a reboot is required, the systemautomatically reboots.

8. ClickYes.

Wait