Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for Configuring Avaya Aura Communication Manager 6.3 with Kurmi Unified Provisioning and Selfcare Issue 1.0 Abstract These Application Notes describe the configuration steps required for Avaya Aura Communication Manager and Kurmi Unified Provisioning and Selfcare. Readers should pay attention to section 2, in particular the scope of testing as outlined in Section 2.1 as well as any observations noted in Section 2.2, to ensure that their own use cases are adequately covered by this scope and results. Information in these Application Notes has been obtained through DevConnect compliance testing and additional technical discussions. Testing was conducted via the DevConnect Program at the Avaya Solution and Interoperability Test Lab. 1 of 23

2 1. Introduction These Application Notes describe the configuration steps to integrate Avaya Aura Communication Manager with Kurmi Unified Provisioning and Selfcare. Kurmi Unified Provisioning and Selfcare simplifies everyday telephone tasks and makes information available which allows optimization of - system management and provisioning. The Kurmi Unified Provisioning and Selfcare functions are divided into different connectors which may be used individually or combined, as required. The main components are installed on a CentOS based server, which is also responsible for the communication with the Avaya environment. A Web client enables access to Kurmi Unified Provisioning and Selfcare functions by using a browser. Kurmi Unified Provisioning and Selfcare enables the user to Add, Change and Delete stations and voice mailboxes. Session Initialization Protocol (SIP) stations can also be administered via the Avaya Aura System Manager. 2. General Test Approach and Test Results The general test approach was to configure Kurmi Unified Provisioning and Selfcare (Kurmi) to interoperate with the Avaya environment including Communication Manager, System Manager and Aura Messaging as implemented on a customer site. See Figure 1 for a network diagram. The interoperability compliance test included both feature functionality and serviceability tests. DevConnect Compliance Testing is conducted jointly by Avaya and DevConnect members. The jointly-defined test plan focuses on exercising APIs and/or standards-based interfaces pertinent to the interoperability of the tested products and their functionalities. DevConnect Compliance Testing is not intended to substitute full product performance or feature testing performed by DevConnect members, nor is it to be construed as an endorsement by Avaya of the suitability or completeness of a DevConnect member s solution. 2 of 23

3 2.1. Interoperability Compliance Testing Feature functionality testing included: Verify synchronization between Kurmi and Communication Manager/System Manager/Aura Messaging Add/Change/Delete Analogue/Digital/IP stations (H323 and SIP) Add/Change/Delete Voice mail boxes Add/Change/Delete Hunt/Pickup groups Change Abbreviation dialling lists Schedule jobs Miscellaneous Kurmi disconnect/reconnection Restart failed job synchronization 2.2. Test Results Tests were performed to insure full interoperability between Kurmi Unified Provisioning and Selfcare and the Communication Manager/System Manager/Aura Messaging. The tests were all functional in nature and performance testing was not included. All the test cases passed successfully. Note: The version of Kurmi Unified Provisioning & Selfcare used during DevConnect testing includes developments that have been validated with Avaya Aura Messaging 6.1. There are minor changes in version 6.3 that were not taken into account to make Kurmi Unified Provisioning and Selfcare compliant with this version. It is an ongoing activity that will be included in the next major Kurmi Unified Provisioning and Selfcare release Support Technical support for Kurmi products can be found as follows: 3 of 23

4 3. Reference Configuration Figure 1 illustrates the network topology used during compliance testing. The Avaya solution consists of Communication Manager, System Manager, Session Manager, Avaya Messaging and a G430 Gateway. The Kurmi Unified Provisioning and Selfcare Server was installed on Virtual Machine running CentOS and connected to the same Network as the Avaya equipment. A client PC with a web browser was used to access the Kurmi application. Figure 1: Avaya and Kurmi Reference Configuration 4 of 23

5 4. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Avaya Equipment Software / Firmware Version Avaya Aura Communication Manager R6.3 Build R016x running on VMware Avaya Aura Session Manager R6.3.7 Software Update running on VMware Avaya Aura System Manager running on VMware R6.3.7 Build Update Avaya Aura Messaging running on a Dell R6.1 Version PowerEdge R610 Avaya G430 Media Gateway Version /1 Kurmi Equipment Software / Firmware Version Kurmi Unified Provisioning and Selfcare Version running on VMware 5 of 23

6 5. Configuration of Avaya Aura Communication Manager The only configuration relating to Communication Manager is that an Administrator account as a Privileged Administrator is required for Kurmi. Also Server access of port 5022 needs to be enabled. Note: The IP address and Release of the Communication Manager will be required for the Kurmi configuration Configure Privileged Administrator To access the OAM web-based interface of the Communication Manager use the URL where x. x. x. x is the selected IP address of Communication Manager. The Management console is displayed. Log in using the appropriate credentials and click on the Login button. In the subsequent page click on Administration followed by Server Maintenance. 6 of 23

7 In the next page select Administrator Accounts from the left pane. On the Administrator Accounts page select the Add Login radio button followed by the Privileged Administrator radio button. Click on the Submit button to continue. 7 of 23

8 In the next page enter the following: Login name Enter Kurmi Additional groups Select prof18 Select type of authentication Click on the Password radio button Enter password or key Enter kurmipwd Re-enter password or key Re-enter the password Force password/key change on next login Click the No radio button Click the Submit radio button to save. 8 of 23

9 5.2. Server Access Port 5022 needs to be enabled so as allow Kurmi access to Communication Manager. Select Server Access from the left pane. In the Server Access page click on the Enable radio button for SAT. Click on the Submit button to save. 9 of 23

10 6. Configuration of Avaya Aura System Manager The only configuration relating to System Manager is that an Administrative User with a System Administrator Role is required for Kurmi. Also TCP port 443 needs to be enabled, this port is opened by default. Note: The IP address and Release of the System Manager will be required for the Kurmi configuration Configure Administrative User To access the OAM web-based interface of the System Manager use the URL where x. x. x. x is the selected IP address of the System Manager. Once the System Manager Web page opens, log in with the appropriate credentials and click the Log On button. In the subsequent page click on Administrators in the Users pane. 10 of 23

11 When the Administrative Users page opens click on the Add button. When the Add New Administrative User page opens enter the following: User ID Enter kurmi Authentication Type Click the Local radio button Full Name Enter Kurmi provisioning User Status Click the radio button Temporary password Enter a Temporary password Re-enter password Re-enter the password Click on the Commit and Continue button. Note: The next time the kurmi user logs on the System Manager the password will be required to be changed. Use kurmipwd as this password. The procedure for changing this password is beyond the scope of these Application Notes. 11 of 23

12 When the next page opens using the scroll bar on the right side of the Roles pane scroll down and click the System Administrator box. Click on the Commit button to save. 7. Configuration of Avaya Aura Session Manager There is no specific configuration of Session Manager. Note: Release of the Session Manager will be required for the Kurmi configuration. 8. Configuration of Avaya Aura Messaging The only configuration requirement on Aura Messaging is to set the LDAP port and LDAP SSL ports. Note: The IP address and Release of the Aura Messaging will be required for the Kurmi configuration Configure the LDAP port and LDAP SSL port To access the OAM web-based interface of Aura Messaging use the URL where x. x. x. x is the selected IP address of Aura Messaging. The Management console is displayed. Log in using the appropriate credentials and click on the Logon button. 12 of 23

13 In the subsequent page click on Administration followed by Messaging. When the Messaging Administration page opens, select System Ports and Access from the left navigation pane. 13 of 23

14 When the System Ports and Access page opens Scroll down to the System TCP/IP Ports section. Configure and enable the LDAP and LDAP SSL ports. The LDAP Port is 389 and the LDAP SSL Port is 636. Select Authenticated or Anonymous from the drop down box. Click on the Save button on the bottom of the page (not shown). 9. Configure Kurmi Unified Provisioning and Selfcare At the request of Kurmi the configuration of Kurmi Unified Provisioning and Selfcare is not required as a part of these Application Notes. Kurmi Unified Provisioning and Selfcare is installed and configured by Kurmi Professional Services or trained Kurmi partners. 14 of 23

15 10. Verification Steps This section provides tests that can be performed to verify correct configuration of the Avaya and Kurmi solution Verify synchronisation To access the OAM web-based interface of Kurmi use the URL where x. x. x. x is the selected IP address of Kurmi. The Sign in page is displayed. Log in using the appropriate credentials and click on the Enter button to continue. In the subsequent page click on the Substitute button 15 of 23

16 On the next page click on admincpn. 16 of 23

17 Verify Avaya Lines synchronisation Click on Lines followed by the Discover icon, a pop up will appear, click on ACM (not shown). Kurmi will synchronise with Communication Manager. A list of extensions that are configured on Communication Manager will be displayed. This list should match the extensions configured on Communication Manager (See Section ). 17 of 23

18 Display Extensions on Avaya Aura Communication Manager Using SAT use the list station command to display all the extensions configured on Communication Manager. Verify that this list matches the Lines shown in Section list station Page 1 STATIONS Ext/ Port/ Name/ Room/ Cv1/ COR/ Cable/ Hunt-to Type Surv GK NN Move Data Ext Cv2 COS TN Jack 1000 S00000 Extn, no S00001 Extn, no S , Extn SIP no S00002 Extn, SIP no V201 Digital, no S00007 Extn,1005-Softphone no S00010 Extn,1006-VideoSoftphone no 1 1 press CANCEL to quit -- press NEXT PAGE to continue Mail box synchronisation Click on Aura Messaging followed by the Discover icon, a pop up will appear, click on Aura Messaging (not shown). Kurmi will synchronise with Aura Messaging. A list of Mail boxes that are configured on Aura Messaging will be displayed. This list should match the mail boxes configured on Aura Messaging (See Section ). 18 of 23

19 User Report on Avaya Aura Messaging Access the OAM web-based interface of Aura Messaging (not shown) and select Administration Messaging (not shown). When the Messaging Administration page opens, select Users from the left pane. In the Reports page that is now displayed, verify that this list matches the mail boxes shown in Section of 23

20 Verify Avaya Aura System Manager synchronisation Click on System Manager followed by the Discover icon, a pop up will appear, click on Aura System Manager (not shown). Kurmi will synchronise with System Manager. A list of SIP Users that are configured on Aura Messaging will be displayed. This list should match the SIP Users configured on System Manager (See Section ) User Management on Avaya Aura System Manager Access the OAM web-based interface of System Manager (not shown) and select User Management. 20 of 23

21 When the User Manager page opens, verify that this list matches the list shown in Section of 23

22 11. Conclusion A full and comprehensive set of feature functional test cases were performed during compliance testing. All test cases passed and met all objectives. Kurmi Unified Provisioning and Selfcare is considered compliant with Communication Manager 6.3/System Manager 6.3 and Aura Messaging 6.1 with one obersavation in Section Additional References These documents form part of the Avaya official technical reference documentation suite. Further information may be had from or from your Avaya representative. [1] Administering Avaya Aura Communication Manager, Release 6.3, October 2013, Document Number , Issue 9.0. [2] Administering Avaya Aura System Manager, Release 6.3, Issue 3, October, 2013 [3] Administering Avaya Aura Messaging, Release 6.1 June 2012 Product Documentation for Kurmi can be obtained at: 22 of 23

23 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 name and filename, located in the lower right corner, directly to the Avaya DevConnect Program at 23 of 23