Joining a Conference
A conversation can be created initially as a conference, or an existing two-party conversation can be escalated to a conference. In both scenarios, the application must join the conference before inviting new participants. An application can access the conference session from the conversation by means of the conversation’s ConferenceSession property.
The following code demonstrates creating a conference session and then joining the conference.
ConferenceSession conferenceSession = conversation.ConferenceSession; ConferenceJoinOptions cjo = new ConferenceJoinOptions(); cjo.JoinAsTrustedApplication = false; conferenceSession.BeginJoin(cjo, Conference_JoinCompleted, conferenceSession);
The BeginJoin() method also has an overload that can be used to join a scheduled conference.
An application cannot use the impersonation API without possessing trust from the server, as provisioned as a GRUU in Active Directory. Once impersonated, an application can join any conference as if it were that user.
New classes and methods added in UCMA 3.0 enable an application to join a conference as a trusted user or as an ordinary user.
To join a conference as a trusted user, an application should set the JoinMode property on a ConferenceJoinOptions instance to TrustedParticipant, a value of the JoinMode enumeration. The conversation must belong to an ApplicationEndpoint instance that is provisioned with a trusted service GRUU.
To join a conference as an ordinary user, an application should set the JoinMode property to Default, another value in the JoinMode enumeration. The application might be placed in the lobby, depending on the current conference access level. An application can also specify the maximum amount of time it is willing to wait for in the lobby using the LobbyTimeout property on a ConferenceJoinOptions instance. The default timeout value is 15 minutes.