The container prescribes a publication mechanism into which presence data is uploaded from a presence sensor and from which the published presence data is pushed to the allowed subscribers. A presence container, thus, defines a mapping between the contained category instances and specified subscribers who are allowed to receive the contained presence data.
A presence container is represented by a category instance. The container ID can be used to signify the access level for the contained presence information. For example, the following containers are defined and used by Office Communications Server 2007 R2 and Office Communicator 2007 R2.
Access Level Name
This container allows anyone who is not blocked to receive the contained data. By default, it contains the user's identity information. This includes the display name and e-mail address of the user publishing the enhanced presence. The data is supplied by the User Replicator, an Office Communications Server component, and is obtained from Active Directory.
This container is for the presence publishing user to store the presence and other data for personal use. Only the publishing user can access this container. Office Communicator uses this container to hold the list of categories published by the user as well as the user information including the telephone numbers, Microsoft Exchange Unified Messaging settings, and the list of contacts whose presence the user has subscribed to.
Office Communicator publishes presence states indicating the status of various endpoints of this user to this container. A publication event that occurs in this container triggers the aggregation script to run on the server. The aggregation script maps presence states from various endpoints to an effective user state, also known as the aggregated state. The aggregated state is then published to Container 100, 200, and 400.
This is another aggregation container. It contains the same input and shares the same aggregation logic as the other aggregation container. However, the resultant aggregated state is published to Container 300 in which the semantics of the Do-Not-Disturb (DND) mode permits the contacts, as specified by the membership of this container, to reach the user. Container 300 is also known as the Team container.
This container is used to publish presence and other data for federated users to subscribe to.
This container contains the presence information that can be subscribed to or queried for by other users belonging to the publisher's enterprise network.
Contains presence information for other users considered to be on the user's team. By default, the Team container has an unspecified membership. The publishing user decides who belong to his or her team by explicitly adding specified users to the container.
Contains presence information for other users considered as the personal contacts of the publishing user. No membership is specified to this container by default. The publishing user must explicitly add specified members to this container.
This container is used to block specified members from seeing the presence and accessing other information of the publishing user. Watchers that are blocked will see the user's presence as offline.
Containers are specific to each publisher. A user can publish presence and other information only to his or her personal container. Other users cannot access or view the contained information unless they are within the container's membership scope.
A user can publish a different set of presence information to different containers to control who can view presence information, and to specify which presence information can be viewed. The following table shows the kinds of presence information published for various types of subscribers by Office Communicator 2007 R2 and Office Communications Server 2007 R2.
* Work Phone, Mobile Phone, Home Phone, and Other Phone are published only if the user allows them to be published (using the Phones tab in Options).