Share via

Trusted Conference Participant (QuickStart)

  • Article

Sample name: TrustedConferenceParticipant

Sample location: %ProgramFiles%\Microsoft UCMA 3.0\SDK\Core\Sample Applications\QuickStarts\TrustedConferenceParticipant

Description

The application establishes an application endpoint and impersonates a user who creates and joins an ad hoc conference. The application endpoint then joins the conference as a trusted participant. The trusted participant then monitors the roster of the MCU for the conference. When a new participant is detected, a new audio-video call is created. This audio-video call is then configured to route DTMF from the new participant to the application and audio from the application to the participant. The application can also send an invitation to a specified user to show how the impersonated and trusted joins are surfaced. For more information about provisioning trusted applications and endpoints in Microsoft Lync Server 2010, see Activating a UCMA 3.0 Core Trusted Application as well as General Application Activation and Activating a Manually-Provisioned Application.

Features

  • Ad hoc conference creation

  • Conversation impersonation

  • Joining a conference as a trusted participant (the trusted participant’s endpoint will not be visible in the roster)

  • Configuration of audio-video call routes

Prerequisites

  • Microsoft Lync Server 2010.

  • Provisioned trusted ApplicationEndpoint

  • A currently-logged-in client on Lync Server 2010.

Running the Sample

  1. Supply the configuration settings to be used by the sample in the accompanying App.config file, you will be prompted for them when you run the sample.

  2. Open the project in Microsoft Visual Studio, and then press F5.

  3. When the conference is established the sample will prompt for URIs to send invitations to the conference. (Pressing ENTER when prompted will skip this step.) This URI should be for a user who is currently signed into Microsoft Lync 2010. This user can join the conference to observe how other participants are presented and see that the entered DTMF or the response audio is not heard by the other participants of the conference.