LocalEndpoint Class

Represents an endpoint used by the current application to communicate and collaborate with other endpoints.

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

public abstract class LocalEndpoint

Conceptually, one can think of LocalEndpoint as a "device" to communicate or collaborate with other endpoints of the network. Similar to the way a phone is owned by someone and used for making voice calls, a LocalEndpoint is owned by a User or an Application and used for collaborating and communicating with other users and applications. The LocalEndpoint and its owner each have a dedicated address or Universal Resource Identifier (URI). It is thus possible to communicate with a specific endpoint or with its owner (through one of its endpoints) depending on the URI that is requested by the initiator of communication. A LocalEndpoint can be used to manage the owner's Contacts and Groups, its Presence data, and to subscribe to the Presence of other applications and users. It can also be used to schedule, update and cancel conferences or participate in communications that can be multi-modal and multi-party. The state of the LocalEndpoint indicates whether the endpoint can receive incoming traffic or not. A LocalEndpoint may register against a server if it represents a user or it represents a service which publishes endpoint bound presence. When the registration fails, an application can retry to establish the endpoint. When the automatic registration refresh fails, the LocalEndpoint will try to re-establish the endpoint and indicate when the re-registration is successful through a State transition.

LocalEndpoint has two concrete implementations: UserEndpoint and ApplicationEndpoint.

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