Based on the pattern for other config commands, have you tried something like: xapi.config.set('Video', { DefaultMainSource: number}) ... View more

You may also consider forwarding this inquiry via email to devsupport@webex.com ... View more

Also ensure the target device names are in the controlled device list for the CUCM user account passed to makeCall.  There is also a 'CTI enabled' checkbox in the user config as well as the device config in CUCM admin - these default to enabled, but might double check them.   Configuring and scanning the JTAPI logs on the local machine might reveal something.  If you can't make any progress, though Cisco Developer Support can take a look at logs from the CTI-Manager/CUCM side to pinpoint the issue - might consider opening a ticket. ... View more

Those are the latest versions and can be considered to cover 11.5+ for now ... View more

The APIs which support Extension Mobility are: - Extension Mobility API: a small HTML/XML API allowing login/logout/logout-all/device-user query.  Requires end-user credentials or a designated E/M 'proxy' user credentials: https://pubhub.devnetcloud.com/media/axl-schema-reference/docs/Files/AXLSoap_doDeviceLogin.html#Link411 - AXL: an extensive SOAP API for configuring/managing all of CUCM.  Required CUCM admin-level credentials: https://developer.cisco.com/site/axl/ * doDeviceLogin: https://pubhub.devnetcloud.com/media/axl-schema-reference/docs/Files/AXLSoap_doDeviceLogin.html#Link411 * doDeviceLogout: https://pubhub.devnetcloud.com/media/axl-schema-reference/docs/Files/AXLSoap_doDeviceLogout.html#Link415   However, neither support cross cluster extension mobility scenarios - only single-cluster.   I have heard of developers examining the HTTP requests/responses of a phone performing EMCC function via the on-screen display and essentially reverse-engineering the HTTP messaging, so its something to consider.  However note this is not an officially supported 'developer interface', which may have support implications if the mechanism changes at some point in the future. ... View more

Wouldn't expect any issues from the spaces...definitely odd behaviour though.  If you do find that it causes any issues, please let us know via opening  DevNet Developer Support ticket, and we'll escalate to engineering for investigation and any potentially needed fix. ... View more

Per the TAPI Developer Guide, it looks like you should be able to retrieve the info via LineGetCallInfo: ... View more

Connect timeout would seem to indicate the JTAPI client is not able to contact the CTI Manager service...a few things to check: - If specifying by server name, make sure the client machine has working DNS.  Might try using the CTI Manager IP address instead - Make sure you have not enabled the 'Standard CTI Secure...' role for your JTAPI user, as connection will fail if the full secure connection steps have not been completed - Check for any firewall/NAT/ACL issues between the client and CTI Manager If everything checks out, you can take a look at the JTAPI logs to see if you can spot an error (though it can be a challenge to read the detailed logs): https://d1nmyq4gcgsfi5.cloudfront.net/site/jtapi/help/case-opening-steps/#JTAPI   For detailed troubleshooting assistance, I would recommend opening a DevNet Developer Support ticket: https://developer.cisco.com/site/support/ ... View more

It looks like PAWS-M is a standalone GUI appliance/app that uses the PAWS API under the covers to perform management tasks.  For your use case, your application/script would be using the PAWS API directly and PAWS-M would not be needed (though its possible PAWS-M might provide the capabilities you are looking for without coding yourself :)   The PAWS API should be present on all CUCM servers and has no licensing requirements - free to use. ... View more

Certainly PAWS would be the API to take a look at for this use-case: https://developer.cisco.com/site/paws/ There is  small sample app, however it is Java based...perhaps it could serve as  template: https://developer.cisco.com/site/paws/learn/sample-apps/ As PAWS is a SOAP API (XML over HTTP), you might consider the Zeep project for Python SOAP: https://python-zeep.readthedocs.io/en/master/ there is a new Python sample for the AXL SOAP API (not too dissimilar from PAWS) using Zeep that you might be able to adapt: https://github.com/CiscoDevNet/python-axl-learning-labs ... View more