Messaging configuration checklist

This topic outlines a procedure for validating the Messaging configuration.

Prerequisites:

Check Steps Result / Validate
Check whether all services are running Verify the status of the: All required services are up and running.
Create Test Users Add the following test users:
  • Create Test User1 with the Standard Class of Service (CoS) setting.

  • Create Test User2 with the Enhanced CoS setting.

For more information, see Adding users.

To check whether the test users are created, click Messaging > Reports (Storage) > Users.
Configure Test Users Open the User Preferences for Test User1 and set the following:
  • Select the General page and enter a valid mobile number in the Other mobile phone or pager field.

  • Select the Notify Me page and enable text Notifications using the With a text message or page to: option using the number configured in the General page.

  • Select the Notify Me page and enable Email Notifications, by providing a valid e-mail address.

Messaging supports only e-mail based (SMTP) pager and cellular notifications.

For more information, see Changing user properties and the Using Avaya Aura Messaging guide.

 
Open the User Preferences for Test User2 and set the following:
  • Select the General page and enter a valid mobile number in the Other mobile phone or pager field.

  • Select the Notify Me page and enable Phone Notifications using the number configured above.

  • Select the Reach Me page and enable and configure two ReachMe numbers that consist of an internal extension and a external number.

Messaging supports only e-mail based (SMTP) pager and cellular notifications.

For more information, see Changing user properties 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 user's assigned extension. Ensure that this call is up for at least 60 seconds.

  • Provide temporary password as prompted.

  • 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, you should be prompted to enter the temporary password, and upon entering the temporary password, you should be guided through the steps to initialize your mailbox in the order noted above.

  • from a number that is different from the one registered to any other user, you should hear the Main Menu prompt, and upon entering your Mailbox and Password, you should be guided through the steps to initialize your mailbox in the order noted above.

This validates:

  • Users are loaded appropriately on the Messaging server.

  • Integrated login.

  • Long duration outbound calls through any SBCs/gateways.

As Test User2, perform the following:
  • Call the Pilot Main Number from a phone that is not registered to any user's assigned extension.

  • Press # to Login as prompted and provide the mailbox number.

  • Provide temporary password as prompted.

  • Change password.

  • Record spoken name.

  • Record greeting.

  • Hangup.

For more information, see the Using Avaya Aura Messaging guide.

Basic call answer Perform the following:
  • From Test User2's extension, call direct extension number for Test User1 and let the call roll over to voice mail.

  • Leave a message; note user and date/time when message was sent.

  • Hangup.

  • From an outside number, dial external Pilot number and enter Test User1 extension.

  • Leave a message; note outside number and date/time when message was 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.

  • User1's greeting is played.

  • MWI changes for Test User1 to On.

  • Observe e-mail 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 Test User1's extension, call main pilot number.

  • Provide password as prompted to login.

  • Listen to both messages - don't delete.

  • Observe MWI turns Off.

For more information, see the Using Avaya Aura Messaging guide.

Observe the following:
  • Test User1 has two messages in inbox with appropriate time.

  • MWI updates to Off for Test User1.

This validates:

  • Ability to retrieve messages via TUI.

  • MWI updates.

  • Subject Line matching.

Outcall notification (You may 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 Test User1's extension, call main pilot number.

  • Provide password as prompted to login.

  • Create a voice message for Test User2; note user and date/time message is supposed to be 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 and the Using Avaya Aura Messaging guide.

Observe the following:
  • Message is not delivered until expected date/time.

  • Date/Time stamp of message is per expected future delivery date.

  • Outcall notification occurs per schedule setting and only after message is delivered.

This validates:

  • System date/time is correct.

  • Outcall Notification.

  • Long duration outbound calls through any SBCs/gateways.

Using Outlook Toolbar (You may 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, Login IMAP account via 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:
  • Message is played via system's media player for play on PC.

  • Message is played via TUI for play on phone.

  • All messages have correct date / 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 may 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:
  • Caller is notified that Test User2 is not answering and that other numbers will be tried.

  • Each configured number is called in the order set.

  • After failing to get an answer for both numbers, the caller is allowed to leave a voice message.

This validates the Basic Reach Me functionality for both types of phone numbers.

AA Call Transfer to User (You may skip these steps, if you do not plan to use this feature.) Perform the following:
  • Call AA Number.

  • Enter Test User1 Extension.

  • Answer Call.

  • Call AA Number.

  • Enter Test User2 extension.

  • Don't 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, Reach Me is invoked and talk path is correct.

This validates:

  • Users loaded appropriately on the application server.

  • Basic AA functionality.

  • Speech addressing, if enabled.

  • Reach Me via AA.