Overview
Logging
Into the Messaging System
You can log in to the messaging system from:
Login
You can create a custom login account and associate it to a Communication Manager profile based on the web pages the user must access. The CM Messaging application uses the user-based profiles created by Communication Manager. User profiles enable you to allow a user to access only a specific set of administration web pages.
For example, the Privileged Administrator account is a sa login and it uses Communication Manager user profile 18. This profile provides access equivalent to the customer super user login.
The Unprivileged Administrator account is a vm login and it uses Communication Manager user profile 19. This profile provides access equivalent to the customer non super user login.
You can add logins from the Server (Maintenance) Web page > Security > Administrator Accounts.
You can use any one of the following logins for the messaging system:
Table: Messaging Logins
|
Login |
Definition |
Allows you to access: |
|
Privileged Administrator |
System administrator |
- All CM Messaging Web-based administration pages
|
Unprivileged Administrator
|
Voice messaging administrator |
- Most CM Messaging Web-based administration pages
|
|
craft |
Services technician |
- All CM Messaging Web-based administration
pages
- All Communication Manager server Web-based administration screens
|
| CM Messaging Access only |
A User with only CM Messaging access only |
All messaging web pages |
| Custom |
Assign a Communication Manager profile to this login |
Depending on the profile associated to this login, the user is able to view associated web pages |
|
The sa & vm logins now come locked after a fresh install. You need to unlock them from an Avaya services login or from the customer login created prior to the authentication file before you can login and change the password.
After an upgrade to Communication Manager release 5.2, it is advised to create a login and assign the existing profile to the new login or you can use the same login account and provide more permissions to the existing profile.
Your service technician installs your system with default passwords.
You need to immediately change these passwords after the installation
is complete. After familiarizing yourself with the basic operations
of the messaging system detailed in the next few sections,
set a new password. |
Note: A user can do messaging administration from custom created logins, but when a custom login is created, assign Voice as the access profile in the Additional Groups text box.
Access the Additional Groups text box from Server (Maintenance) Web page, on the left hand navigation panel under Security, select Administration Accounts. |
Login
procedure for the messaging web pages
To log in to the web pages:
- Open a compatible Internet browser on your
computer desktop. Currently only Internet Explorer 6.0 SP 1 or Internet Explorer 7.0 is supported.
The system displays
your Internet Home page.
- In the Address (or Location) field of your browser,
type the IP address or name of the Communication Manager server and press Enter.
|
Note: You can determine
the IP address by contacting your LAN administrator or selecting
the Configure Server main menu option
and accessing the Configure Ethernet Interfaces screen. |
The system displays the Avaya
Security Notice screen.
- Press Continue.
The system displays a security certificate.
- Click Yes
if you feel secure about the certificate. (If you do not feel secure,
select Install Avaya Root Certificate under the heading 'Security' on the Server (Maintenance) Web page main
menu after you log in.)
The Login Page
appears.
- In the Username field, type your
login ID (for example, sa or vm), and
press Enter or click Login.
The Password field or the Access Security Gateway (ASG) challenge
appears.
- Type your password (initially you get this from your installer)
or the correct ASG response and press Enter or click Login.
|
Note: If you are
logging in as craft, the Suppress
Alarm screen appears. Enter y
to prevent alarming (during installation or maintenance) or
n to allow new alarm to work normally. |
The system displays the Communication Manager System Management Interface Web page.
-
On the Administration menu, click Messaging.
- Select Messaging Administration under Miscellaneous to access the Messaging Administration main
menu.
Logging Out of the Messaging System
To log out of the Messaging System:
Using the Messaging Administration
Main Menu and Pages
The Messaging Administration main menu and the pages it
leads to provide general system administration and settings for the
messaging system.
Enabling or Disabling CM Messaging
By default the messaging application is enabled when you install CM Messaging on a server.
If you do not wish to use the messaging application and would like to disable the messaging application, you can disable the messaging application.
To disable the messaging application:
- Click Server (Maintenance) from the Administration menu.
- On the Miscellaneous list, click Messaging Software.
- Click Disable on the Messaging Software page.
Changing
Administration Passwords
When your system is installed, the sa and vm
logins come with a default password. You are required to change this
password immediately. There are certain minimum standards that passwords
must follow.
| Note: To change
administrator passwords, you must
log in to the Communication Manager server SAT screen using the dadmin
login and password. If dadmin does not exist, you must create a dadmin account that is part of the susers group. |
Additionally, you can administer several parameters
of the password aging feature that will enhance the level of security
that the system maintains.
This section provides the procedures for changing
passwords by setting password aging.
Guidelines
for Administrator Passwords
To minimize the risk of unauthorized people using
the messaging system, follow these guidelines for system administrator
passwords.
- Establish a new password as soon as the messaging system is installed.
- Use from 6 to 11 alphanumeric characters. The
password must include at least one�numeric character and two alphabetic
characters.
- Never use obvious passwords, such as a telephone
extension, room number, employee identification number, social security
number, or easily guessed numeric or letter combinations.
- Do not post, share, print, or write down passwords.
- Do not put the password on a programmable function
key.
- Change the password at least once per month.
You can administer your system to age the password and notify you
that a new password is required.
Changing
Administrator Passwords
You have to immediately change the password
for your login account after your system is installed.
Once the new password is established, establish a regular schedule for
changing the password, for example, at least monthly. Be sure to inform
any other messaging administrators or system administrators of the change
in passwords.
Both system administrators and messaging administrators
can change passwords. messaging administrators who log in with the Non Privileged Administrator account (vm
login) can change the password for the that login only. System administrators
who log in with the Privileged Administrator account (sa login) can change the password for both
the Privileged and Non Privileged Administrator login.
Changing
an Administrator Password or Password Aging
To change the password for the Privileged (sa) or
Non Privileged Administrator (vm) login account:
- Use the dadmin login and password. If dadmin does not exist, you must create a dadmin account that is part of the susers group.
- At the
enter command: prompt, enter change
password login account name (sa or vm or another login
previously administered).
The system displays the Change Password
screen.
- Complete the fields on this screen by using
the information in the table for Field
Definitions: Change Password screen.
- When you finish entering password information,
press F3 to save the information in the system database.
The cursor returns to the command line,
and the system displays the message:
Command
Successfully Completed.
- Enter another administrative command
at the
enter command: prompt or enter exit.
Checking
and Setting the System Clock
The messaging system uses the Linux system
clock to perform certain time-dependent tasks, such as placing a time
stamp on voice messages and doing the nightly backup of critical system
data. The clock was probably set during the installation of your system,
but you need to check it during this getting-started phase. Check it
again monthly and whenever a Daylight savings time change occurs.
Use the Set Server Date/Time
option from the Server (Maintenance) Web page.
Top of page
