While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves the
right to make changes and corrections to the information in this
document without the obligation to notify any person or organization of
such changes.
Documentation disclaimer
“Documentation” means information published by Avaya in varying
mediums which may include product information, operating instructions
and performance specifications that Avaya generally makes available
to users of its products. Documentation does not include marketing
materials. Avaya shall not be responsible for any modifications,
additions, or deletions to the original published version of
documentation unless such modifications, additions, or deletions were
performed by Avaya. End User agrees to indemnify and hold harmless
Avaya, Avaya's agents, servants and employees against all claims,
lawsuits, demands and judgments arising out of, or in connection with,
subsequent modifications, additions or deletions to this documentation,
to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked Web
sites referenced within this site or documentation provided by Avaya.
Avaya is not responsible for the accuracy of any information, statement
or content provided on these sites and does not necessarily endorse
the products, services, or information described or offered within them.
Avaya does not guarantee that these links will work all the time and has
no control over the availability of the linked pages.
Warranty
Avaya provides a limited warranty on its Hardware and Software
(“Product(s)”). Refer to your sales agreement to establish the terms of
the limited warranty. In addition, Avaya’s standard warranty language,
as well as information regarding support for this Product while under
warranty is available to Avaya customers and other parties through the
Avaya Support Web site:
you acquired the Product(s) from an authorized Avaya reseller outside
of the United States and Canada, the warranty is provided to you by
said Avaya reseller and not by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE,
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,
ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER
(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED
FROM ANYONE OTHER THAN A V A Y A, AN A V A Y A AFFILIA TE OR AN
AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT
TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE
USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY
INSTALLING, 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 INTERCHANGEABL Y AS “YOU” 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 types
described below. The applicable number of licenses and units of
capacity for which the license is granted will be one (1), unless a
HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE
http://support.avaya.com. Please note that if
different number of licenses or units of capacity is specified in the
Documentation or other materials available to End User. “Designated
Processor” means a single stand-alone computing device. “Server”
means a Designated Processor that hosts a software application to be
accessed by multiple users. “Software” means the computer programs
in object code, originally licensed by Avaya and ultimately utilized by
End User, whether as stand-alone Products or pre-installed on
Hardware. “Hardware” means the standard hardware originally sold by
Avaya and ultimately utilized by End User.
Concurrent User License
Concurrent User License (CU). End User may install and use the
Software on multiple Designated Processors or one or more Servers,
so long as only the licensed number of Units are accessing and using
the Software at any given time. A “Unit” means the unit on which Avaya,
at its sole discretion, bases the pricing of its licenses and can be,
without limitation, an agent, port or user, an e-mail or voice mail account
in the name of a person or corporate function (e.g., webmaster or
helpdesk), or a directory entry in the administrative database utilized
by the Software that permits one user to interface with the Software.
Units may be linked to a specific, identified Server.
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, or Hardware
provided by Avaya. All content on this site, the documentation and the
Product provided by Avaya including the selection, arrangement and
design of the content is owned either by Avaya or its licensors and is
protected by copyright and other intellectual property laws including the
sui generis rights relating to the protection 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 unless expressly authorized by Avaya. 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
may contain software distributed under third party agreements (“Third
Party Components”), which may contain terms that expand or limit
rights to use certain portions of the Product (“Third Party Terms”).
Information regarding distributed Linux OS source code (for those
Products that have distributed the Linux OS source code), and
identifying the copyright holders of the Third Party Components and the
Third Party Terms that apply to them is available on the A vaya Support
Web site:
Preventing Toll Fraud
“T oll fraud” is the unauthorized use of your telecommunications system
by an unauthorized party (for example, a person who is not a corporate
employee, agent, subcontractor, or is not working on your company's
behalf). Be aware that there can be a risk of Toll Fraud associated with
your system and that, if Toll Fraud occurs, it can result in substantial
additional charges for your telecommunications services.
Avaya Toll Fraud Intervention
If you suspect that you are being victimized by T oll Fraud and you need
technical assistance or support, call Technical Service Center Toll
Fraud Intervention Hotline at +1-800-643-2353 for the United States
and Canada. For additional support telephone numbers, see the Avaya
Support Web site:
vulnerabilities with Avaya products should be reported to Avaya by
sending mail to: securityalerts@avaya.com.
Trademarks
Avaya® and Avaya Aura® are registered trademarks of Avaya Inc. in
the United States of America and/or other jurisdictions.
All non-Avaya trademarks are the property of their respective owners,
and “Linux” is a registered trademark of Linus Torvalds.
For the most current versions of Documentation, see the Avaya
Support Web site: http://support.avaya.com.
Contact Avaya Support
Avaya provides a telephone number for you to use to report problems
or to ask questions about your Product. The support telephone number
is 1-800-242-2121 in the United States. For additional support
telephone numbers, see the Avaya W eb site:
Delete Confirmation field descriptions..............................................................................................
Entity Links field descriptions...........................................................................................................
Bulk import for Entity Links...............................................................................................................
Time Ranges.............................................................................................................................................
About the Time Ranges....................................................................................................................
Creating Time Ranges......................................................................................................................
Modifying Time Ranges....................................................................................................................
Deleting Time Ranges......................................................................................................................
Delete Confirmation field descriptions..............................................................................................
Time Ranges field descriptions........................................................................................................
Time Range List field descriptions....................................................................................................
Bulk import for Time Ranges............................................................................................................
System Status...........................................................................................................................................
User Registrations............................................................................................................................
System Tools.............................................................................................................................................
This book provides information on administration, ongoing management of Avaya Aura
Session Manager and includes procedures for
• Using System Manager Common Console
• Creating user accounts
• Administering routing for Session Manager and various SIP entities
• Configuring, and monitoring Session Manager instances
™
Required skills and knowledge
The audience is expected to have some experience installing Avaya products and be able to
perform administration procedures. They must also have a basic understanding and working
knowledge of the following areas:
Operating systems in
general
Graphical and
command line
interfaces such as
Windows and Linux
TCP/IPSSHSIP
FTP and SFTPLAN/WANHostname/DNS
Overview of System Manager
System Manager is a central management system that delivers a set of shared management
services and a common console across multiple products. System Manager includes the
following shared management services categorized as follows:
• Under Users
- Administrators
Manage administrative users within Avaya Unified Communications Management.
- Events
Manage alarms, view and harvest logs generated by System Manager and other
components of System Manager.
- Licenses
View and configure licenses for individual components of Avaya Aura Unified
Communication System.
- Replication
Track data replication nodes, repair replication nodes.
- Scheduler
Schedule, track, cancel, update and delete jobs.
- Security
Manage Security Certificates.
- Templates
Manage Templates for Communication Manager and Messaging System objects.
System Manager Common Console is the management interface for Session Manager. You
must log on to the System Manager Common Console to perform any administration or
configuration.
Log on to System Manager
Logging on to System Manager Web interface
The System Manager Web interface is the main interface of Avaya Aura System Manager . You
must log on to the System Manager Web console before you can perform any tasks.
Before you begin
A user account to log on to the System Manager Web interface. If you do not have a user
account, contact your system administrator to create your account.
Procedure
1. On the browser, open the System Manager URL (https://<SERVER_NAME>/
SMGR).
• Match an authorized System Manager user account, the System Manager
home page appears with the System Manager version_number. The System
Manager home page displays a navigation menu. This menu provides access
to shared services with which you can perform various operations supported
by System Manager. The tasks you can perform depends on your user role.
• If you enter incorrect login credentials on the System Manager login page,
System Manager displays an error message and prompts you to re-enter the
user name and password so that you can log in again.
Login information for users with user name admin
This login information applies only to users with log-on name admin.
• When you log on to System Manager for the first time after a fresh installation or an
upgrade, enter admin123 as the default password.
• After you log on, the system displays the Forced Change Password page. There is no
Cancel button on this page. You must change your password when you log on using the
default password.
• If you access System Manager through IP address, and you log on as “admin” for the first
time, you must use the Change Password link to change the password manually.
Y our password should contain a combination of alphanumeric and special characters. To know
more about the password strength policy, see
page 17.
Note:
In System Manager 6.1, you require two separate administrator user IDs for managing
System Manager and UCM. Users with the log-on name admin can manage both using the
same ID.
Password and security policies for users with username admin
Password and security policies for users with username
admin
Password aging policy enforcement
Note:
All password policies are applicable ONLY for users with the log-on name “admin”.
The password aging policy has the following time-based password thresholds that the network
administrator can configure as the number of days:
• Minimum password age
• Password expiration warning
• Password expiration
The following table describes what occurs when a user logs on to System Manager when the
password aging policy thresholds expire.
Password thresholdWhat occurs when the threshold expires
Minimum password ageYou cannot change the password until the minimum
password age has been reached. For example, you cannot
change the password for three days after the last change was
made.
Password expiration
warning
Password expiration periodYou are forced to change the password after the threshold for
You receive a password expiration warning when the
password is about to expire and before the password
expires.
the password expires and before the threshold to disable the
account. The password is locked until it is reset by the
network administrator.
Password strength policy enforcement
Passwords must contain a combination of alphanumeric and special characters as defined by
the network administrator. The password strength policy enforces the following constraints:
• Passwords must have a total character length from 6 to 25. Default is eight.
• Passwords are not required to have a minimum character type; however, the default is
one lower- and upper case character, one numeric character, and one special character,
such as exclamation mark (!). The sum cannot exceed the minimum total length.
After you enable the password strength policy, ensure that the following standards are met:
• Password must not have a character repeated more than twice consecutively.
• Passwords must not be your user ID, in forward or reverse order.
If a password does not contain the required parameters for password requirements, the system
rejects the password.
Note:
You can disable the password strength policy.
Password history policy enforcement
The password history policy verifies that a password is new. The previous blocked passwords
can range from 1 to 99. The default is six.
Password lockout policy enforcement
The lockout policy provides a limit for the number of attempts to access System Manager. The
user is locked out of System Manager when the specified number of logon attempts is reached.
By default, the user is locked out for two minutes after five failed attempts if the consecutive
attempts occur within a ten-minute period.
Inactive session termination policy
By default, the system suspends a user session after 30 minutes of inactivity . A user must log
on to System Manager again when this occurs.
Logon warning banner
System Manager provides the text for the logon warning banner that a network administrator
can change.
Administrators can edit the password settings through this procedure.
Procedure
1. On the System Manager console, under Services, click UCM Services.
2. Click Security > Policies in the left navigation pane.
3. In the Password Policy section, click Edit.
4. Edit the required fields on the Password Policy page.
5. Click Save.
Click Cancel to undo your changes and return to the previous page.
Important:
An invalid logon message appears for the following scenarios:
Password and security policies for users with username admin
• A logon attempt is made on a disabled account
• The password is invalid.
• The maximum number of logon attempts is reached.
• The password is expired.
For each scenario, the system responds with a message that invalid logon
credentials were used. You must contact the network administrator for additional
information.
Related topics:
Password policies field descriptions on page 20
Editing Session Properties
Procedure
1. On the System Manager console, under Services, click UCM Services.
2. Click Security > Policies in the left navigation pane.
3. On the Policies page, in the Session Properties section, click Edit.
4. On the Session Properties page, edit the required fields.
System Manager provides a customizable logon banner that appears when a user logs on to
the system. The customizable banner is intended for use by customers with security policies
that require network equipment to display a specific message to users when they log on.
Editing the login warning banner
Procedure
1. On the System Manager console, under Services, click UCM Services.
2. Click Security > Policies in the left navigation pane.
3. Click Security > Policies in the left navigation pane.
4. On the Policies page, in the Security Settings section, click Edit.
5. On the Security Settings page, edit the text as required in the Login Warning Banner
text area.
Note:
The maximum number of characters allowed is 2500.
6. Click Save.
Password policies field descriptions
This page is applicable only for users with the user name “admin”.
Aging section
Name
Enforce password aging policiesSelect this check box if you want to enforce
Password and security policies for users with username admin
NameDescription
Enable expired password changeSelect this check box if you want to allow
users to change password after it expires.
Expiration periodSpecifies the maximum allowable days to
maintain the password. Default value is 90.
You can enter values from 1 to 365.
Expiration warningSends a warning to the user if the password
is about to expire. You can type in any value
from 1 to 15. The default value is 7.
Minimum ageMinimum allowable days for password age.
You can type in a number from 0 to 7. The
default value is 3. Ensure that the number for
the expiration period is greater than the
minimum password age number.
History section
NameDescription
HistorySelect this check box to enforce policies
against previously used passwords.
Previous passwords blockedThe number of passwords maintained in the
history. You cannot reset your password to
these values. The default value is 6.
Strength section
Name
StrengthSelect this check box to enforce password
Minimum Total LengthMinimum number of characters required for
Minimum by character Type: Lower caseMinimum number of lower case characters
Minimum by character Type: Upper caseMinimum number of upper case characters
Description
content standards.
the password. The default value is 8. Y ou can
set the value from 6 to 25.
ButtonDescription
SaveSaves your entries in the Session Properties
CancelCancels your entries and takes you to the
SIP Application Server
Overview of SIP Application Server
The SIP Application Server (SIP A/S) is a scalable, highly available and high-performance
server for the development and deployment of real-time, multimedia, presence-enabled IP
communications applications. The SIP Application Server is composed of the following
components:
SIP Application Server
page.
previous page.
• Service Director — This performs decision-based routing of incoming SIP messages to
the Service Host for processing.
• Service Host — This hosts applications and interacting with external entities. It processes
SIP messages received from Service Directors and other SIP end points.
• Management Server — This hosts the SIP Application Server management console for
monitoring component statistics.
Session Manager software is an application that runs on the SIP A/S.
Starting the SIP Application Server management console
Procedure
1. On the System Manager console, under Elements, click SIP AS 8.1.
2. On the SIP A/S Connection Details page, enter the host name and administration
port of the Management Access Point Hostname / IP of the Session Manager.
The default port as 5759 is filled in. This should not be changed.
3. Click Connect.
For more information, see the Avaya Aura® System Manager online Help system.
NameDescription
Primary HostnameThe name of the machine hosting the primary
Management Server of the SIP Application
Server cluster to which you are connecting.
This is mandatory.
Primary PortThe administration port of the primary
Management Server.
This is mandatory.
Backup HostnameThe name of the machine hosting the backup
Management Server of the SIP Application
Server cluster to which you are connecting.
Backup PortThe administration port of the backup
Management Server.
ConnectConnect to the SIP Application Server
cluster.
About SIP Application Server Management Console
The SIP Application Server Management Console enables viewing of the following details:
• System Status
• Service Director statistics
• Service Host statistics
Warning:
Changing the existing configurations using the SIP Application Server Management Console
voids your product warranty.
The System Status page of the SIP Application Server Management Console shows a graphic
representation of the SIP Application Server cluster . A status icon next to each cluster element
node specifies the operational status of that element, as defined in the following table.
Status IconCluster element status
Green check symbolThe cluster element is running.
Red cross mark symbolThe cluster element is in an error state.
Yellow triangle symbolOther configuration error.
1. On the SIP Application Server Management Console, click Monitoring > Statistics
> Service Directors.
The Statistics: Service Directors page opens showing details of the listed Service
Director.
2. Select the Service Director instance and click View.
The Service Director Statistics page opens where you can view statistics for the
selected Service Director instance.
Statistics: Service Directors field descriptions
SIP Application Server
NameDescription
IdA number assigned to the Service Director.
Host NameThe host name or IP address of the Service
Director.
Administrator PortThe administration port number of the
Service Director.
VersionThe version of SIP Application Server.
StatusThe operational state of each the Service
Director.
Options include:
• RUNNING: The Service Director has been
started and is operating normally.
• DOWN: The Service Director is
unavailable.
• UNKNOWN: The operational status of the
Service Director cannot be determined.
• RESTARTING: The Service Director is
rebooting from a previously up state and
will soon become available.
• STARTING: The Service Director is
starting up from a down state and will soon
become available.
1. On the SIP Application Server Management Console, click Monitoring > Statistics
> Service Hosts.
The Statistics: Service Hosts page opens showing the list of Service Hosts.
2. In the section Service Host Instance Statistics, select a Service Host instance and
click View.
The Service Host Statistics page opens where you can view statistics for the
selected Service Host instance.
3. In the section View Statistics from Last 24 Hours, select a statistic record to view
and click View Data.
The Statistics Detail View page opens where you can view the 24 hour details for
the selected statistics.
4. On the Statistics Detail View page, click Export CSV to export the data into commaseparated value format for display in a spreadsheet application.
SIP Application Server
Statistics: Service Hosts field descriptions
Name
IdA number assigned to each Service Host.
Host NameThe host name or IP address of the Service
Administrator PortThe administration port number of the
VersionThe version of SIP Application Server.
StatusThe operational state of each Service Host.
Description
Host.
Service Host.
Options include:
• RUNNING: The Service Host has been
started and is operating normally.
• DOWN: The Service Host is unavailable.
• UNKNOWN: The operational status of the
Service Host cannot be determined for
some reason.
Free Physical Memory (Mb)The amount of free physical memory
available on the Service Host hardware
platform.
Container Sip Application SessionsThe number of SIP application sessions
currently being processed by the Service
Host. This equals the sum of the number of
sessions which represent subscriptions from
endpoints and the number of currently active
calls handled by the Session Manager.
Service Host Statistics field descriptions
Some of the important fields are listed below:
NameDescription
SIP Protocol VersionThe SIP protocol version used by the Service
Host.
SIP Application Server
StatusThe operational state of the Service Host.
Up TimeThe time since Service Host initialization.
RunningThe running state of the Service Host.
SIP Application SessionsThe number of SIP Application Sessions
currently being processed by the Service
Host.
Active SIP Application SessionsThe number of SIP transactions currently
being processed by the Service Host.
Summary Statistics
Name
SIP Initial Requests Per Second InSIP initial requests per second received by
SIP Initial Requests Per Second OutSIP initial requests per second sent from the
Unsupported URI CountThe total number of unsupported URIs that
Total Requests InThe total number of SIP requests received by
Description
the Service Host since last reported.
Service Host since last reported.
have sent SIP requests to the Service Host.
the Service Host.
Total Requests OutThe total number of SIP requests sent by the