<?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>numberOfScreens Parameter in scheduleRendezvousMeeting</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&amp;threadId=11756070" />
  <subtitle>numberOfScreens Parameter in scheduleRendezvousMeeting</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&amp;threadId=11756070</id>
  <updated>2013-05-26T03:45:21Z</updated>
  <dc:date>2013-05-26T03:45:21Z</dc:date>
  <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>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>
</feed>

