dCloud test_mate PVT

Test_mate PVT

Test_mate is an automated UC testing platform, providing Migration, Assurance and Accreditation testing. This lab will be utilising the PVT ( Postchange Verification Testing)

We are going to set up Test_mate to control Two Jabber Clients on the Source Cluster to perform Onnet calls and to simulate incoming and outgoing PSTN calls.

To simulate a remote PSTN endpoint, a pretend PSTN configuration with a fictitious PSTN number will be created on the Target Cluster and a sip trunk between them.

Note: It's recommended to have a remote session with ad1 to perform Test_mate configuration in firefox. Once Test_mate is controlling the Jabber phones, wkst1 and wkst2 will be displaying screen pops and playing sounds.

This lab guide is for use with the yarnlab dCloud for wrangler_

Configuration on Target CUCM

Procedure

Configure the following Partitions on the Target Cluster

Configure the Following Calling Search Spaces on the Target Cluster

Configure a new Siptrunk on the Target Cluster

Create CTI Routepoint on Target Cluster

Create CTI Routepoint Line 1 on Target Cluster

Create CTI Routepoint Line 2 on Target Cluster

Create Translation Pattern on Target Cluster

Create Route Pattern on Target Cluster

Create Application user on Target Cluster

Configuration on Source CUCM

Create Sip Trunk on the Source Cluster

Create Route Pattern on Source Cluster

Create Application user on Source Cluster.

Configuration of Yarnman Admin Interconnects

We will create two new CUCM interfaces with the jtapi users we created above for the Source and Target Cluster. These accounts will be used to control the Jabber Endpoints and CTI Route point.

Note: If you have previously configured yarnman, we can’t reuse the existing interfaces as the CUCM administrator account doesn’t allow control of CTI route points.

Add a 2^nd interconnect service. Click on Services > Add Service > Interconnect Service.

1. Call the service name Interconnect Service2, Bind to standalone, and press submit.

   

2. Confirm you have two interconnect services

Note: you may only have 1 interconnect service if you haven’t completed the wrangler lab; repeat the above to add another.

Configure jade-berlin

Click on Nodes > Standalone.

Scroll down to click on Download Jtapi/Jar

Use the publisher address of the source cluster.

Restart the Jade-Berlin service

Configure CUCM interfaces

Create two new CUCM interfaces with the following details

1. Click on Interfaces > Add Interface and select CUCM / Cisco Unified Commutations Manager/ CallManager

   

2. select CUCM / Cisco Unified Commutations Manager/ CallManager

Associate the interface to the Arm. Click on Arm Bindings

Select standalone and press bind to arm

Press Updater/Set Credentials

Enter in the details of the Application user created earlier and press use for all interfaces, followed by submit

Press test connection, Ensure that you click on the blue ribbon once completed, as this will ensure that the AXL version is populated.

Configure Terminator Service

Test_mate uses this service to send and receive RTP using a CTI Routepoint. The IP address is required as this will be bound to the RTP packets. It’s possible to have Multiple Arms with different IP addresses in complex networks.

Click on Services > Add Service > Terminator Service

Select standalone for the node/arm, the IP address for Test_mate (if you are using the prebuild VM, this will be 198.18.133.6), set the last port number to 6709, and press submit

You can ignore the message about the mismatched address.

Add Testmate App

Add a new service of Testmate App

Click on Services > Add Service > Testmate App

Click on Bind to standalone Node/Arm, and select central DB-Only Authentication policy.

Add the testmate app to the Yarman Proxy service

Click on Services > Standalone Yarnman Proxy.

Click on Service Routing

Click on Add Yarnapp > Testmate App

Click on Submit to save the changes.

Configure Testmate App

Navigate to the Testmate App

Set the CTI route point used by Testmate

Scroll down and click on CUCM instances > Click on testmate_target

Select the testmate_t_RP route point we created earlier and click add.

The page will reload and show the two DN’s of the CTI route point on the Target cluster.

Note: If you cannot see the CTI Routepoint from the dropdown, make sure the Application user has been associated with the CTI route point in CUCM

Start Cisco Jabber clients

Connect to Workstations 1 and 2 and start each jabber client

First PVT Test Plan

We are now ready to create our first test plan.

The first test will use the default tests to make an incoming and outgoing onnet and PSTN call.

Navigate to the Testmate App > Test Plans > Create Testplan

Enter a name for the test, in this case, First Test; select Post Verification Testing from the dropdown and click Submit.

Click on the devices tab.

Select testmate_source

Select dCloud-DP

Click in search for devices by name.

Search for the two jabber devices and press add devices

Press Check status; in this example, we have added the wrong jabber device and will add the correct one.

Remove the offline device.

Press Save only

Click on Test Cases, scroll to external call test cases, and add the remote Endpoint we created earlier (the cti route point)

Scroll down and press Save and Run; when the screen refreshes, press Test Cases.

You can watch the progress of the tests; each test step will be marked with a green tick or a red cross. Further detailed steps can be viewed by checking for calling/called numbers and other test criteria.

Click on the results tabs once the test is finished (some tabs can only be accessed at the end of the tests)

Note: you may need to press refresh to get the latest results

Click on the report to produce a detailed test report that can be exported as a CSV or xls.

Second PVT Test Plan

We will Create another test plan with more compressive tests to check for

DTMF transmission and reception

Supplementary features such as conference, pickup and park

Media statistics to/from the CTI route point via the Terminator service

Some test cases require three devices (e.g. Device C in the test steps). Connecting another Jabber client via dCloud using Cisco-anyconnect VPN from your desktop or laptop is possible. Refer to the dCloud guides for VPN connectivity.

We will use the External Call Test Cases, allowing us to test the PSTN and simulate the 3^rd endpoint. This test is helpful for both troubleshooting and commissioning a new site.

Create a new test as type Post Verification Testing

Select the following test

Make and Receive call

Call Pickup Call

Call Park Call

Select the remote endpoint Testmate_t_RP:4201 @ Testmate_target and select the following tests

Codec G711 64K

Make call

Receive Call

Transfer Internal call externally

Transfer external call internally

Forward Internal call externally

Forward external call internally

Forward external call externally

Continue Selecting

Conference call

Call pickup call

Call Park call

Scroll down to the Media terminator section and select the Terminator service we created earlier and select the following

DTMF signalling – Test DTMF Signalling Before and after hold

A and B party hold and resume – A then B party Hold/Resume

Note: Enabling Check Packet Statistics will show packets from the Terminator service. However, there will be no packet statistics from Jabber or Phones via an expressway.

Press Save Only, scroll back to the top of the page, and select devices.

Add the 2 Jabber phones from the testmate_source CUCM and press Save and Run.

Press Test Cases to monitor the progress; the test will take about 8 minutes to complete. You may hear music from the terminator service via the Remote desktop session.

As we have enabled DTMF testing before and after putting the call on hold, Test mate will randomly select a 4-digit number to transmit and will be checked by the CTI route point to validate it matches.

Call Park DN that was used when placing the call on Park

Testmate instruction jabber to create a 3-party conference with another Jabber endpoint and a PSTN endpoint

CUCM Target bulk load files

Optional use of the import/export function within CUCM to load most of the config required on the Target Cluster. Use Workstation 2, which will have the tar file named testmatetarget.tar

The Import/Export file contains the following.

Partitions

• Calling Search Spaces

• Route and Translation pattern

• Sip Trunk

• CTI route point*

Note: There is a known issue with the Importing of CTI Routepoints with DN’s in cucm 12; you will need to manually add the DN’s to the route point device and create the Application user.

Navigate to the Bulk Administration menu on the Target CUCM

Click Add New

Browse to the file tetmatetarget.tar, select import/export as the file type and select the transaction as Import Configuration

Once the file has been updated, navigate to the Import/Export menu in Bulk Administration and select Import.

Select the file that was uploaded

Press Select all to check all the configuration items and select Run Immediately before pressing Submit.

Verify the configuration items have been added to the Target CUCM, and continue by manually adding the Route point DN’s and application user

Troubleshooting

The calls are not working.

Check SIP Trunk on the source cluster is showing Full Service

Check Route Pattern added to use this trunk

Try resetting the sip trunk on both Source and Target CUCM clusters.

Unable to select External Endpoint

Make sure the CTI Route point is associated with the testmate_t_jtapi application user.

The correct permissions are applied to the application user

CTI route point selected and showing in CUCM Instances > Testmate_target

Unexpected jtapi error

Redownload the jtapi.jar via jade-Berlin

Restart the jade-Berlin service

No packet statistics on terminator service

You may need to allow the UDP port range configured on the UFW firewall on Migration Assistance.

From the AD1 server, use Putty to connect to ma.dcloud.cisco.com ( or 198.18.133.6 )

Issue the command sudo ufw allow 6700:6709/udp