Microsoft Unified Communications Managed API (UCMA) 3.0 introduces new automatic presence publications for UCMA 3.0 endpoints during endpoint establishment. This applies to the ApplicationEndpoint and UserEndpoint types.
Automata and automated service applications that persist their presence information (such as by publishing “always online”) can use new and simplified APIs to publish this information one time during endpoint startup. Similarly, user endpoints can have their presence information enabled at startup and can use the simplified APIs to maintain their presence information for the life of the endpoint. This functionality can be achieved by setting a single property.
Using UCMA 3.0, it is also easy to modify or delete an existing presence publication. UCMA 3.0 can be used to delete or modify all publications that are made to different relationship levels to address different types of watchers.
For more information, see Presence, Contacts, and Groups.
For applications whose publishing needs are more complex, UCMA 3.0 provides new classes for common presence categories, including the ContactCard, PresenceState, Note, and Services classes. The developer is not expected to know the XML schema for the common presence categories. However, XML can be used in advanced scenarios that involve publishing advanced categories (such as the routing category, which is used to specify routing rules for forwarding incoming calls), or publishing a custom category. For more information about registering a custom category name with Microsoft Lync Server 2010, see “Registering Custom Category Names” in Unified Communications Enhanced Presence Schema Reference (2010 Release).