Default Container and Category Settings for New Users

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

When a new user endpoint is created, the platform applies an access control entry (ACE) to two of its containers, and populates specific categories in two other containers. This process is known as bootstrapping. The details of this process are described in this topic.

Automatically Populated Container Memberships

The federated and sameEnterprise ACEs are applied to the Public and Company containers.

Container (Container ID)	Initial setting
Public (100)	The federated access control entry (ACE) is applied to this container. This container contains presence information accessible by contacts at businesses allied with the user’s company. By default, public internet cloud (PIC) users do not have access to this presence information in this container.
Company (200)	The sameEnterprise ACE is applied to this container. This container contains presence information accessible by contacts within the user’s workplace.

Automatically Populated Categories

A number of categories in the Public and Blocked containers are initialized as shown in the following table.

Container (Container ID)	Category	Initial setting
Public (100)	contactCard	Empty XML document for instances 1 and 2.
	calendarData	Empty XML document.
	note	Empty XML document.
Blocked (32000)	contactCard	Empty XML document for instances 1, 2, 3, and 4.
	services	Empty XML document.
	routing	A routing category instance that disables routing for blocked users. The XML code for this category instance appears after this table.
	calendarData	Empty XML document.
	aggregateState	Offline (18500).
	note	Empty XML document.

The routing category in the Blocked container is initialized as shown in the following XML code.

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