Detailed End Point IVT Test Plan and Report for Cisco Communications Manager 11.0 and Ascom i62

Transcription

1 Test Report Detailed End Point IVT Test Plan and Report for Cisco Communications Manager 11.0 and Ascom i62 Test Date/ Result (Completed by Cisco) December 7, PASS Partner Product Name Partner Product Type Ascom i62 Wireless SIP phone Partner Product Version # 5.4 Cisco Product Name Cisco Product Version CUCM 11.0 Cisco Unified Communications Manager, Business Edition 6000, Business Edition 7000 API/Protocol(s) Used SIP Date Testing Completed December 7-12, 2015 IVT Contact Gert.wallin@ascom.com The following information is to be provided at the completion of the Test/Submission of Test Report. Failure to provide all information requested below will result in rejection of test for consideration. Lab Test was completed in: Engineer that executed the test Sandbox Johan Andrén / Johan.andren@ascom.com Important Note: Once testing is completed, this report must be submitted to Cisco. The engineer named above to have executed the test is confirming that all tests listed as executed were run and the results are those recorded (pass/fail). If it is determined that any test was not executed or any results are false, Cisco reserves the right to retract the Compatibility logo, rights to use, status of compatibility without testing fee refund. YEAR Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 60

2 Contents 1 Interoperability Verification Testing (IVT) Overview Interoperability Verification Testing Requirement IVT Objectives IVT Focus Instructions Product and Testing Information IVT Request info here Test Set Up and Tools Product Platform Description Product Deployment Description Product Description Product Integration Diagram Product Integrated Use Cases Test Plan Introduction Entry Criteria Exit Criteria Executive Summary Testing Details Items Tested Items Not Tested Assumptions Administration, Testing and Debugging tools Sandbox Topology Components Lab Network Topology Test Case Result Reporting Test Cases Endpoint Workflow & Test Case Mapping Installation Tests Entrance Tests Features and Services Manual Functional Tests Manual Negative Tests Appendix A: Test Result Matrix 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 2 of 60

3 1 Interoperability Verification Testing (IVT) Overview 1.1 Interoperability Verification Testing Requirement Successful completion of Endpoint IVT is required for Partner Products to be designated as Cisco Compatible and for Partner Products to be listed in the Cisco Solution Marketplace. 1.2 IVT Objectives The IVT program s objective is to provide verification that 3rd party Partner product(s) meet the following criteria: Successfully Integrate and scale as defined by Cisco design guides and 3 rd party product specifications Install and functionally operate/perform as indicated in collateral and specifications (from integration perspective only) Successfully integrate with Cisco products while not adversely affecting Cisco product operation or the integrated solution. Use only supported integration methods. Supported integration methods (API s and protocols) can be found on the DevNet web site: IVT Focus Testing is focused on integration points of Partner products and Cisco products, not on the Partner product itself, to ensure quality integrations between 3rd party products and Cisco products. Test categories include: Installation and connectivity of partner product Validation of integrated features between Cisco product and partner product Negative testing (connectivity failure, redundancy, recovery) Performance and load testing of integration points/functionality, using a subset of functional test scenarios 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 3 of 60

4 2 Instructions Provide the requested information on the following pages for the product being submitted for Interoperability Verification Testing (IVT). 3 Product and Testing Information 3.1 IVT Request info here 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 4 of 60

5 4 Test Set Up and Tools This section refers to the product test tools that have been used during the development testing of the product being submitted for IVT Question Response What if any commercial test tools are used in the development and test of this product Can these tools and test scripts for these products be made available to support IVT Are there proprietary test tools that could be made available to support IVT 5 Product Platform Description 5.1 Product Deployment Description Provide the following information about the product and integration. Each of the items below is required in order to proceed with test scheduling. CUCM Configurations Cisco Unified Communications Manager (CUCM), version 11.0 configuration Caller Line Identities (CLI) require additional configuration CUCM license for Third-party SIP device implies some limitations, e.g. no Music-on-Hold (MoH) and lack of telephony features configurable from the handset etc Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 5 of 60

6 Device->Phone: Adding a device (phone). Part Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 6 of 60

7 Device->Phone: Adding a device (phone). Part 2 Note. Digest User (6500) refers to the End User created in next step Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 7 of 60

8 User Management -> End User: Adding an user ID Note. Digest Credentials is only used if Enable Digest Authentication is set in the security profile Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 8 of 60

9 System->Security->Security Profiles. - Third-party SIP Device Advanced - Standard SIP Non-Secure Profile default security profile Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 9 of 60

10 Ascom i62 configurations Note. The network settings may vary depending on the WLAN infrastructure used Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 10 of 60

11 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 11 of 60

12 5.2 Product Description Ascom i62 The Ascom i62 is a VoWiFi handset that offers enterprise-grade telephony, messaging and personal alarm capabilities. It is based upon modern Wi-Fi technology, with support for a/b/g/n standards. The Ascom i62 is an extremely durable, feature rich, and is designed specifically to support mission critical communication where reliability is a must. Supported by Ascom s comprehensive interoperability program, the Ascom i62 integrates seamlessly with CUCM, as well as infrastructure from leading vendors. Features The Ascom i62 is an extremely durable, feature rich, and is designed specifically to support mission critical communication where reliability is a must. Supported by Ascom s comprehensive interoperability program, the Ascom i62 integrates seamlessly with CUCM, as well as infrastructure from leading vendors. High quality telephony Interactive messaging Personal alarm with a dedicated button and man-down alarm Push-To-Talk Location with WiFi access points and Ekahau Centralized Management WiFi standards a/b/g/n, to operate in the existing WiFi infrastructure Integrates to CUCM via SIP, to provide a feature-rich telephony solution 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 12 of 60

13 5.3 Product Integration Diagram 5.4 Product Integrated Use Cases Ascom i62 will be used for telephony services with CUCM, BE6000 and BE7000 in enterprise customer deployments. 6 Test Plan 6.1 Introduction This document is the detailed Interoperability Verification Test Plan and Report for Cisco Unified Communications Manager and Third-Party SIP Endpoint. 6.2 Entry Criteria Before testing can begin 3rd party partner shall run this entire test plan in their lab and verify the results. If there are any test cases not supported, not applicable or are not successful, the partner should consult with IVT program team. Once testing has been initiated, the device under test is considered frozen for compatibility testing purposes. No software/firmware load can be changed during the testing period. However, configuration can be modified to accommodate testing Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 13 of 60

14 6.3 Exit Criteria To be deemed certified as configured, the devices under test should have zero severity 1 and severity 2 defects and up to two severity 3 defects. If a severity 1 or 2 failure occurs, irrespective of whom is responsible for the problem (Cisco or the 3rd party product), testing is considered unsuccessful. Defect Severity Level Severity Level Description 1 Catastrophic Common circumstance causes the entire system or a major subsystem to stop working. Affects other areas/devices and there is no workaround 2 Severe Important functions are unusable and does not affect other areas/devices. No workaround. 3 Moderate Very unusual circumstances cause failure. Minor feature does not work at all. It has low impact. There is a workaround. If any tests fail, the configuration will be verified to resolve the issue. If the issue cannot be resolved, the tester will attempt to continue testing if possible. If the testing is blocked due to this issue, then testing is considered complete and the devices under test will not receive a Compatibility Logo. Follow the procedures when testing fails: Preliminary analysis is made to determine the source of the problem. If the problem is related to a device under test, then the problem is reported to that partner. If the problem is deemed Cisco related, the problem will be reported to Cisco, but the partner is responsible to open a case with Cisco Developer Services. Partner should provide the Developer Services case number to the test team so they can document it in the report. If testing can continue past this failure, the other test cases will be tested and verified for pass or fail. If the testing cannot progress past this problem, testing will be halted and a final test report submitted to Partner and Cisco. All problems and resolutions encountered during testing are documented in the final test report If a severity 1 failure occurs, irrespective of whom is responsible for the problem (Cisco or the 3 rd party product), testing is considered unsuccessful. Any deviations of the test execution or problem acceptance are documented in the test report. NOTE: Cisco approval process may increase/decrease the severity level of the defect after the test cycle if considered necessary 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 14 of 60

15 7 Executive Summary The following summarizes results: No Test Case Failure but there are not supported or Not Applicable See Appendix 1 for details Features Not Supported: Cisco Soft key implementation, DND (Don t disturb), Speed dial, Call park, shared line Meet me conference, Callback, Advanced authentication, Group pickup. 8 Testing Details 8.1 Items Tested Features that are specific in this section are the high level categories the testing will focus on. 3 rd Party installation, configuration and validation Security Requirements Functional testing of the various features interfacing through the 3 rd party product to the Cisco product Negative tests in relation to service outages, restarts, bad files etc. 8.2 Items Not Tested Features that are specific to the internals of the 3 rd party product or any features not listed will not be tested. 8.3 Assumptions Interoperability of 3rd party products Testing will cover only features in 3rd party products that result in events to and/or from the Cisco product. Traffic Generation Simulation tools will be used to generate network traffic. 8.4 Administration, Testing and Debugging tools Tools used/required Identify any tools required by 3 rd party (partner under test). Also add Trace and Debug settings here. Administration, Testing and Debugging Tools Product Name Version Type Purpose Units Notes Test Tools Remote Phone Control 4.2 Phone Tool Controls Physical IP Phones remotely 1 Phoneview 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 15 of 60

16 Camelot Call Processing Simulate IP Endpoints and generate calls 3 3rd Party Tools Wireshark Version Collection of SIP trace information 1 Debug Tools Product Version Units Description CUCM PUB & 1SUB HQ & Branch CUCM Clusters CUPS Cisco Presence Server CUC Cisco Unity Connection Cisco PSTN Gateway IP Phones 5 Models:796, 794, 797, 89, 99 Camelot 3 IP Traffic Generator Lab Services 1 FTP/SFTP Server/RPC/AD DUT(s) Ascom i Sandbox Topology Components 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 16 of 60

17 8.6 Endpoint IVT Sandbox Topology 8.7 Test Case Result Reporting Result Pass (P) Fail (F) N/A N/S N/T Blocked (B) Description The test case passed with no exceptions The test case failed details of the failure are noted in the Comments column The test case is not applicable to the product under test. Provide justification in the Comments column. Not supported. While the feature tested by this test case generally would be considered a standard feature for this product category, this specific product (or this specific release) does not support the feature. Not tested. The feature is supported by the product under test, but external factors (lab configuration, e.g.) prevented execution of the test. Justification must be provided in the Comments column. Other test case failures prevented the execution of this test. Reference the failed test case in the Comments column Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 17 of 60

18 . 9 Test Cases This section details the tests that will be performed during the testing period. Partner is responsible for identifying any features or functions not supported covered in the test cases prior to start of testing 9.1 Endpoint Command Work Flow & Test Case Mapping Automation Work Flow Sections Test Case # Total Tests A/M Part1: Setup EP-1 1 M Part2: Functional Testing - Manual Call Generation EP-2 to EP M Part3: Negative Testing EP-43 to EP-46 4 M Part4: Load Testing EP-47 1 M Part5: Wrap Up Generate Report This section covers Integration & Validation of Third-Party Endpoint for CUCM Version 10.5 or 11.0 (selected at the time of reservation) Refer to Sandbox Guide for Sandbox Portal guidance Run cmds in Part1: Setup on the Endpoint IVT Sandbox Portal upon product integration Note: Pre-Test conditions for all test cases are provisioned in CUCM unless highlighted in green Integration Test Test is focused on ensuring that the 3 rd party product (DUT) is registered with Call Manager successfully 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 18 of 60

19 Test Case # EP-1 Category ConnectValidate RFC_Standard Y Objective Verify Third-Party SIP endpoints DUT(s) are registered in Call Manager successfully Hardware VPN Router setup to EP IVT Sandbox network Device-under-Test (DUT) DN Assignment: Local CUCM: ; Remote CUCM:8500; End Users: dutuser01, dutuser02, rdutuser01; Password: ciscopsdt; PIN:123456; 1. Select Setup category in SB Command pane 2. Run cmd Start_Traffic with duration=8 days 3. Connect three DUT(s) to the Hardware VPN router ports 4. Check if the DUT(s) are auto-registered with CUCM 5. If DUT(s) are not auto-registered with CUCM, do the following: Select Setup category in SB Command pane Run cmd My_Endpoint_Registration : Phone ModelThird_Party_SIP_Advanced Phone Load TypeSIP MAC AddressMAC Address of DUT-1 6. Repeat step 5 for DUT-2 7. Access 8. Provision DUT-3 manually with the following settings: DevicePhoneAdd New Phone TypeThird-party SIP Device (Basic/Advanced) MAC AddressMAC Address of DUT-3 Device PoolDefault Phone Button TemplateThird-party SIP Device Media Resource Group ListMGR-LIST1 OwnerUser Owner User IDrdutuser01 Device Securtiy ProfileSelect the unsecure profile SIP ProfileStandard SIP ProfileSave Select LineDN8500 Directory URI: rdutuser01@abc.inc Associate End User: 8500rdutuser01 User ManagementEnd UserUser IDrdutuser01 Device Association8500 Primary Extension Change TFTP IP address on DUT(s): DUT-1 & DUT-2:TFTP IP (Local Cluster) DUT-3: TFTP IP (Remote Cluster) 10. Check the network settings and dial-tone on DUT(s): DNS/DHCP IP Default Gateway (DUT-1 & 2) (DUT-3) CUCM IP (DUT-1 & 2); (DUT-3) 11. Access Update the following fields for DUT-1: DevicePhone: DN of DUT-1: OwnerUser Owner User IDdutuser01 Select Line6500 Directory URI: 6500dutuser01@abc.inc Associate End User: 6500dutuser01 User ManagementEnd User: Enduser of DUT-1:dutuser01 Device Association6500 Primary Extension Repeat step 12 for DUT-2: DN6501; Userdutuser02; Directory URIdutuser02@abc.inc Background traffic is running 3 DUT(s) provisioned and registered with CUCM(s) 2 DUT(s) registered with Local Cluster & 1 DUT registered with Remote Cluster Dial tone present on all DUT(s) when phone is off-hook DUT(s) network data is correct (DNS, DHCP, Default Gateway, TFTP, CUCM) DUT(s) DN updated to (Local) & 8500 (Remote) DUT(s) phone attributes updated accordingly All 3 DUT(s) registered with local and remote CUCM with the appropriate phone attributes Note: Auto-Registration is enabled on Local & Remote CUCM 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 19 of 60

20 OK, register manually This section covers Manual Call Flows Use Remote Phone Control (RPC) Tool to remotely control Cisco IP Phones for manual calls Execute instructions highlighted in green in each test case. Run cmd in Part2: Record_Manual_Call_Test_Execution on EP IVT Sandbox Portal when all the 9.2 Entrance Tests manual test cases are executed Retrieve CDR(s) in CUCM to validate calls Test to verify the basic functionality before proceeding further in certification testing. Test Case # EP-2 Category Entrance Test: Intra-Cluster Calls RFC_Standard Y Objective Verify intra-cluster calls between DUT and SIP endpoints G L O B A L Local CUCM Cluster ; Remote CUCM Cluster ; PSTN ; 9200 SIP Endpoints registered in Local Cluster Background Traffic running at 17K BHCA Background Performance Data Collection Configure Audio & Video Playback on an RDP Session on PC accessing Remote Phone Control Tool Server (RPC-Phoneview) RDP to RPC-Phoneview (IP: ) Refer to Sandbox Guide for Instructions on: Sandbox Portal Navigation RPC-Phoneview CUCM CDR Retrieval 2-Way Audio Path Validation Local CUCM DUT(s): ; SIP:9200; RPC-Phoneview remotely controls IP Phones: 9200; dials answers goes on-hook after 30s dials answers (Phoneview) 3. Select Headphone icon to enable monitoring 9200 on Phoneview 4. Enter Play:AreYouThere.raw & hit Send on the command line speaks Testing on-hook after 60s 7. Calling & Called party release calls alternatively 8. Retrieve CDR from CUCM 9. Check CDR(s) for the selected fields below Note: If Phones used in test case are in un-registered state, replace it with Phones that are in registered state. Call 1 established between 6500 & 6501 with 2-way audio Calling and Called parties hear ring-back and ring tone DUT receives Caller ID Call 1 terminated normally Call 2 established between 6501 & 9200 Calling and Called parties hear ring-back and ring tone DUT receives Caller ID 9200 displays monitoring active message with 6501 hears Are you There 9200 hears Testing 1234 Audio for 9200 is heard on pc running Phoneview 2-way audio path for call 2 is confirmed Call 2 terminated normally Retrieved CDR(s) matched calls CDR field Call 1 Call 2 callingpartynumber OriginalCalledPartyNumber finalcalledpartynumber origcause_value 16 0 destcause_value 0 16 duration Couldn t hear any sound from Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 20 of 60

21 9.3 Features and Services Tests Tests focused on CUCM features and services and the operational behavior of the third-party product (Device under Test - DUT) to ensure it corresponds to its design specifications. Test Case # EP-3 Category Functional Test: Inter-Cluster Call RFC_Standard Y Objective Verify inter-cluster calls between DUT(s) and SIP endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; Remote CUCMDUT:8500; SIP:6300; RPC-Phoneview remotely controls IP Phones :6300; dials answers goes on-hook after 30s dials answers 4. Select Headphone icon to enable monitoring on 6300 in Phoneview 5. Enter Play:AreYouThere.raw and hit Send on the command line speaks Testing goes on-hook after 60s 8. Calling & Called party release calls alternatively 9. Retrieve CDR(s) from CUCM 10. Check CDR(s) fields to verify call attributes accuracy Call 1 established between 6500 & 8500 with 2-way audio Calling and Called parties hear ring-back and ring tone DUT receives Caller ID Call 1 terminated normally Call 2 established between 6501 & 6300 Calling and Called parties hear ring-back and ring tone DUT receives Caller ID 6300 displays monitoring active message with 6501 hears Are you There 6300 hears Testing 1234 Audio for 6300 is heard on pc running Phoneview 2-way audio path for call 2 confirmed Call 2 terminated normally Retrieved CDR(s) matched calls 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 21 of 60

22 Test Case # EP-4 Category Functional Test: Off-Net Calls RFC_Standard Y Objective Verify basic calls between DUT(s) and PSTN endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones : ; dials answers 2. Select Headphone icon to enable monitoring on PSTN phone in Phoneview 3. Enter Play:AreYouThere.raw and hit Send on the command line speaks Testing goes on-hook after 60s dials Repeat steps 2-4 to check 2-way audio path goes on-hook after 60s 9. Retrieve CDR(s) from CUCM 10. Check CDR(s) fields to verify call attributes accuracy 2 calls established between 6500 & Calling and Called parties hear ring-back and ring tone DUT receives Caller ID displays monitoring active message with DUT(s) hears Are you There hears Testing 1234 Audio for is heard on pc running Phoneview 2-way audio path confirmed for both calls Call 2 terminated normally Retrieved CDR(s) matched calls Called instead of Test Case # EP-5 Category Functional Test: SIP URI RFC_Standard Y Objective Verify intra-cluster SIP URI calls between DUT and SIP endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Local CUCM DUT(s):6500 URIdutuser01@abc.inc; 6501 URIdutuser02@abc.inc; 9200 URIcuser01@abc.inc; RPC-Phoneview remotely controls IP Phones: 9200; Note: Provision URI on device page: DevicePhoneDNLineDirectory URI (Known bug if provisioned via End User Page) 1. Access to configure URI Speed Dial on DUT(s): DevicePhone: DN6500Select button 3Add new SDdutuser02@abc.inc DN6501Select button 3Add new SDcuser01@abc.inc hits Speed Dial button answers goes on-hook after 30s hits Speed Dial button answers goes on-hook after 30s hits Speed Dial button answers goes on-hook after 30s 8. Retrieve CDR(s) from CUCM 9. Check CDR(s) fields to verify call attributes accuracy DUT(s) receives Caller ID 3 calls established with 2 way audio 3 calls terminated normally Retrieved CDR(s) matched calls Not supported by i Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 22 of 60

23 Test Case # EP-6 Category Functional Test: SIP URI RFC_Standard Y Objective Verify inter-cluster SIP URI calls between DUT and SIP endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; Remote CUCMDUT:8500; SIP:6300; Local CUCM DUT(s):6500 URIdutuser01@abc.inc, 6501URIdutuser02@abc.inc; Remote CUCM DUT :8500 URIrdutuser01@abc.inc; 6300 URIrcuser01@abc.inc; RPC-Phoneview remotely controls IP Phones: 6300; Note: Provision URI on device page: DevicePhoneDNLineDirectory URI (Known bug if provisioned via End User Page) 1. Access to configure URI Speed Dial on DUT(s): DevicePhone: DN6500Select button 3Add new SDrdutuser01@abc.inc DN6501Add new SD (3) rcuser01@abc.inc hits Speed Dial button answers goes on-hook after 30s hits Speed Dial button answers goes on-hook after 30s hits Speed Dial button answers goes on-hook after 30s 8. Retrieve CDR(s) from CUCM 9. Check CDR(s) fields to verify call attributes accuracy DUT(s) receives Caller ID 3 calls established with 2 way audio 3 calls terminated normally Retrieved CDR(s) matched calls Not supported by i Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 23 of 60

24 Test Case # EP-7 Category Functional Test: Call Forward All (CFA) RFC_Standard Y Objective Verify CFA calls between DUT(s), SIP and PSTN endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: 9200, 6300, ; 1. Access 2. Configure CFA: DevicePhoneDN: 6500LineCFA LineCFA LineCFA dials answers6500 goes on-hook after 30s dials answers9200 goes on-hook after 30s 5. Access 6. Configure CFA: DevicePhoneDN: 8500LineCFA LineCFA dials answers6501 on-hook after 30s dials answers dials 9200hears busy tone6500 goes on-hook goes on-hook 11. Access Clear CFA settings for all DN(s): DevicePhoneDN: 6500LineCFABlank 6501LineCFABlank 9200LineCFABlank dials answers6500 goes on-hook after 30s 14. Access Clear CFA settings for all DN(s): DevicePhoneDN: 8500LineCFABlank LineCFABlank 16. Retrieve CDR(s) from CUCM 17. Check CDR(s) fields to verify call attributes accuracy CFA configured for DN(s):6500, 6501, & is forwarded to 8500 with 2-way audio 8500 is forwarded to 9200 with 2-way audio CFA configured for DN(s):8500 & is forwarded to 6300 with 2-way audio 6501 is forwarded to 6300 with 2-way audio 6500 hears busy tone because 6300 is busy CFA cleared for DN(s):6500, 6501 & is forwarded 6500 CFA is cleared for DN(s): All calls terminated normally Retrieved CDR(s) matched calls Randomly check 2-way audio using instructions in Lab Guide 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 24 of 60

25 Test Case # EP-8 Category Functional Test: Call Forward No Answer (CFNA) RFC_Standard Y Objective Verify CFNA calls between DUT(s), SIP and PSTN endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: 9200, 6300, ; 1. Access 2. Configure CFNA & disable Voice Mail & Call Waiting: DevicePhoneDN: 6500LineCFNA LineCFNA LineCFNA DevicePhoneDN: 6500LineVoice Mail ProfileNone 6501LineVoice Mail ProfileNone 9200LineVoice Mail ProfileNone DevicePhoneDN: 6500LineMax. Calls & Busy Trigger1 6501LineMax. Calls & Busy Trigger1 9200LineMax. Calls & Busy Trigger dials does not answer answers goes on-hook after 30s dials does not answer9200 answers goes on-hook after 30s dials does not answer8500 answers goes on-hook after 30s 9. Access (Credentials in Sandbox Portal) 10. Clear CFNA settings for all DN(s): DevicePhoneDN: 6500LineCFNABlank 6501LineCFNABlank 9200LineCFNABlank 11. Retrieve CDR(s) from CUCM 12. Check CDR(s) fields to verify call attributes accuracy CFNA configured for DN(s):6500, 6501, & is forwarded to with 2-way audio 6300 is forwarded to 9200 with 2-way audio 6501 is forwarded to 6300 with 2-way audio CFA cleared for DN(s):6500, 6501 & is forwarded 6500 CFNA is cleared for DN(s): 6500, 6501, & 9200 All calls terminated normally Retrieved CDR(s) matched calls Randomly check 2-way audio using instructions in Lab Guide 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 25 of 60

26 Test Case # EP-9 Category Functional Test: Call Forward Busy (CFB) RFC_Standard Y Objective Verify CFB calls between DUT(s), SIP & PSTN endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: , , ; 1. Access 2. Configure CFB: DevicePhoneDN: 6501LineCFB LineCFB LineCFB dials answers dials answers6300 goes on-hook after 30s goes on-hook dials answers dials answers9200 goes on-hook after 30s goes on-hook dials answers dials answers6300 goes on-hook after 30s goes on-hook 12. Go to Local & Remote CUCM Admin to clear CFB on DN(s): DevicePhoneDN: 6501LineCFBBlank 9200LineCFBBlank 8500LineCFBBlank 13. Retrieve CDR(s) from CUCM 14. Check CDR(s) fields to verify call attributes accuracy CFB configured for DN(s):6500, 6501, 9200 & 8500 Call established between 9201 & is forwarded to 9200 with 2-way audio Call established between 6300 & is forwarded to with 2-way audio Call established between 6301 & is forwarded to 6500 with 2-way audio CFB is cleared for DN(s):6500, 6501, 9200 & 8500 All calls terminated normally Retrieved CDR(s) matched calls Randomly check 2-way audio using instructions in Lab Guide 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 26 of 60

27 Test Case # EP-10 Category Functional Test: Call Hold & Resume RFC_Standard Y Objective Verify Hold & Resume calls between DUT(s), SIP and PSTN endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: 9200, 6300, ; 1. Access 2. Enable Call Waiting settings: DevicePhoneDNLine: 6500Max. Calls4; Busy Trigger2 6501Max. Calls4; Busy Trigger2 9200Max. Calls4; Busy Trigger dials answers 6500 hits Hold after 20s hits Resume after 20s6500 goes on-hook after 30s dials answers dials answers incoming call8500 is on-hold hits Resume after 60s goes on-hook goes on-hook after 30s dials answers hits Hold after 30s dials answers incoming call goes on-hook after 30s resumes call after 10s goes on-hook after 30s 15. Retrieve CDR(s) from CUCM 16. Check CDR(s) fields to verify call attributes accuracy Call Waiting enabled for DN(s) Call established between 6500 & 6501 with 2-way audio 6501 is On-Hold (MOH) Call resumed between 6500 & 6501 Call established between 6500 & 8500 with 2-way audio 8500 is On-Hold (MOH) Call established between 6500 & 6300 with 2-way audio Call resumed between 6500 & 8500 with 2-way audio Call established between 6500 & is On-Hold (MOH) Call established between 6500 & 9200 with 2-way audio Call resume between 6500 & All calls terminated normally Retrieved CDR(s) matched calls Randomly check 2-way audio using instructions in Lab Guide No MOH 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 27 of 60

28 Test Case # EP-11 Category Functional Test: Call Waiting RFC_Standard Y Objective Verify Call Waiting calls between DUT(s), SIP and PSTN endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: 9200, 6300, ; dials answers dials answers incoming call goes on-hook after 30s dials answers incoming call goes on-hook after 30s goes on-hook after 60s dials answers dials answers incoming call goes on-hook after 60s 10. Retrieve CDR(s) from CUCM 11. Check CDR(s) fields to verify call attributes accuracy Randomly check 2-way audio using instructions in Lab Guide Call established between 6500 & 6501 with 2-way audio 6500 notified of incoming call (tone /display) 6500 answers incoming call 6501 is On-Hold (MOH) Call established between 5500 & 8500 with 2-way audio 6500 & 8500 terminated normally Call resumed between 6500 & notified of incoming call (tone /display) 6501 answers incoming call 6500 is On-Hold (MOH) Call established between 6501 & 9200 with 2-way audio 6501 & 9200 terminated normally Call resumed between 6500 & & 6501 terminated normally Call established between 6300 & 6501 with 2-way audio 6501 notified of incoming call (tone /display) 6501 answers incoming call 6300 is On-Hold (MOH) Call established between 6501 & with 2-way audio 6501 & terminated normally Call resumed between 6501 & & 6300 terminated normally Retrieved CDR(s) matched calls No MOH 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 28 of 60

29 Test Case # EP-12 Category Functional Test: Blind Transfer RFC_Standard Y Objective Verify Blind Transfer calls between DUT(s), SIP and PSTN endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: 9200, 6300, ; dials answers6501 hits Transfer after 30s dials , hits Transfer and goes on-hook answers8500 goes on-hook after 60s dials answers6500 hits Transfer after 30s dials , hits Transfer and goes on-hook hears reorder tone and goes on-hook dials answers6500 hits Transfer and goes on-hook hears call disconnect tone and goes on-hook dials answers6500 hits Transfer after 30s dials , hits Transfer and goes on-hook answers9200 goes on-hook after 20s dials answers6501 hits transfer after 30s dials , hits Transfer and goes on-hook goes on-hook after 30s dials answers dials , hits Transfer and goes on-hook dials hears incoming call tone and answers call goes on-hook after 30s resumes call with goes on-hook after 30s 20. Retrieve CDR(s) from CUCM 21. Check CDR(s) fields to verify call attributes accuracy Randomly check 2-way audio using instructions in Lab Guide Call established between 6500 & 6501 with 2-way audio 6500 is On-Hold (MOH) 6500 blind transferred to 8500 with 2-way audio path All calls terminated normally Call established between 6500 & 6501 with 2-way audio 6501 is On-Hold (MOH) 6501 blind transferred to Invalid DN: hears reorder tone All calls terminated normally Call established between 6500 & 6501 with 2-way audio 6501 hear call disconnect tone and call disconnected Call established between 6500 & 9200 with 2-way audio 9200 is On-Hold (MOH) 9200 blind transferred to 8500 with 2-way audio path All calls terminated normally Call established between 6501 & is On-Hold (MOH) is blind transferred to 8500 All calls terminated normally Call established between & is On-Hold (MOH) 6500 is blind transferred to answers incoming call after blind transfer 6500 is On-Hold (MOH) Call established between 6501 & 9200 Call between 9200 & 6501 terminated Call between 6500 & 6501 resumed All calls terminated normally Retrieved CDR(s) matched calls Ok except nr 7, i62 Will reestablish the ongoing call if you press transfer and then on-hook 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 29 of 60

30 Test Case # EP-13 Category Functional Test: Consult Transfer RFC_Standard Y Objective Verify Consult Transfer calls between DUT(s), SIP, and PSTN endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: 9200, 6300, ; dials answers6501 hits Transfer after 30s dials answers hits Transfer after 30s and goes on-hook goes on-hook after 60s dials answers6500 hits Transfer after 30s dials answers hits Transfer after 30s and goes on-hook goes on-hook after 60s dials answers hits Transfer after 30s and dials answers hits Transfer after 30s and goes on-hook goes on-hook after 60s 13. Retrieve CDR(s) from CUCM 14. Check CDR(s) fields to verify call attributes accuracy Randomly check 2-way audio using instructions in Lab Guide Call established between 6500 & 6501 with 2-way audio 6500 is On-Hold (MOH) 6500 consult transferred to 8500 with 2-way audio path All calls terminated normally Call established between 6500 & 9200 with 2-way audio 9200 is On-Hold (MOH) 9200 consult transferred to 6501 with 2-way audio path All calls terminated normally Call established between 6501 & with 2-way audio is On-Hold (MOH) consult transferred to 6500 with 2-way audio path All calls terminated normally Retrieved CDR(s) matched calls No MOH 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 30 of 60

31 Test Case # EP-14 Category Functional Test: Conference Call RFC_Standard Y Objective Verify Conference calls between DUT(s), SIP and PSTN endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: 9200, 6300, ; dials answers and hits Conference after 30s dials answers6501 hits Conference after 30s 4. All parties goes on-hook after 60s dials answers6500 hits Conference after 30s dials answers6500 hits Conference after 30s goes on-hook after 60s goes on-hook after 30s dials answers6500 hits Conference after 30s dials answers hits Conference after 30s goes on-hook after 30s goes on-hook after 60s dials answers9200 hits Conference after 30s dials answers9200 hits Conference after 30s 16. All parties goes on-hook after 60s dials answers hits Conference after 30s dials answers6500 hits Conference after 30s 20. All parties goes on-hook after 60s 21. Retrieve CDR(s) from CUCM 22. Check CDR(s) fields to verify call attributes accuracy Randomly check 2-way audio using instructions in Lab Guide Call established between 6500 & 6501 with 2-way audio 6500 is On-hold (MOH) 8500 is conferenced-in 3 parties in conference call with 3-way audio All parties left conference and calls terminated normally Call establish between 6500 & 6501 with 2-way audio 6501 is On-Hold (MOH) 9200 is conferenced-in 3 parties in conference call with 3-way audio Call to 9200 terminated normally 6500 & 6501 are connected directly Call terminated normally Call established between 6500 & 8500 with 2-way audio 8500 is On-hold (MOH) is conferenced-in 3 parties in conference call with 3-way audio Call to terminated normally 6500 & 8500 are connected directly Call terminated normally Call established between 9200 & 6501 with 2-way audio 6501 is On-hold (MOH) 8500 is conferenced-in 3 parties in conference call with 3-way audio All parties left conference and calls terminated normally Call established between & 6500 with 2- way audio is On-hold (MOH) 6300 is conferenced-in 3 parties in conference call with 3-way audio All parties left conference and calls terminated normally Retrieved CDR(s) matched calls No MOH 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 31 of 60

32 Test Case # EP-15 Category Functional Test: Call Park RFC_Standard N Objective Verify Call Park calls between a DUT(s), SIP and PSTN endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: 9200, 6300, ; Call Park Code: dials answers hits Park softkey after 10s dials park code:3001 after 20s goes on-hook after 30s dials answers hits Park softkey after 10s dials park code:3001 after 20s goes on-hook after 30s dials answers hits the Park softkey after 10s dials park code:3001 after 20s goes on-hook 13. Retrieve CDR(s) from CUCM 14. Check CDR(s) fields to verify call attributes accuracy Randomly check 2-way audio using instructions in Lab Guide Call establish between 6500 & 8500 with 2-way audio 8500 is parked 6501 picks up parked call Call established between 6501 & 8500 with 2-way audio All calls terminated normally Call establish between 9200 & 6501 with 2-way audio 9200 is parked 6500 picks up parked call Call established between 9200 & 6500 with 2-way audio All calls terminated normally Call established between & 6500 w is parked 6501 picks up parked call Call established between 6501 & All calls terminated normally Retrieved CDR(s) matched calls No MOH 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 32 of 60

33 Test Case # EP-16 Category Functional Test: Call Park Reversion RFC_Standard N Objective Verify Call Park Reversion call for DUT(s), SIP endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: 9200, 6300, ; Call Park Code: RoutingCall Park dials answers hits Park softkey after 10s 3. Do not pickup parked call for 60s is ringing6500 answers goes on-hook after 30s dials answers hits Park softkey after 10s 8. Do not pickup parked call for 60s is ringing9200 answers goes on-hook after 30s dials answers hits Park softkey after 10s 13. Do not pickup parked call for 60s is ringing6501 answers goes on-hook after 30s 16. Retrieve CDR(s) from CUCM 17. Check CDR(s) fields to verify call attributes accuracy Call established between 6500 & 8500 with 2-way audio 8500 is parked 6500 picks up parked call Call re-established between 6500 & 8500 with 2-way audio Call terminated normally Call established between 6500 & 9200 with 2-way audio 6500 is parked 9200 picks up parked call Call re-established between 9200 & 6500 with 2-way audio Call terminated normally Call establish between & is parked 6501 picks up parked call Call reestablished between 6501 & Call terminated normally Retrieved CDR(s) matched calls Randomly check 2-way audio using instructions in Lab Guide Call Park is not implemented in i Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 33 of 60

34 Test Case # EP-17 Category Functional Test: Directed Call Park RFC_Standard N Objective Verify Assisted Directed Call Park call between DUT(s) and SIP endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: 9200, 6300, ; Directed Call Park Code:3011; Retrieval Prefix:21; 1. Access 2. Update Phone Button Template of all DUT(s): DevicePhoneDN: 6500Phone Buttom TemplateBLFSave Select Line Add new BLF Directed Call ParkDN Phone Buttom TemplateBLFSave Select Line Add new BLF Directed Call ParkDN Phone Buttom TemplateBLFSave Select Line Add new BLF Directed Call ParkDN dials answers hits BLF button for Assisted Directed Call Park after 20s goes on-hook selects line 3011 after 10s, enters retrieval prefix 21 when BLF is flashing goes on-hook after 30s dials answers selects line 3011 after 20s enters retrieval prefix 21 when BLF is flashing goes on-hook 13. Retrieve CDR(s) from CUCM 14. Check CDR(s) fields to verify call attributes accuracy Randomly check 2-way audio using instructions in Lab Guide Call established between 8500 & 9200 with 2-way audio 8500 is parked 6501 retrieves parked call Call established between 8500 & 6501 with 2-way audio Calls terminated normally Call established between 6500 & 6300 with 2-way audio 6300 is parked 6501 retrieves parked call Call established between 6300 & 6501 with 2-way audio Calls terminated normally Retrieved CDR(s) matched calls Call Park is not implemented in i Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 34 of 60

35 Test Case # EP-18 Category Functional Test: Direct Transfer RFC_Standard N Objective Verify Direct Transfer call from a shared line between DUT(s), SIP and PSTN endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: 9200, 6300, ; 1. Access 2. Configure Shared Line on DUT-1: DevicePhoneDN6500Line 29201Save dials answers selects shared line:dn:9201 after 30s dials answers 6. Scroll to 1 st call and hit select 7. Scroll to 2 nd call and hit select and hit DirTfr softkey goes on-hook goes on-hook after 30s 10. Retrieve CDR(s) from CUCM 11. Check CDR(s) fields to verify call attributes accuracy `Call establish between 6501 & 6500 with 2-way audio 6501 is On-Hold (MOH) Call establish between 9201 & 8500 with 2 way audio 6501 direct transferred to 8500 with 2 way audio 9201 dropped off from call Call terminated normally Retrieved CDR(s) matched calls Randomly check 2-way audio using instructions in Lab Guide Shared line is not implemented in i Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 35 of 60

36 Test Case # EP-19 Category Functional Test: Automated CDR Creation RFC_Standard N Objective Verify joining two Ad-Hoc Conference using DUT(s), SIP, and PSTN endpoints Test Case EP-2 Global Settings Local CUCM DUT(s): ; SIP:9200; Remote CUCMDUT:8500; SIP:6300; PSTN: ; RPC-Phoneview remotely controls IP Phones: 9200, 6300, ; dials answers hits Conference after 30s dials answers6500 hits Conference after 30s dials answers 2 nd incoming call hits Conference after 20s dials answers9200 hits Conference after 20s selects conference 1 and hits the Join softkey goes on-hook after 60s goes on-hook after 70s 10. All other participants ended call after 120s 11. Retrieve CDR(s) from CUCM 12. Check CDR(s) fields to verify call attributes accuracy Randomly check 2-way audio using instructions in Lab Guide Call established with 6501 & is On-Hold (Tone/Silence) Call established between 6500 & 6501 with 2-way audio All 3 participants joined conference-1 Call established between 9200 & 6501 with 2-way audio 6501 is On-Hold (Tone/Silence) Call established between 9200 & 8500 with 2-way audio All 3 participants join in conference-2 All participants in conference 1 & 2 are joined 6501 left conference 8500 left conference All other participants terminated normally Retrieved CDR(s) matched calls 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 36 of 60