Export (0) Print
Expand All

OC Presence: Containers

As shown in the figure below, an Office Communicator user can right-click a presentity, choose Access Level, and put that presentity in one of five containers: Public, Company, Team, Personal, or Blocked.

Setting container membership using Office Communicator
Dd941373.3f3e85d3-e7e4-4c71-9674-ab5af4e4da85(en-us,office.13).bmp

Note: In some Unified Communications documentation, the Company container is called Workplace and the Blocked container is called Block.

The following table indicates which presence information is available to subscribers in which containers.

Presence information published by Office Communicator for specific containers
Dd941373.06fdf771-0ab7-44e0-868d-95521197068c(en-us,office.13).bmp

*If these attributes are defined in Microsoft Active Directory, they are visible to all contacts in your company, regardless of Access Level. They are also visible to federated contacts, depending on the assigned Access Level. They are not visible to public instant messaging contacts.

When a user adds members to the Blocked container, they are blocked from seeing most presence information. The Public container includes a member that allows access for users across domains but in the same federation regardless of enterprise membership. This membership scope includes Public Internet Cloud (PIC) users of services like MSN and Yahoo!. The Company container contains a member that allows access to all users in the same enterprise. The Team container is intended for users who are on the user’s team, and the Personal container is intended for users from whom the user has a personal relationship. The Team, Personal, and Blocked containers start out empty, and members are added through the user interface.

The following table shows the containers that are used by Office Communicator with short descriptions. Office Communications Server and its Aggregation script use containers with IDs from 0 to 3 for special purposes, and Office Communicator does not add members to these containers. For example, states published to Aggregation 1 (ID = 2) and Aggregation 2 (ID = 3) containers are used by the Aggregation script to publish an aggregated state to other containers. More information about aggregation is described in the Aggregation section.

Containers used by Office Communicator

Container IDNameDescription

0

Default

Contains a member that represents everyone. All subscribers have access to this container. Contains the display name and e-mail address that identifies presentity.

1

Self

A user’s own presentity is the only member of this container, which includes data for userProperties, alerts, rccOptions, userInformation, and calendarData.

2

Aggregation 1

The Aggregation script aggregates the user, machine, phone, and calendar states published to this container and then publishes the aggregated state to containers 100, 200, or 400.

3

Aggregation 2

The Aggregation script aggregates the user, machine, phone and calendar states published to this container and then publishes the aggregated state to container 300.

100

Public

Contains a member that represents public, federated subscribers. Subscribers from domains in the federation have access to this container.

200

Company

Contains a member that represents users in the same enterprise. Subscribers from the enterprise have access to this container.

300

Team

Designed for members of the presentity’s team and are given special privileges around interruption. Subscribers are added by the user.

400

Personal

Designed for subscribers that the presentity knows personally. Subscribers are added by the user.

32000

Blocked

Blocked subscribers. Subscribers added to this container always see the presentity as offline and can only see the display name.

Community Additions

ADD
Show:
© 2015 Microsoft