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
...
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
...
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 | ||||
---|---|---|---|---|
|
...
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
...