Getting Started With TelePresence Reporting API

Developers interested in developing an application for collecting CTS-Manager data need;

  1. Sign up as a Cisco Developer and provide information to Cisco about your application and intended use.
  2. Once approved as a Cisco Developer and CDN Developer Support Contract is in place development to the Reporting API can begin.
  3. Download the CTS-Manager Reporting API Developers Guide to understand the development requirements and API in detail.

Pre-Requisites

Developers will need Cisco Telepresence products for development and testing their application.

It is recommended the following be purchased for the developers lab;

1) Cisco TelePresence Manager 1.7 or higher running on an approved MCS 7800 series server. As an alternative consider the Cisco Telepresence Commercial Express Bundle (CTS-COMM-EXP1.7-K9) which includes a MCS Server using VMware to support CTS Manager, CTS Multipoint Switch, and CTS Recording Server. (Part# CTS-COMM-EXP1.7-K9).

2) License for CTS-Manager Metrics Dashboard and Reporting API (Part# LIC-CTS-MAN-RPT)

2) Cisco Communications Manager 7.1.3 or higher Enterprise edition.

3) Cisco Telepresence endpoints are not required, but recommended. The CTS-500 series is best for testing. If you don't have CTS endpoints, you can create in Communications Manager phantom endpoints which will allow for scheduling in your goupware application. 

4) A groupware calendaring scheduling solution like Microsoft Exchange or IBM Domino.

5) An LDAP Active Directory Server.

Registering as a Cisco Developer will allow for purchase of Cisco lab equipment at not for resell discounts.

The Reporting API is a CTS-Manager Licensed Feature, the part # LIC-CTS-MAN-RPT if ordering with CTS-Manager or if adding on use part # L-LIC-CTS-MAN-RPT=

 

License Requirements
The Reporting API feature is a licensed feature on CTS-Manager. If ordering a new lab system, make sure to include the part# LIC-CTS-MAN-RPT. If adding on to an existing system, use L-LIC-CTS-MAN-RPT=. 

The PAK id for registration and receving the license file will be sent with new orders as a piece of paper in the MCS Server box. Add on orders using L-LIC-CTS-MAN-RPT= will receive PAK id via email.

After receipt of the PAK, then install and configuration of CTS-Manager must be done. This document PAK number and License MAC address for the CTS-Manager then needs to  be registered at http://cisco.com/go/license to receive the license file. Once the licensing file is received via email after registration, upload the license file to CTS-Manager to enable the Scheduling API.

Development Platforms

The API would work in most SOAP development environments but has been tested in this release with Apache Axis2. Documentation provides examples in Java. The Java examples are based on Apache Axis2 (1.3) and JDK 5.0 (Java 2 Platform Standard Edition Development Kit 5.0). For more information about Apache Axis 2, go to http://ws.apache.org/axis2/.

Note: Different development platforms vary in their specification implementations. Implementation differences might prevent access to some or all of the features in the API.