A place for general comments, questions, support, and enhancement requests for all CTX APIs http://developer.cisco.com/c/message_boards/find_category?p_l_id=&mbCategoryId=3094633 2013-05-23T00:41:55Z 2013-05-23T00:41:55Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=10051142 2013-01-08T22:53:37Z 2013-01-08T22:53:37Z

Hi Balan, It is probably best for you to continue working directly with David Wong in Product Management and your contacts within Advanced Services (AS).  The individual test cases are less important than your existing contacts.  By the way, I was unable to locate the CDN test case xls that you are referring to.  It may be best for Cisco to remove that from the CDN site.   - John

John Yontz 2013-01-08T22:53:37Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=6201610 2012-07-30T19:45:01Z 2012-07-30T19:45:01Z

Hi Mike, That setting has been moved to the Global Configuration page, which is found under the System tab on the left in the CTX Admin. The parameter is called "MeetMe Default Screens". - John

John Yontz 2012-07-30T19:45:01Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=5876732 2012-06-15T19:50:28Z 2012-06-15T19:50:28Z

Yes, you are correct. For a rendezvous meeting, the lock only applies to the current instance. When that instance ends, the lock state is reverted so the next instance will begin unlocked. - John

John Yontz 2012-06-15T19:50:28Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=3126503 2011-03-03T20:41:06Z 2011-03-03T20:41:06Z

The CTX APIs use basic HTTP authentication with base64 encoding.  This requires a user name and password to be submitted with each API request.  The client proxy framework (e.g. Axis) should have a simple way to set this up.  The user needs to be configured in the CTX Admin application with role of API.  A password is configured also.  Then this combination of user name and password is used for the basic HTTP authentication.   Basic HTTP authentication is sufficient given the assumption that the client portal and CTX reside in a private protected network.  In the future, the APIs may provide an SSL/TLS certificate-based authentication for greater security and deployment flexibility.

John Yontz 2011-03-03T20:41:06Z Kulai Bhandary http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=3124890 2011-03-03T20:25:04Z 2011-03-03T20:25:04Z

What method of authentication is used with the APIs?

Kulai Bhandary 2011-03-03T20:25:04Z Kulai Bhandary http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=3121067 2011-03-03T02:15:44Z 2011-03-03T02:15:44Z

There are several options to generate the client proxy files from the WSDL. One option is to use a web service stack like JBossWS. These contain command line tools like [b]wconsume[/b] that "consumes" the WSDL and produces the necessary client artifacts. These artifacts can then be imported in to your projects. The Eclipse IDE provides a wizard that will create the java proxy files for you. To access the wizard follow these steps: 1) select the project in the Project Explorer 2) Right click to bring up the context menu 3) Select New->Other from the menu 4) In the 'Select a wizard' dialog click on Web Services 5) Select Web Service Client and click on Next 6) In the next dialog enter the location of the WSDL for Service Definition 7) Click on Next 8) Select the Output Folder 9) Click on Define custom mapping for namespace to package if necessary 10) Click on Finish The wizard will generate the client proxy files ready to use in your project.

Kulai Bhandary 2011-03-03T02:15:44Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=3117133 2011-03-02T00:33:20Z 2011-03-02T00:33:20Z

What is the best way for a Java developer to generate client proxy files from the WSDL?

John Yontz 2011-03-02T00:33:20Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=3112728 2011-03-01T02:17:20Z 2011-03-01T02:15:35Z

In general, CTX will conform to Cisco policy of supporting up to two major releases backwards.   Our versioning scheme will be invocation context-based.  That is, we will include the version number in the URL path for subsequent versions.  For example, the initial version of the CDR API will be located at a URL that looks like this:   [b]http://1.2.3.4/ctxapi/api/cdr[/b]   Our next version will be located at a path something like this:   [b]http://1.2.3.4/ctxapi/api/[color=#0000ff]v2.0[/color]/cdr[/b]   In this example, if CTX is currently at version 2.0, a client designed to work with the initial version can continue to use the first URL path above.  CTX will be able to differentiate these down-rev requests and respond in a backward compatible way.

John Yontz 2011-03-01T02:15:35Z Andrew Brindamour http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=3112243 2011-03-01T02:00:07Z 2011-03-01T02:00:07Z

What are the plans for versioning the API?

Andrew Brindamour 2011-03-01T02:00:07Z