LocalOwnerPresence class

Lync 2013

LocalOwnerPresence allows the publication and subscription to presence categories and management of access control lists. It also provides access to a list of subscribers and delegates.


Namespace:  Microsoft.Rtc.Collaboration.Presence
Assembly:  Microsoft.Rtc.Collaboration (in Microsoft.Rtc.Collaboration.dll)

public class LocalOwnerPresence : PublishSubscribeSession

This is the main class for managing the presence of the endpoint owner. Here, the application can publish presence categories, subscribe to presence notifications, and assign and manage access control lists. Both UserEndpoint and ApplicationEndpoint instances can publish presence, although they do so in different ways. An ApplicationEndpoint cannot use the grammar-based method in which container IDs and instance values are automatically generated. Instead, this endpoint type must explicitly specify these values. Presence categories are well defined types recognized by the server such as state, note, device, contact card etc.

Container management enables an application to add specific URIs, domain names, and network flags to containers, as well as to remove them from containers. These operations permit an application to control subscriber access to presence categories published in these containers. The network flags consist of sameEnterprise, publicCloud, and federated.

Calling BeginSubscribe on a LocalOwnerPresence instance enables an endpoint to receive notifications about changes made to presence categories, container memberships, and subscriber and delegate lists. This is especially useful in an multiple points of presence (MPOP) scenario to keep all endpoints of a unified communications entity synchronized.

Bootstrapping is another process unique to UserEndpoints. Here, the newly created containers can be initialized with default container memberships and publications decided by the Microsoft Lync Server administrator.

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.