External Contacts container

Applies to: Lync 2013 | Lync Server 2013

This container has a container ID value of 100. The default access control list contains a single entry for federated users. Non-private category instances published to this container are visible to all the users of a federated network by default.

The following category instances are published to this container.

Category instances published by Lync Server 2013

Category name	Instance ID	Description
contactCard category instance value element	0	Contains the local user’s identity that consists of the display name and email address as provisioned from the Active Directory domain. The following is an example of this category instance. <contactCard xmlns="http://schemas.microsoft.com/2006/09/sip/contactcard"> <identity> <name> <displayName>John Barr</displayName> </name> <email>john.barr@exchange.contoso.com</email> </identity> </contactCard>
legacyInterop category instance value element	1	Contains the availability number of the local user’s current state[@type='aggregateState'] element. It makes the local user’s presence status available to the container members that use legacy clients. The following is an example of this category instance. <legacyInterop availability="3500" xmlns="http://schemas.microsoft.com/2006/09/sip/categories" />

Category instances published by aggregation script

Category name	Instance ID	Description
state[@type='aggregateState'] element	1	Contains only the local user’s current availability number. The following is an example of this category instance. <state xsi:type="aggregateState" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/2006/09/sip/state"> <availability>3500</availability> </state>
services category instance value element	0	Contains the endpoint-independent presence capabilities of the local user. This is shown in the following example. <services xmlns="http://schemas.microsoft.com/2006/09/sip/service"> <service uri="sip:kdeding@microsoft.com"> <capabilities> <text render="true" capture="true" deviceAvailability="3500" /> <gifInk render="true" capture="false" deviceAvailability="3500" /> <isfInk render="true" capture="false" deviceAvailability="3500" /> <applicationSharing render="true" capture="true" deviceAvailability="3500" /> <voice render="true" capture="true" deviceAvailability="3500" /> <video render="true" capture="true" deviceAvailability="3500" /> <contentWhiteboard render="true" capture="true" deviceAvailability="3500" /> <contentPoll render="true" capture="true" deviceAvailability="3500" /> <contentPowerPoint render="true" capture="true" deviceAvailability="3500" /> <contentNativeFile render="true" capture="true" deviceAvailability="3500" /> </capabilities> </service> </services>

Category instances published by Lync 2013

Category name	Instance ID	Description
contactCard category instance value element	1	Contains an empty value of this category instance as shown in the following example. <contactCard xmlns="http://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 this kind of information.
contactCard category instance value element	3	Contains the local user’s company description and job title, which are obtained from the underlying Lync Server 2013 Address Book Server. This is shown in the following example. <contactCard xmlns="http://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 category instance value element	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="http://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 category instance value element	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="http://schemas.microsoft.com/2006/09/sip/contactcard"> <title>SENIOR EMPLOYEE</title> <delimiter xmlns:auto-ns1="http://schemas.microsoft.com/2006/09/sip/contactcard" xmlns="http://schemas.microsoft.com/2006/09/sip/commontypes"> </delimiter> <delimiter xmlns:auto-ns1="http://schemas.microsoft.com/2006/09/sip/contactcard" xmlns="http://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 category instance value element	0	Contains an empty value. This effectively blocks the external contacts from accessing the local user’s working-hours information that is obtained from the user’s Microsoft Exchange account.
calendarData category instance value element	A hash dependent on the local user’s email address.	Contains an empty value for the free-busy information, as shown in the following example. <calendarData xmlns="http://schemas.microsoft.com/2006/09/sip/calendarData"> </calendarData> This effectively blocks the container members from accessing the local user’s free-busy information.
dndState category instance value element	0	Contains an empty value when the local user is not in the Do not disturb availability mode and it contains an availability number of 9500 when the user is in the Do not disturb mode. This is shown in the following example. <state xmlns="http://schemas.microsoft.com/2006/09/sip/state" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="userState" manual="true" />
note category instance value element	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="http://schemas.microsoft.com/2006/09/sip/note"> <body type="personal" uri="">A message for public</body> </note>
note category instance value element	A hash dependent of the local user’s email address	Published during an OOF period, this instance contains an out-of-facility (OOF) note with an empty value as shown in the following example. <note xmlns="http://schemas.microsoft.com/2006/09/sip/note"></note> This effectively prevents the external contacts from viewing the OOF message.
routing category instance value element		One or more routing category instance value element category instances that contain the user-configurable routing rules that are used to handle incoming calls from a member of this container. The following is an example of such an instance. <routing xmlns="http://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>

See also

Concepts

Container semantics defined and conformed by Lync