Avaya Solution & Interoperability Test Lab Configuring Avaya Aura Messaging R6.1 Connectivity with Microsoft Outlook Express R6.0 IMAP4 based Email Client using SSL Issue 1.0 Abstract These Application Notes present a sample configuration of a network consisting of a Centralized Avaya Aura Messaging Solution supporting Microsoft Outlook Express as an IMAP4 Email client. Testing was conducted via the Internal Interoperability Program at the Avaya Solution and Interoperability Test Lab. 1 of 26
1. Introduction These Application Notes document the interoperability of Avaya Aura Messaging with Microsoft Outlook Express email client using Internet Message Access Protocol Version 4 (IMAP4) over the SSL (Secure Socket Layer) protocol connection. The SSL connection is created based on the negotiation/handshake between Messaging and Email Client. With the appropriate Email and Messaging settings, Avaya Aura Message subscribers can use standardsbased email clients to receive, send, delete, purge and manage messages from a desktop computer. Subscribers can gain access to messages and deal with those messages by using any email clients of Standards based IMAP4. IMAP4 based email clients act on the message stored on the message store server such that message status is synchronized with the actions of other clients, such as the Telephone User Interface (TUI). For example, if a message is deleted by using a TUI then synchronization would happen to ensure that a given message also gets deleted from the IMAP4-supporting email client. Microsoft Outlook Express 6.0 can be configured as such an email client and these Application Notes describe how to achieve this. 2. Interoperability Testing The general test approach was to configure a Avaya SIP telephony solution that would support a third party IMAP4 based email application over an SSL connection. The third party application in this case was Microsoft Outlook Express email client. The main focus was on the Messaging capability to support subscribers with the ability to manipulate voicemail messages by using an email client. Failover (e.g. by CM reset, unplug LAN cable etc), AUDIX TUI, testing with the use of the CallerApp Utility, as well as interaction between email users/accounts belonging to different CoS (Classes Of Service) were not test. 2.1. Test Description and Coverage The interoperability test areas included the following: Basic calls with voicemail messages Subscribers ability to access/login to the Messaging Voicemail notification sent to subscriber via email Voicemail attachment (.wav files) to sent/generated notification Email MWI behavior upon email manipulation Email (mailbox) behavior upon deletion via TUI Voicemail (on storage server/messaging) behavior when deleted via Email client Forwarding of email with attached voice message file Forwarding of email with message attachment from TUI Sending of plain text (email) messages between subscribers/email accounts 2 of 26
2.2. Test Results and Observation Interoperability testing of the sample configuration was completed with successful results for the Messaging support of Microsoft Outlook Express IMAP4 based email client. No issues were observed. 3 of 26
3. Reference Configuration The sample network configuration used is illustrated in Figure 1, where SIP and H.323 handsets are used to generate calls for voicemail into Messaging. References [1], [2] and [3] in Section 9 describe how to install and provision stations on Communications Manager and Session Manager that would enable using Messaging for voice messages. Therefore, these Application Notes do not describe the integration of Messaging and Communication Manager as well as Session Manager but rather focus on Messaging and Microsoft Outlook Express Email Client integration. These Application Notes also assume that Microsoft Outlook Express client has been installed on a computer according to the installation instructions provided by Microsoft. Figure 1: Sample Configuration for Avaya Aura Messaging and Microsoft Outlook Express IMPA4 Email Client 4 of 26
4. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Avaya Aura Communication Manager running on Avaya S8800 Server Avaya Aura System Manager running on Avaya S8800 Server Avaya Aura Session Manager running on Avaya S8800 Server Avaya Aura Messaging running on Avaya S8800 Server Avaya G650 Media Gateway Software R6.2.0 Build/CM_Simplex R016x.02.0.823.0 VSP: 6.2.0.0.27 R6.2.0 SP1 Build No. - 6.2.0.0.15669-6.2.12.105 Software Update Revision No: 6.2.13.1.1871 VSP: 6.2.0.2.27 R6.2.1.0.621007 VSP : 6.2.0.2.27 R6.1-11.0 655A (Power Supply) TN2312BP HW28 FW054 (IP Service Interface) TN799DP HW16 FW040 (C-LAN) TN2602AP HW08 FW062 (IP Media Processor) TN2464CP HW13 FW025 (DS1 Interface) SIP Firmware S96x1_SALBR6_0_3_V470.tar H.323 Firmware ha96xxua3_11.bin Avaya IP Phone 9621G Avaya IP Phone 9650 Microsoft Outlook Express Version 6.00.3790.3959 on Windows 7 5. Configure Avaya Aura Messaging Messaging was configured for SIP communication with Session Manager. The procedures include the following areas: Administer Sites Administer Class Of Service Administer Telephony Integration Administer Subscribers See reference [4] in Section 9 for standard installation and configuration information. General knowledge of the configuration tools and interfaces is assumed. 5 of 26
5.1. Administer Sites A Messaging Pilot number and a Messaging Auto Attendant number needs to be defined for every site. Log into the Messaging System Management Interface (SMI) and go to Administration Messaging. In the left panel, under Messaging System (Storage) select Sites. In the right panel fill in the following: Under Main Properties: Messaging access number (external) Enter a Messaging Pilot number Message access number (internal) Enter a Messaging Pilot number Subscriber number length Set the digit length. In this example it s set to 5 Under Site Internal Dial Plan: Short extension length Set the extension length. In this example set to 5 Short mailbox length Set the extension length. In this example set to 5 6 of 26
5.2. Administer Class Of Service Log on to the Messaging System Management Interface (SMI) go to Administration Messaging. In the left panel, under Messaging System (Storage) select Class of Service. In the right panel fill in the following: Class of Service: Under General: IMAP4/POP3 access Set the Class of Service that is currently being used, in this example was set to Standard Ensure is set to Full Set Message Waiting Indicator (MWI) on user s desk phone Ensure this check box is ticked 7 of 26
Under Greetings: Two greeting (different greetings for busy and no-answer) Ensure this radio button is checked/selected Maximum length Set the maximum greetings length Under Notifications: Allow text message (or page) notification Set to Yes Allow outcalling notification Select Yes Allow email notification Select Yes, with or without recording Click Save 8 of 26
5.3. Administer Telephony Integration A SIP trunk needs to be configured from Messaging to Session Manager. Log into the Messaging System Management Interface (SMI) and go to Administration Messaging. In the left panel, under Telephony Settings (Application) select Telephony Integration. In the right panel fill in the following: Under Basic Configuration: Switch Integration Type: Under SIP Specific Configuration: Transport Method: Connection 1 Messaging Address SIP Domain Click Save to save changes. SIP TCP Enter the Session Manager signaling IP address and TCP port number Enter the Messaging IP address and TCP port number Enter the Messaging and Session Manager domain names 9 of 26
5.4. Administer Subscribers Log into the Messaging System Management Interface (SMI) and go to Administration Messaging. In the left panel, under Messaging System (Storage) select User Management. In the right panel fill in the following: Under User Properties: First Name Enter first name Last Name Enter last name Display Name Enter display name Site Enter site name, in the example Default was used Mailbox Number Enter desired mailbox number i.e. 35000 Extension Enter desired extension number i.e. 35000 Class Of Service Select a Class Of Service Pronounceable Name Enter a pronounceable name to be used when dialing the extension using voice commands MWI Enabled Enable MWI light New Password/Confirm Password Enter desired extension password Click Save to save changes. 10 of 26
Under User Preferences for the configured user click Open User Preferences for then click Notify Me Under Email Notifications Email me a notification for each voice message Ensure this box is ticked To email address Type the email address e.g., 35000@mango61.mmsil.local Include the recording Ensure this check box is ticked Click Save. Repeat this section for all phones that will use Messaging for voice messaging services. 11 of 26
6. Configure Microsoft Outlook Express From the top bar of Microsoft Outlook Express click Tools Accounts From the emerging screen click Add Mail.. Type the Display Name, in this example it was set to 35003. Click Next 12 of 26
Type the E-mail address to be used. In the example it was set to 35003@mango61.mmsil.local Click Next. 13 of 26
For E-mail Server Names: My incoming mail server is a Set to IMAP Incoming mail (POP3, IMAP or HTTP) server Enter the incoming IMAP mail server, in this example the mail server was 10.10.9.25 Outgoing mail (SMTP) server Enter an outgoing mail server, in this example the same 10.10.9.25 was used Click Next. Note: In this configuration the Messaging was used as the Outgoing mail (SMTP) server. This will allow users to forward emails to other subscribers IMAP email accounts. The Messaging was also used as Message Storage Server. It can also be configured to use an existing corporate email system. 14 of 26
Under Internet Mail Logon: Account name Enter account name, in the example set to 35003 Password Enter the password as set in the Messaging for a given extension. This password will be used by the email client to access Messaging for a given user/extension credentials Remember password Ensure this box is ticked to avoid having to enter password each time the client accesses the account on the Messaging Click Next followed by Finish 15 of 26
New account is now created, in the example screen below the new account is named as 10.10.9.25. Click Close. Click Yes on the question Would you like to download folders from the mail server you added? 16 of 26
Click OK on the emerging screen. 17 of 26
The new email is created with the account name 10.10.9.25. 18 of 26
Modify the mailbox name to an appropriate account name. To do this, right-click on the newly created account 10.10.9.25 on the screen below and select Properties. Under General tab Mail Account Set to meaningful account name, e.g. 35003 10.10.9.25 Under Outgoing Mail Server on the Servers tab My server require authentication Ensure the check box for this option is ticked 19 of 26
Under Server Port Numbers on the Advanced tab This server requires a secure connection (SSL) Ensure the check box for this option is ticked for both Outgoing Mail (SMTP) and Incoming Mail (IMAP) Click Apply then OK. 20 of 26
The finally created email account is seen below. 21 of 26
At the top bar of the Outlook Express client click Tools Options select Maintenance tab and check the Purge deleted messages when leaving IMAP folder box. This will enable automatic removal of the messages marked for delete. Then click Apply followed by OK 7. Verification Steps This section provides verification methods that can be performed on Session Manager, Messaging, and Microsoft Outlook Express email client to verify their working configurations. 7.1. Avaya Aura Messaging Verification To verify basic email interaction between the newly created Outlook Express email client/account and the Messaging as a server the following steps can be followed for a chosen subscriber. In the example below email client/account for extension 35003 was used. 22 of 26
Log on to the Messaging http://messagingip/ with the appropriate login and password then select Administration Messaging under Diagnostics select Mail Delivery then under Mail Delivery Test set the following: Sender Enter the sending extension, in this example 42203 Sender s Password Enter the corresponding messaging password associated with this client Recipient Enter Recipient s extention, in this example 35003 Click Run Test to enable Messaging to generate a test/diagnostic email to the set mailbox account. If the test is successful then the following Test Results should be displayed on the Messaging test screen as seen below: 23 of 26
A Diagnotics test email message will be generated by the Messaging to the email account of extension 35003. If the setup is correct then Microsoft Outlook Express email client should show a received email for extension 35003 as seen below. Note: Click Send/Receive button at the top bar of the Microsoft Outlook Express email client to force an immediate email retrieval if nothing received yet. 7.2. Verification of Outlook Express upon new Voicemail To verify receiption of email notification in a subscriber s email box when a new voicemail is left on Messaging the following steps can be followed: Dial that subscriber s number and leave a message on their voice mail. Ensure the MWI light on their handset lights up Verify that an email is then received by that subscriber s Outlook Express email client. This email will have an attached.wav file containing the voice message Read/play the message and ensure the MWI light on their handset is extinguished The message can then be deleted by clicking the Delete button at the top bar of the Outlook Express client. To remove the message from the Messaging (i.e., local Message Store Server), the message can also be purged using the Tools Purge Deleted Message option. 24 of 26
8. Conclusion As illustrated in these Application Notes, Avaya Aura Messaging can interoperate, via Avaya Aura Session Manager, with Microsoft Outlook Express Email client over IMAP4 protocol, so overall Microsoft Express is supported by Messaging. Refer to Section 2.2 for test/observation details. 9. References Product documentation for Avaya products available at http://support.avaya.com 1. Administering Avaya Aura Communication Manager 03-300509 Release 6.2 Issue 7.0 2. Administering Avaya Aura Session Manager 03-603324 Release 6.2 Issue 1.0 3. Maintaining Troubleshooting Avaya Aura Session Manager 03-603325 Release 6.2 Issue 1.0 4. Administering Avaya Aura Messaging Release 6.1 CID: 151610 Product Documentation for Microsoft Products may be found at http://support.microsoft.com/ 5. How to Set Up Outlook Express http://support.microsoft.com/kb/2409264 25 of 26
Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please e-mail any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at interoplabnotes@list.avaya.com 26 of 26