Remotely accessible category instances
Applies to: Lync 2013 | Lync Server 2013
The following category instances are published for remote users to subscribe to.
Category name |
Container Id |
Description |
|---|---|---|
100, 200, 300, 400, 32000 |
The calendarData category instances in Container 100, 200, 300, and 400 contain the local user’s working hours and/or free-busy information that is intended to be shared with the specified container members through remote subscriptions. Those in Container 32000 are used to block the specified container members from accessing the local user’s calendar data. |
|
0, 100, 200, 300, 400, 32000 |
The contactCard category instances contain various contact information about the local user. They are intended for share with members of the hosting containers other than the Blocked container. The contactCard category instances placed in Container 32000 (Blocked container) are used to block any members of that container from accessing the local user’s contact information. |
|
100, 200, 300, 400, 32000 |
The legacyInterop category instances are created and published by Microsoft Lync Server 2013 to provide some backward compatibility for clients that do not support the enhanced presence data model. A legacyInterop category instance contains an availability number, the value of which corresponds to the availability number of the state[@type='aggregateState'] element category instance in the same container. |
|
100, 200, 300, 400, 32000 |
The note category instance in each container prescribes the presence note to be shared with or blocked to the members of the hosting container. |
|
100, 200, 300, 400, 32000 |
A noteHistory category instance is just a note category instance value element category instance with a registered category name of noteHistory. Such category instances are used to enumerate the most recently published note category instances and will appear in the presence feed of the container members who have subscribed to the note category instance value element category instances of the local user. By default the last three note category instances are published to Container 200, 300, and 400 and no such category instances are published to Container 100 and 3200. |
|
100, 200, 300, 400, 32000 |
The state category instances in these containers are of the aggregateState type. They are produced by the aggregation script. |
|
100, 200, 300, 400, 32000 |
The services category instances are produced by the aggregation script and represent the device-independent user-bound presence capabilities of the local user. |