Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.1 New Initial version 4/25/2008 0.2 Minor Revised and edited the technical content 6/27/2008 1.0 Major Revised and edited the technical content 8/15/2008 1.01 Minor Revised and edited the technical content 12/12/2008 2.0 Major Revised and edited the technical content 2/13/2009 2.01 Minor Revised and edited the technical content 3/13/2009 2.02 Minor Revised and edited the technical content 7/13/2009 2.03 Revised and edited the technical content 8/28/2009 2.04 Editorial Revised and edited the technical content 11/6/2009 2.05 Editorial Revised and edited the technical content 2/19/2010 2.06 Editorial Revised and edited the technical content 3/31/2010 2.07 Major Updated and revised the technical content
4/30/2010 2.08 Editorial Revised and edited the technical content 6/7/2010 2.09 Editorial Revised and edited the technical content 6/29/2010 2.10 Editorial Changed language and formatting in the technical content. 7/23/2010 2.10 None No changes to the meaning, language, or formatting of the technical content. 9/27/2010 3.0 Significantly changed the technical content. 11/15/2010 3.0 None No changes to the meaning, language, or formatting of the technical content. 12/17/2010 3.0 None No changes to the meaning, language, or formatting of the technical content. 3/18/2011 3.0 None No changes to the meaning, language, or formatting of the
technical content. 6/10/2011 3.0 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 4.0 Major Significantly changed the technical content. 4/11/2012 4.0 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 4.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 5.0 Major Significantly changed the technical content. 2/11/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 5.0 None No changes to the meaning, language, or formatting of the
technical content. 11/18/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 5.0 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 5.1 Minor Clarified the meaning of the technical content. 7/31/2014 5.1.1 Editorial Changed language and formatting in the technical content. 10/30/2014 5.2 Minor Clarified the meaning of the technical content. 3/30/2015 6.0 Major Significantly changed the technical content. 9/4/2015 6.0 None No changes to the meaning, language, or formatting of the technical content. 7/15/2016 6.0 None No changes to the meaning,
Informative References [MS-LCID] Microsoft Corporation, "". [MS-SIPREGE] Microsoft Corporation, "". Overview intending to invite into a first create the conference at a . The Focus Factory provides a that is subsequently used to join the conference through the . This protocol specifies the mechanism by which a protocol client application interacts with the Focus Factory to create a new conference and additionally performs the following actions within the context of a specific organizer: Query for a list of created conferences that have not expired. Query for the details of a created conference. Modify the details of an existing conference. Delete an existing conference. Perform ancillary operations necessary to create a conference. The distribution of the conference-URI to a participant is outside the scope of this protocol. Relationship to Other Protocols The conferencing architecture described in section 1.3.1 depends on this protocol for provisioning conferences. The and its corresponding are used for transmitting . The message syntax for the content of the SIP messages is described in . Prerequisites/Preconditions To send messages to the Focus Factory using , protocol client applications first obtain the Focus Factory . This URI can be obtained by using the mechanism described in section 2.2.2 and section 3.3. This protocol assumes that SIP requests are authenticated as described in . Applicability Statement This protocol is meant to be used in conjunction with the conferencing architecture described in section 1.3.1. Versioning and Capability Negotiation This protocol covers versioning issues in the following areas: Supported Transports: This protocol can be implemented using SIP on top of , and , as discussed in section . Capability Negotiation: This protocol supports capability negotiation through the getConferencingCapabilities request specified in section . A protocol client application can also determine that it is interfacing with a Focus Factory that supports its version by issuing a test request to create a conference, as specified in section .
Obtain a list of MCU-types 50 Obtain an encryption key 49 Obtain focus factory capabilities 50 Other local events client 37 37 37 40 9 P 56 9 9 57 Q Query for a list of conferences 46 for the details of a conference 48 R 8 9 8 9 19 19 20 21 21 21 22 21 20 22 22 25 27 25 26 28 26 24 S Security 56 56 Sequencing rules client 35 36 35 35 36 36 35 34 34 35 38 38 39 40 39 39 40 40 39 38 10 T Timer events 36 focus factory 40 Timers 32 37 60 11 Triggered events client 32 delete a conference ( 33, 34) 32 34 34 33 33 Triggered events - higher-layer 38 U 16 V 10 10