There are two aggregation containers. The container ID of the first container is 2 and the second container ID is 3. They are not accessible by anyone other than the container owner. The first aggregation container is used by the Microsoft Lync Server 2013 aggregation script to aggregate the endpoint-specific presence states and to generate the endpoint-independent presence capabilities of the presentity. The results are published to the External Contacts (100), Colleagues (200), and Friends and Family (400) containers. The second aggregation container is used to generate the aggregate state category instance for publication in Workgroup Container (300).
First aggregation container
Microsoft Lync 2013 publishes the following endpoint-specific category instances to the first aggregation container. They are supplied as input to produce aggregated states by the aggregation script whenever this kind of category instance is added, modified, or removed. The first aggregation container is used to produce aggregated presence state (state[@type='aggregateState'] element) for publication in Container 100, 200, and 400.
This is a static category instance and represents the presence state of the user. There are two kinds of user states. When the user resets his or her status by using Lync 2013, the event causes this instance to be published. This instance appears in the next example.
This is a time-bounded category instance of a user state that contains the Busy or Do Not Disturb availability mode. This instance appears in the next example.
A hash that is dependent on the local user’s SMTP address.
This is a time-bounded category instance and corresponds to a scheduled meeting or an OOF activity in the user’s calendar. The following shows an example of the calendar state for an OOF activity.
This is an endpoint-bounded category instance and is published when a phone conversation is established. The following shows an example of a phone state instance.
This is an endpoint-bounded category instance and describes a signed-in device, including the device’s capabilities. The following shows an example of a device instance.
Contains an empty value when the local user is not in the Do not disturb availability mode and contains an availability number of 9500 when the user is in the Do not disturb mode. This scenario is shown in the following example.
This is a user-bounded category instance and represents the endpoint-independent overall availability and/or activity of the user. The following shows an example of this category instance.
Lync 2013 publishes the following endpoint-specific category instances to the second aggregation container. They are supplied as input to produce aggregated states by the aggregation script whenever any such category instance is added, modified, or removed. The second aggregation container is used to produce aggregated presence state (state[@type='aggregateState'] element) for publication in Container 300.
This is a static category instance and represents the presence state of the user. When the user resets his or her status by using Lync 2013, the event causes this instance to be published.
This is a time-bounded category instance of a user state that contains the Busy availability mode (6500) or the Busy availability mode with urgent-interruptions-only activity token (6900). 6900 is published when the local user sets his or her status to Do not disturb on Lync 2013. The following example shows this instance.
This is an endpoint-bounded category instance and it indicates the availability of a signed-in device. The following example shows this category instance.
A hash dependent on the local user’s SMTP address.
This is a time-bounded category instance and corresponds to a scheduled meeting or an OOF activity in the user’s calendar. The following is an example of this category instance for an OOF activity.
A hash dependent on the phone URI and device GRUU.
This is an endpoint-bounded category instance and is published when a phone conversation is established. Depending on the deployed topology of Lync Server 2013, three kinds of phone states are possible:
RCC
VoIP
PSTN
The following is an example of this category instance when the local user is on the phone.
This is a user-bounded category instance and it represents the endpoint-independent overall presence state of the user. The following is an example of such a category instance.
Lync 2013 uses the second aggregation container to block inbound calls from the user’s work group when the user is in a Do Not Disturb state differently than for other contacts. When the user sets the Do Not Disturb status, Lync 2013 creates a state[@type='userState'] element category instance in the first aggregation container to contain an availability number of 9500. It also creates a state[@type='userState'] element category instance in the second aggregation container to contain an availability number 6900 and an activity token of "urgent-interruptions-only". The availability number of 9500 corresponds to a Do Not Disturb state whereas 6900 corresponds to a busy state. This means that the user’s presence status appears to the user’s Workgroup contacts as "Busy – Urgent interruptions only" and to the user’s other contacts as "Do Not Disturb". Thus, calls from any Workgroup contacts are not blocked while calls from other contacts are blocked.