Open

Contents

The Testmate platform has been designed to provide tightly integrated and relevant test automation for Cisco Unified Communications. Specific test plans have been built for the following functions:

• Commissioning Testing (new customer)

• Post Migration (new sites)

• Post change (assurance BAU)

• System Accreditation (new CSR)

• Stress Testing

• IP Readiness Assesment (Prattler)

Open

Dial plan testing in HCS environments is a complex and time-consuming task, which becomes significantly more complex and time consuming, when new countries and their associated dial plans are added to the HCS solution over time.
The dial plan test plan provides automated testing, that enables a robust and consistent test regime, that ensures a quality user experience, before and after planned updates and changes in the HCS dial plan.
Use Cases

• Testing, to assist with verification of the new dial plan, used by CUCDM 10/VOSS4UC/Kurmi.

• Reduce resources required for testing for the dial plan.

• Minimize potential human errors, by using test automation.

Open

The migration capabilities are made of the following components:

• Site Migration

Enables automated testing by deployment engineers during a migration, to automatically test, that the porting has been successful and that media services and basic calling is functioning correctly.

• PSTN Load Test

Enables stress testing with a configurable number of calls between two CTI objects, controlled by Testmate, to ensure sufficient capacity is available, which is not practical to test, using other means.

• Prattler

Providing a mechanism, to test Jabber and media services beyond the network boundary, to support assurance and deployment teams, by testing the required DNS records, certificates and media paths for Jabber.

The site migration test plan has been designed for testing and verification of porting and site migration activities. During the setup and execution of this test plan, Testmate takes control of registered devices in the nominated device pool and orchestrates a variety of tests between phones and the JTAPI remote.
This test plan focuses on the test of site specific PSTN and media services and is intended for use by deployment engineers, to be able to quickly perform pre-site commissioning testing in an automated manner.
Use Cases

• Samples DID's from all ranges in device pool(s) under test and verifies, if both in- and outbound calls are correct.

• Basic media service testing (MOH, MTP, CONF, transfer)

• Extension mobility

• Media path verification (packet statistics)

• Re-run test run, following the resolution of issues

• Public work space testing

• Simulated emergency call testing

Open

The PSTN load test plan enables load testing and verification of a number of calls, that can be established between two CTI route points. The CTI route points can be located on either two different clusters, connected by either PSTN or private trunks, to determine the maximum number of calls supported on the trunking infrastructure – or for testing Call Admission Control limits between two different locations on the same cluster.
Use Cases

• Verify number of concurrent calls (channels) between two JTAPI remotes (CTI Route Points) – these can either be across the PSTN, internally (CAC testing/AAR) or across private trunks.

• Test SIP Connect Services

Open

Supporting Jabber beyond the network boundary has become a complex and time-consuming task, due to the limited control of the environment. When issues arise, the traditional methods of troubleshooting require a high level of expertise, operational resources and direct involvement by the end user, with issues normally taking several interactions to resolve. This leads to diminished customer satisfaction with the solution.
Providing effective assurance faces the same challenges beyond the network boundary, to determine, if call quality is being affected by network degradation or impairments.

• Reduce resources, required for troubleshooting Jabber.

• Improve customer satisfaction with soft phones.

• Minimize potential human errors, by using test automation.

• Provide a mechanism for site pre-commissioning testing, for Jabber to ensure, that the environment is configured correctly.

The solution is broken down into three separate components:

• Client-Side Testing (Prattler)

This component provides an application, that can be downloaded by end customers, to perform testing for reactive support. This does not require any infrastructure, to be deployed in the customer network.

• Ad-Hoc Media Probe (Prattler Remote)

Extends the client-side, to enable media testing end to end.

• Problem Report Analytics

Provides a mechanism, to easily provide Jabber problem reports to assurance teams and performs automated log analysis.

The PVT test plan is targeted for post change verification testing, that allows for a selection of affected shared services and customer specific systems, to determine, what systems require post change verification testing. This test plan will be modular, which allows adding future extensions, to support additional test cases, as well as backup, health checks and functionality checks of impacted systems.
The first step of the PVT test plan will be, to select customer systems and nominate, what devices to use for testing, then select the test cases required, then select any manual mix-ins, then select the JTAPI remote to use, then start testing.
PVT also has the manual test case, that allows interactive testing with the Testmate users mobile phone or other external destination, to make and receive calls from, as well as verify call statuses.
Use Cases