Application Notes for VoSKY Technologies Exchange 9140 with Avaya PARTNER ACS - Issue 1.0

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for VoSKY Technologies Exchange 9140 with Avaya PARTNER ACS - Issue 1.0 Abstract These Application Notes describe the configuration required for VoSKY Technologies Exchange 9140 to successfully interoperate with Avaya PARTNER ACS. Exchange 9140 is a 4-port Voice over IP (VoIP) gateway that connects to Avaya PARTNER ACS analog station ports, and is used to route calls to/from a 3 rd party VoIP Service Provider such as Skype. 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 29

2 1. Introduction These Application Notes describe the configuration required for VoSKY Technologies Exchange 9140 to successfully interoperate with Avaya PARTNER ACS. Exchange 9140 is a 4-port Voice over IP (VoIP) gateway that connects to Avaya PARTNER ACS analog station ports, and is used to route calls to/from a 3 rd party VoIP Service Provider such as Skype. Figure 1 illustrates the network configuration used to verify VoSKY Technologies Exchange 9140 with Avaya PARTNER ACS. The configuration consisted of Avaya PARTNER ACS with Avaya PARTNER 18D and analog telephones, VoSKY Technologies Exchange 9140, VoSKY Technologies Exchange Server, and an Internet VoIP user (Skype user). Analog station ports on Avaya PARTNER ACS were connected to the Exchange The Exchange 9140 had a USB connection to the Exchange Server, which was connected to the Internet. The test configuration also included an analog trunk port connection to the Public Switched Telephone Network (PSTN). Figure 1: Network Configuration Avaya DevConnect compliance testing focused on VoSKY Exchange 9140 product interoperability with Avaya PARTNER ACS. Though a 3 rd party VoIP Internet Service Provider such as Skype was used to complete the compliance test, Skype was not certified as part of this compliance test. 2 of 29

3 2. Equipment and Software Validated The following equipment and software/firmware were used for the sample configuration provided: Equipment Software Avaya PARTNER ACS R6 (89.T) Avaya PARTNER Voice Messaging 3.0 Avaya PARTNER 18D Telephones - Analog Telephones - VoSKY Technologies Exchange VoSKY Technologies Exchange Server Configure Avaya PARTNER ACS The configuration information provided in this section describes the steps required to configure Avaya PARTNER ACS to interoperate with VoSKY Technologies Exchange For all other configuration information, please refer to the Avaya PARTNER ACS product documentation in Section Physically connect an available analog station port on Avaya PARTNER ACS to an available FXO port on the Exchange Make a note of the extension number connected to the Exchange Configure Automatic Line Selection for the extension setup in Step 1 as follows: From PARTNER ACS extension 10 or 11, press (Feature) (0) (0) (System Program) (System Program) (Central Tel Program). Enter the number of the extension setup in Step 1. Press (*) (*). Press (Right Intercom) (Left Intercom). For each button pressed, a display similar to the following appears: Automatic Line Selection To exit Automatic Line Selection, press (*) (*). Press (Central Tel Program). Press (Feature) (0) (0) to exit System Program mode. 3. Repeat Steps 1 2 for each analog station port to be connected to Exchange Note: Disable voic for any extension connected to the Exchange Configure VoSKY Technologies Exchange 9140 There was no special configuration required for the Exchange 9140 to interoperate with Avaya PARTNER ACS besides physically connecting its FXO ports to station ports on Avaya PARTNER ACS as described in Section 3. For all other configuration information, please refer to the VoSKY Technologies product documentation in Section of 29

4 5. Configure VoSKY Technologies Exchange Server The configuration information provided in this section describes the steps required to configure VoSKY Technologies Exchange Server to interoperate with Avaya PARTNER ACS. For all other configuration information, please refer to the VoSKY Technologies product documentation in Section 10. Note: Screens demonstrating the installation and configuration of Exchange Server for this test configuration has been provided in Section 11 as a reference. 1. Launch the Line Probe Utility provided in the VoSKY Technologies Exchange 9140 Installation CD to detect the telecom parameters of Avaya PARTNER ACS (not shown). 2. In the Line Probe Utility window that appears, set Hunt Group Ext. Number to the extension number of the 1 st extension connected to the Exchange In the test configuration, the extension number was 15. Click the Scan button in the Generic Tone Scan portion of the window. 3. In the popups that appear, click the OK button. 4 of 29

5 4. In the Line Probe Utility window, set Ext Number in the Congestion Tone Scan portion of the window to a valid extension number. In the test configuration, it was set to 11. Click the Scan button in the Congestion Tone Scan portion of the window. 5. In the popup that appears, click the OK button. 5 of 29

6 6. In the Line Probe Utility window, click the Analyze button in the Analysis portion of the window. 7. In the popup that appears, click the OK button. 6 of 29

7 8. In the Line Probe Utility window, click the Save button in the Analysis portion of the window to save the scanned settings. In the Warning popup that appears, click Yes. Note: The Line Probe Utility was unable to detect Busy Tone on Avaya PARTNER ACS during its analysis. This missing information was manually entered in Step In the Open File popup that appears, browse to a directory in which to save the scanned settings file, type a file name and click the Save button. Make a note of where the file is stored. In the test configuration, the file custom.ini was saved on the Desktop. 7 of 29

8 10. In the popup that appears, click the OK button. 11. Close the Line Probe Utility (not shown). 12. Install and configure Skype software on the VoSKY Exchange Server as instructed in the VoSKY Technologies product documentation referenced in Section Install and configure Exchange Server on the VoSKY Exchange Server PC as instructed in the VoSKY Technologies product documentation referenced in Section Restore the VoSKY Console window to the Desktop (not shown). Note: The Console window is automatically launched once it is activated during installation. 15. In the Console window that appears, select the Settings tab. In the Settings tab that appears, click the Change button. 8 of 29

9 16. In the window that appears, click the Import button. In the Open popup that appears, browse to the file created in Step 9, select it and click the Open button. 17. In the Console window, set Busy Tone 2 Frequency (Hz) to 480 and 620 and Cadence to 500 and 500. Click the Save Settings button to save the changes. Minimize the Console window. 9 of 29

10 18. Browse to the VoSKY Exchange administration page on or from the VoSKY Exchange Server PC and log in using administrative credentials. 19. In the VoSKY Exchange web page that appears, click Options in the left pane. 10 of 29

11 20. In the Options page that appears, scroll down to the PBX Settings portion of the page as shown and click the Add button. 21. In the VoSKY Exchange window that appears, type in the extension numbers that were connected to the Exchange 9140 in Section 3. In the test configuration, extensions 15 and 16 were connected to the Exchange Click the OK button. 11 of 29

12 22. In the VoSKY Exchange window, scroll to the bottom of the page and click the SAVE button. 6. Interoperability Compliance Testing Interoperability compliance testing included feature/functionality and serviceability testing. Feature/functionality testing examined Exchange 9140 and Exchange Server s ability to place inbound and outbound VoIP calls. Serviceability testing introduced failure scenarios to verify Exchange 9140 and Exchange Server could resume placing and receiving calls after failure recovery General Test Approach Feature/functionality testing was performed manually on Avaya PARTNER ACS configured in Key mode. An analog loop start trunk from the central office was connected to an available trunk port on Avaya PARTNER ACS. A couple of designated analog station ports on Avaya PARTNER ACS were connected to FXO ports on the Exchange The general test approach was to manually place calls from Avaya PARTNER ACS telephone extensions to Avaya PARTNER ACS telephone extensions connected to the Exchange Upon receiving a call from a telephone extension, the Exchange auto attendant would answer the call and prompt the caller for a valid speed dial number. The Exchange 9140 would only place VoIP calls to Skype user IDs that are listed in the Exchange Server phonebook. Inbound calls from a Skype user were placed to Skype user accounts associated with the Exchange These calls rang and were answered by the Exchange auto attendant, which would prompt the Skype user for the 12 of 29

13 desired extension number. Upon entering an extension number, the Exchange auto attendant would transfer the caller to the desired extension on Avaya PARTNER ACS. Calling features such as hold, transfer, and conference were exercised on PARTNER ACS telephone extensions involved in calls to a Skype user. Testing also included verifying successfully leaving and retrieving voic from inbound calls placed by a Skype user to the Exchange For serviceability testing, failures such as power failures affecting PARTNER ACS, Exchange 9140 and Exchange Server were performed Test Results Barring the issues described below, all remaining feature and serviceability tests passed. Exchange 9140 and Exchange Server properly routed inbound Skype calls to PARTNER ACS and outbound calls from PARTNER ACS to Skype users. Unable to leave voic when calling from an Internet VoIP (Skype) user. Attempts to leave voic for calls placed by a Skype user to an Avaya PARTNER ACS telephone extension that went to voic coverage were unsuccessful. This is under investigation by VoSKY Technologies. Unable to retrieve voic when calling from an Internet VoIP (Skype) user. Attempts to retrieve voic for calls placed by a Skype user to an Avaya PARTNER ACS telephone extension that went to voic coverage were unsuccessful. This is under investigation by VoSKY Technologies. Disconnect issue for analog trunk calls routed to extensions connected to Exchange One test scenario involved an inbound analog trunk call routed to an extension connected to the Exchange Though Exchange 9140 s auto attendant properly connected the call to a remote Skype user. When both parties dropped the call, the analog trunk line was not released on Avaya PARTNER ACS. This is under investigation by VoSKY Technologies. Skype login file had to be recreated on Exchange Server power failure. When the Exchange Server was subjected to a power failure, it appeared to lose the Skype login file settings. This is under investigation by VoSKY Technologies. 7. Verification Steps The following steps may be used to verify the configuration. From a PARTNER 18D telephone extension, dial the extension number of the extension connected to the Exchange When the Exchange auto attendant prompts for a number, enter a speed dial number already entered in the Exchange phonebook. Verify the Skype user associated with the speed dial number receives and answers the call as shown below. Verify the call clears when the Skype user hangs up. Place a call from a Skype user to a Skype account associated with the Exchange Verify Exchange auto attendant answers the call and prompts for an extension number. Enter a valid extension number and verify it rings at the desired Avaya PARTNER ACS telephone 13 of 29

14 extension. Answer the call at the extension. Verify the call connects properly and the call clears when the Skype user hangs up. 8. Support Technical support for VoSKY Technologies Exchange 9140 and VoSKY Technologies Exchange Server can be obtained by calling (719) or sending to or online via 9. Conclusion These Application Notes describe the configuration required for VoSKY Technologies Exchange 9140 and VoSKY Technologies Exchange Server to successfully interoperate with Avaya PARTNER ACS. Barring the issues described in Section 6.2, VoSKY Technologies Exchange 9140 and VoSKY Technologies Exchange Server successfully passed compliance testing. 10. Additional References Product documentation for Avaya products may be found at [1] Avaya PARTNER Advanced Communications System Installation, Programming, and Use, , Issue 6, July 2004 Product documentation for the Exchange 9140 may be found as follows. [2] Exchange 91XX Quick Start Guide, May 2007 may be found at [3] Exchange 91XX User Manual, May 2007 may be found at 14 of 29

15 11. Appendix A VoSKY Exchange Server test configuration screens This section is provided as a reference on how the VoSKY Exchange Server was configured in the compliance test configuration. Note: aevis1 was the Skype ID associated with the Exchange 9140 Port 1 aevis2 was the Skype ID associated with the Exchange 9140 Port 2 aetempx was the Skype ID associated with the Internet VoIP (Skype) user Install Skype application: 15 of 29

16 Install VoSKY Exchange 9140 Server software: 16 of 29

17 17 of 29

18 18 of 29

19 Configure VoSKY Exchange 9140 Server and Skype: 19 of 29

20 20 of 29

21 21 of 29

22 22 of 29

23 23 of 29

24 24 of 29

25 25 of 29

26 12. Appendix B Internet VoIP (Skype) End User Configuration Screens This section is provided as a reference on how the Internet VoIP (Skype) was configured on an end user desktop client in the compliance test configuration. Note: aevis1 was the Skype ID associated with the Exchange 9140 Port 1 aevis2 was the Skype ID associated with the Exchange 9140 Port 2 aetempx was the Skype ID associated with the Internet VoIP (Skype) user 26 of 29

27 27 of 29

28 28 of 29

29 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 29 of 29