This topic outlines a procedure for validating the Messaging configuration. Prerequisites:
• You have completed the installation and configuration of the Messaging system. • You have installed the Microsoft Outlook form using Microsoft Exchange.
• You have configured the Microsoft Outlook client for each test user for IMAP access.
Tasks Steps Result / Validate
Check whether all the services are running
Verify the status of the: • storage role. For more
information, see Verifying the status of the storage role on page 40.
• application role. For more information, see Verifying the status of the application role on page 348.
All required services are up and running.
Create test users Add the following test users: • Create Test User1 with the
Standard CoS setting. • Create Test User2 with the
Enhanced CoS setting. For more information, see
Adding users on page 134.
To check whether the system creates the test users, click
Messaging > Reports (Storage) > Users.
Tasks Steps Result / Validate
Configure test users Open User Preferences for Test User1 and set the following:
• Select the General page and enter a valid mobile number in the Mobile Phone or Pager area. • Select the Notify Me page
and enable text
Notifications using the With a text message or page to: option using the number you configured in the General page.
• Select the Notify Me page and enable Email
Notifications by providing a valid email address. Messaging supports only email based (SMTP) pager and cellular notifications. For more information, see
Changing user properties on page 136 and the Using Avaya Aura® Messaging
guide.
Open User Preferences for Test User2 and set the following:
• Select the General page and enter a valid mobile number in the Mobile Phone or Pager area. • Select the Notify Me page
and enable Phone Notifications using the number you configured in the General page.
• Select the Reach Me page and enable and configure two Reach Me numbers that consist of an internal extension and an external number.
Tasks Steps Result / Validate
Messaging supports only email based (SMTP) pager and cellular notifications. For more information, see
Changing user properties on page 136 and the Using Avaya Aura® Messaging
guide.
User initialization As Test User1, perform the following:
• Call the Pilot Main Number from a phone registered to the extension assigned to the user. Ensure that this call is up for at least 60 seconds.
• Provide temporary password as per system prompts.
• Change password. • Record spoken name. • Record greeting. • Hangup.
For more information, see the Using Avaya Aura® Messaging guide.
If you are calling: • from an extension
registered to the test user, the system prompts you to enter the temporary password. Upon entering the temporary password, the system guides you through the steps to initialize your mailbox. • from a number that is
different from the one registered to any other user, you hear the Main Menu prompt. Upon entering your Mailbox and Password, the system guides you through the steps to initialize your mailbox.
This validates: • Users are loaded
appropriately on the Messaging server. • Integrated login.
• Long duration outbound calls through any SBCs or gateways.
As Test User2, perform the following:
• Call the Pilot Main Number from a phone that is not registered to the extension assigned to the user. • Press # to login as per
system prompts and provide the mailbox number.
• Provide temporary password as per system prompts.
• Change password. • Record spoken name.
Tasks Steps Result / Validate
• Record greeting. • Hangup.
For more information, see the Using Avaya Aura®
Messaging guide. Basic call answer Perform the following:
• From extension of Test User2, call direct extension number for Test User1 and let the call roll over to voice mail.
• Leave a message; note user details, and date and time when the message is sent.
• Hangup.
• From an outside number, dial external Pilot number and enter Test User1 extension.
• Leave a message; note outside number, and date and time when the message is sent. • Hangup.
For more information, see the Using Avaya Aura®
Messaging guide.
Observe the following: • No Answer greeting for
Test User1 plays in first case and busy greeting plays in second case. • The system plays greeting
for User1.
• MWI changes for Test User1 to On.
• Email notification delivery, text message notification delivery, and subject line
- Voice Message from Test User2 (ext#here)) for first two calls. - Voice Message from
(external#here) for third call.
This validates:
• Basic Call Answering • Basic MWI functionality • Email notifications
• Text message notifications • Subject line matching Basic messaging Perform the following:
• From extension of Test User1, call main pilot number.
• Provide password to login as per system prompts. • Listen to both messages -
do not delete.
• Observe MWI turns Off.
Observe the following: • Test User1 has two
messages in inbox with appropriate time.
• MWI updates to Off for Test User1.
Tasks Steps Result / Validate
For more information, see the Using Avaya Aura®
Messaging guide.
This validates: • Ability to retrieve
messages via TUI. • MWI updates.
• Subject line matching. Outcall notification. You
might skip these steps, if you do not plan to use this feature.
Perform the following: • Configure Enhanced CoS
to allow Outcalling notification.
Select the Enhanced CoS from the Class of Service
drop-down list. Set Allow outcalling notification to Yes. In order to shorten test time, change the Start after value for outcalling notification to be 5
minutes.
• From extension of Test User1, call main pilot number.
• Provide password to login as per system prompts. • Create a voice message for
Test User2; note user details, and date and time message is sent.
• Address the outcall for future delivery in n minutes.
• Verify that outcall is launched after n+5 minutes. Ensure that this call is up for at least 60 seconds.
• Reset the Start after value to real system value. For more information, see
Changing a Class of
Service on page 156 and the
Using Avaya Aura®
Messaging guide.
Observe the following: • The system does not
deliver the message until expected date and time. • Date and time stamp of
message is as per expected future delivery date.
• Outcall notification occurs as per schedule setting and only after the system delivers the message. This validates:
• System date and time is correct.
• Outcall Notification. • Long duration outbound
calls through any SBCs or gateways.
Tasks Steps Result / Validate
Using Outlook toolbar. You might skip these steps, if you do not plan to use this feature.
Perform the following: • As Test User1, set up the
IMAP account.
• As Test User1, log in to the IMAP account using Outlook and inspect voice messages.
• Use Play on PC for a message.
• Use Play on Phone for a message.
• Test Help link on Outlook Toolbar.
• Select User Preferences Link on Outlook toolbar and login.
For more information, see the Using Avaya Aura®
Messaging guide.
Observe the following: • The system plays the
message using the media player for playing on PC. • The system plays the
message using the TUI for playing on phone.
• All messages have correct date and time, and subject line information.
• Online Help for toolbar is accessible.
• User Preferences is accessible.
This validates: • Most Outlook form
actions.
• Subject line matching. • Access to online help. • DNS for User Preferences
is correctly set. Reach Me. You might skip
these steps, if you do not plan to use this feature.
Perform the following: • Call the extension for Test
User2.
• Do not answer any call. For more information, see the Using Avaya Aura®
Messaging guide.
Observe the following: • The system notifies the
caller that Test User2 is not answering and that other numbers are being tried. • The system calls each
configured number in the set order.
• After failing to get an answer for both numbers, the system allows the caller to leave a voice message. This validates the Basic Reach Me functionality for both types of phone numbers.
Tasks Steps Result / Validate
AA call transfer to user. You might skip these steps, if you do not plan to use this feature.
Perform the following: • Call Auto Attendant
number.
• Enter Test User1 Extension. • Answer Call. • Call Auto Attendant
number.
• Enter Test User2 extension.
• Do not answer call and allow Reach Me.
• Answer second Reach Me number.
For more information, see the Using Avaya Aura®
Messaging guide.
Observe the following: • Call reaches Test User1
extension and talk path is correct.
• Call reaches Test User2 extension, system invokes Reach Me, and talk path is correct.
This validates: • Users are loaded
appropriately on the application server. • Basic Auto Attendant
functionality.
• Speech addressing, if enabled.
• Reach Me using Auto Attendant.