Unify Ready. Technology connectivity certification. Konftel 300Wx via Konftel IP DECT 10

Transcription

1 Unify Ready Technology connectivity certification The connectivity of Konftel 300Wx via Konftel IP DECT 10 developed by Konftel AB has been certified at the SIP Interface of in accordance with the respective test report. Konftel AB is now entitled to label the above mentioned product with the Unify Ready emblem. The test was conducted conforming to DIN EN ISO This certificate is only valid in conjunction with the full test report and the notes contained therein. Please consider that the test report only covers the functionality of the interface. The certificate and test report are not good for a statement of end-to-end functionality. Munich, February 17 th 2017 Luzia Stephan Director Technology Partner Program Copyright Unify Software and Solutions GmbH & Co. KG, 2017 Mies-van-der-Rohe-Str. 6, D Munich, Germany All rights reserved. Unify, OpenScape, OpenStage and HiPath are registered trademarks of Unify Software and Solutions GmbH & Co. KG. All other company, brand, product and service names are trademarks or registered trademarks of their respective holders.

2 Test Report of Certification Konftel 300Wx IP DECT 10 with OpenScape Business Version 2 Test Status: Released with restrictions Release Date: February 3, 2017 Copyright Unify Software and Solutions GmbH & Co. KG, 2017 Reproduction and distribution of this document as well and the use and communication of the information contained without explicit permission is prohibited. Violation of this copyright will result in claim for compensation. All rights, including rights created by patent grant or registration of model or design, are reserved.

3 Contents: History of Change Overview Test Object Basic Equipment Konftel Test Strategy Test Intensity Measuring / Test Instruments Realisation Data Test Results Summary Problems Restrictions Remarks Configuration Konftel 300Wx OpenScape Business Configuration Block Diagram Test Results in Detail Connectivity and Basic Operation Basic call Telephony features Multi-account Support Audio features Remarks Configuration Data OpenScape Business System Basics Konftel Documentation Basic Configuration Confirmation Page 2 of 15

4 History of Change Date Description Name September 2016 Initial Version UNIFY Service PS Phone: Eddy Sterckx eddy.sterckx@unify.com Phone: September 2016 Certification tests UNIFY Service PS michel.lambrecht@unify.com Phone: Oktober 2016 Review test document & update results UNIFY Service PS michel.lambrecht@unify.com Phone: October -December 2016 Interaction with Konftel for open issues UNIFY Service PS michel.lambrecht@unify.com Phone: Oktober 2016 Final review Eddy De Braekeleer UNIFY Service PS eddy.debraekeleer@unify.com Phone: Oktober 2016 Release Eddy De Braekeleer UNIFY Service PS eddy.debraekeleer@unify.com Phone: Page 3 of 15

5 1 Overview 1.1 Test Object Test system: Basic Equipment OpenScape Business Software Version: - Switch Type: OpenScape Business X5 with OCAB - Software Version osbiz_v2_r2.0.0_243 Gateways Konftel Certification: Test the functionality of the Konftel 300Wx (conference device) / IP DECT 10 (DECT base station) with the OpenScape Business Test Equipment: OpenScape Business, Openstage SIP, OpenStage HFA, OpenStage T, Konftel 300Wx/IP DECT 10 Software Release: Released on 4-Oktober-2016 (latest version of Konftel available at this time) HW / FW Release: Konftel 300Wx/IP DECT 10 Manufacturer: Description: Documentation: Test Network: Test Configuration: Konftel Konftel 300Wx/IP DECT 10 functions as a SIP device on the OpenScape Business. Installation Guide Test network of OpenScape Ready Lab Brussels See section Test Strategy This certification test for the Konftel 300Wx with the Unify OpenScape Business focused on the verification of the SIP interface in the following scenarios: Basic phone configuration and registration Basic calls Telephony feature verification Page 4 of 15

6 Multi account support Audio features, including codec s and DTMF Following topics were not part of the certification: - security/encryption (802.1x) q (vlan tagging) - Factory reset - Softclient Unify - SRTP (Secure RTP) - OpenScape Business build in call center - External OpenScape Call Center (OSCC) - Redundance - OpenScape Business in networking - Stress tests - UC calls (One Number Service, smartphone applications, UC clients etc) - External voic systems - DECT base station other than Konftel IP DECT10 (reason is that Konftel seems to send proprietary codes to the DECT base station to start conference etc) Test Intensity Scope of the tests is to execute and verify the solution performs within the limits of the system requirements, targeting the end product. To accomplish this, feature and solution based test cases are created, inspected, and executed under a real system environment (mirroring as close as possible a real customer's environment). Note: The testing of the product with regard to compliance to requirements for Product Safety, EMV, Network Access Interfaces and Radiation Protection were not performed. Unify Communications therefore assumes no responsibility for the compliance to these requirements Measuring / Test Instruments No special hardware for tracing. Tracing was done on the switch equipment (mirroring ports, Wireshark) and on the OpenScape Business server. 1.3 Realisation Data Test Preparation: September 19 th 2016 Test Duration: September th 2016 Test Location: Unify Communications Demeurslaan Huizingen International Solution Lab Page 5 of 15

7 Test Personnel: Unify: Eddy Sterckx Coordination: Eddy De Braekeleer Test Results Summary For the details please have a look at the test results Problems 1 Test case SNTP can be configured (NTP datagram s can be found in Wireshark trace and are ) on the IP DECT 10 but the date and time info is not send to the 300Wx. Time and Date needs to be configured manual on the 300Wx. 2 Test case No SIP message is sent from DUT to initialize the Hold (only microphone and speaker are disabled) this means that the OSBiz phone continues streaming RTP. DUT indicates HOLD on display. The OSBiz phone also does not know he was being put on hold, and thus does not play back any MOH. 3 Major issue: Test case &21 Second call is activated on DUT. 200 can initiate the second call and gets ring back tone but there is no indication of this on DUT and it not possible to accept the second call. This means that a second person can never call the DUT, so the DUT can never initiate a conference, unless he calls himself the second, 3 rd party member etc. This is a major problem, which makes that the DUT is hardly usable as conference device, since it can receive/indicate only one incoming call Restrictions 1 Test case 3.2.1&2&8&9 and and Functionality is but in ringing and connect state, no calling number nor calling name is shown on DUT. 2 Test case 3.2.5&6&10&11 Functionality is but In ringing state DUT displays the from calling name but not the from calling number. In connect state neither calling number nor calling name is shown on DUT. 3 Test case No possibility on DUT to retrieve the first call. Going ON-hook at DUT, both calls are disconnected. 4 Test case Functionality is. No display indication of conference on DUT. Neither calling number nor calling name. 5 Test case Works as designed: Call Pickup not supported for SIP devices. 6 DECT base station other than Konftel IP DECT10 were not tested. Reason is that Konftel seems to send proprietary codes to the DECT base station to start conference etc. Page 6 of 15

8 Remarks Page 7 of 15

9 2 Configuration 2.1 Konftel 300Wx The Konftel 300Wx device has been configured by Unify. 2.2 OpenScape Business - Switch Type: OpenScape Business X5 with OCAB - Software Version osbiz_v2_r2.0.0_243 Openstage SIP V3 R4.8.0 OpenStage HFA V3 R Configuration Block Diagram OpenScape Business V2 Konftel IP DECT 10 phones PSTN PSTN Konftel 300Wx Admin PC Page 8 of 15

10 3 Test Results in Detail 3.1 Connectivity and Basic Operation The following table shows the list of test cases and the associated results for the verification of basic phone connectivity via the SIP interface. Test Case Test Description Result Comment 300Wx/IP DECT 10 Connect the test phone to its AC power supply and the LAN. Verify that the phone obtains a valid IP address from the DHCP server. Connect the test phone to a PoE source and verify that it powers up correctly and obtains a valid IP address from the DHCP server. Connect a PC to the lab LAN and verify that access to the web GUI of the test phone is possible. User ID= admin, password= admin. Program the phone via web GUI with the OpenScape Business registrar information and verify that the phone registers. Change the OpenScape Business subscriber settings so that Digest Authentication is required for the registration. Verify that the phone does not register. Add the information for Digest Authentication to the test phone settings via web GUI and verify that the phone registers. Verify that the test phone displays the local date and time correctly that is provided by the SNTP server. NA N IP address is also visible on the 300Wx IP DECT 10 requires a power supply. Note: when changing from SIP via UDP to SIP via TCP, the IP DECT 10 Base station needs to reboot manually to operate correctly. See 1 in section Page 9 of 15

11 3.2 Basic call The following table shows the list of test cases and the associated results for the verification of basic calls. All tests are executed with G.711A codec setting. Test Case Test Description Result Comment 300Wx/IP DECT 10 Initiate a call from the DUT to internal subscriber 100. See 1 in section Verify that 100 is ringing (DUT receives ring back) and that the displays on the DUT and 100 show the correct N called/calling number/name information. From the previous test case answer the call at 100 and verify speech path between both phones. Verify that the phone displays show the correct information after the call connected. From the previous test case disconnect the call at the DUT and verify that both phones return to idle state. Repeat the previous call, but disconnect the DUT before 100 answers. Verify that the DUT returns to idle state. Initiate a call from 100 to the DUT. Verify that the DUT is ringing (100 receives ring back) and that the displays on the DUT and 100 show the correct called/calling number/name information. From the previous test case answer the call at the DUT and verify speech path between both phones. Verify that the phone displays show the correct information after the call connected. From the previous test case disconnect the call at the DUT and verify that both phones return to idle state. Initiate a call from the DUT to an external number. Verify that the external phone is ringing (DUT receives ring back) and that the displays on the DUT and the external phone show the correct called/calling number. From the previous test case answer the call at the external phone and verify speech path between both phones. Verify that the phone displays show the correct information after the call connected. Initiate a call from an external number to the DUT. Verify that the DUT is ringing (external phone receives ring back) and that the displays on the DUT and the external phone show the correct called/calling number. From the previous test case answer the call at the DUT and verify speech path between both phones. Verify that the phone displays show the correct information after the call connected. N N N N N N N See 1 in section See 2 in section See 2 in section See 1 in section See 1 in section See 2 in section See 2 in section Page 10 of 15

12 3.3 Telephony features The following table shows the list of test cases and the associated results for the verification of telephony features in various call situations. All tests are executed with G.711A codec. Test Case Test Description Result Comment 300Wx/IP DECT 10 Initiate a call from the DUT to internal subscriber 100. Answer the call at 100. Put the DUT on hold and verify that it receives Music-on-hold. From the previous test case retrieve the DUT from hold and verify speech path between the DUT and 100. Initiate a call from internal subscriber 100 to the DUT. Answer the call at the DUT. From the DUT put 100 on hold and verify that it receives Music-on-hold. From the previous test case retrieve 100 from hold and verify speech path between the DUT and 100. Initiate a call from the DUT to internal subscriber 100. Answer the call and initiate consultation at 100. Verify that the DUT receives Music-on-hold. From the previous test case return from consultation and verify speech path between the DUT and 100. Initiate a call from internal subscriber 100 to the DUT. Answer the call and initiate consultation at the DUT. Verify that 100 receives Music-on-hold while the DUT receives dial tone. From the previous test case dial 200 at the DUT. Answer the call at 200. Verify that the DUT can toggle between 100 and 200. From the previous test case initiate a supervised transfer at the DUT so that 100 and 200 are connected. Verify that 100 and 200 have speech path, the displays are correct, and that the DUT returns to idle state. Initiate a call from the DUT to internal subscriber 100. Answer the call and initiate consultation at the DUT. Dial 200 and perform a blind transfer to 200. Answer 200 and verify that 100 and 200 have speech path, the displays are correct, and that the DUT returns to idle state. From the previous test case (3.3.9) invoke the last number redial function on the DUT and verify that it calls 200. Initiate a call to the DUT from an external number. Answer the call, then disconnect. Verify that the external number can be called from the call history list. Initiate a call from the DUT to internal subscriber 100. Answer the call and initiate a three-way conference from the DUT with 200. Verify that all parties have speech path and that the displays on the phones indicate the conference. N NA NA NA DUT indicates HOLD on display See 2 section See 3 in section No toggle function on DUT No supervised transfer function on DUT No blind transfer function on DUT Page 11 of 15

13 Test Case Test Description Result Comment 300Wx/IP DECT 10 From the previous test case go on-hook at 100. Verify that the DUT and 200 are in two-party talk and the displays are updated accordingly. Call an external number from 100. Once connected use 100 to add the DUT to a three-way conference. Verify that all parties have speech path and that the displays on the phones indicate the conference. From the previous test case release the conference master 100. Verify that the DUT and the external phone disconnected. Call the DUT from 100 after the Do-Not-Disturb function was activated. Verify that the call is rejected. Activate call forwarding on the DUT to 200. Call the DUT from 100 and verify that the call is forwarded to 200. Put the DUT and 100 in the same pickup group. Call 100 from 200. Works As Designed: DUT not indicating any call. SIP devices cannot be part of a call pickup. Call the DUT from 100. While connected, call the DUT from 200 and verify that a call waiting indication is presented on the DUT that shows the calling party information. From the previous test case accept the waiting call and verify that speech path is established between the DUT and 200. Verify that 100 is put on hold. NA NA N N Call 100 from the DUT and reject the call at Call 100 from the DUT and deflect the call to Verify that the DUT indicates the call deflection. Make the DUT busy and then call it from 100. Verify that the call is forwarded to the voic system (Xpressions) and that the message waiting indication (MWI) on the DUT is turned on. From the previous test case retrieve the voic message and verify that the MWI is turned off. While the MWI is lit on the DUT, disconnect the DUT from power and force a reboot. Verify that after the reboot is complete, the MWI is turned on. While the MWI is lit on the DUT, reboot the Xpressions server. Verify that after the reboot is complete, the MWI is turned on. N NT NT NT NT No DND function on DUT DUT supports CFU, CFB, CFNA, all three have been tested. See 5 in section See 3 in section See 3 in section See 1 in section No Xpressions VM available Page 12 of 15

14 3.4 Multi-account Support The following table shows the list of test cases and the associated results for the verification of multi account support of the Konftel SIP phones. Test Case Test Description Result Comment 300Wx/IP DECT 10 Program the second phone (account) via web GUI with the OpenScape Business registrar information and verify that the phone registers. Change the OpenScape Business subscriber settings so that Digest Authentication is required for the registration. Verify that the phone does not register. Add the information for Digest Authentication to the test phone settings via web GUI and verify that the phone registers. Set the second account as default account, check if DUT indicates that this account is active. Initiate a call from the DUT to internal subscriber 100. Verify that 100 is ringing (DUT receives ring back) and that the displays on 100 show the correct called/calling number/name information. From the previous test case answer the call at 100 and verify speech path between both phones Initiate a call from 100 to the DUT account 1. Verify that the DUT is ringing (100 receives ring back). Answer the call and verify speech path between both phones. From DUT, setup a five-way conference, two outgoing call from account 2 and two incoming calls to account 1. Verify that the conference can be established NS N NS First account/extension is always the default account See 1 in section Called name/number extension 1 on 100. Only two simultaneous calls supported. Page 13 of 15

15 3.5 Audio features The following table shows the list of test cases and the associated results for the verification of various audio features, including codec settings and DTMF transmission. Test Case Test Description Result Comment 300Wx/IP DECT 10 Configure 100 to use the G.729 codec only. Call the DUT and verify that the connection is established with G.729 (use Wireshark). Configure 100 to use the G.729 codec preferably. Call the DUT and verify that the connection is established with the first matching codec supported by the DUT or rejected if no match is found. DUT G711 only Configure 100 to use the G.722 codec preferably. Call the DUT and verify that the connection is established with G.722 (use Wireshark). Configure the DUT for DTMF transmission via RFC Call the Auto Attendant (Conf bridge) from the DUT. Verify that the Auto Attendant responds to the phone s DTMF keys (also use Wireshark). Configure the DUT for DTMF transmission via inband tones. Call the Auto Attendant (Conf bridge) from the DUT. Verify that the Auto Attendant responds to the phone s DTMF keys. 100 G.729 only, call rejected 100 G.729 and G.711, call G.711 Activate on DUT via the Menu, Activate DTMF 3.6 Remarks Meanings of Abbreviations: Testcase successful N Testcase NOT successful NA Testcase not applicable NP Testcase not processed NS Situation not supplied N *X Error / restriction with description * X Remark to Functionality DUT Device Under Test CFU Call Forwarding Unconditional CFNR Call Forwarding on No Reply CFB Call Forwarding on Busy MLHG Multi Line Hunt Group moh music-on-hold DND Do Not Disturb Page 14 of 15

16 Unify Konftel 300Wx/IP DECT 10 4 Configuration Data 4.1 OpenScape Business For each SIP user that represents a Konftel user, an IP User license is needed on OpenScape Business System Basics The OpenScape Business configuration (KDS). 4.2 Konftel Documentation Basic Configuration Konftel 300Wx-IP DECT 10 configuration (screenshots): 5 Confirmation Testing personnel confirms that all the test cases were performed and that the results were as described in this document. Unify Belgium Konftel Page 15 of 15