Konftel Konftel 300IP User manual

© YEAR Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 64
Test Report
Detailed End Point IVT Test Plan and Report for Cisco
Communications Manager and Konftel 300IP
Test Date/ Result
(Completed by Cisco or Authorized Test House) MM/DD/YY - PASS/FAIL
Partner Product Name Konftel 300IP
Partner Product Type Konftel 300IP
Partner Product Version # 2.4.4
Cisco Product Name Cisco Unified Communication Manager
Cisco Product Version 10.5
API/Protocol(s) Used SIP
Date Testing Completed 2015-10-18
IVT Contact Email [e-mail]

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 2 of 64
Contents
Pre-Testing Information.............................................................................................................. 3
IVT Pre-requisites.................................................................................................................... 3
Submission Instructions........................................................................................................... 3
1Interoperability Verification Testing (IVT) Overview.......................................................... 4
1.1 Interoperability Verification Testing Requirement......................................................... 4
1.2 IVT Objectives................................................................................................................ 4
1.3 IVT Focus ....................................................................................................................... 4
2Instructions............................................................................................................................. 5
3Product and Testing Information........................................................................................... 6
3.1 IVT Request info here..................................................................................................... 6
4Test Set Up and Tools............................................................................................................ 7
5Product Platform Description ................................................................................................ 7
5.1 Product Deployment Description.................................................................................... 7
5.2 Product Description ........................................................................................................ 7
5.3 Product Integration Diagram .......................................................................................... 8
5.4 Product Integrated Use Cases......................................................................................... 8
6Test Plan ................................................................................................................................ 8
6.1 Introduction..................................................................................................................... 8
6.2 Entry Criteria .................................................................................................................. 8
6.3 Exit Criteria..................................................................................................................... 8
7Executive Summary............................................................................................................. 10
8Testing Details..................................................................................................................... 11
8.1 Items Tested.................................................................................................................. 11
8.2 Items Not Tested........................................................................................................... 11
8.3 Assumptions.................................................................................................................. 11
8.4 Administration, Testing and Debugging tools.............................................................. 11
8.5 Equipment Requirements.............................................................................................. 12
8.6 Lab Network Topology................................................................................................. 12
8.7 Test Case Result Reporting........................................................................................... 13
9Test Cases ............................................................................................................................ 13
9.1 Endpoint Workflow & Test Case Mapping.................................................................. 13
9.2 Installation Tests........................................................................................................... 14
9.3 Entrance Tests............................................................................................................... 15
9.4 Features and Services.................................................................................................... 20
9.5 Manual Functional Tests............................................................................................... 21
9.6 Manual Negative Tests ................................................................................................. 54
9.7 Miscellaneous Tests...................................................................................................... 57
10 Appendix A: Test Result Matrix

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 3 of 64
Pre-Testing Information
The purpose of this section is to gather information about the 3rd party Solution Partner Program (SPP) product being
submitted for Interoperability Verification Testing (IVT) in support of receiving a Cisco Compatibility logo. The information
collected in this section will be used to complete customization of test plan for the product integration with Cisco product(s).
This section must be completed thoroughly to ensure that products features and requirements are properly understood and
reflected appropriately in the test plan. The limits stated in this questionnaire will be tested. Anything (limits,
functionality, interfaces) not reported in this document will not be supported.
Complete all sections with <PARTNER COMPLETED>
This document will be reviewed for content, completeness and appropriate integration methods by Cisco and will not be
submitted for test plan generation or test scheduling until approval. This process generally takes about 10 business days,
though can be more or less dependent on complexity and current demand.
IVT Pre-requisites
The following prerequisites must be complete prior to submitting a request for testing:
1) Approved application in SPP for the product pairing being submitted for test.
a) Product Pairing = Cisco Product Major Version + Partner Product Major Version
b) Cisco Product Major Version must be generally available
c) Partner Product Major Version must be generally available
2) Any use of Cisco Intellectual Property (proprietary protocols or interface methods) must have been approved by Cisco
and have appropriate agreements in place. This is not appliEPle to standard published integration methods. Questions
regarding interface methods should be directed to Developer Services or your Cisco Partner Manager.
Submission Instructions
Provide the requested information on the following pages for the product being submitted for Interoperability Verification
Testing (IVT).
Complete Current Test Request Information, Product Category, and Product Description for all product pairings (Cisco Product
+ Program Member Product) being submitted. Only requests with all required sections completed

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 4 of 64
1 Interoperability Verification Testing (IVT) Overview
1.1 Interoperability Verification Testing Requirement
Successful completion of Endpoint / USB Accessory 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 3rd 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: https://developer.cisco.com/site/collaboration/overview.gsp
1.3 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 5 of 64
2 Instructions
Provide the requested information on the following pages for the product being submitted for Interoperability Verification
Testing (IVT).
1) Complete Current Test Request Information, Product Category, and Product Description for all product pairings
(Cisco Product + Program Partner Product) being submitted. Only requests with all required sections completed will
be accepted. Failure to provide this information will result in the request being denied.
2) Submission:
a) Access your Developer Dashboard, go to the Registered Products Tab and select "Actions" and
"Add New IVT Request" next to the product to be submitted for IVT
b) Upload this document to the IVT Request, failure to upload this document will result in an
incomplete request
c) Save using filename: <COMPANY_PRODUCT_VX_X+CISCO_PRODUCT_VX_X>.doc Example
Filename: CiscoSystems_FASTAPP_V1_1+CIscoProduct_1_0.doc
Click on link below for detailed instructions:
http://solutionpartner.cisco.com/documents/8974369/0/DeveloperPartnerGuide.pdf
Help or questions related to SPP Portal, listings or application status::[e-mail]
General Questions: Contact your Cisco representative or send email to [e-mail]

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 6 of 64
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 7 of 64
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
In the table below, provide specific details on the platform/server that your product resides. If your application is an
appliance, it will need to be onsite for testing; otherwise, a VM will be provided for your installation of OS and application.
Minimum Configuration Server
Requirements Maximum Configuration Server Requirements OS and Version
CPU
Disk
Memory
Max Users supported
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.
5.2 Product Description
The Konftel 300IP is a flexible SIP-based conference phone, perfect for companies that use IP voice services. It's
clear, natural sound comes from OmniSound HD, Konftel's patented wideband audio technology. The stylishly
designed Konftel 300IP is packed with intelligent features for more efficient conference calls. Record and store
meetings on a SD memory card. Use the conference guide to call pre-programmed groups with just a few simple
pushes of a button. Conveniently import and export contact details via the web interface. Create your phone book with
the personal user profile feature. The Konftel 300IP is also ideal for larger conferences since it can accommodate
expansion microphones, an external wireless headset and a PA system. With the Konftel 300IP your company will
have a conference phone that combines all the benefits of IP voice service with innovative new features.

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 8 of 64
5.3 Product Integration Diagram
5.4 Product Integrated Use Cases
Konftel 300IP is an excellent SIP conference phone with support for local 5-way calls. It can be used in small and large
meeting rooms (with expansion microphones as accessory).
6 Test Plan
6.1 Introduction
This document is the detailed Interoperability Verification Test Plan and Report for Cisco Unified Communications
Manager and Endpoint/USB Accessory partner product.
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.
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.

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 9 of 64
If a severity 1 or 2 failure occurs, irrespective of whom is responsible for the problem (Cisco or the 3rd party product),
the testing is considered unsuccessful.
Table 1. Defect Severity Level
Severity
Description
1
Catastrophic
Common circumstance causes the entire system or a major subsystem to stop working affects
other areas/devices no workaround
2
Severe
Important functions are unusable does not affect other areas/devices no workaround
3
Moderate
Very unusual circumstances cause failure minor feature doesn't work at all there's a low impact
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.
The following procedures are followed 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 3rd party product), the
testing is considered unsuccessful.
Any deviations of the test execution or problem acceptance are documented in the test report. The 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 10 of 64
7 Executive Summary
Short summary of the test effort, summarizing the lab findings during testing.
The following summarizes results:
●Test Case Failures: 0
●Features Not Supported: 24
●Test Cases that are Not Applicable:1
●Test Cases that were Not Executed: 2
●Observations: Konftel 300IP does not support the most Cisco specific features. No softkeys on Konftel 300IP.

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 11 of 64
8 Testing Details
8.1 Items Tested
Features that are specific in this section are the high level categories the testing will focus on.
●3rd Party installation, configuration and validation
●Security Requirements
●Functional testing of the various features interfacing through the 3rd 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 3rd 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.
8.4 Administration, Testing and Debugging tools
Tools used/required – Identify any tools required by 3rd party (partner under test). Also add Trace and
Debug settings here.
Table 2. 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
3rd Party Tools
Wireshark 1.12.4 Network
debug tool Watch SIP traffic from/to DUT
1
Debug Tools
<Update based on IVT>

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 12 of 64
8.5 Equipment Requirements
Table below identifies all equipment/versions used in this IVT.
Table 3. Sandbox Topology Components
Product Version Units Description
CUCM 10.5 2 PUB & 2 SUB HQ & Branch CUCM Clusters
CUPS 10.0 1 Cisco Presence Server
CUC 10.01 Cisco Unity Connection
Mediasense 10.0 1 Cisco Mediasense
Cisco 2811 2 PSTN Gateways
IP Phones 5 6941,79XX, 8851, 8861, 8945, 8961,9951,9971,DX650
Phoneview 1 Remote Phone Control Server (RPC)
DUT(s) 3 or more Konftel 300IP
8.6 Lab Network Topology

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 13 of 64
8.7 Test Case Result Reporting
Table 4. Test Results Legend
Result Description
Pass (P) The test case passed with no exceptions
Fail (F) The test case failed – details of the failure are noted in the Comments column
N/A The test case is not applicable to the product under test. Provide justification in the “Comments” column.
N/S 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.
N/T 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.
Blocked (B) Other test case failures prevented the execution of this test. Reference the failed test case in the“Comments
”
column.
.
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 IVT Workflow & Test Case Mapping
Test Work Flow Sections Test Case # Total Tests A/M
Endpoint Registration & Validation (Step 1 & 2)
EP-1 1 M
Functional Tests (Step 3)
EP-2 EP-45 44 M
Negative Tests (Step 4)
EP-46 EP-50 5 M
Miscellaneous Tests (Step 5)
EP-51EP-56 6 M

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 14 of 64
9.2 Integration Test
Test is focused on ensuring that the 3rd party product (DUT) is registered with Call Manager successfully
Test Case #
EP-1
Category
Connect

Validate
RFC_Standard
Y
Objective
Verify 3rd party endpoints (DUT) are registered in Call Manager successfully
Pre-Test Conditions
•Enable auto-registration in Local CUCM with DN range 7100 – 7199
•Local CUCM ClusterNPA-NXX410-444-XXXX
•Remote CUCM ClusterNPA-NXX322-234-XXXX
•CUCM Administration GUI: https://X.X.X.X:8443 (X.X.X.X= CUCM-PUB IP)
•Hardware VPN Router setup to EP_IVT Lab
Test Procedure
Expected Results
1. Connect two DUT(s) in local CUCM cluster
2. Connect one DUT in remote CUCM cluster
3. Run “Step1_Endpoint Registration” cmd to register DUT(s)
4. Run “Utility_Device_Status” cmd to check registration status
5. Go off-hook on DUT(s) to check for dial tone
6. Go to DUT(s) settings to verify network and load information
7. In local CUCM cluster, change DN of DUT(s) to 7100 & 7101
with device poolep_pool
8. In remote CUCM cluster, change DN of DUT to 8000
9. Assign all DUT(s) a softkey template of “SIP_EP_User”
10. Associate end users to DUT(s) as follows:
DevicePhoneLineAssociate End Users
DUT:7100dutuser01
DUT:7101dutuser02
DUT:8000rdutuser01
Note:
•Endpoint Registration command is setup to register endpoints to
local CUCM Cluster
•To register endpoints to remote CUCM cluster, manually enter the
TFTP IP address of remote CUCM to DUT
•DUT(s) goes through CUCM auto-registration process
•CUCM Administration .GUI display the DUT(s)
•DUT(s) are in “Registered” state
•DUT(s) have a DN assigned
•Dial tone played when phone goes off-hook
•DUT(s) network data is correct:
(VLAN, DNS, DHCP, TFTP, CUCM)
•DUT(s) Phone Load version is correct
•DUT(s) DN changed to proceed with test cases
•DUT(s) softkey template updated to “SIP_EP_User”
•Users associated to DUT(s) respectively
Test Results: Comments
P
F
N/A
N/S
N/T
B
X
Run “Step 1_Endpoint_Registration” command to register endpoints.
Run “Step 2_Record_Connectivity_Validation” command after verifying the endpoints are
registered with the correct network and load information.

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 15 of 64
9.3 Entrance Tests
Tests will be focused on features and the operational behavior of the 3rd party product (DUT) to ensure it
corresponds to its design specifications.
Test Case #
EP-2
Category
Entrance Test: Intra-Cluster Calls
RFC_Standard
Y
Objective
Verify intra-cluster calls between DUT, SCCP and SIP endpoints
Pre-Test Conditions
•Local CUCM DUT(s):7100 & 7101; SCCP:1000; SIP:2000;
•Configure Audio & Video Playback on an RDP Session for a PC accessing RPC Tool Server (Refer to Lab Guide for instructions)
Launch RDPOptionsLocal Resources SettingsPlay on this computer
Access RPC Server via RDP
•RPC is used to remotely control IP Phones :1000 & 2000;
Test Procedure
Expected Results
1. 7100 dials 71017101 answers7100 on-hook after 30s
2. 7101 dials 1000Select 1000 and answer call using RPC
3. Select “Headphone” icon
4. Enter “Play:AreYouThere.raw” & hit “Send” on the Command Line
5. 7101 speaks “Testing1234”1000 on-hook after 60s
6 Repeat steps 2-5 with Calling DN:2000 & Called DN;7100
7. Repeat steps 2-5 with Calling DN:7101 & Called DN;2000
8. Calling & Called party release calls alternatively
9 Retrieve CDR from CUCM
10. Check Calling, Called, Duration, Origination & Termination
Cause Codes
•4 calls establish with 2-way audio path
•Calling and Called Parties hear ring-back and ring tone
•DUT receives Caller ID
•Phone on RPC displays “monitoring active” message with
symbol
•7100 & 7101 hear “Are you There”
•1000 & 2000 hear “Testing 1234”
•Audio for RPC phones heard on pc running Phoneview
•4 calls terminate normally
•4 CDR(s) retrieved
•Selected fields in CDR(s) match table
CDR field
Call 1
Call 2
Call 4
Call 5
callingPartyNumber
7100
7101
7101
2000
OriginalCalledPartyNumber
7101
1000
2000
7100
finalCalledPartyNumber
7101
1000
2000
7100
origCause_Value
16
0
16
0
destCause_Value
0
16
0
16
duration
30
60
60
60
Test Results: Comments
P
F
N/A
N/S
N/T
B
X
Note:
•In RPC Tool, if any of the Phones used in test case is in un-registered state, use any available registered IP Phones.
Phone displays without a DN assigned are un-registered.
•Refer to Lab Guide for instructions on:
CDR Retrieval from CUCM
Phoneview User Guide
2-Way Audio Path Validation
Tests in this section requires RPC tool to remotely control Cisco IP Phones for manual calls. Follow
instructions highlighted in green in each test case before execution. It is important to restore
endpoints to it’s original state in some test cases before proceeding to next test case.
Run “Step 3: Record_Functional_Test_Execution” command after executing all tests in this section
Retrieve CDR(s) in CUCM to validate calls

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 16 of 64
9.4 Features and Services
Test Case #
EP-3
Category
Functional Test: Inter-Cluster Call
RFC_Standard
Y
Objective
Verify inter-cluster calls between DUT(s), SCCP and SIP endpoints
Pre-Test Conditions
•Local CUCMDUT(s):7100 & 7101;
•Remote CUCM DUT:8000; SCCP:5200; SIP:6200;
•RPC is used to remotely control IP Phones: 5200, 6200;
Test Procedure
Expected Results
1. 7100 dials 23480008000 answers8000 on-hook after 30s
2. 7101 dials 2345200Select 5200 and answer call using RPC
3. Select “Headphone” icon
4. Enter “Play:AreYouThere.raw” and hit “Send” on the Command Line
5. 7101 speaks “Testing1234” 5200 on-hook after 60s
6. Repeat steps 2-5 with Calling DN:7101 & Called DN;6200
7. Calling & Called party release calls alternatively
8. Retrieve CDR from CUCM
9. Check Calling, Called, Duration, Origination & Termination
Cause Codes
•3 calls establish with 2-way audio path
•Calling and Called Parties hear ring-back and ring tone
•DUT receives Caller ID
•Phone on RPC displays “monitoring active” message with
symbol
•7100 & 8000 hear “Are you There”
•5200 & 6200 hear “Testing 1234”
•Audio for RPC phones heard on PC running Phoneview
•3 calls terminate normally
•3 CDR(s) retrieved
•Selected fields in CDR(s) match calls
Test Results: Comments
P
F
N/A
N/S
N/T
B
X
Test Case #
EP-4
Category
Functional Test: Off-Net Calls
RFC_Standard
Y
Objective
Verify basic calls between DUT(s) and PSTN endpoints
Pre-Test Conditions
•Local CUCM DUT(s):7100 & 7101;
•Remote CUCM DUT:8000;
•PSTN: 210-222-5400 (SIP);
•RPC is used to remotely control PSTN Phone:[phone];
Test Procedure
Expected Results
1. 7100 dials 92102225400Select 2102225400 & answer using RPC
2. Select “Headphone” icon
3. Enter “Play:AreYouThere.raw” and hit “Send” on the Command Line
4. 7100 speaks “Testing1234” 2102225400 on-hook after 60s
5. Repeat steps1-4 with Calling DN:2102225400 & Called
DN:94104447101
6. Retrieve CDR from CUCM Server
7. Check Calling, Called, Duration, Origination & Termination
Cause Codes
Note: Inbound & Outbound PSTN calls are dialed with a prefix of “9”
•2 Calls establish with 2-way audio path
•Calling and Called Parties hear ring-back and ring tone
•DUT receives Caller ID
•Phone on RPC displays “monitoring active” message with
symbol
•7100 & 7101 hear “Are you There”
•2102225400 hears “Testing 1234”
•Audio for RPC phones heard on PC running Phoneview
•2 Calls terminate normally
•2 CDR(s) retrieved
•Selected fields in CDR(s) match calls
Test Results: Comments
P
F
N/A
N/S
N/T
B
Called to 6201 instead of 6200
X

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 17 of 64
Test Case #
EP-5
Category
Functional Test: SIP URI
RFC_Standard
Y
Objective
Verify intra-cluster SIP URI calls between DUT and SIP endpoints
Pre-Test Conditions
•Local CUCMDUT(s):7100 (URI:[email protected] ); 7101 (URI:[e-mail] ); SIP:2000 (URI:cus[email protected] );
•Configure Speed Dial on button 3 for 7100, 7101, 2000:
DevicePhone7100Add new SD[email protected] on both fields
DevicePhone7101Add new SD[email protected] on both fields
DevicePhone2000Add new SD[email protected] on both fields
•RPC is used to remotely control IP Phones: 2000;
Note: Provision URI on device page: DevicePhoneDNLineURI (Known bug if provisioned via End User Page)
Test Procedure
Expected Results
1. 7100 hits Speed Dial button 37101 answers
2. 7101 goes on-hook after 30s
3. 2000 hits Speed Dial button 3 7100 answers
4. 2000 goes on-hook after 30s
5. 7101 hits Speed Dial button 32000 answers
6. 7101 goes on-hook after 30s
7. Retrieve CDR from CUCM Server
8. Check Calling, Called, Duration, Origination & Termination
Cause Codes
•DUT(s) receives Caller ID
•3 calls establish with 2 way audio
•3 calls terminate normally
•3 CDR(s) retrieved
•Selected fields in CDR(s) match calls
Test Results: Comments
P
F
N/A
N/S
N/T
B
No speed dial button
X
Test Case #
EP-6
Category
Functional Test: SIP URI
RFC_Standard
Y
Objective
Verify inter-cluster SIP URI calls between DUT and SIP endpoints
Pre-Test Conditions
•Local CUCMDUT(s):7100 (URI: [email protected]) & 7101(URI: dutus[email protected]); SIP:2000 (URI: [email protected]);
•Remote CUCMDUT :8000 (URI: r[email protected]nc); SIP:6200 (URI: [email protected] );
•Configure Speed Dial on button 3 for 7100, 7101 & 6200:
DevicePhone7100Add new SD[email protected] on both fields
DevicePhone7101Add new SD[email protected] on both fields
DevicePhone6200Add new SD[email protected] on both fields
•RPC is used to remotely control IP Phones: 2000 & 6200;
Note: Provision URI on device page: DevicePhoneDNLineURI (Known bug if provisioned via End User Page)
Test Procedure
Expected Results
1. 7100 hits Speed Dial button 38000 answers
2. 8000 goes on-hook after 30s
3. 7101 hits Speed Dial button 36200 answers
4. 6200 goes on-hook after 30s
5. 6200 hits Speed Dial button 37100 answers
6. 7100 goes on-hook after 30s
7. Retrieve CDR from CUCM Server
8. Check Calling, Called, Duration, Origination & Termination
Cause Codes
•DUT(s) receive Caller ID
•3 calls establish with 2 way audio
•3 calls terminate normally
•3 CDR(s) retrieved
•Selected fields in CDR(s) match calls
Test Results: Comments
P
F
N/A
N/S
N/T
B
No speed dial button
x

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 18 of 64
Test Case #
EP-7
Category
Functional Test: CFA
RFC_Standard
Y
Objective
Verify “CFA” calls between DUT(s), SCCP, SIP and PSTN endpoints
Pre-Test Conditions
•Local CUCMDUT(s):7100 & 7101; SCCP:1000; SIP:2000;
•Remote CUCMDUT:8000; SCCP:5200; SIP:6200;
•PSTN: 210-222-5400
•Enable CFA for DN(s):
DevicePhone7100CFA1000 (SCCP)
DevicePhone7101CFA2348000 (DUT)
DevicePhone8000CFA6200 (SIP)
DevicePhone5200CFA4447101 (DUT)
DevicePhone2000CFA2348000 (DUT)
DevicePhone210222540094104447100 (DUT)
•RPC is used to remotely control IP Phones: 1000, 2000, 5200, 6200, 2102225400;
Test Procedure
Expected Results
1. 7100 dials 71018000 answers7100 on-hook after 30s
2. 8000 dials 44471001000 answers1000 on-hook after 30s
3. 7101 dials 23480006200 answers7101 on-hook after 30s
4.7101 dials 20008000 answers
5. 7100 dials 23452007100 on-hook - hears busy tone
6. 7101 goes on-hook
7. 7101 dials 921022254007100 answers
8. 2102225400 goes on-hook after 30s
9. 2102225400 dials 941044471018000 answers
10. 8000 goes on-hook after 30 secs
11. Retrieve CDR from CUCM
12. Check Calling, Called, Duration, Origination & Termination
Cause Codes
Note:
Upon test completion, remove “CFA” feature for devices highlighted
in yellow before proceeding to next test case
CUCM Administration GUI:
DevicePhoneDNLineCall Forward All Destinationblank
•“CFA” phones displays the CFA # on scree
•Call forward to 8000 and phone rings
•Call establish between 7100 & 8000 with 2-way audio
•Call terminate normally
•Call forward to 1000 and phone rings
•Call establish between 8000 & 1000 with 2-way audio
•Call terminate normally
•Call forward to 6200 and phone rings
•Call establish between 7101 & 6200 with 2-way audio
•Call terminate normally
•Call forward to 8000 and phone rings
•Call establish between 7101& 8000 with 2-way audio
•Call forward to 7101 and phone rings
•Call forward to 8000 and phone returns busy tone
•7100 hears busy tone and release call
•Call on 7101 terminate normally
•Call forward to 7100 and phone rings
•Call establish between 7101& 7100 with 2-way audio
•Call terminate normally
•Call forward to 8000 and phone rings
•Call between 2102225400 & 8000 with 2-way audio
•Call terminate normally
•7 CDR(s) retrieved
•Selected CDR(s) fields match calls
Test Results: Comments
P
F
N/A
N/S
N/T
B
x

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 19 of 64
Test Case #
EP-8
Category
Functional Test: CFNA
RFC_Standard
Y
Objective
Verify “CFNA” calls between DUT(s), SCCP and SIP endpoints
Pre-Test Conditions
•Local CUCMDUT(s):7100 & 7101; SCCP:1000; SIP:2000;
•Remote CUCMDUT:8000; SCCP:5200 SIP:6200;
•Voicemail and Call Waiting disabled for all DN(s) DevicePhoneDNLineVoicemailNoVoiceMail
Call WaitingMax. Calls1; Busy Trigger1;
•Enable CFNA for DN(s):
DevicePhone7100CFNA1000 (SCCP)
DevicePhone7101CFNA2348000 (DUT)
DevicePhone8000CFNA6200 (SIP)
DevicePhone5200CFNA4447101 (DUT)
DevicePhone2000CFNA2348000 (DUT)
•RPC is used to remotely control IP Phones: 1000, 2000, 5200, & 6200,
Test Procedure
Expected Results
1. 7100 dials 71017101 does not answer8000 answers
2. 7100 goes on-hook after 30s
3. 8000 dials 44471007100 does not answer1000 answers
4. 1000 goes on-hook after 30s
5. 7101 dials 23480008000 does not answer6200 answers
6. 7101 goes on-hook after 30s
7.7101 dials 20002000 does not answer8000 does not answer
8. 6200 answers call
9. 8000 dials 52005200 does not answer7101 does not answer
10. 8000 goes on-hook - hears busy tone
11. 6200 goes on-hook
12. Retrieve CDR from CUCM
13. Check Calling, Called, Duration, Origination & Termination
Cause Codes
Note:
Upon test completion, remove “CFNA” feature for devices highlighted
in yellow before proceeding to next test case
CUCM Administration GUI:
DevicePhoneDNLineCFNADestinationblank
•Call forward to 8000 after ring timeout
•Call establish between 7100 & 8000 with 2-way audio
•Call terminate normally
•Call forward to 1000 after ring timeout
•Call establish between 8000 & 1000 with 2-way audio
•Call terminate normally
•Call forward to 6200 after ring timeout
•Call establish between 7101 & 6200 with 2-way audio
•Call terminate normally
•Call forward to 6200 after ring timeout
•Call establish between 7101& 6200 with 2-way audio
•Call terminate normally
•8000 hears busy tone and terminate call
•Call on 6200 terminate normally
•Call forward to 7100 after ring timeout
•Call establish between 7101& 7100 with 2-way audio
•Call terminate normally
•Call forward to 8000 after ring timeout
•5 CDR(s) retrieved
•Selected fields in CDR(s) match calls
Test Results: Comments
P
F
N/A
N/S
N/T
B
x

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 20 of 64
Test Case #
EP-9
Category
Functional Test: CFB
RFC_Standard
Y
Objective
Verify “CFB” calls between DUT(s), SCCP and SIP endpoints
Pre-Test Conditions
•Local CUCMDUT(s):7100 & 7101; SCCP:1000; SIP:2000;
•Remote CUCM DUT:8000; SCCP:5200; SIP:6200;
•Voicemail and Call Waiting disabled for all DNs
•Enable CFB for DN(s):
DevicePhone7100CFB1000 (SCCP)
DevicePhone7101CFB2348000 (DUT)
DevicePhone8000CFB6200 (SIP)
DevicePhone6200CFB4447101(DUT)
DevicePhone1000CFB2348000 (DUT)
•RPC is used to remotely control IP Phones: 1000, 2000, 5200 & 6200;
Test Procedure
Expected Results
1. 1000 dials 71017101 answers
2. 7100 dials 71018000 answers7100 on-hook after 30s
3. 5200 dials 80008000 answers
4. 7100 dials 71017100 on-hook – hears busy tone
5. 5200 goes on-hook
6. 7100 dials 10008000 answers7100 on-hook after 30s
7. 7101 goes on-hook
8. 2000 dials 10001000 answers
9. 5200 dials 80008000 answers
10. 7101 dials 10007101 on-hook – hears busy tone
11. 1000 goes on-hook
12. 1000 dials 62006200 answers
13. 7100 dials 23462007101 answers7101 on-hook after 30s
14. 2000 dials 71017101 answers
15. 7100 dials 23462007100 goes on-hook –hears busy tone
16. 2000 & 6200 goes on-hook
17. Retrieve CDR from CUCM
18. Check Calling, Called, Duration, origination & termination
cause codes matches the calls
Note:
Upon test completion, remove “CFB” feature for devices highlighted
in yellow before proceeding to next test case
CUCM Administration GUI:
DevicePhoneDNLineCFBDestinationblank
•Call establish between 1000 & 7101 with 2-way audio
•Call forward to 8000 and phone rings
•Call establish between 7100 & 8000 with 2-way audio
•7100 terminate call
•Call establish between 5200 & 8000 with 2-way audio
•7100 hears busy tone and release call
•5200 terminate call
•Call forward to 8000 and phone rings
•Call establish between 7100 & 8000 with 2-way audio
•7101 terminate call
•Call establish between 2000 & 1000 with 2-way audio
•Call establish between 5200 & 8000 with 2-way audio
•7101 hears busy tone and release call
•1000 terminate call
•Call establish between 1000 & 6200 with 2-way audio
•Call forward to 7101 and phone rings
•Call establish between 7100 & 7101 with 2-way audio
•7101 terminate call
•Call establish between 2000 & 7101 with 2-way audio
•7100 hears busy tone and release call
•2000 & 6200 terminate call
•Call establish between 2000 & 7100 with 2-way audio
•2000 & 7101 terminate call
•12 CDR(s) retrieved
•Selected fields in CDR(s) match calls
Test Results: Comments
P
F
N/A
N/S
N/T
B
x