Site Defaults Reference¶
When the End-to-End feature is installed and the system is provisioned for users, reference data representing a sample dial plan is stored as a template instance of a Site Defaults data model.
This reference data shows text values or combines default text and references with the feature’s macros and configuration templates.
For example, when site hierarchy and user administration is carried out, input administrator data (stored as for example a named macro called SITENAME) is combined with this reference data to provide default or generated values. If a customer administrator at for customer “VS-Corp” created a site called “Boston”, the line and call partitions associated with the site are called “Site-Boston” when the macro is resolved.
The sample dial plan is an instance of the site defaults and contains illustrative values. Where the name of the data refers to a Template, the Configuration Template itself contains or results in further data defaults that are applied when the End-to-End feature is used for user and site administration.
For example, the template called “Default CUCM RDP Template” sets a number of default Remote Destination Profile values when it is added:
Name |
Value |
|---|---|
product |
“Remote Destination Profile” |
protocol |
“Remote Destination” |
description |
“Created by default template” |
callInfoPrivacyStatus |
“Default” |
protocolSide |
“User” |
devicePoolName |
“{{macro.CUCM_PHONE_devicePoolName}}” |
class |
“Remote Destination Profile” |
The specified values for the CUCM Remote Destination Profile data are defaulted, while the macro called macro.CUCM_PHONE_devicePoolName looks up the Default Device Pool value for the Dial Plan name obtained from the Site Defaults instance. This value is based on the Customer ID and Site ID, for example “Cu12Si3-DevicePool” where the Customer ID is 12 and the Site ID is 3. This value is based on an ID lookup. These IDs are not reset during subsequent imports of the sample dial plan, so that existing instances on the system that use an ID will not be overwritten.
Most of these settings are populated with default values based on an example dial plan that ships with the core product. Typically, HCS templates overwrites these settings with different default values which are in line with a required dial plan.
All of the Day-2 features (provisioning of Subscriber, Phone, Line, and so on) have macros that point to the Site Defaults Document (SDD) when viewing the features in the GUI. This serves two main purposes:
It simplifies the administration of these features, because as soon as the administrator opens a GUI form to provision any of these features, the bulk of the settings are pre-populated with correct values (based on correct values in the SDD).
A abstracted view of Day-2 templates is possible by means of Field Display Policies that can hide complex and technical information while still populating these (hidden from view) by means of the SDD.
If changes are made in the SDD, for example new attributes are added, then pre-existing SDD instances must be manually updated to include these new attributes (if necessary).