2.2.3.4 addUser Response Document Format for Focus INVITE Responses

  • Article

In addition to the syntax rules given in section 2.2.1 for C3P responses, the following additional rules apply.

conferenceKeys: This element MUST have the same values as those specified in the corresponding addUser request.

The following rules apply to the user element:

  • Exactly one user element MUST be present inside the addUser body.

  • The entity attribute of the user element MUST be the same as the entity attribute specified in the request.

  • The roles element MUST be present and listed exactly once.

  • The endpoint element SHOULD<23> contain a session-on-behalf-of element if it was present in the request. If the user is not joining the conference, the endpoint element SHOULD NOT be present in the response.

The following rules apply to the roles element:

  • The roles element MUST be present and listed exactly once.

  • The entry element MUST be populated with the granted role and exactly one entry element SHOULD be present. This might be different from the requested role in some cases because of policy.

The following example is an addUser document. Note that the conference ID is shown with four characters for readability, although it is a string with 8 to 32 alphanumeric characters, as defined in [MS-CONFPRO].

 <addUser>
   <conferenceKeys
     confEntity="sip:user@fabrikam.com;gruu;opaque=app:conf:focus:id:BE92"/>
   <user entity="sip:user@fabrikam.com">
     <roles>
       <entry>attendee</entry>
     </roles>
       <clientInfo   
          xmlns="http://schemas.microsoft.com/rtc/2005/08/confinfoextensions" >
         <separator xmlns="urn:ietf:params:xml:ns:conference-info-separator" />
         <lobby-capable
              xmlns="http://schemas.microsoft.com/rtc/2008/12/confinfoextensions">
                true
         </lobby-capable>
       </clientInfo>
       <separator xmlns="urn:ietf:params:xml:ns:conference-info-separator"/>
       <session-on-behalf-of>
         <entity>sip:carol@fabrikam.com</entity>
       </session-on-behalf-of>    </endpoint>
   </user>
 </addUser>