Contents
| Table of Contents |
|---|
...
Select Node/Arm and Submit
...
JTAPI
...
node Setup
| Note |
|---|
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
...
...
Yarnman CUCM app user requires
...
Standard CCM End Users
...
Standard CTI Enabled
...
Standard CCM Super Users
...
This is the error seen if jade-berlin is not setup and test_mate tries to run
| Code Block |
|---|
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
| Note |
|---|
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 https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2730393636/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
...
Administration
| Anchor | ||||
|---|---|---|---|---|
|
...
The Dialplan test will perform testcalls from a selected phone, using configured CSS’s, to the PSTN to numbers with automatic answer or alternatively to another phone via
...
back to back trunks. A sample configuration to set up a trunk to CUBE using TCL script for test may be found below in Testmate Configuration section below
Other Prerequisites for running a Dialplan test is that CSS Groups (Required CSS’s to be tested), Number Groups (Numbers to be used for the tests) and Optionally Geographic Locations have been configured. See below in Testmate Configuration section
...
After Connect Failure
After Connect Success
JTAPI Connect Command
Pressing "Save" will save all changes made to the Dialplan test plan, that you have made.
Pressing "Refresh Tests" will update data for this very test, that might have been changed in existing CSS or Number Groups before.
Pressing "Start" will bring you to the following screen:
First, select a CUCM Instance.
After that, select the corresponding Device Pool.
Then select Device to be used for the test, Registration status of the selected device will display once selected.
Select the Line to be used and if to be scheduled, pick a date and time for the test (once you have clicked on the 'Schedule Test-Run' field, a calendar will open and after you picked a date, take you to pick a specific time automatically).
(Pressing 'Cancel' will bring you back to the previous page, where you can select Test Timeout and Test Generation Options.)
Pressing "Start" will take you to the following screen:
...
Select the source and target endpoint
Number of calls
Codec
Note, that the endpoints (CTI route points) need to be added to Testmate in the CUCM instances configuration.
There are options for:
Disable DTMF identification
Continue calls on error
Timeout for call talking
Timeout for call identification
...
The configuration uses a Cisco Dev Support sample TCL (Tickle) script - available below followed by sample CUBE CLI config
| View file | ||
|---|---|---|
|
application
service robodest Sample CUBE configuration
| Code Block |
|---|
application service robodest bootflash:robodest.tcl |
...
param robodest_maxtime-ringback 10 |
...
param robodest_mintime-ringback 0 |
...
! |
...
dial-peer voice |
...
9004400 voipservice robodestsession protocol sipv2 incoming called-number . |
...
dtmf-relay rtp-nte |
...
codec g711ulaw |
...
! |
...
dial-peer voice |
...
200 voipdescription *** Calls to Primary CUCM*** |
...
destination-pattern [2-9]......... |
...
(Dial Peer if return trunk required to dest CUCM adjust dial peer as required) session protocol sipv2 session target ipv4:<ip address of target CUCM here> dtmf-relay rtp-nte codec g711ulaw |
Firewall Configuration
Local Firewall Configuration
...