Share via

2.2.2.4 Extensions to conf-uris Element Semantics

  • Article

Implementations conforming to this protocol MUST generate and consume the conf-uris element based on the following extension semantics, in addition to those defined in [RFC4575] section 5.3.1:

  • An entry element MUST be listed for each MCU in the conference.

  • An entry element MUST be listed for each alternative conference join URLs.

  • This specification specifies the following for the purpose subelement:

    • audio-video: An Audio-Video MCU.

    • chat: An Instant Messaging MCU.

    • meeting: A legacy Web Conferencing/Application Sharing MCU.

    • data-conf: A Web Conferencing MCU implementing the protocols specified in [MS-PSOM]<15>.

    • phone-conf: A Phone Conferencing MCU.

    • applicationsharing: An Application Sharing MCU<16>.

    • web-internal: A URL to join the conference via a web browser interface from inside the enterprise<17>.

    • web-external: A URL to join the conference via a web browser interface from outside the enterprise<18>.

  • The uri subelement lists a SIP URI corresponding to an audio-video, chat, meeting, data-conf, phone-conf, applicationsharing purpose element.

  • The encrypted-uri subelement lists the encrypted URL corresponding to the web-internal or web-external purpose element<19>.

Extensions to this document can specify one or more signaling protocols to enable clients to join and access these MCUs.