Expert Reference Series of White Papers
The Role of Session
Manager in Applying
Features to Calls via
Sequenced Applications,
The Role of Session Manager in Applying
Features to Calls via Sequenced Applications, Part 1
Jose Gaona, Global Knowledge Principal Instructor and Course Director
for Avaya Aura System and Session Manager
Introduction
This is the first of a three-part series of white papers describing the implementation and configuration of Se-quenced Applications. In this initial document, I will describe how the Communication Manager, once defined as an Entity within the Avaya Aura Session Manager, can be configured as a feature server within a sequenced application. As such, it can then be applied explicitly to users whose SIP devices are registered with Session Manager. In Part 2, I will discuss how an Application Sequence can be applied implicitly to users whose com-munication devices are registered within other network elements. Finally, Part 3 will include implementing an Application Sequence to a Third-Party Feature Server.
Avaya Aura Session Manager
Avaya Aura Session Manager is a sophisticated SIP routing engine that sits at the heart of an Avaya Aura envi-ronment. Session Manager supports the use of sequenced applications that make new and custom call fea-tures available and able to be applied to users without needing to upgrade or make changes to the underlying network infrastructure
Application Sequencing
Applications Sequencing is the provisioning of communications features and functions from a variety of appli-cations servers working behind an Avaya Aura Session Manager Server to a user community distributed across a network of multi-vendor IP telephony systems. Because all systems would be compatible for networking purposes, features are common across systems, and centralized applications can be shared. In a multi-vendor environment the capabilities of Session Manager are required to disable boundaries between disparate systems
Administering Communication Manager as a Feature Server
within an Application Sequence
These are the steps in order of implementation to configure Communication Manager as a Feature Server within an Application Sequence. These steps will be discussed in more detail later.
1. Define Communication Manager as an Entity
2. Define Communication Manager as a Managed Element 3. Define Communication Manager as an Application
4. Add the Application to an Application Sequence 5. Apply Application Sequence to SIP users
Communication Manager as an Entity
To add Communication Manager as an entity, you must navigate from the System Manager home page to
Routing > SIP Entities, click Add.
Communication Manager as a Managed Element
During this process, we are selecting Communication Manager as a new Managed Element. By doing so, we connect to it and synchronize the entire database from Communication Manager to System Manager.
To add Communication Manager as a Managed Element, navigate from the System Manager home page to
Inventory > Managed Element > click New.
Use the General Tab to determine the element type that will be managed via System Manager. Specify the name and IP address of the Communications Manager 172.62 x 53.
Figure 3. Communication System Manager (continued) Figure 2. Communication System Manager
Identify the Communication Manager and credentials to login to it. The login used must have ssh/sat access to the Communication Manager and credentials to login to it. It is during this process that System Manager logs into Communication Manager through valid credentials and synchronizes with the Communication Manager database.
The Process for Data Synchronization Begins
After Communication Manager has been added as a Managed Element, it will automatically be scheduled for an initial and subsequent incremental data synchronization.
• Subsequent changes made in System Manager will immediately update underlying Communication Manager when committed.
• In 6.2 Synchronization enhancements include almost immediate synchronization from Communication Manager to Session Manager.
Communication Manager as an Application
Once we have defined Communication Manager as an Entity and a Managed Element we can now proceed to configure it as an Application.
• Navigate to Session Manager > Application > Configuration > Applications • Define the name of your Communication Manager Application
• Select your Communication Manager SIP entity
• Select your Communication Manager System for SIP Entity (managed element) • Commit
Figure 6. Define the Application for CM Figure 5. Element Manager – Data Synchronization
Application Sequence for Communication Manager
Once the application for Communication Manager has been configured, it must be added to an Application Sequence. To create the Application Sequence, navigate from System Manager to Session Manager >
Application Configuration > Application Sequence.
The Sequence and the Application for Communication have now been configured. Select the + [plus sign] next to Communication Manager Application to add it to the Sequence.
Applying Application Sequence to Users
At this point, four of the five steps associated with sequence applications have been completed. The final step is to associate the sequence to individual SIP users.
In this example we are editing an existing SIP phone; however, applying the sequence to users can also be done as you build new users providing all previous steps have been completed.
Edit SIP User to apply Application Sequence to User’s Communication Profile. If you already have a significant number of SIP users configured, you can apply the sequence in bulk to multiple users by navigating to Session
Figure 9. Applying Application Sequence (Continued) Figure 8. Applying Application Sequences
Modify the Communication Manager End Point Profile
It is during this step that we assign a Communication Manager station profile to a SIP Communication Profile. In other words, there will be a SIP profile within Session Manager and another one for the SIP phone within via Communication Manager. In this example, the assumption is that the SIP profile within Communication Manager has previously been configured. However you can also use this screen to build the profile within Communication Manager as you build the SIP client within Session Manager.
The End Result
• The IETF defines the number of features for a native SIP phone to around 30.
• Advanced SIP phones, those associated to Communication Manager stations, support approximately all Avaya 700 telephone features.
• How do these phones get access to Communication Manager telephony features? By subscribing to certain Avaya features using the SUBSCRIBE message and then in turn being NOTIFIED when these features are being applied.
Figure11. SUBSCRIBE and NOTIFY Messages
In Figure 12, the middle figure represents those SIP Phone features derived from Communication Manager which are therefore not native to Session Manager.
Conclusion
The Communication Manager Server, once defined as an SIP Entity and a Managed Element, becomes, in its new role, a feature server to be shared across Avaya and third-party IP telephony systems. It provides telephony features and media control to communications devices.
Session Manager will provide device support and routing control. All server-to-server signaling will be SIP-based. Session Manager, with a centralized directory profile database, will directly support SIP communications devices; non-SIP device support will require an intermediary SIP proxy server.
Additional application server solutions, such as Avaya Modular Messaging, Voice Portal, and Meeting Exchange, will also work behind Session Manager and support user needs in a multi-vendor IP telephony system environ-ment, as will third-party applications
Learn More
Learn more about how you can improve productivity, enhance efficiency, and sharpen your competitive edge through training.
Avaya Aura® System Manager Implementation, Administration, Maintenance, and Troubleshooting (R6.2) (5U00095)
Avaya Aura® Session Manager Implementation, Administration, Maintenance, and Troubleshooting (R6.2) (5U00096)
Avaya Aura® Session and System Manager Implementation, Administration, Maintenance, and Trouble-shooting (R6.2) (5U00097)
CS 1000 Upgrade and Avaya Aura® Integration Boot Camp (9U00166I)
Visit www.globalknowledge.com or call 1-800-COURSES (1-800-268-7737) to speak with a Global Knowledge training advisor.
