The Workgroup Container has a container ID value of 300. The default access control list does not contain any entry. When a user changes the privacy relationship with a contact to that of Workgroup using Change Privacy Relationship menu in Microsoft Lync 2010, the affected contact is added as a member of this container.
The following category instances are published to this container.
Category Instances Published by Microsoft Lync Server 2010
Category Instances Published by Aggregation Script
Category Instances Published by Lync 2010
contactCard |
1 |
Contains an empty value of this category instance as shown in the following example
<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 effectively blocks members of this container from accessing such information. |
contactCard |
3 |
Contains the local user’s company description and job title, which are obtained from the underlying Lync Server 2010 Address Book Server. This is shown in the following example.
<contactCard xmlns="https://schemas.microsoft.com/2006/09/sip/contactcard"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<company>Contoso</company>
<title>Senior Employee</title>
</contactCard>
|
contactCard |
4 |
Contains the server-provisioned voice mail URL of the local user when the user has unified communications (UC) enabled. This is shown in the following example.
<contactCard xmlns="https://schemas.microsoft.com/2006/09/sip/contactcard" isUCEnabled="true">
<url type="voicemail">sip:johnd@contos.com;opaque=app:voicemail;local-resource-path=voicememo</url>
</contactCard>
|
contactCard |
6 |
Contains the local user’s job title and display photo. This causes the local user’s photo displayed to members of this container. This is shown in the following example.
<contactCard xmlns="https://schemas.microsoft.com/2006/09/sip/contactcard">
<title>SENIOR EMPLOYEE</title>
<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>
<displayADPhoto>true</displayADPhoto>
<photo type="enterprise" updated="2010-05-24T21:08:59Z">
<uri></uri>
<hash>10b394d3bdc9b3f999e44efb5c269dda</hash>
</photo>
</contactCard>
|
calendarData |
0 |
Contains the local user’s working-hours information obtained from the user’s Exchange account.
<calendarData
xmlns="https://schemas.microsoft.com/2006/09/sip/calendarData"
mailboxID="johnd@exchange.contoso.com">
<WorkingHours
xmlns:auto-ns1="https://schemas.microsoft.com/2006/09/sip/calendarData"
xmlns="https://schemas.microsoft.com/exchange/services/2006/types">
<TimeZone>
<Bias>480</Bias>
<StandardTime>
<Bias>0</Bias>
<Time>02:00:00</Time>
<DayOrder>1</DayOrder>
<Month>11</Month>
<DayOfWeek>Sunday</DayOfWeek>
</StandardTime>
<DaylightTime>
<Bias>-60</Bias>
<Time>02:00:00</Time>
<DayOrder>2</DayOrder>
<Month>3</Month>
<DayOfWeek>Sunday</DayOfWeek>
</DaylightTime>
</TimeZone>
<WorkingPeriodArray>
<WorkingPeriod>
<DayOfWeek>Monday Tuesday Wednesday Thursday Friday</DayOfWeek>
<StartTimeInMinutes>480</StartTimeInMinutes>
<EndTimeInMinutes>1020</EndTimeInMinutes>
</WorkingPeriod>
</WorkingPeriodArray>
</WorkingHours>
</calendarData>
|
calendarData |
A hash dependent on the local user’s email address |
Contains the local user’s freeBusy information, as shown in the following example.
<calendarData xmlns="https://schemas.microsoft.com/2006/09/sip/calendarData" mailboxID="johnd@exchange.contoso.com">
<freeBusy startTime="2010-06-21T07:00:00Z" granularity="PT15M" encodingVersion="1">AAAAAAAAAAAAAAAAVVUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAVQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAVQAAAAAAAAAAAAAAAAAAAAAAAABUUVVVBQAAAAAAAAAA</freeBusy>
</calendarData>
Note
Notice that the local user’s free-busy information is visible to the Colleagues, Workgroup, and Friends and Family container members, while it is not visible to the External Contacts container members.
|
dndState |
0 |
Contains an empty value whether the local user is in the Do not disturb availability mode or not. This is shown in the following example.
<state xmlns="https://schemas.microsoft.com/2006/09/sip/state"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="userState" manual="true" />
|
note |
0 |
Contains a personal note set by the local user. This is shown in the following example.
<note xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="https://schemas.microsoft.com/2006/09/sip/note">
<body type="personal" uri="">A personal message</body>
</note>
|
note |
A hash dependent of the local user’s email address |
Published during an OOF period, this instance contains an out-of-facility (OOF) note the local user set in Microsoft Outlook as shown in the following example.
<note xmlns="https://schemas.microsoft.com/2006/09/sip/note">
<body type="OOF"
uri="johnd@exchange.contoso.com"
startTime="2010-06-22T19:00:00Z"
endTime="2010-06-23T19:00:00Z">A OOF message set in Outlook</body>
</note>
Notice that OOF note is visible to the Colleauges, Workgroup, and Friends and Family container members, while it is not visible to the External Contacts container members. |
noteHistory |
|
Contains a local user’s previously published personal note, as shown in the following example.
<noteHistory xmlns="https://schemas.microsoft.com/2006/09/sip/note">
<body type="personal" uri="">Out to lunch</body>
</noteHistory>
Notice that noteHistory is published to Colleagues, Workgroup, and Friends and Family container members, but not to the External Contacts container. By default, there can be up to three noteHistory category instances and they correspond to the three most recent note instances published before the current one. |
routing |
various |
One or more routing category instances containing the user-configurable routing rules to handle incoming calls from a member of this container. The following is an example of such an instance.
<routing xmlns="https://schemas.microsoft.com/02/2006/sip/routing"
name="rtcdefault" version="2" minSupportedClientVersion="4.0.0.0">
<preamble>
<flags name="clientflags" value="simultaneous_ring"></flags>
<wait name="total" seconds="20"></wait>
<list name="forwardto"></list>
<wait name="user" seconds="0"></wait>
<wait name="team1" seconds="0"></wait>
<wait name="team2" seconds="0"></wait>
<list name="simultaneous_ring">
<target uri="sip:+12065551111@contoso.com;user=phone"></target>
</list>
</preamble>
</routing>
|