Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for the Integration of Avaya Modular Messaging, Avaya Directory Enabled Management, and Avaya SIP Enablement Services for Instant Messaging and Directory Services using Avaya IP Softphone - Issue 1.0 Abstract These Application Notes describe the steps required to integrate Avaya Modular Messaging, Avaya Directory Enabled Management, and Avaya SIP Enablement Services for Instant Messaging and Directory Services using Avaya IP Softphone with Avaya S8710 Media Servers running Avaya Communication Manager. 1 of 45

2 1. Introduction These Application Notes describe the steps required to integrate Avaya Modular Messaging, Avaya Directory Enabled Management, and Avaya SIP Enablement Services for Instant Messaging and Directory Services using Avaya IP Softphone with Avaya S8710 Media Servers running Avaya Communication Manager. Avaya IP Softphone is a telephony application programming interface (TAPI) compliant application that functions over an IP network in conjunction with Avaya Communication Manager. Avaya Modular Messaging is a powerful IP based voice and fax-messaging platform designed for single or multi site global enterprises. Messages are accessible any time, anywhere from a wide array of access devices including telephones; fax machines, or PC graphical user interfaces. Avaya Directory Enabled Management (DEM) and Netscape Directory Server will be used for Lightweight Directory Access Protocol (LDAP) requests and directory information retrieval. These Application Notes will use these products, in conjunction with Avaya Modular Messaging to create an on-line electronic public directory for use by Avaya IP Softphone. Avaya IP Softphone will utilize Avaya SIP Enablement Services (SES) for instant messaging and presence. Avaya SES creates a communication services layer within the Avaya Communications Architecture that mediates between Avaya MultiVantage applications and a wide range of standards-based user agents, web-based applications, and communication devices. The benefits of using Avaya IP Softphone as a client to incorporate the utilization of directory services and instant messaging, along with integration of Microsoft desktop applications (specifically Microsoft Outlook) allows for more efficient communication and storage of information via a single point of exchange. 2 of 45

3 2. Configuration The Avaya IP Telephony reference configuration used to verify these Application Notes is shown in Figure 1. Avaya S8710 Media Servers are at the core in a Multi-Connect High Reliability Configuration with dual IPSI and dual Media Processor boards. The Avaya Modular Messaging S3500 servers consist of the Message Application Server (MAS), and the Message Storage Server (MSS). The Avaya Directory Enabled Management (DEM) application and Netscape Directory Server, with the LDAP database, reside on the same Windows 2003 server. Two Windows XP PCs are used for Avaya IP Softphones. For these Application Notes, connectivity between Avaya Modular Messaging and Avaya Communication Manager was accomplished via a SIP trunk, which is provided by an Avaya SES Server named TF-SES- SIP.trade.com. One of these PCs also acts as a SAT terminal for access to Avaya Communication Manager. An additional Windows 2003 Server is configured as a Microsoft Exchange Server, which is used for electronic mail. Avaya S8710 Media Server Pair Multi-Connect Server 1: Server 2: Microsoft Exchange Server Avaya DEM Netscape Directory Server LDAP Database Control Network Server 1: Server 2: IPSI(s) Ethernet C-LAN(s) Ethernet Ethernet Avaya SES Server TF-SES-SIP.trade.com Avaya SCC1 Media Gateways MEDPRO(s) Avaya IP Softphone x Avaya IP Softphone x Avaya Modular Messaging S3500 Servers MAS: MSS: Figure 1: Network Configuration 3 of 45

4 3. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment & Software Avaya SCC1 Media Gateways Avaya Communication Manager Avaya S8710 Media Server Avaya SIP Enablement Services 3.1 (114.0) Avaya IP Softphone, running on Windows XP Professional with Service Pack Avaya Modular Messaging Message Application Server Message Storage Server Avaya Directory Enablement Management and Netscape Directory Server running on Windows 2000 Server Enterprise Edition with Service Pack 1 Microsoft Exchange Server running on Windows 2000 Server Enterprise Edition with Service Pack 1 Table 1: Equipment List Version N/A (632.1) Avaya DEM 3.1 Netscape 4.12 Version of 45

5 4. Configuring Avaya Communication Manager This section highlights the important commands for defining IP Softphones in Avaya Communication Manager. IP Softphones are configured in the same manner as an IP phone. The station is added via the add station command from SAT Add Stations Use the add station command to add a station for each IP Softphone to be supported. The extension defined here in Avaya Communication Manager must match the extension number that will be administered in Avaya SES later in Section 8. On Page 1: Use the default value for the Station Type, x for the Port. The Name field is optional and is shown on the display of Avaya non-sip telephones when receiving calls from this station. Set IP SoftPhone? to y indicating that this station is a Softphone client. The example below is for the configuration of an IP Softphone at extension add station Page 1 of 5 STATION Extension: Lock Messages? n BCC: 0 Type: 6408D+ Security Code: TN: 1 Port: X Coverage Path 1: COR: 1 Name: Avaya IP Softphone Coverage Path 2: COS: 1 Hunt-to Station: STATION OPTIONS Loss Group: 2 Personalized Ringing Pattern: 1 Data Module? n Message Lamp Ext: Speakerphone: 2-way Mute Button Enabled? y Display Language: english Figure 2: Add Station Form Page 1 Media Complex Ext: IP SoftPhone? y Remote Office Phone? n 5 of 45

6 On Page 2: Set Multimedia Mode to enhanced, which is required for Softphone configurations. The defaults for all other fields can be used. change station Page 2 of 5 STATION FEATURE OPTIONS LWC Reception: spe Auto Select Any Idle Appearance? n LWC Activation? y Coverage Msg Retrieval? y LWC Log External Calls? n Auto Answer: none CDR Privacy? n Data Restriction? n Redirect Notification? y Idle Appearance Preference? n Per Button Ring Control? n Bridged Idle Line Preference? n Bridged Call Alerting? n Restrict Last Appearance? y Active Station Ringing: single H.320 Conversion? n Per Station CPN - Send Calling Number? Service Link Mode: as-needed Multimedia Mode: enhanced Audible Message Waiting? n MWI Served User Type: Display Client Redirection? n AUDIX Name: Select Last Used Appearance? n Coverage After Forwarding? s Multimedia Early Answer? n Remote Softphone Emergency Calls: as-on-local Direct IP-IP Audio Connections? y Emergency Location Ext: Always Use? n IP Audio Hairpinning? n Figure 3: Add Station Form Page 2 6 of 45

7 5. Configure Avaya Modular Messaging This section describes the configuration procedure for Avaya Modular Messaging to allow login access for Avaya Directory Enabled Management and for Subscriber Management Add Trusted Server Step 1. Before Avaya Directory Enabled Management can connect to Avaya Modular Messaging, a new trusted server must be created within Avaya Modular Messaging. From the Messaging Administration form, which is the first web page displayed after a successful login to an Avaya MSS server, select the Global Administration link. Selecting this link will launch the Global Administration page as seen in Figure 5 in the next step. Figure 4 Messaging Administration 7 of 45

8 2. From the Global Administration Page, select the Trusted Server Management link. This will load the Manage Trusted Server page as seen in Figure 6 in the next step. Figure 5 Global Administration 8 of 45

9 3. From the Manage Trusted Servers Page, click on the Add a New Trusted Server button to load the Add Trusted Server page. Figure 6 - Manage Trusted Server 9 of 45

10 4. The following list shows the data entered in the Add Trusted Server page for these Application Notes: The Trusted Server Name must be dem. Enter a unique Password for this Trusted Server. The Service Name is DEM Server. This is a read only field, and will be updated when the Special Type field is manually set as described in the next bullet. Special Type must be DEM Server. Enter an IP address or qualified host name of the DEM server for the Machine Name / IP Address. Set Connection Security appropriately, based on specific user needs. Click Save when complete. Figure 7: Add Trusted Server 10 of 45

11 5.2. Subscriber Management Step 1. Avaya Modular Messaging accounts are set up as local subscribers to the MSS. From the Messaging Administration form, which is the first web page displayed after a successful login to an Avaya MSS server, select the Global Administration link. Selecting this link will launch the Global Administration page as seen in Figure 9 in the next step. Figure 8 Messaging Administration 11 of 45

12 2. From the Global Administration Page, select the Subscriber Management link. This will load the Managing Subscribers page as seen in Figure 10 in the next step. Figure 9 Global Administration 12 of 45

13 3. From the Managing Subscribers page, enter the extension number in the Local Subscriber Mailbox Number field and click on Add or Edit to add the subscriber. This will load the Add Local Subscriber form as seen in Figure 11 in the next step. Figure 10 Managing Subscribers 13 of 45

14 4. Figure 11 shows the data entered in the Add Local Subscribrer page for these Application Notes. Last Name, Password, Mailbox Number, and Numeric Address are all required fields to create a new subscriber account. The Mailbox Number and PBX Extension should be the same value as the station number created in Avaya Communication Manager back in Section 4.1. The Numeric Address is a unique value among all addresses in the voice mail network. For these Application Notes, the Numeric Address was set equal to the Mailbox Number and PBX Extension. In the example below, a new local subscriber is added for extension Defaults for all other fields can be used. Scroll down and click on Save once all information is entered. Repeat this step to create a subscriber account for extension Figure 11: Add Local Subscriber 14 of 45

15 6. Configure Netscape Directory Server Netscape Directory Server, in conjunction with Avaya DEM, LDAP, and Avaya Modular Messaging will be used to establish and create an on-line electronic public directory for use with IP Softphone later in Section 9.3. The entire configuration for Netscape Directory Server is done as part of the initial installation. This installation procedure can be found in reference [2]. This section will not repeat these procedures but will highlight the steps taken, the input required and the values used for these Application Notes. Step 1. Install Netscape Directory Server as per the installation procedures described in reference [2]. The following list shows the fields that need to be populated for Netscape Directory Server access to Avaya DEM and the values used for these Application Notes. Installation Directory [drive]:\netscape\server4 This represents the directory on the Windows 2003 server where Netscape Directory server will be installed. The [drive]:\netscape\server4 directory is directory and will be created automatically if that directory path does not already exist on the server. Directory Server Location This instance will be the configuration directory server These Application Notes assume that a Netscape Directory server does not exist, and a new server needs to be configured. Data Store Location - Store data in this directory server These Application Notes assume that a Netscape Directory server does not exist, and a new server will store this data. Server Identifier dem-ldap By default, this field is set to the configured 2003 Windows Server machine name. Server Port 389 The server port uses a default value of 389, which should not be changed. Suffix o=dem-ldap.avaya.com Fully qualified host name of the Windows 2003 Server, if one exists. Administration Domain demldap.avaya.com The default value for this field is the fully qualified domain name of the server, if one exists. If this is a stand-alone configuration, use a descriptive, unique domain name. Directory Manager DN cn=directory Manager This Directory Manager distinguished name (DN) will be used for LDAP client access to Avaya DEM. The Directory Manager DN of cn=directory Manager is the default and should not be edited. Directory Manager Password Unique password for the Directory Manager Administration Port This port is used for access to the Netscape Directory Server Graphical User Interface. 15 of 45

16 7. Configure Avaya Directory Enabled Management Avaya DEM, in conjunction with Netscape Directory Server, LDAP, and Avaya Modular Messaging will be used to establish and create an on-line electronic public directory for use with IP Softphone later in Section 9.3. The entire configuration for Avaya DEM is done as part of the initial installation. This installation procedure can be found in reference [3]. This section will not repeat these procedures but will highlight the steps taken, the input required and the values used for these Application Notes. Step 1. Install Avaya Directory Enabled Management as per the installation procedures described in reference [3]. As part of the installation, the administrator is prompted to add Avaya Communication Manager Server, Intuity Audix Server, and Avaya Modular Messaging server for each module to which Avaya Directory Enabled Management will communicate. For these Application Notes, only Avaya Modular Messaging will be added. As noted in earlier sections, Avaya Modular Messaging will be the primary data source used for a public on-line directory. The following list shows the fields that need to be populated for Avaya DEM access to Avaya Modular Messaging and the values used for these Application Notes. Avaya Modular Messaging: DSM Name MM Host IP Port 389 Root dc=avaya This represents the LDAP root for the Avaya Modular Messaging system. For Avaya Modular Messaging, this root is usually dc=avaya. User cn=dem, dc=avaya This represents the user (or trusted server) that DEM will use to log into Avaya Modular Messaging. For Avaya Modular Messaging, this user is usually cn=dem, dc=avaya. Password Password configured in step 4 of Section 5 for the trusted server of dem. 16 of 45

17 2. Follow the procedures in reference [3] to configure the default parameters for each of the internal components of Avaya Directory Enabled Management. The procedures will cover the following: Configure the LDAP Schema. Copy schema files provided by Avaya DEM to the directory where Netscape Directory Server is installed. Configure the default triggers in the GWAgent. The GWAgent monitors changes made to the LDAP store. This is accomplished by a simple login to DEM as the Directory Manager of Netscape, and set default triggers based on the LDAP schema. Activate the Synchronization Engine using the default settings. No additional mappings or routing rules are needed. Activate and attach the DataStore Manager that connects to the Netscape Directory LDAP Server. This creates a DataStore Manager with the default name of GWDSM, which is the DataStore Manager for Avaya DEM. This step requires the following information about the LDAP database. o LDAP base: The LDAP base is the topmost entry in a Directory Information Tree. This is also known as the LDAP root. This is represented using the following notation: o=demldap.avaya.com. An organization normally uses their DNS domain name as part of the root entry for their LDAP tree. In the example listed here, avaya.com is the DNS domain name, and demldap is the machine name hosting the LDAP database. This will be demonstrated and further explained in section 10, Verification Steps. o LDAP IP address: This represents the IP address of the LDAP server. For example, the IP address of the LDAP server used in the Application Notes is o LDAP server port: The LDAP server port is typically 389 or 636 if using Secure Sockets Layer (SSL). LDAP clients will use port This is the agent port that DEM uses to update the LDAP data store. This will be demonstrated and further explained in Section 9.3 when creating the public directory in Avaya IP Softphone and in Section 10, Verification Steps. o A LDAP user id and password with administrative privileges. Activate and attach the DataStore Managers that connects to Avaya Modular Messaging. DataStore Managers are software processes that interface with each device type that connects to Avaya DEM. A DataStore Manager is the connector technology for Avaya DEM, enabling different Avaya DEM devices (i.e. Avaya Modular Messaging and LDAP servers) to communicate with each other. This is demonstrated in steps 3 and 4 below. 17 of 45

18 3. Once the installation procedures are complete, all the Avaya Directory Enabled Management DataStore Managers (DSMs) should be in the Ready state. Next, the Avaya Directory Enabled Management Administrator will be used to move all the DSMs to the Running state. Launch the Avaya Directory Enabled Management Administrator by navigating from the Windows Start Menu to Start Programs Avaya Directory Enabled Management DEM Admin. Select the DataStore Managers tab. Select the Run All button. This will move all configured DSMs to the Running state. For the example below, the DataStore manager of MM represents Avaya Modular Messaging, and GWDSM is the DataStore Manager that connects to the LDAP Server. Figure 12: DEM Administrator 18 of 45

19 4. Once the DSMs are in the Running state, the indicators on the left turn green and the status is Running. Figure 13: DataStore Managers Tab 19 of 45

20 8. Configuring Avaya SIP Enablement Services The following steps describe configuration of Avaya SIP Enablement Services for use with Avaya IP Softphone. Other standard administration functions are covered in Reference [4]. The following example adds a user with extension These steps should be repeated for extension as well Add Users Step 1. Avaya SIP Enablement Services is configured using a web browser. Set the URL of the browser to where IP-address is the IP address of the Avaya SIP Enablement Services server. Enter the login, followed by the password when prompted. Figure 14: SES Logon Screen 20 of 45

21 2. The main administration screen will be displayed after logging in. Click on Launch Administration Web Interface. Figure 15: SES Main Menu 21 of 45

22 3. From the left pane of the Administration web interface, expand the Users option and select Add. This displays the Add User screen. Fill in the required fields, which are indicated by an * next to the field. Enter the extension number in the Primary Handle field. The Host field should be set to the IP address or Host Name of the Avaya SIP Enablement Services server to which the user s phone will register. In this configuration, the Avaya IP Softphone will register to Check the Add Media Server Extension checkbox to associate a new extension number with this user in the database now. Click on Add. Figure 16: Add User Screen 22 of 45

23 4. The Add Media Server Extension page will be displayed after a new user is added. Although not required, it is recommended to use the same extension in the Extension field that was entered as the Primary Handle in Step 3. The Media Server corresponding to the SIP trunk between the S8710 Media Server and the Avaya SES Server is selected automatically. Click on Add. Figure 17: Add Media Server Extension Screen 23 of 45

24 5. To apply the administration in the above steps, click on Update on the left side of the page. This link appears on the current page whenever updates are outstanding, and can be used at any time to save the administration performed to that point. Figure 18: User Administration Screen 24 of 45

25 9. Configuring Avaya IP Softphone This section highlights the steps needed to configure Avaya IP Softphone for both instant messaging and public directory access. These Application Notes assume that Avaya IP Softphone is already installed and operable for basic telephony functionality. The example below will set up instant messaging and public directory access for an Avaya IP Softphone at extension These steps should be repeated to add an Avaya IP Softphone at extension Instant messaging for Avaya IP Softphone does not come with the standard installation package. To enable Avaya IP Softphone to support instant messaging, from download and run the Enable IM Setup program from Avaya IP Softphone Instant Messaging Wizard Step 1. After downloading and installing instant messaging support for Avaya IP Softphone, there will be a new menu option on the Avaya IP Softphone Call Bar called Instant Messaging. From the Instant Messaging menu, select IM Wizard to configure instant messaging for this subscriber. Figure 19 Avaya IP Softphone 25 of 45

26 2. Select Yes, continue with Configuration on the first Instant Messaging Setup Wizard screen. Click on the Next button to proceed with the configuration. Figure 20 - Instant Messaging Setup Wizard Screen 1 26 of 45

27 3. Enter the User Name in the form of and Password on the next Instant Messaging Setup Wizard screen. The User Name contains the Primary Handle of the user on the Avaya SES server created in Section 8.1, step 3, as well as the domain name of the Avaya SES server. In the example below, represents the Primary Handle, and trade.com represents the domain name of the Avaya SES server. Using the IP address of the Avaya SES Server can also represent the User Name. For example, can also be represented as where is the IP address of the Avaya SES Server. Click on the Next button to proceed with the configuration. Figure 21 - Instant Messaging Setup Wizard Screen 2 27 of 45

28 4. Enter the server address (either the IP address or the fully qualified host name) in the next Instant Messaging Setup Wizard screen. In the example below, the IP address of was used, but could be replaced with the fully qualified host name of the Avaya SES server. Click the Finish button to complete the configuration. Figure 22 - Instant Messaging Setup Wizard Screen 3 28 of 45

29 5. The last Instant Messaging Setup Wizard screen indicates a successful configuration. Click the Finish button to complete the configuration. Figure 23 - Instant Messaging Setup Wizard Screen 4 29 of 45

30 9.2. Log Into Instant Messaging Avaya IP Softphone allows login to a instant messaging server only at startup. Therefore, a logoff and logon with Avaya IP Softphone from Avaya Communication Manager is required to log into the Avaya SES server for instant messaging use. This section highlights the steps required to perform this action. Step 1. From the Avaya IP Softphone Call Bar, select File Logoff. Performing this action will log off the station from Avaya Communication Manager. The status is displayed in the title bar: Avaya IP Softphone Not Logged In Figure 24 Avaya IP Softphone Not Logged In 2. From the Avaya IP Softphone Call bar, select File Log In. This will display the Login screen. Figure 25 Avaya IP Softphone Log In 30 of 45

31 3. From the Login screen, Select Log into Avaya instant messaging server checkbox, and then press the Log in button. Figure 26 Avaya IP Softphone Login Screen 31 of 45

32 4. After a successful login, the Title Bar will display the Avaya Communication Manager extension followed in brackets by the instant messaging address or contact name. In the example below, is the Avaya Communication Manager extension, and 34000@trade.com represents the instant messaging address. Two new icons now become active on the Call bar. These icons represent the following items under the Instant Messaging menu. Send a message: This icon is used to initiate a chat with a specific contact. Status: This icon displays the current instant messaging status. The example below shows a status of Online. Other selections include: Busy, Away, On the phone, Appear Offline. Figure 27 Avaya IP Softphone Login with IM 32 of 45

33 9.3. Configure Public Directory for Search Capabilities This section describes the steps necessary to configure the public directory. The public directory that will be used for these Application Notes will be Avaya Modular Messaging. Once the public directory is established, contacts can be added to an Avaya IP Softphone Directory. Once the contacts are established, chat sessions can then be initiated from Avaya IP Softphone. This is accomplished by incorporating both Avaya DEM and Netscape Directory Server for LDAP access. Step 1. From the Avaya IP Softphone Call Bar, select Tools Search Public Directory to open the Search Public Directory window. Figure 28 Avaya IP Softphone Tools Menu 2. From the Search Public Directory window, select File Add Public Directory, or click on the Add button to add a new public directory. This will open the Directory Properties window. Figure 29 Search Public Directory Window 33 of 45

34 2. From the Directory Properties window, enter the following information in the General tab. The values used for these Application Notes are highlighted in italics. The values for steps 3,4, and 5 below were configured back in Section 6, step : MM Descriptive name of the public directory. MM was used in these Application Notes as an abbreviation for Avaya Modular Messaging. 2. Server address: Represents the IP address of Avaya DEM and Netscape Directory Server. 3. Login: cn=directory Manager Login name for Netscape Directory manager used for access to Avaya DEM. 4. Password: Password assigned to Directory Manager. 5. Search Root: o=demldap.avaya.com This represents the LDAP root for the Avaya Modular Messaging system. Figure 30 Directory Properties Window General tab 34 of 45

35 3. In the Advanced tab, change the Port from 389 to Port 4000 is the agent port that Avaya DEM uses for access to LDAP. Refer back to step 2 in Section 7 for more details. The other values can remain as shown in the example below. Click the OK button to add the public directory to Avaya IP Softphone. Figure 31 Directory Properties Window Advanced tab 35 of 45

36 10. Verification Steps These verification steps can be performed to check the integration of Avaya Modular Messaging, Avaya Directory Enabled Management, and Avaya SIP Enablement Services for Instant Messaging and Directory Services using Avaya IP Softphone. The verification steps will use Avaya IP Softphone for the following activities: Using the public directory created in Section 9.3 to search for additional Avaya IP Softphone users. Define a calling number based on the public directory. Send an message to the new contact via Microsoft Outlook Initiate a chat session with the new contact Step 1. From the Avaya IP Softphone Call Bar at extension 34000, select Tools Search Public Directory to display the Search Public Directory window. Figure 32 Search Public Directory window 2. From the Search Public Directory window, click the Directory Menu button, and select the directory to search. For this example, select the MM directory that was created in Section 9.3. Figure 33 Select Public Directory Menu 36 of 45

37 3. From the Search Public Directory window, click the Search by button, and select the search key. The Search by button is located underneath the Menu bar and to the left of the search text box. The search key selected appears as the button label once selected. For this example, Name was selected. Figure 34 Search Public Directory Window 4. To change the column names displayed in the Search Public Directory window, select Edit Field Organizer from the menu bar. This will load the Field Organizer window. Figure 35 Search Public Directory Window 37 of 45

38 5. In the Field Organizer window, the available fields listed on the left are the data fields that are available from the Avaya Modular Messaging public directory. Select the fields to display on the Search Public Directory window by highlighting an entry in the Available Fields list, select the button to add that field to the Show fields in this order list. To change the order in which these fields are displayed in the Search Public Directory window, use the and buttons. Click OK to add and order the fields on the Search Public Directory window. An example of the displayed fields can be seen in Figure 37 in the next step. Figure 36 Field Organizer Window 38 of 45

39 6. In the search text box, enter the information to find. In this example, the search contains the name Avaya. Click to initiate the search. The information is displayed for each entry that matches the search criteria. The title bar changes to reflect the directory name and search string after the results are displayed. In this example, MM is the public directory name, and Avaya is the search string. The search returns the two stations created for Modular Messaging in Section 5.2. Figure 37 Search Results 7. To initiate calls from the search results listed in Figure 36 above, the telephone number field must first be defined. To define this number, select Edit Select Phone Numbers. This will load the Select Phone Number window. Figure 38 Search Results Window Edit 39 of 45

40 8. In the Select Phone Numbers window, the available fields listed on the left are the data fields that are available from the Avaya Modular Messaging public directory. Define the call number by selecting the appropriate field in the Available Fields list, and select the button to add that field to the Phone Numbers Fields list. Click OK to define the call number. Figure 39 Select Phone Numbers Window 9. To call station 34001, double click that contact from Figure 37 or click the Call button on the tool bar to initiate a call to that station. 40 of 45

41 10. To send an to station 34001, select that extension from Figure 37, and then select Action Send or click the Send button on the tool bar. This action will launch the default mail application and create an addressed to extension using the address listed for that extension. In the example below, an message was generated using Microsoft Outlook. Figure 40 New 41 of 45

42 11. To add station as a contact, highlight the station in Figure 37 and select File Add to Directory. This launches the Properties window for that contact. Enter all known information. Since Avaya Modular Messaging does not store instant messaging addresses, the default IM address is the default address. Change this to reflect the correct IM address. In this example, the IM address is 34001@trade.com, which was configured back in Section 9. Select Track availability for tracking the IM status for this station. Click OK when all information is entered. Figure 41 - Properties Window 42 of 45

43 12. From the Avaya IP Softphone Call Bar, select Tools Contacts to verify that the new contact was added. This will load the Contact Directory window. In this example, the contact Avaya IP Softphone2 has a business calling number of and is Online and available for a chat session. Figure 42 Contact Directory Window 11. To initiate a chat with the contact, highlight the contact in the Contact Directory window in Figure 42, and then select Action Send Instant Message This opens the Instant Message Session window. The title bar of the window also displays the contact name. An example of a chat session is shown below. 12. To end the chat session, close the window. Figure 43 Instant Message Session Window 43 of 45

44 11. Conclusion These Application Notes verify the steps required to integrate Avaya Modular Messaging, Avaya Directory Enabled Management, and Avaya SIP Enablement Services with Instant Messaging using Avaya IP Softphone with Avaya S8710 Media Servers running Avaya Communication Manager. 12. Additional References The following Avaya product documentation can be found at : [1] Modular Messaging for the Avaya Message Storage Server (MSS) Configuration, Release 3.0, Installation and Upgrades-Issue 1, July [2] Application Notes for Interoperability Between Netscape Directory Server and Avaya Directory Enabled Management in Support of Avaya Communication Manager and Avaya Modular Messaging Issue 1. [3] Avaya Directory Enabled Management Release 3.0 Installation and Implementation, , Issue 9. This document can be found at [4] SIP Support in Release 3.1 of Avaya Communication Manager Running on the Avaya S8300, S8500, S8500B, S8700, and S8710 Media Server. Issue of 45

45 2006 Avaya Inc. All Rights Reserved. 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 any questions or comments pertaining to these Application Notes along with the full title and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at 45 of 45