Container Semantics Defined and Conformed by Microsoft Lync

  • Article

This section describes the containers Microsoft Lync 2010 uses to control user access to published presence data.

In This Section

  • Default Container
    Used to allow access to the contained non-private category instances by users or entities that are not members of any other containers and to apply specified routing rules to forward or block calls from such remote users.

  • Self Container
    Used as a local cache of category instances that are accessible to the local user only.

  • Aggregation Containers
    Used to contain presence data that are subject to aggregation by the server-hosted aggregation script. The contained data is visible to the local user only.

  • External Contacts Container
    By default, this is used to allow federated network users to access the contained non-private presence data and to apply specified routing rules to forward or block calls from such remote users.

  • Colleagues Container
    Used to allow users of the same enterprise network to access the contained non-private presence data and to route or block calls from such remote users.

  • Workgroup Container
    Used to allow the specified users, who are considered as belonging to the local user’s work groups, to access the contained non-private presence data and to apply the specified routing rules to forward or block calls from such remote users.

  • Friends and Family Container
    Used to allow the specified users, who are considered as the local user’s friends and family members, to access the contained non-private presence data and to apply specified routing rules to forward or block calls from such remote users.

  • Blocked Contacts Container
    Used to prevent the specified users from accessing the specified category data and to apply specified routing rules to block calls from such remote users.