Local-access only category instances
Applies to: Lync 2013 | Lync Server 2013
The following category instances are published or used by Microsoft Lync 2013 for local access only or self-consumption.
Category name |
Container Id |
Description |
|---|---|---|
1 |
Present in the Self container, this category instance specifies how the user is notified of the events when the user is added to someone’s contact list or when the user is in a Do Not Disturb (DND) state. These options can be set through the Alerts option panel on Lync 2013. |
|
1 |
Present in the Self container, this type of category instances contains the user’s working-hours specification or a contiguous block of free-busy time intervals. This kind of calendar data is provisioned from the Microsoft Exchange calendar store. |
|
2 |
Present the first aggregation container, this kind of category instances contains the information about signed-in devices. The device information includes the device capabilities that are used as the input to the aggregation script to produce aggregated capabilities attributed to a device-independent user-bound enhanced presence services category instance. |
|
0, 2, 3, 100, 200, 300, and 400 |
This type of category instance is used to determine whether to block routing inbound calls from any container members (specified) or not (unspecified) when the local user is in a Do Not Disturb state. A dndState category instance is just an empty state category instance value elements category instance of the userState type, but has a registered category name of dndState. |
|
1 |
The otherOptions category instances include the privacy mode settings, timestamps of the last access to the user’s voice mail, permissions for handling personal information. Multiple instances are used to describe different parts of such data. |
|
1 |
The rccOptions category instances contain roaming options for remote call control when PSTN/PBX phones are supported by Microsoft Lync Server 2013. |
|
0, 100, 200, 300, 400, and 32000 |
The routing category instances contain routing rules to forward inbound calls made by any members of a hosting container. They are private category instances and are not visible to the remote users who are members of the hosting containers. |
|
2, 3 |
Non-aggregated state category instances are used as input to the aggregation script that, in turn, produces aggregated state category instance as the output. Non-aggregated state category instances in the first aggregation container (2) are used to produce the aggregated state for publication in Container 100, 200, and 400. Those in the second aggregation container (3) are used to produce the aggregated state for publication in Container 300. |
|
2 |
The services category instance is produced by the aggregation script and represents the device-independent user-bound presence capabilities of the user. |
|
1 |
Present in the Self container only, this type of category instances contains phone numbers that can be set by the local user or provisioned by the server. Server-provisioned phone numbers are read-only. User-configurable phone numbers can be set through the Lync Options dialog box. |
|
1 |
This type of category instances contains server-provisioned user data that includes phone lines assigned to the user and the voice mail URL if the user has unified messaging enabled. |
|
1 |
This type of category instances contains the user’s working-hours specification. A workingHours category instance is just a calendarData category instance value element category instance containing working-hours information, where the category name of workingHours is registered. A workingHours category instance is used to determine the user’s working hour period when incoming calls should be routed. |