Introduction - Avaya 9600 Series Configuring

1. Introduction

These Application Notes present a sample configuration for a network that uses two Avaya
Aura® Session Managers to support registration of Avaya 9600 Series SIP endpoints. Two
Session Managers are deployed so that one Session Manager can serve as backup for the other in
case of a network or Session Manager failure.
As shown in Figure 1, Avaya 9600 Series IP Deskphones configured as SIP endpoints utilize the
Avaya Aura® Session Manager User Registration feature and are supported by Avaya Aura®
Communication Manager. To improve the reliability of the configuration, SIP endpoints are
registered to both Session Managers.
For the sample configuration, SIP users are not IP Multimedia Subsystem (IMS) users and
Communication Manager is configured as an Evolution Server in the Avaya Aura® Session
Manager architecture. When Communication Manager is configured as an Evolution Server, it
applies both origination-side and termination-side features in a single step. For more information
regarding configuring Communication Manager as an Evolution Server, see Reference [8] in
Section 9.
Avaya Aura® Communication Manager is connected to both Session Managers via non-IMS SIP
signaling groups and associated SIP trunk groups.
Avaya Aura® Communication Manager also supports non-SIP endpoints such as Avaya 9600
Series IP Deskphones (running Avaya one-X® H.323 firmware) and 2420 Digital Telephones.
Avaya Aura® Session Manager is managed by Avaya Aura® System Manager. For the sample
configuration, two Avaya Aura® Session Managers running on separate Avaya S8800 Servers
are deployed as a pair of active-active redundant servers. Avaya Aura® Communication
Manager Evolution Server runs on a pair of duplicated Avaya S8800 servers with an Avaya
G650 Media Gateway.
These Application Notes will focus on the configuration of the SIP telephones, SIP trunks and
call routing. Detailed administration of other aspects of Communication Manager or Session
Manager will not be described. See the appropriate documentation listed in Section 9 for more
information.
Note: IP addresses have been partially hidden in Figure 1 for security.
DJH Reviewed:
SPOC 07/08/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
4 of 51
SM6-1_CMES