![microsoft lync conference call microsoft lync conference call](https://s1.mzstatic.com/us/r30/Purple/v4/c7/74/33/c77433ad-80d0-be55-6eaa-518ec93fc9b5/mzl.qtnlrkud.png)
Register for participant events on the remote participant.Īs the previous figure illustrates, the procedure to send an IM message involve many more steps than those you execute to receive and render an instant message from a remote participant. Register for InstantMessageReceived message received events to catch incoming instant messages from other participants. The IM modality is ready to use when you obtain it from the conversation's modalities collection.Ĭast the Modality class instance to the InstantMessageModality class to obtain instant messaging receive features.
![microsoft lync conference call microsoft lync conference call](https://i.stack.imgur.com/kP2z1.png)
You do not need to call Connect on this modality. The IM modality is auto-accepted at both the local and remote endpoints. Get the remote participant InstantMessageModality from Participant by reading the Modalities property collection and returning the InstantMessageModality. The following steps should not be executed for the self-participant. Read the IsSelf property of the added participant exposed by Participant property.
![microsoft lync conference call microsoft lync conference call](http://i.ytimg.com/vi/lzMn__he8vM/maxresdefault.jpg)
Get the IM Modality instance from the Modalities property of the Conversation instance in the data parameter of the ConversationAdded event handler: .Ĭomplete the following steps within a callback method that handles ParticipantAdded. If you can add a participant, get a Contact instance to add to the conversation by calling into GetContactByUri.Ī contact that resolves to the passed URI is returned. Continue the steps if a true value is returned.
![microsoft lync conference call microsoft lync conference call](http://kb.plexhosted.com/260/1.png)
Register for conversation state change events on the Conversation instance.Ĭall the CanInvoke method and pass ConversationAction. The ConversationAdded event is raised when either a local user starts a conversation or a remote user invites the local user to a new conversation. For this procedure, handle the event for only the conversation added by the local user. Notified, the conversation was not started by the local user. To handle the ConversationAdded eventĬheck the modality state of the IM modality on the added conversation. Handle the ConversationAdded eventĬomplete the following steps within a callback method that handles ConversationAdded. Examples of the event handler methods are included later in this topic. The next two procedures are examples of the steps to create event handlers for conversation-related events. If you have a conference URL and intend to join the associated conference, call JoinConference instead of AddConversation. Register for the ConversationAdded event. Get the ConversationManager class instance by reading the ConversationManager property. Get the LyncClient instance and verify that the client is signed in to the server.įor information about signing in to Microsoft Lync Server 2013, see How to: Sign a user in to Lync. To start an IM conversationĬreate a callback method that handles the ConversationAdded event.Ĭreate a callback method that handles the ParticipantAdded event. The following procedure obtains a conversations manager and adds the conversation. The following diagram shows you how the objects interact. Read about How to: Sign a user in to Lync and be sure that your application logic provides this capability before adding an IM feature to your UI.Ī Lync 2013 IM conversation is represented by three API objects:Įach of these objects exposes properties, methods, and events that play a role in programmatic interaction with the conversation. The following topics describe the three components of a Lync 2013 conversation.ĭescribes the role of the conversation manager in creating conversations.ĭescribes how conversation modes are encapsulated by modalities.ĭescribes how conversation participants are encapsulated.Ĭonversations can only be started when the user is signed in to Lync 2013. Microsoft Lync 2013 SDK must be installed on the development computer. You must have sign-in credentials for Microsoft Lync Server 2013. Microsoft Lync 2013 must be installed and running on the development computer. The prerequisites for starting an IM conversation are as follows: