Share via

Blocked Contacts Container

  • Article

The Blocked Contacts container has a container ID value of 32000. The default access control list contains a single entry for users from the public cloud. This container is used to block its members from accessing the contained presence data and having their calls routed. The blocking is accomplished by publications of the to-be-blocked category instances with empty values and by a publication of the block routing category instance.

The following category instances are published to this container.

Category Instances Published by Microsoft Lync Server 2010

Category Name

Instance ID

Description

contactCard

0

Contains the local user’s identity consisting of the display name and e-mail address as provisioned from the Active Directory. The following is an example of this category instance.

<contactCard xmlns="https://schemas.microsoft.com/2006/09/sip/contactcard">
  <identity>
    <name>
      <displayName>John Barr</displayName>
    </name>
    <email>john.barr@exchange.contoso.com</email>
  </identity>
</contactCard>

Publication of this contactCard category instance ensures that all user identities visible, making all the users discoverable by anyone.

legacyInterop

1

Contains the availability number of the corresponding state[@type='aggregateState'] category instance in this container. This makes the local user’s presence status available to the container members using legacy clients. The following is an example of this category instance.

<legacyInterop availability="18500" xmlns="https://schemas.microsoft.com/2006/09/sip/categories" />

The local user’s presence state always appears Offline to the members of this container.

Category Instances Published by Aggregation Script

Category Name

Instance ID

Description

state[@type='aggregateState']

1

Contains only the local user’s current availability number. The is shown in the following.

<state xmlns="https://schemas.microsoft.com/2006/09/sip/state" 
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
       manual="false" 
       xsi:type="aggregateState">
  <availability>18500</availability>
</state>

This publication makes the local user appears offline to the members of this container.

services

0

Contains an empty value as shown in the following.

<services xmlns="https://schemas.microsoft.com/2006/09/sip/service" />

This publication makes the local user’s presence capabilities invisible to members of this container.

Category Instances Published by Lync 2010

Category Name

Instance ID

Description

contactCard

1

Contains an empty value of this category instance as shown as follows.

<contactCard xmlns="https://schemas.microsoft.com/2006/09/sip/contactcard">
</contactCard>

This category instance is meant to contain the local user’s contact information as constructed from the user-configurable options, such as the local user’s home phone number. This publication renders this piece of the local user’s contact information invisible to the members of this container.

contactCard

3

Contains an empty value of this category instance as shown as follows.

<contactCard xmlns="https://schemas.microsoft.com/2006/09/sip/contactcard">
</contactCard>

This particular contactCard category instance is meant for the local user’s company description and job title, which are obtained from the underlying Lync Server 2010 Address Book Server. This publication renders this piece of the local user’s contact information invisible to the members of this container.

contactCard

4

Contains an empty contactCard category instance without the server-provisioned voice mail URL. This is shown as follows.

<contactCard xmlns="https://schemas.microsoft.com/2006/09/sip/contactcard" isUCEnabled="true">
</contactCard>

This instance is meant for representing the server-provisioned voice mail URL of the local user when the user has unified communications (UC) enabled. This publication renders the local user’s voice mail URL invisible to the members of this container.

contactCard

6

Contains a contactCard category instance without the intended information about the local user’s display photo and job title. This is shown as follows.

<contactCard xmlns="https://schemas.microsoft.com/2006/09/sip/contactcard">
  <delimiter xmlns:auto-ns1="https://schemas.microsoft.com/2006/09/sip/contactcard" 
             xmlns="https://schemas.microsoft.com/2006/09/sip/commontypes">
  </delimiter>
  <delimiter xmlns:auto-ns1="https://schemas.microsoft.com/2006/09/sip/contactcard" 
             xmlns="https://schemas.microsoft.com/2006/09/sip/commontypes">
  </delimiter>
</contactCard>

This contactCard instance is meant to contain the local user’s job title and display photo. The publication of this instance without such information renders the local user’s display photo not displayed to the members of this container.

calendarData

0

Contains an empty value as shown as follows.

<calendarData xmlns="https://schemas.microsoft.com/2006/09/sip/calendarData">
</calendarData>

This category instance is meant to contain the local user’s working hours information as obtained from the user’s Microsoft Exchange account. This publication renders this working-hours information invisible to the members of this container.

calendarData

A hash dependent on the local user’s email address

Contains an empty value for the freeBusy information, as shown as follows.

<calendarData xmlns="https://schemas.microsoft.com/2006/09/sip/calendarData">
</calendarData>

This effectively blocks the container members from accessing the local user’s free-busy information.

note

0

Contains an empty personal note as shown as follows

<note xmlns="https://schemas.microsoft.com/2006/09/sip/note">
</note>

note

A hash dependent of the local user’s email address

Published during an OOF period and when the OOF message is set, this instance contains an empty out-of-facility (OOF) note as shown as follows.

<note xmlns="https://schemas.microsoft.com/2006/09/sip/note"></note>

This renders the OOF note message invisible to the members of this container.

routing

0

Contains a routing instance containing the block rule. This is shown as follows.

<routing xmlns="https://schemas.microsoft.com/02/2006/sip/routing" name="rtcdefault" version="1">
  <preamble>
    <flags name="clientflags" value="block" />
  </preamble>
</routing>

This will cause incoming calls from any member of this container blocked and routed to the local user’s voice mail.