Versions Compared

Old Version 4

changes.mady.by.user Zane England

Saved on

compared with

New Version Current

changes.mady.by.user Glen Steedman

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Call routing between the CUCM hosting the JTAPI remote and the webex calling MT organsiation 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

...

Each webex organisation will require a dedicated interface at this time although the same Webex XSI oAuth Intergration Integration can be used

Log in to Yarnman, open Administration App-> Interfaces.

...

Request Webex XSI intergration

Warning

Contact Yarnlab support to get an

intergration

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 to perform the OAuth part of the Webex credentials.

Its recommended to preform this step in a private browser window, to make sure the correct webex account is used

for Yarnman version 2.5.24 and lower

Select Node to bind the interface and click Bind to Arm

Info

Note the Redirect URL; This will be needed in the credentials settings and the Webex integration portal.For Yarnman V 2.6.3 and higher select test_mate-WxC as the role before continuing, refer to https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2918973483/Yarnman+Photon+Interfaces for more information

image-20240403-003928.pngImage Added

Click Update / Set Credentials to enter the Webex details.

...

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

...

Code Block
yarnman@yarnman:/opt/yarnlab/yarnman/scripts$ curl "https://webexapiwebexapis.com" -I
curl: (6) Could not resolve host: webexapi.com
yarnman@yarnman:/opt/yarnlab/yarnman/scripts$

...

Code Block
sudo systemd-resolve --interface=ens33 --set-dns=8.8.8.8

yarnman@yarnman:/opt/yarnlab/yarnman/scripts$ curl "https://webexapiwebexapis.com" -I
HTTP/1.12 302401 Found
date
x-content-type-options: nosniff
servertrackingid: Apache
set-cookieROUTERGW_xxxxxx
vary: 
locationaccept-encoding
content-type: http://ww17.webexapi.com/
content-type: text/html; charset=UTF-8
connection: closeapplication/json
date: 
server: istio-envoy
x-envoy-upstream-service-time: 2

Below shows successful connection via a proxy

Code Block
yarnman@yarnman:/opt/yarnlab/yarnman/scripts$  curl --proxy "http://10.101.10.87:3130" "https://webexapiwebexapis.com/" -I
HTTP/1.1 200 Connection established

HTTP/1.12 302401 Found
date
x-content-type-options: nosniff
servertrackingid: Apache
set-cookie:
location: http://ww17.webexapi.com/ROUTERGW_xxxxxx
vary: accept-encoding
content-type: text/html; charset=UTF-8
connection: closeapplication/json
date: 
server: istio-envoy
x-envoy-upstream-service-time: 2

Below shows proxy requiring authentication

Code Block
yarnman@yarnman:/opt/yarnlab/yarnman/scripts$ curl --proxy "http://10.101.10.87:3129" "https://webexapiwebexapis.com/" -I
HTTP/1.1 407 Proxy Authentication Required
Server: squid/4.13
Mime-Version: 1.0
Date: 
Content-Type: text/html;charset=utf-8
Content-Length: 3516
X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0
Vary: Accept-Language
Content-Language: en
Proxy-Authenticate: Digest realm="web-proxy", nonce="", qop="auth", stale=false
X-Cache: MISS from 18a6e4fa9a26
X-Cache-Lookup: NONE from 18a6e4fa9a26:3128
Via: 1.1 18a6e4fa9a26 (squid/4.13)
Connection: keep-alive

curl: (56) Received HTTP code 407 from proxy after CONNECT