|
Test Result |
Pass |
|
Test Date |
July 17, 2006 |
|
Product Name |
accessaphone™ |
|
Product Version # (must be generally available) |
2.X |
|
Call Manager Version X.X (x) |
4.2 (1) |
|
Cisco® Security Agent Version (CSA) |
Sub - N/A Pub - 4.51.645-2.0.4 |
|
Product Type (Billing, Voice Recording, phone apps etc) |
IP Phone Apps |
|
API/Protocol(s) Used |
TAPI |
|
Developer Services Contract # |
2648946 |
|
IVT Lab Location (EMEA or US) |
US |
|
Partner Main Support Number |
877-362-2489 |
1 - Introduction
This document is the detailed Interoperability
Verification Testing (IVT) Test Report for Release 2.X of accessaphone™.
It defines the scope, approach, resources, schedule, risks/mitigations, and entry/exit
criteria for IVT testing.
2 - Objective(s)
The principle objective of the IVT is to provide Cisco® CTDP program partners with an approved,
consistent and comprehensive verification methodology for acceptance of their application
product into the Cisco® Technology Developer Program (CTDP). Testing is focused on
functionality and compliance with the open standards followed by the Cisco® Call
Manager and design within context of a Cisco® internetworking infrastructure.
3 - Scope
The IVT test activities between third party devices and the Cisco® IVT test bed determines
whether the implementation of third-party devices provides basic functionality without
compromising the Cisco® network. This document provides the test strategy and test
case procedures to validate the mandatory standard requirements and a variety of
optional requirements for the device. The device under test must satisfy all the
mandatory requirements, and selected optional requirements in order to pass the
test. This test determines whether the product performs as required and inter-operates
on a pass/fail basis. The test suite therefore emphasizes error detection, not error
diagnosis or correction; however, if there is a failure, data will be captured for
further analysis, and, if possible, will be traced to the specification of the standard
to determine the cause of the problem. Any problems found will be reported to Cisco®
and to the vendor for correction.
4 - Product Overview
accessaphone™ uses Microsoft® TAPI 2.1 and Cisco® TSP 4.x to integrate with our software.
We also provide an extensive accessibility interface using TTS (Text-To-Speech)
to communicate all information to the end user, making Cisco® telephony devices COMPLETELY
accessible to blind and low vision users. Our software is Section 508 compliant with the
government accessibility standards.
4.1 - What Will Be Tested
-
Installation and configuration
-
Call Manager registration
-
Application stability and reliability
-
Basic application functionality
-
Core functionality (call hold, call transfer, conferencing, call forwarding,
call park and retrieval, call pick up)
-
Advanced functionality (shared extension, Message Waiting Indicator (MWI), call waiting, phone template
modifications, phone reset)
-
Performance testing: impact on Call Manager
-
Extension mobility
-
Port scan
-
Negative testing
7 - Test Approach
The goal of the IVT is to test in a customer-like environment to ensure that it
behaves in a reliable manner under conditions that reflect typical customer usage
and product deployment. This includes the exercise of provisioning, generating call
traffic of supported types, maintenance activities, troubleshooting, and fault insertion.
The IVT will focus on the following seven main areas:
7.1.1 - Phase 1 Installation & Configuration
This phase included making sure the third-party application installed correctly and
that it registered correctly with the Call Manager. These tests will also focus
on clean installation, configuration and removal of any software components on the
Call Manager server(s).
7.1.2 - Phase 2 Application Reliability Verification
These tests test the various features of the third-party application and its various
components. Also involves the testing of the application against the Application
note and IVT questionnaire requirements to ensure that it functions reliably and
consistently in a manner that meets the requirements.
7.1.3 - Phase 3 Scalability, Stress, Performance and Load Testing
These tests are executed to determine the impact of the third-party software on the
Cisco® Call Manager’s ability to process calls. Testing will also determine the outer
limits of the applications ability to properly function under stress and perform
characterizing measurements on the Call Manager.
7.1.4 - Phase 4 Informational tests
These tests are executed to verify specific information about the third-party product
to Cisco® in relation to the IVT questionnaire and Application notes from the vendor.
7.1.5 - Phase 5 Negative Tests
These tests are executed to determine the ability of the impact on calls, the Call
Manager and the third-party application when combinations of the aforementioned fail
by power failure or network connectivity problems. Testing robustness of the application
through hardware and software fault insertion i.e. Failover/fallback.
 
|