Share via

Self Container

  • Article

Self Container has an instance ID value of 1 (one). It is invisible to all users except the container owner or the local user. It is used to cache the user or application data. The data can be used to construct the local user’s contact information, to facilitate presence publication, and to establish communications sessions.

The following category instances are published to this container:

Category Name

Instance ID

Description

alerts

0

This category instance contains the Alerts pane that the local user can set using the Lync Options panel in Lync 2010. Such options specify how the local user be notified when the user is added to the contact list of some other users or when the local user is in a Do Not Disturb state.

The Following code example shows an alerts category instance value when a user deselects the Notify me when someone adds me to his or her contact list option under the Alerts pane in the Lync Options panel.

<alerts xmlns="https://schemas.microsoft.com/2006/09/sip/options/alerts">
   <notifyAdditionToContactList>false</notifyAdditionToContactList>
</alerts>

calendarData

0

This static bound instance contains one or more time periods designated as the working hours of the local user. The information is provisioned from the Microsoft Exchange Server as the workingHours information.

The following code example is from a calendarData category instance containing the workingHours information.

<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 mailbox URI

This time-bound instance is meant to contain a calendar period of the local user. This calendar period is represented by a contiguous block of free-busy timeslots and is provisioned from the Microsoft Exchange Server as the freeBusy information. For the Self Container, this instance carries an empty value.

otherOptions

These category instances contains the Personal Information Manager’s setting, the privacy mode selection, voice mail last access records, and other optional settings that can be configured using the Lync Options panel.

The following code example shows an otherOptions category instance containing privacy mode settings:

<otherOptions xmlns="https://schemas.microsoft.com/2006/09/sip/options/otherOptions">
   <privacyModeUserSelection>standard</privacyModeUserSelection>
   <currentPrivacyMode>standard</currentPrivacyMode>
   <lastQueryPrivacyEnabled>false</lastQueryPrivacyEnabled>
   <publishActivityHistory>true</publishActivityHistory>
   <EnableContactSyncUserOption>2</EnableContactSyncUserOption>
</otherOptions>

The following code example shows an otherOptions category instance containing the Personal Information Manager settings:

<otherOptions xmlns="https://schemas.microsoft.com/2006/09/sip/options/otherOptions">
  <permissions>
    <personalInformationManager>outlook</personalInformationManager>
    <autoRetrieveOofFromOutlook>true</autoRetrieveOofFromOutlook>
    <publishCalendarPresence>true</publishCalendarPresence>
    <imAutoArchiving>true</imAutoArchiving>
    <callLogAutoArchiving>false</callLogAutoArchiving>
    <publishMeetingSubjectAndLocation>true</publishMeetingSubjectAndLocation>
  </permissions>
</otherOptions>

rccOptions

When PBX phones are supported in Lync Server 2010, published rccOptions category instances contain the specification on how to such phones are controlled in unified communications.

userProperties

0

The userProperties category instance contains the server-provisioned user information like the phone lines controlled by the user, the postal address of the user, the telephony mode the user is in, and whether the user has voice mail enabled for unified communications (UC). Each phone line is described by a telephone mode, a TEL URI, and the TEL URI of the line server to support remote call control (RCC). A phone line can be in one of the three types: UC-enabled or VoIP (Uc), PBX-based (Rcc), and both (Dual). The supported telephony modes are: Uc, Rcc, Dual, and None. The information is provisioned from Active Directory.

The following code example shows a userProperties category instance.

<userProperties xmlns="https://schemas.microsoft.com/2006/09/sip/categories">
    <lines>
        <line lineType="Uc">tel:+14255550180;ext=46666</line>
    </lines>
    <telephonyMode>Uc</telephonyMode>
    <exumEnabled>1</exumEnabled>
    <exumURL>EUM:johnd@contoso.com;phone-context=EX-OCS-SIPSec.exchange.corp.contoso.com</exumURL>
</userProperties>

The <exumEnabled> element represents a bit flags indicting whether voice mail is enabled for the user. A bit value 1 indicates voice mail is enabled. Otherwise, it is not enabled. The accompanying <exumURL> element contains the voice mail URL supported by the Microsoft Exchange Unified Messaging.

userInformation

0

The userInformation category instance contains the sharable user information about the local user. The information includes various phone numbers that remote users can use to contact the local user. It is extracted from the server-provisioned data and/or provided by the user using the Lync Options panel. The userInformation category instance is published by Lync 2010.

The following example shows a userInformation category instance.

<userInformation xmlns="https://schemas.microsoft.com/2006/09/sip/options/userInformation">
    <callHandlingList>
        <lastPhone>
            <displayString>+114255550150</displayString>
            <uri>tel:+114255550150</uri>
        </lastPhone>
    </callHandlingList>
    <phones>
        <phone type="work">
            <readOnly>true</readOnly>
            <displayString>+1 (425) 5550160 X63872</displayString>
            <uri>tel:+14255550160;ext=63872</uri>
        </phone>
        <phone type="mobile">
            <displayString>+14255550170</displayString>
            <uri>tel:+14255550170</uri>
        </phone>
        <phone type="home">
        </phone>
        <phone type="other">
        </phone>
    </phones>
</userInformation>

In addition, in-band provisioning data, including server configuration, unified communications policies, enhanced presence publication grammars, or location profile, is also stored in Self Container. Most unified communications APIs, including Microsoft Lync 2010 SDK and Microsoft Unified Communications Managed API (UCMA) 3.0, encapsulate these information with API-specific objects.