Versions Compared

Key

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

...

The XSI is a special permission that may not be available on your webex org, Yarnlab has an integration available for this to provide this function, see the following page for further information about the permissions for test_mate for webex calling. Test_mate Webex Calling Multi Tenant (WxC-MT) https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2873851905

Note

Yarnlab do NOT need to know the webex credentials

...

Code Block
yarnman@ym-ph4-wxc-glen [ ~ ]$  curl --proxy-anyauth -x http://basicuser:basicuser123@10.101.10.87:3129 -4 "https://webexapis.com/" -I
HTTP/1.1 407 Proxy Authentication Required
Server: squid/4.13
Mime-Version: 1.0
Date: Wed, 13 Mar 2024 03:38:10 GMT
Content-Type: text/html;charset=utf-8
Content-Length: 3519
X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0
Vary: Accept-Language
Content-Language: en
Proxy-Authenticate: Basic realm="Squid"
X-Cache: MISS from 18a6e4fa9a26
X-Cache-Lookup: NONE from 18a6e4fa9a26:3129
Via: 1.1 18a6e4fa9a26 (squid/4.13)
Connection: keep-alive

HTTP/1.1 200 Connection established

HTTP/1.1 401 Unauthorized
x-content-type-options: nosniff
trackingid: ROUTERGW_cc737ef5-1e1d-4e2f-8a1e-840dd944250f
vary: accept-encoding
content-type: application/json
date: Wed, 13 Mar 2024 03:38:11 GMT
server: istio-envoy
x-envoy-upstream-service-time: 3
transfer-encoding: chunked

Cisco Unified Communications Manager

This interface is used by Wrangler_ and test_mate to communicate with multiple services provided by the publisher or subscriber(s).

The following CUCM permissions are required for wrangler_

  • Standard CCM End Users

  • Standard Admin Users

  • Standard CCM Server Monitoring

  • 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

The following Permissions are required for test_mate

  • 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

Create a new interface in yarnman

  • name the interface and press submit

  • Bind the interface to the required arm(s)

  • Press update/set Credentials

  • Type in the ip address of the publisher (this will automatically fill in the details to all the other services)

  • Type in the user and password, press use for all interfaces.

  • Press submit followed by test connection.

Info

the default cucm administrator account can not control jtapi devices

Jade-Berlin

Whilst not technically an interface, this service provide jtapi control and uses the cucm interface within yarnman applications, mainly test_mate.

The jtapi.jar must be downloaded from the cucm.

This is done by navigating to Nodes > clicking on the node name > Pressing (re)download jtapi.jar image-20240812-151555.pngImage Added

Provide the ip address of the publisher, once jtapi.jar has downloaded press restart Jade-Berlin image-20240812-151657.pngImage Added

Info

Not all jtapi.jar versions are backwards compatible with different versions of cucms.

Common error messages from jtapi

Unable to create provider -- User connected on an invalid port

Most likely Secure CTI permission applied to the application user in cucm, remove secure CTI and only have standard cti

Unable to create provider -- connect timed out

This could be related to firewall or network connectivity between yarnman and cucm, CTI Manager not running on the target node

Unable to create provider -- bad login or password

Most likely wrong username/password/permission on the application user

Unable to create provider -- Incompatible Protocol version

The version of jtapi.jar cached in jade-berlin is not compatible with the target cucm, Download jtapi.jar from target cucm and restart jade-berlin

Unable to create provider -- directory login timeout

Can related to LDAP/AD timeout, high database load on cucm or jtapi not responding