The endpoint type conveys the nature of the local or remote endpoint. EndpointType can only be set on a local endpoint and read on a remote endpoint. An application is responsible for setting the type of the LocalEndpoint to indicate to remote endpoints of the network how they should communicate with the local endpoint. On one hand, an endpoint type "user" indicates that the owner of the endpoint is conceptually a human being. Unlike most Applications, a User can participate in a multimodal communication with a given remote participant by using several endpoints at the same time: a desktop for video, a phone for audio, and a laptop for Application Sharing. Advertising that an endpoint is of type "User" will trigger a remote endpoint communicating with it to target the User Uri (Owner Uri) rather than the endpoint Uri when adding a modality. On the other hand, an endpoint type "application" indicates that the owner of the endpoint is an Application as opposed to a human being. Applications differ from one to the other in the way other endpoints should communicate with them. Hence the need to further refine the Application type by appending a sub-type. The sub-type indicates if the application is a voicemail or an auto-attendant for example. The endpoint sub-type can be set or read by using the endpoint sub-type property. Other endpoint types include "Gateway" to indicate a Central Office or Private Branch Exchange trunk or "Conference" to indicate a conferencing component such as a media control unit or the Centralized Conferencing Control Protocol (C3P) focus. Note that this value is represented at the protocol level as a Contact header feature tag based on the RFC 3840.