Publication behaviors of category instances

Applies to: Lync 2013 | Lync Server 2013

The following table summarizes the default publication behaviors of category instances that are used in Microsoft Lync 2013. For more information, including the aggregation logic, see [MS-PRES]: Presence Protocol Specification.

Category instances published or used by Lync 2013

Category	Instance ID	Description
alerts category instance value element	0	Published to Container 1 as static instance when one or more Alerts options are updated.
calendarData category instance value element	0	Published to Containers 1, 200, 300, or 400 as a static instance that contains the user’s working-hours information when the information is updated in Microsoft Exchange. Published to Container 100 or 32000 as a static instance that contains an empty value when the workingHours information is updated in Microsoft Exchange. Note The workingHours information is used by the aggregation script.
	A hash dependent on the user’s SMTP address.	Published to Containers 200, 300, or 400 as a time-bounded instance that contains the local user’s freeBusy information when the information is updated in Microsoft Exchange. Published to Container 1, 100, or 32000 as a time-bounded instance containing an empty value when the user signs in or when the user’s freeBusy information is updated in Microsoft Exchange.
contactCard category instance value element	0	Published to Container 0, 100, 200, 300, and 400 as static instances containing the user’s identity information consisting of the display name and email address. Published to Container 32000 as a static instance containing an empty value.
	1	Published to Container 400 as a static instance containing the user’s home, cell, and other phone numbers if any is specified. Published to Container 300 as a static instance containing the user’s cell phone number if it's specified. Published to Container 100, 200, and 32000 as static instances, each containing an empty value.
	3	Published to Container 100 as a static instance containing the user’s job title and company name. Published to Container 200, 300, and 400 as a static instance containing the user’s job title, company name, office location, and work phone number. Published to Container 32000 as a static instance containing an empty value.
	4	Published to Container 100, 200, 300, and 400 as a static instance containing the user’s voice mail URL. Published to Container 32000 as a static instance containing an empty value.
	6	Published to Container 100 as a static instance containing the user’s job title and photo display information. Published to Container 200, 300, and 400 as a static instance containing the user’s job title, office location, and photo display information. Published to Container 32000 as a static instance containing an empty value.
device category instance value element	A hash dependent on the device GRUU.	Published to Container 2 as an endpoint-bounded instance when the user signs in to Microsoft Lync Server 2013 or when the device changes its state from active to idle or from idle to active. These include user sign-in or sign-out, screen lock, or unlock.
dndState category instance value element	0	Published to Containers 0, 2, 100, 200, and 400 as static instance containing the availability number of 9500 to enable blocking in-bound calls when the user’s availability mode is Do Not Disturb. Published to Containers 3 and 300 as static instance containing an empty value to disable blocking in-bound calls when the user’s availability mode is Do Not Disturb. Published to Containers 0, 2, 3, 100, 200, 300, and 400 as static instance containing an empty value to disable blocking in-bound calls when the user’s availability mode is not Do Not Disturb.
legacyInterop category instance value element	1	Published to container 100, 200, 300, and 400 as a user-bounded instance containing the availability numbers of the corresponding state[@type='aggregateState'] element instances in their respective containers.
note category instance value element	0	Published to Container 100 and 32000 as a static instance containing an empty value when the user sets a personal note by using Lync 2013. Published to Container 200, 300, and 400 as a static instance containing a user-specified text message when the user sets a personal note by using Lync 2013.
	A hash dependent on the user’s SMTP address.	Published to Container 100 and 32000 as a time-bounded instance containing an empty value for the OOF message when Automatic Replies is turned on in Microsoft Exchange. Published to Container 200, 300, and 400 as a time-bounded instance containing the specified OOF message when Automatic Replies is turned on in Microsoft Exchange.
noteHistory category instance value element		Published to Container 200, 300, and 400 as a static instance representing a previously published personal note when a new personal note category instance value element instance is published. By default, no more than three publications of noteHistory instances are kept in each container. When two note instances are published less than 30 seconds apart, the latest publication of the noteHistory replaces the most recently prior publication of the noteHistory instance.
otherOptions category instance value element	0	Published to Container 1 as a static instance containing the permissions to use the personal information manager when this kind of information is changed.
	1	Published to Container 1 as a static instance containing the last access timestamp for voice mail or missed conversations when the timestamp is changed.
	2	Published to Container 1 as a static instance containing the privacy mode-related options when this kind of option is changed.
routing category instance value element		Published to Container 0, 100, 200, 300, and 400 as a static instance containing various in-bound call routing rules when such rules were specified.
services category instance value element	0	Published, by aggregation script, to Container 2 as a user-bounded instance containing presence service and calendar service capabilities of the local user. Published, by aggregation script, to Containers 100, 200, 300, and 400 as a user-bounded instance containing presence service capability of the local user. Published, by aggregation script, to Container 32000 as a user-bounded instance containing an empty value.
state[@type='aggregateState'] element	0	Published to Container 32000 as a static instance containing an availability number of 18500 indicating the Offline presence status.
	1	Published to Container 100 as a user-bounded instance containing an aggregated availability number. Published to Container 2, 200, and 400 as a user-bounded instance containing an aggregated availability number of 9500 as well as aggregated location, time zone and device type when the user sets the availability to Do Not Disturb. Published to Container 3 and 300 as a user-bounded instance containing an availability number of 6900 and an activity token of "urgent-interruptions-only" as well as aggregated location, time zone, and device type when the user sets the availability to Do Not Disturb. Published to Container 2, 3, 200, 300, and 400 as a user-bounded instance containing the aggregated availability number, location, time zone and device type when the user sets the availability to any mode other than Do Not Disturb.
state[@type='aggregateMachineState'] element	0x10000000	Published to Container 2 as a user-bounded instance containing the current aggregated machine availability status that is determined by the most active device that has the lowest availability number.
state[@type='userState'] element	0x20000000	Published to Container 2 and 3 as a static instance when the local user sets an availability mode that is not Busy or Do Not Disturb.
	0x24000000	Published to Container 2 and 3 as a time-bounded instance containing the availability number of 6500 when the user sets the availability mode to Busy. By default, this publication expires in 24 hours if it's left unchanged. Published to Container 2 as a time-bounded instance containing the availability number of 9500 when the user sets the availability mode to Do Not Disturb. By default, this publication expires in 24 hours if it's left unchanged. Published to Container 3 as a time-bounded instance containing the availability number of 6900 (Busy with Urgent interruptions only) when the user sets the availability mode to Do Not Disturb. By default, this publication expires in 24 hours if it's left unchanged.
state[@type='machineState'] element	A hash dependent on the device GRUU and of the 0x3YYYYYYY format.	Published to Container 2 and 3 as an endpoint-bounded instance when the local user signs in, when the device times out because it becomes idle or away, when the device is disconnected or reconnected, or when the device detects a mouse or keyboard activity. However, when a not-the-most active device has an active machine state published three times in three minutes, further detections of user input on this device will not cause any new publication of an active machine state until the device becomes idle or until three minutes has elapsed.
state[@type='calendarState'] element	A hash dependent on the SMTP address and of the 0x4YYYYYYY format.	Published to Container 2 and 3 as an endpoint-bounded instance containing an availability number of 6500 (Busy) and an "in-a-meeting" activity token, plus any specified meeting subject or location about an ongoing meeting scheduled in the Microsoft Exchange calendar store.
	A hash dependent on the SMTP address and uses the 0x6YYYYYYY format.	Published to Container 2 and 3 as a static instance containing the "out-of-office" activity token when Automatic Replies is turned on in Microsoft Exchange.
state[@type='phoneState'] element	A hash dependent on the local user’s SIP URI plus the phone device GRUU and uses the 0x8YYYYYYY format.	Published to Container 2 and 3 as an endpoint-bounded instance containing an availability number of 6500 (Busy) and the "on-the-phone" activity token when the user has established a VoIP call.
	A hash dependent on the local user’s SIP URI plus the phone device GRUU and uses the 0x7YYYYYYY format.	Published to Container 2 and 3 as an endpoint-bounded instance containing an availability number of 6500 (Busy) and the "on-the-phone" activity token when the user has established a RCC phone call.
	A hash dependent on the local user’s SIP URI plus the phone device GRUU and uses the 0x9YYYYYYY format.	Published to Container 2 and 3 as an endpoint-bounded instance containing an availability number of 6500 (Busy) and the "on-the-phone" activity token when the user has established a UC-enabled PSTN phone call.
userInformation category instance value element	0	Published to Container 1 as a static instance containing the use-specified Phone options. The information is used to construct contactCard category instance value element of Instance ID 1.
userProperties category instance value element	0	Published to Container 1 as a static instance containing the server-provisioned user identity information. The information is used to construct contactCard category instance value element of Instance ID 0.
workingHours category instance value element	0	Published to Container 1 as a static instance containing the Microsoft Exchange-provisioned workingHours information. This is used by the call routing script to block in-bound calls outside of the user’s working-hours period.

See also

Reference

[MS-PRES]: Presence Protocol Specification

Concepts

Presence data source and category instance ID

Presence category instances published or used by Lync