Specific questions about usage, parameters, context, and scope of the Scheduling API http://developer.cisco.com/c/message_boards/find_category?p_l_id=&mbCategoryId=3112752 2013-06-19T10:17:28Z 2013-06-19T10:17:28Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=16171690 2013-06-13T16:52:04Z 2013-06-13T16:52:04Z

I see.  When creating the rendezvous meeting, the max is deducted from the overbooked pool capacity.  The min is only relevant at attend time. - John

John Yontz 2013-06-13T16:52:04Z Dustin Grant http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=16148520 2013-06-13T00:35:54Z 2013-06-13T00:35:54Z

I wasnt too clear.  What I mean is, when creating the rendezvous meeting, capacity is deducted from the overbooked pool capacity.  Is the min or the max deducted form that capacity. Not the attend time capacity.

Dustin Grant 2013-06-13T00:35:54Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=16147010 2013-06-12T23:55:51Z 2013-06-12T23:55:51Z

When the first participant joins, the rendezvous meeting will allocate the minimum capacity from the pool, which is normally at least enough for two participants.  As additional participants join, if more capacity is needed, the meeting will attempt (i.e. best effort) to allocate additional capacity from the pool.  This will continue until the maximum provisioned for the meeting is reached. - John

John Yontz 2013-06-12T23:55:51Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15458256 2013-05-21T17:04:23Z 2013-05-21T17:04:23Z

Hi Jannik, Yes, it appears that the CDR API and the Scheduling API present different numbers in the totalNumberFound value.  I will try to have this changed in a future release to be more consistent.  For your other question, the meetingKey returned in the APIMeeting object from the GetMeetings method is not usable in the CTX Admin (i.e. web interface).  However, the conferenceId in the APIMeeting object can be used on the Meetings list page (Collaboration Services > Meetings) to find the meeting.  You can also filter by subject, start time, scheduler, etc., on that page using the column filters.  I hope that answers your question. - John

John Yontz 2013-05-21T17:04:23Z Jannik Hochfeld http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15447448 2013-05-21T12:50:57Z 2013-05-21T12:50:57Z

Hello John, Thanks for your help. It guided me to correct conclusion. My mistake was to expect the Scheduling API to work the same way as the CDR API. But there is a difference, as the CDR API tells you all elements with the totalNumberFound Value and the scheduling API tells you only the elements of the currect request I've got another Question: Is it possible to get directly to a meeting in the CTX webinterface with the "meetingKey" or with another value requestable via the API?

Jannik Hochfeld 2013-05-21T12:50:57Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15381718 2013-05-17T22:48:04Z 2013-05-17T22:48:04Z

Hi Jannik, The getMeetings request has additional parameters for pagination that will solve your problem.  The API Guide documentation has a paragraph (with an example) that describes how to do pagination for datasets that are larger than 100. You can find the documentation here:  http://developer.cisco.com/documents/3094533/11264455/CTX+1.1+API+Guide.  Hope that helps. - John

John Yontz 2013-05-17T22:48:04Z Jannik Hochfeld http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=15362183 2013-05-17T11:52:35Z 2013-05-17T11:50:31Z

Hi guys, i wonder how i raise the number of maximum Meetings, that are in the getMeetings result. When i do a soapCall with getMeetings and check the totalNumberFound Value it is always 100. When i look in the CTX Web Interface there are more than 100 Meetings. I want to build a overview of todays meetings and don't get all the meetings because of this limitation. CTX Version 1.1.0.5.1.1

Jannik Hochfeld 2013-05-17T11:50:31Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12763933 2013-03-07T21:21:21Z 2013-03-07T21:21:21Z

Mike, We verified that your observations are correct, both through the Admin and the API.  CTX will limit to 45 characters as you mentioned.  This limit was imposed because of limits in the TPS 8710 bridge resource. If you feel that 45 is too restrictive, please open a defect with CTX and we will try to address this. Thanks - John

John Yontz 2013-03-07T21:21:21Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12741667 2013-03-07T11:48:28Z 2013-03-07T11:48:28Z

We are getting this error in the API response. You also get the error if you schedule a meeting directly in CTX.

Michael Nelson 2013-03-07T11:48:28Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12728071 2013-03-07T02:06:17Z 2013-03-07T02:06:17Z

Hi Mike, I cannot find any limitation of 45 characters within the CTX code.  In fact, I see that the schema allows up to 128 characters.  Is it possible that your scheduling portal is enforcing that limit? - John

John Yontz 2013-03-07T02:06:17Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12703287 2013-03-06T16:04:22Z 2013-03-06T16:04:22Z

It seems that the CTX limits the number of characters that can be specified in the Number field for a dial-out endpoint to 45 characters. Is this configurable?

Michael Nelson 2013-03-06T16:04:22Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=11904095 2013-02-13T19:30:01Z 2013-02-13T19:30:01Z

It looks like you want to use scheduled with best effort instead of guaranteed perhaps because you want to take advantage of overbooking on the resource pool?  In any case, you are correctly inferring what the proper behavior should be.  Rather than needing to calculate the number of screens for your given scheduled meeting + endpoints, you can simply provide a sufficiently large value (e.g. 100) for your minScreens value and CTX will do a minimum of that value and the calculated value for the meeting.  Doing so will guarantee that when/if the meeting happens, it will have the required capacity for all participants allocated at the beginning of the meeting. - John

John Yontz 2013-02-13T19:30:01Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=11895348 2013-02-13T16:10:42Z 2013-02-13T16:10:42Z

Can you provide guidance on what to set the minScreensDefinitionType and minScreens fields to in a scheduleMeeting request when the meeting is best-effort but we want all the screens to be allocated when the meeting starts. Do we have to calculate the number of screens in the meeting or can we send a number that is greater than the number of screens that will be in the meeting and expect CTX to do a minimum on the that number and the number of actual screens scheduled for the meeting.

Michael Nelson 2013-02-13T16:10:42Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=11757069 2013-02-09T01:22:18Z 2013-02-09T01:22:18Z

The new value of additional capacity in the modify active meeting request will replace the prior value.  It is not an incremental value. - John

John Yontz 2013-02-09T01:22:18Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=11757055 2013-02-09T01:19:00Z 2013-02-09T01:19:00Z

Hi Mike, In CTX 1.1, the number of endpoints got converted to capacity units by CTX.  Since CTX couldn't know what type of endpoints would be joining, the required capacity for the meeting would assume the worst case for each endpoint given that bridge type.  This assumption allowed for "endpoint substitutability" so that for example, all endpoints could be 3-screen on the CTMS.  The downside is that CTX 1.1 didn't allow an easy per-meeting way to have finer control of the size of the meeting. With CTX 1.2, the client specifies exactly the number of screens that are required.  The number of screens gets directly translated into capacity, with one additional capacity per endpoint on the CTMS for the 30 fps data.  CTX then doesn't have to make any "worst case" assumptions for the endpoints.  This number of screens can be consumed by any arbitrary mix of endpoints at meeting time, as long as they don't exceed that total capacity. - John

John Yontz 2013-02-09T01:19:00Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=11756232 2013-02-08T23:25:45Z 2013-02-08T23:25:45Z

If the newAdditionalCapacity parameter is specified in the modifyActiveMeeting request, will the value specified add that much additional capacity or is it an update/replacement for the additional capacity specified when the meeting was scheduled?

Michael Nelson 2013-02-08T23:25:45Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=11756069 2013-02-08T23:13:38Z 2013-02-08T23:13:38Z

Can you explain how the numberOfScreens parameter works when specified in the scheduleRendezvousMeeting request. In CTX 1.1 there was a parameter numberOfEndpoints. numberOfScreens seems to have replaced it. numberOfEndpoints allocated based on the settings in the CTX so specifying 6 for instance didn't mean that just 6 segments/ports/screens would be allocated. Does numberOfScreens work the same way or does it allocate differently?

Michael Nelson 2013-02-08T23:13:38Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=10632644 2013-01-15T01:36:48Z 2013-01-15T01:36:48Z

Good question.  I confirmed that this behavior was introduced with CTX 1.1.  With CTX 1.0.3, the number of endpoints returned was not limited in this way. - John

John Yontz 2013-01-15T01:36:48Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=10640079 2013-01-15T01:26:49Z 2013-01-15T01:26:49Z

Is this new with CTX 1.1 or was this the case with CTX 1.0.3 as well?

Michael Nelson 2013-01-15T01:26:49Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=10632345 2013-01-15T01:15:46Z 2013-01-15T01:15:46Z

Hi Mike, For any of the get* API requests that are paginated, if neither the startIndex nor the numberToReturn are not specified, the query will default to the 1st 100 entries in the result set. - John

John Yontz 2013-01-15T01:15:46Z