Testmate Setup and Administration
Contents
Testmate Setup
The setup chapter describes the required services and apps for Testmate to operate
Firewall Rules
Required Services
To setup Testmate, Log in to Yarnman, open Administration App->Services
Testmate will require three services described below
Testmate App
Interconnect Service x 2
Terminator Service
From Top hand corner on services screen, select Testmate App from drop down
Define Service Name, select Yarnman Node and Authentication policy from drop downs and optionally Customer to be associated → Submit
Select Services Menu → Select Proxy Service
From Proxy Configuration Page, select ‘Service Routing’ from top right corner
Select ‘Add Yarnapp' and from drop down select the Testmate App ->Submit
The Testmate App has now been added and may be selected from top Right Drop down
Testmate requires 2 x Interconnect services. By default, there will always be one interconnect service running in Yarnman. To create a second service
Go Services → ‘Add Service’, select 'Interconnect Service
Name service, select Node/Arm, then Submit
Terminator service is created from Services → ‘Add Service’
Select Node/Arm and Submit
JTAPI node Setup
Any test_mate node that user JTAPI requires downloading the jtapi.jar from CUCM – this is required for test_mate to be able to communicate with CUCM
Browse to administration application and select the required node
Download and restart jade berlin service – it will ask what CUCM IP to download from. Enter the IP and OK
This is the error seen if jade-berlin is not setup and test_mate tries to run
Error: connect ECONNREFUSED 127.0.0.1:6666
ERROR Found test-run marked for this service that is "processing", marking test-run "failed" and aborting its tests.
CUCM Configuration
Yarnman CUCM app user requires
Standard CCM End Users
Standard Admin Users
Standard CTI Enabled
Standard CCM Server Monitoring
Standard CTI Allow Control of Phones supporting Rollover Mode
Standard CTI Allow Control of Phones supporting Connected Xfer and conf
Standard AXL API Access
Standard AXL API Access Role may need to be added to a custom Access Control Group, an alternative approach is to use
Standard CCM Super Users
Interfaces
Before initiating Testplans, Interfaces to CUCM needs to be configured. This is described in Yarnman Setup Guide under interfaces chapter Yarnman Administration | Interfaces
JTAPI Remote Setup
You will require a CTI route point with 2 DN's (lines) each with external number mask (e164). The CTI route point must be associated with the Testmate User
Click on CUCM instances then select the CUCM interface that the Remote (CTI Route Point) is on and add it
CUCM CDR Access
This optional configuration is only needed if using testmate to query CDR records for Packet Stats from IpPhones that send stats when a call is completed.
To use the CDR feature to collect CMR details, a few settings need to be configured on CUCM. Some of these settings may already be enabled, depending if the Cucm server is sending CDR records to a billing server etc.
CUCM
By default, the Cucm CDRs are disabled; the following settings should be obtained by Axl/soap to get valid data.
CDR file time interval determines how often the CDRs are written to disk and transferred from other Cucm nodes in the cluster to the publisher. This is set in System > Enterprise Parameters Configuration . This should be set to 1 if not already.
CDRs need to be enabled on a Per Node basis; the zero duration flag is optional, which would log calls that were busy/ring out. Non-standard errors would still be logged in the CDR, such as numbers not found.
System > Service Parameters > Select Call Processing Node(s) > Service > Cisco CallManager
Set CDR Enabled Flag to True (If the option isn't there Press the Advance button on the magnifying glass)
Do this for Each server in the cluster
Scroll down and set the Call Diagnostics Enabled, this is a Cluster Wide setting.
Call Maintenance Records (also called diagnostic records) records packet statistics details captured in a separate file as a CMR.
CAR
This application is installed by default and runs on the publisher , you can browe to it via https://ip.of.cucm.publisher/car
By default only the CDRs are loaded, and the CMRs are ignored, we need to enable CMRs to be loaded.
System > Scheduler > CDR Load
Select Continuous Loading 24/7, Untick Load CDR Only , press update.