<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Scheduling API</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_category?p_l_id=&amp;mbCategoryId=3112752" />
  <subtitle>Specific questions about usage, parameters, context, and scope of the Scheduling API</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_category?p_l_id=&amp;mbCategoryId=3112752</id>
  <updated>2013-05-19T20:44:29Z</updated>
  <dc:date>2013-05-19T20:44:29Z</dc:date>
  <entry>
    <title>RE: Limited Results for getMeetings Request?</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=15381718" />
    <author>
      <name>John Yontz</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=15381718</id>
    <updated>2013-05-17T22:48:04Z</updated>
    <published>2013-05-17T22:48:04Z</published>
    <summary type="html">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</summary>
    <dc:creator>John Yontz</dc:creator>
    <dc:date>2013-05-17T22:48:04Z</dc:date>
  </entry>
  <entry>
    <title>Limited Results for getMeetings Request?</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=15362183" />
    <author>
      <name>Jannik Hochfeld</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=15362183</id>
    <updated>2013-05-17T11:52:35Z</updated>
    <published>2013-05-17T11:50:31Z</published>
    <summary type="html">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</summary>
    <dc:creator>Jannik Hochfeld</dc:creator>
    <dc:date>2013-05-17T11:50:31Z</dc:date>
  </entry>
  <entry>
    <title>RE: 45 Character Limit for Dial-out URI</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12763933" />
    <author>
      <name>John Yontz</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12763933</id>
    <updated>2013-03-07T21:21:21Z</updated>
    <published>2013-03-07T21:21:21Z</published>
    <summary type="html">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</summary>
    <dc:creator>John Yontz</dc:creator>
    <dc:date>2013-03-07T21:21:21Z</dc:date>
  </entry>
  <entry>
    <title>RE: 45 Character Limit for Dial-out URI</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12741667" />
    <author>
      <name>Michael Nelson</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12741667</id>
    <updated>2013-03-07T11:48:28Z</updated>
    <published>2013-03-07T11:48:28Z</published>
    <summary type="html">We are getting this error in the API response. You also get the error if you schedule a meeting directly in CTX.</summary>
    <dc:creator>Michael Nelson</dc:creator>
    <dc:date>2013-03-07T11:48:28Z</dc:date>
  </entry>
  <entry>
    <title>RE: 45 Character Limit for Dial-out URI</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12728071" />
    <author>
      <name>John Yontz</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12728071</id>
    <updated>2013-03-07T02:06:17Z</updated>
    <published>2013-03-07T02:06:17Z</published>
    <summary type="html">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</summary>
    <dc:creator>John Yontz</dc:creator>
    <dc:date>2013-03-07T02:06:17Z</dc:date>
  </entry>
  <entry>
    <title>45 Character Limit for Dial-out URI</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12703287" />
    <author>
      <name>Michael Nelson</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=12703287</id>
    <updated>2013-03-06T16:04:22Z</updated>
    <published>2013-03-06T16:04:22Z</published>
    <summary type="html">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?</summary>
    <dc:creator>Michael Nelson</dc:creator>
    <dc:date>2013-03-06T16:04:22Z</dc:date>
  </entry>
  <entry>
    <title>RE: minScreensDefinitionType/minScreens for Schedule Meeting</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11904095" />
    <author>
      <name>John Yontz</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11904095</id>
    <updated>2013-02-13T19:30:01Z</updated>
    <published>2013-02-13T19:30:01Z</published>
    <summary type="html">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</summary>
    <dc:creator>John Yontz</dc:creator>
    <dc:date>2013-02-13T19:30:01Z</dc:date>
  </entry>
  <entry>
    <title>minScreensDefinitionType/minScreens for Schedule Meeting</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11895348" />
    <author>
      <name>Michael Nelson</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11895348</id>
    <updated>2013-02-13T16:10:42Z</updated>
    <published>2013-02-13T16:10:42Z</published>
    <summary type="html">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.</summary>
    <dc:creator>Michael Nelson</dc:creator>
    <dc:date>2013-02-13T16:10:42Z</dc:date>
  </entry>
  <entry>
    <title>RE: newAdditionalCapacity in AMM modifyActiveMeeting</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11757069" />
    <author>
      <name>John Yontz</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11757069</id>
    <updated>2013-02-09T01:22:18Z</updated>
    <published>2013-02-09T01:22:18Z</published>
    <summary type="html">The new value of additional capacity in the modify active meeting request will replace the prior value.  It is not an incremental value.
- John</summary>
    <dc:creator>John Yontz</dc:creator>
    <dc:date>2013-02-09T01:22:18Z</dc:date>
  </entry>
  <entry>
    <title>RE: numberOfScreens Parameter in scheduleRendezvousMeeting</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11757055" />
    <author>
      <name>John Yontz</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11757055</id>
    <updated>2013-02-09T01:19:00Z</updated>
    <published>2013-02-09T01:19:00Z</published>
    <summary type="html">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</summary>
    <dc:creator>John Yontz</dc:creator>
    <dc:date>2013-02-09T01:19:00Z</dc:date>
  </entry>
  <entry>
    <title>newAdditionalCapacity in AMM modifyActiveMeeting</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11756232" />
    <author>
      <name>Michael Nelson</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11756232</id>
    <updated>2013-02-08T23:25:45Z</updated>
    <published>2013-02-08T23:25:45Z</published>
    <summary type="html">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?</summary>
    <dc:creator>Michael Nelson</dc:creator>
    <dc:date>2013-02-08T23:25:45Z</dc:date>
  </entry>
  <entry>
    <title>numberOfScreens Parameter in scheduleRendezvousMeeting</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11756069" />
    <author>
      <name>Michael Nelson</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=11756069</id>
    <updated>2013-02-08T23:13:38Z</updated>
    <published>2013-02-08T23:13:38Z</published>
    <summary type="html">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?</summary>
    <dc:creator>Michael Nelson</dc:creator>
    <dc:date>2013-02-08T23:13:38Z</dc:date>
  </entry>
  <entry>
    <title>RE: What is the Maximum Number of Entries for getEndpointsForOrganization</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=10632644" />
    <author>
      <name>John Yontz</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=10632644</id>
    <updated>2013-01-15T01:36:48Z</updated>
    <published>2013-01-15T01:36:48Z</published>
    <summary type="html">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</summary>
    <dc:creator>John Yontz</dc:creator>
    <dc:date>2013-01-15T01:36:48Z</dc:date>
  </entry>
  <entry>
    <title>RE: What is the Maximum Number of Entries for getEndpointsForOrganization</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=10640079" />
    <author>
      <name>Michael Nelson</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=10640079</id>
    <updated>2013-01-15T01:26:49Z</updated>
    <published>2013-01-15T01:26:49Z</published>
    <summary type="html">Is this new with CTX 1.1 or was this the case with CTX 1.0.3 as well?</summary>
    <dc:creator>Michael Nelson</dc:creator>
    <dc:date>2013-01-15T01:26:49Z</dc:date>
  </entry>
  <entry>
    <title>RE: What is the Maximum Number of Entries for getEndpointsForOrganization</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=10632345" />
    <author>
      <name>John Yontz</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=10632345</id>
    <updated>2013-01-15T01:15:46Z</updated>
    <published>2013-01-15T01:15:46Z</published>
    <summary type="html">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</summary>
    <dc:creator>John Yontz</dc:creator>
    <dc:date>2013-01-15T01:15:46Z</dc:date>
  </entry>
  <entry>
    <title>What is the Maximum Number of Entries for getEndpointsForOrganization</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=10627441" />
    <author>
      <name>Michael Nelson</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=10627441</id>
    <updated>2013-01-15T00:07:42Z</updated>
    <published>2013-01-15T00:07:42Z</published>
    <summary type="html">What is the maximum number of entries that are returned in the response for the getEndpointsForOrganization request when neither the startIndex and numberToReturn are not specified?</summary>
    <dc:creator>Michael Nelson</dc:creator>
    <dc:date>2013-01-15T00:07:42Z</dc:date>
  </entry>
  <entry>
    <title>RE: maximumNumberOfEndpoints in Rendezvous Meeting</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5938646" />
    <author>
      <name>John Yontz</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5938646</id>
    <updated>2012-06-28T00:01:05Z</updated>
    <published>2012-06-28T00:01:05Z</published>
    <summary type="html">Hi Mike,

Good question, and you are not the first to ask this.

The maximumNumberOfEndpoints is used to specify the size the rendezvous meeting.  It is possible, as you say, to simply set this to 0 and specify the size entirely using the additionalCapacity (although we try to discourage usage of additionalCapacity if possible).  The allowedHostEndpoints do not contribute to the size calculation.  They only indicate which provisioned endpoints will be recognized as the host.  In fact, for this reason, you may even have a number of allowed host endpoints greater than the total size of the rendezvous meeting.

- John</summary>
    <dc:creator>John Yontz</dc:creator>
    <dc:date>2012-06-28T00:01:05Z</dc:date>
  </entry>
  <entry>
    <title>RE: CTX1.0 Schedule Meeting Result capacityAllocated equivalent in CTX 1.1</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5813942" />
    <author>
      <name>John Yontz</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5813942</id>
    <updated>2012-06-04T19:48:08Z</updated>
    <published>2012-06-04T19:48:08Z</published>
    <summary type="html">Yes, Mike, you are exactly correct.  What was returned in the ScheduleMeetingResult as "capacityAllocated" in 1.0 is now shown as "requiredCapacity" in the 1.1 apiMeetingElement.</summary>
    <dc:creator>John Yontz</dc:creator>
    <dc:date>2012-06-04T19:48:08Z</dc:date>
  </entry>
  <entry>
    <title>RE: Bridge Capabilities</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=3150447" />
    <author>
      <name>Andrew Brindamour</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=3150447</id>
    <updated>2011-03-08T20:38:59Z</updated>
    <published>2011-03-08T20:32:30Z</published>
    <summary type="html">Bridge capabilities help the system determine what kind of bridging resource is best suited to host your meeting. If the wrong kind of bridging resource is chosen, some kinds of endpoint will not be able to attend your meeting, or you may wind up wasting a valuable, expensive resource hosting a meeting that would be just fine with a cheaper resource.

However, the system does have some intelligence to determine the correct bridging resource without any bridge capabilities being specified. So, strictly speaking, they can be left empty. However, this kind of inference only works with provisioned endpoints, so if you have either unprovisioned or remote endpoints in the meeting, you probably want to explicitly set bridge capabilities.

To summarize, it is OK to omit bridge capabilities:
- When your meeting contains only provisioned endpoints and you trust the inference algorithm
 
You should probably NOT omit bridge capabilities:
- If any of the endpoints in your meeting are unprovisioned or remote endpoints.
- If you need to override the inference algorithm, for instance you want a more expensive bridge for some reason even if the supplied endpoints would work with a cheaper bridge.
 
You CANNOT omit bridge capabilities:
- If your meeting contains no provisioned endpoints, as there is nothing to infer.</summary>
    <dc:creator>Andrew Brindamour</dc:creator>
    <dc:date>2011-03-08T20:32:30Z</dc:date>
  </entry>
  <entry>
    <title>RE: Custom Layout</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=3144838" />
    <author>
      <name>Kulai Bhandary</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=3144838</id>
    <updated>2011-03-08T00:12:38Z</updated>
    <published>2011-03-08T00:12:38Z</published>
    <summary type="html">The custom layouts are not supported for CTMS. They apply to meetings scheduled on an 8510 bridge. The 8510 bridge supports only single screen endpoints (Tandberg as well as single screen endpoints from other vendors like Polycom). Please refer to the section Conference Layouts on page 78 of the attached document for more information on the layout IDs:

http://www.cisco.com/en/US/docs/telepresence/infrastructure/mcu/api_guide/MCU_API.pdf</summary>
    <dc:creator>Kulai Bhandary</dc:creator>
    <dc:date>2011-03-08T00:12:38Z</dc:date>
  </entry>
</feed>

