Managing self-published contact lists
Applies to: Lync 2013 | Lync Server 2013
Microsoft Lync 2013 uses the enhanced presence publication and subscription mechanism to store the user’s contact list on the server and to roam the contact list across multiple user endpoints.
In Lync 2013, a contact list is described by a collection of the contacts and groups category instances. When the user adds another user to his or her contact list, Lync 2013 publishes a contacts category instance to the user’s self-container. When a new group is created for organizing the entries in the contact list, a groups category instance is published to the container, as well. Each time when Lync 2013 starts, it retrieves the contact list from the server by subscribing to the already published contacts and groups category instances.
At the protocol level, receiving a contact list involves submitting a SUBSCRIBE request. The returned contact list does not contain any presence information of the contacts. To receive the contacts presence publications, a separate subscription must be created and maintained.
At the API level, the SIP messages are encapsulated by the API types and the associated operations are exposed as methods of the API types. This section discusses how to use Microsoft Unified Communications Managed API 4.0 to manage a contact list.
In this section
See also
Concepts
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for