Test_mate Webex Calling Multi Tenant (WxC-MT)
- 1.1.1 Webex Integration Account using yarnlab webex Integration
- 1.1.2 Add Webex Interface
- 1.1.3 Internet Proxy Configuration
- 1.1.4 Request Webex XSI intergration
- 1.1.5 Contact Yarnlab support to get an integration created https://support.yarnlab.io/ or support@yarnlab.io
- 1.1.6 Arm Bindings and Webex Credentials
- 1.1.7 Test Webex connection
- 1.2 Webex Calling (WbC-MT) Test Plan
- 1.3 Test plan settings
- 1.4 Test Runs Results
- 2 Troubleshooting
Â
Call routing between the CUCM hosting the JTAPI remote and the webex calling MT organisation must exist
Only the primary device for users can be tests if a use has phones - the XSI api that test_mate uses only allows testing of primary device
The following webex clients are not supported
Web based
Mobile
Tablet
To test Webex desktop client the user under test must only have the Desktop webex application enabled, Web Mobile and Tablet must not be checked
Webex Integration Account using yarnlab webex Integration
To get up and running use the yarnlab webex integration, this already has the XSI feature enabled, with the correct permissions set.
You authorise the integration with your own webex admin credentials that has access to control phones.
Add Webex Interface
Each webex organisation will require a dedicated interface at this time although the same Webex XSI oAuth Integration can be used
Log in to Yarnman, open Administration App-> Interfaces.
From the top right corner, click +Add interface, select Interface type Webex API (OAuth2 - Cloud)
Define Interface Name, Description, then click Submit.
Internet Proxy Configuration
A proxy may be required if test_mate doesn’t have direct access to the internet for API calls. test_mate supports the following authentication modes.
No Authentication
Basic Authentication
Digest Authentication
To configure the proxy, toggle the Enable Proxy to ON, and provide the HTTP Proxy details, which will be used for both HTTP/S.
Request Webex XSI intergration
Contact Yarnlab support to get an integration created https://support.yarnlab.io/ or support@yarnlab.io
Provide Yarnlab with the redirect URL provided on the interface page as per below, This will be unique per interface added and if multiple organisations/interfaces are being tested multiple redirect URLs will need to be provided
Â
Arm Bindings and Webex Credentials
Firefox is required for Yarnman version 2.5.24 and lower
Select Node to bind the interface and click Bind to Arm
Click Update / Set Credentials to enter the Webex details.
Enter in the Application name of yarnlab-integration , Client ID as Provided by Yarnlab and the Redirect URL click Submit
you will be presented with the Webex OAuth login flow; provide the Webex user details that will be used for test_mate
Â
If prompted, accept the Webex permissions to be granted.
You will be redirected back to test_mate to re-authenticate, login as the yarnman administrator.
Finally, add the Client Secret provided yarnlab and click submit.
The interface page will refresh and the Access Token Expires and Refresh Token will be populated with expiry dates.
Test Webex connection
Click the Test Connection button. This will return the Webex user details that granted the Webex integration.
Â
Webex Calling (WbC-MT) Test Plan
Â
Test plan settings
Setting | Description |
---|---|
Name | Name of the test plan. |
Webex Account / Interface | name of the webex interface used for testing |
Webex Organization | organisation that is use including xsi url |
Endpoints | List of webex calling endpoints |
Webex Request Pause After Error (secs) | Time to wait after a backoff error during a Webex request (i.e. status, join or mute). |
Webex Request Retries After Error | How many times to retry before raising an error, related to the pause above. |
Test Runs Results
Â
Troubleshooting
API errors
Problem: Blank page after submitting Webex credentials
Â
Suggested course of action:
Try using an alternate browser such as Firefox in a private window/tab
Â
Problem: Expired credentials/tokens in Webex
Suggested course of action:
Click on Update / Set Credentials to reauthorise with the account that grated the Webex integration and/or check the correct details supplied.
Problem: Missing Redirect URL for Webex integration account
Â
Suggested course of action :
Ensure the Redirect URL is the same as displayed within the test_mate interface.
Ensure this URL has been provided to yarnlab, as yarnlab need to add this to the integration
Internet / Proxy Errors
Problem: Wrong Protocol
Suggested course of action:
Check the correct protocol has been specified, e.g. HTTP
Check the correct port number provided
Problem: Wrong User/Password
Suggested course of action:
Check correct username / password entered ( password could be case sensitive depending on the 3rd party proxy).
Check Proxy allows access to the domains required for API calls to the providers.
Problem: DNS access and/or internet access are unavailable
Direct internet access will need to be able to resolve the webexapi url
Below shows the yarnman server not able to resolve DNS
yarnman@yarnman:/opt/yarnlab/yarnman/scripts$ curl "https://webexapis.com" -I
curl: (6) Could not resolve host: webexapi.com
yarnman@yarnman:/opt/yarnlab/yarnman/scripts$
Set the DNS server via systemd
sudo systemd-resolve --interface=ens33 --set-dns=8.8.8.8
yarnman@yarnman:/opt/yarnlab/yarnman/scripts$ curl "https://webexapis.com" -I
HTTP/2 401
x-content-type-options: nosniff
trackingid: ROUTERGW_xxxxxx
vary: accept-encoding
content-type: application/json
date:
server: istio-envoy
x-envoy-upstream-service-time: 2
Below shows successful connection via a proxy
yarnman@yarnman:/opt/yarnlab/yarnman/scripts$ curl --proxy "http://10.101.10.87:3130" "https://webexapis.com/" -I
HTTP/1.1 200 Connection established
HTTP/2 401
x-content-type-options: nosniff
trackingid: ROUTERGW_xxxxxx
vary: accept-encoding
content-type: application/json
date:
server: istio-envoy
x-envoy-upstream-service-time: 2
Below shows proxy requiring authentication