Share via

2.2.1.2 conference-description Element

  • Article

The conference-description element specifies some basic properties for the conference using the following child elements. For details about the conference-description Extensions see [MS-CONFBAS] section 2.2.2.3.

display-text: This element is used to specify a description for the conference.

subject: This element is used to specify a subject of the conference.

conference-id: Every conference MUST be identifiable by a string that is unique among all conferences belonging to an organizer. Constraints on the length and value space of this string are implementation-specific. Implementations SHOULD allow for a minimum of 8 and a maximum of 32 alpha-numeric characters from the ASCII set.

conference-key: This element is deprecated.

last-update: This element specifies the Coordinated Universal Time (UTC) date and time when the conference was created or last modified. The format of this value is defined by the XML Schema dateTime data type. The dateTime data type is defined in the internet standard XML specifications [XML10] and its related specifications. This element is not required for request, but MUST be specified in responses.

last-activate: This element specifies the UTC date and time when the conference was last activated in the Focus Factory. The format of this value is defined by the XML Schema dateTime data type. This element appears only in responses. The dateTime data type is defined in the internet standard XML specifications [XML10] and its related specifications.

is-active: This element indicates whether the conference is active in the Focus Factory at the time this value is set. The format of this value is defined by the XML schema Boolean data type where the value can be either true or false. This element appears only in responses. If "true," the conference is active, if "false," the conference is not active.

expiry-time: This element indicates the UTC time after which the conference can be deleted by the Focus Factory. An implementation SHOULD enforce a constraint on how long a conference is available, but the exact value of that upper bound is specific to the implementation. The format of this value is defined by the XML schema dateTime data type. When not specified, the default value is specific to the implementation. The dateTime data type is defined in the internet standard XML specifications [XML10] and its related specifications.

admission-policy: This element specifies the types of participants that are allowed to join this conference and MUST contain one of the following values:

  • "closedAuthenticated": All participants MUST be on the pre-set roster that is provided at conference-creation time. See section 2.2.1.4 for more details on how to specify the preset roster.

  • "openAuthenticated": All participants MUST have an enterprise identity that is verified by the local enterprise or federated users.

  • "anonymous": All participants with a verified enterprise identity or any user with a valid anonymous passcode are permitted into the conference.

organizer-roaming-data: This element MUST contain well-formed XML. The root element of this XML MUST NOT belong to the namespace of the containing organizer-roaming-data element. This XML is meant for protocol client applications to store arbitrary contextual data for the conference with the Focus Factory. The server doesn’t run any business logic based on this data. It is purely used by the organizer to store and roam data. An implementation SHOULD enforce constraints on the size of this XML. Limits are defined by the implementation, but SHOULD allow at least 4,096 bytes (4 kilobytes).

notification-data: This element MUST contain well-formed XML. The root element of this XML MUST NOT belong to the namespace of the containing notification-data element. This XML is meant for protocol client applications to store arbitrary contextual data for the conference with the Focus Factory so that this data can later be provided to any participant joining the conference. The server doesn’t run any business logic based on this data. It is purely used by the organizer to store and roam data to other participants in the meeting.  An implementation SHOULD enforce constraints on the size of this XML. Limits are defined by the implementation, but SHOULD allow at least 4,096 bytes (4 kilobytes).

lobby-capable: This element is specified in [MS-CONFBAS] section 2.2.2.3.

anonymous-type-allowed: This element is specified in [MS-CONFBAS] section 2.2.2.3.

join-url: This element specifies the HTTP join URL for joining the meeting.

pstn-access: This element is specified in [MS-CONFBAS] section 2.2.2.3.

autopromote: This element is an unsigned integer. The server interprets this value to indicate who needs to be promoted to presenters upon being admitted to the conference. People in the lobby, once moved into the meeting, also follow these rules. The currently defined bits are<2>:

  • None: 0x00000000 (the default)

  • Everyone: 0x80000000 (bit 31)

  • Company (Authenticated users): 0x00008000 (bit 15)

autopromote-allowed: This element is specified in [MS-CONFBAS] section 2.2.2.3.

pstn-lobby-bypass: This element is a Boolean value. If "true," all the users, including external users, joining over the phone can join the conference without going to the lobby. If "false," they go to the lobby and wait for the organizer or presenter to bring them into the meeting<3>. The term "external user" is defined in [MS-SIPRE].

pstn-lobby-bypass-allowed: This element is specified in [MS-CONFBAS] section 2.2.2.3.

recording-allowed: This element is specified in [MS-CONFBAS] section 2.2.2.3.

externaluser-recording-allowed: This element is specified in [MS-CONFBAS] section 2.2.2.3.

server-mode: This element is deprecated. Irrespective of value specified the conference behavior  would default to what was previously known as server mode 14. This is further defined in [MS-CONFBAS] section 2.2.2.3.

  • The created conference supports the lobby experience. Lobby-aware meeting participants placed in an "on-hold" state will wait to be admitted. More details on lobby and the "on-hold" state are specified in [MS-CONFBAS].

  • Application sharing is allowed only by users with the "presenter" role.

  • Federated users are treated as anonymous users when applying admission-policy.

  • All users except for the conference organizer, are placed in an on-hold state if they join while the conference is locked.

recording-notification: This element is specified in [MS-CONFBAS] section 2.2.2.3.

custom-invite: This element is specified in [MS-CONFBAS] section 2.2.2.3.

anonymous-dialout-allowed: This element is specified in [MS-CONFBAS] section 2.2.2.3.

endorse-allowed: This element is specified in [MS-CONFBAS] section 2.2.2.3.

main-video-mute-allowed: This element is specified in [MS-CONFBAS] section 2.2.2.3.

pano-video-mute-allowed: This element is specified in [MS-CONFBAS] section 2.2.2.3.