Site Defaults Templates#

When a provider hierarchy is created in VOSS, the system automatically generates a default site-level template called PROVIDER_TEMPLATE at the Provider level.

Cisco UCM environments#

If you’re working in a Cisco UCM (CUCM) environment, the PROVIDER_TEMPLATE can be pre-populated with CUCM-specific values. This occurs only when the Enable Cisco CUCM Global Setting is turned on.

During template creation, VOSS checks this setting before adding CUCM-related default values.

How templates propagate through the hierarchy#

  • Provider - Customer

    Each time a customer is added under a provider, VOSS uses the provider’s PROVIDER_TEMPLATE to create the customer-level template called CUSTOMER_TEMPLATE.

  • Customer - Site

    When a site is added to a customer, that customer’s CUSTOMER_TEMPLATE is used to generate the site’s own site default template instance.

Purpose of site-level default templates#

Site-level templates are especially valuable for organizations with multiple sites and countries. They allow providers or higher-level administrators to define location-specific values that keep multinational deployments consistent.

Site-level templates:

  • Take the same name as the site

  • Are pre-populated with several default values

  • Supply the default values required for various onboarding tasks

Interaction with Cisco HCS dial plans#

For provider deployments using Cisco HCS:

  • When a site dial plan is created, VOSS updates the site’s defaults with dial plan-related attributes.

  • Any existing values affected by the dial plan are overwritten.

  • If the dial plan is removed, those updated attributes are cleared and reset to empty values.

Customizing templates#

Administrators with sufficient permissions can modify both PROVIDER_TEMPLATE and CUSTOMER_TEMPLATE to adjust the default settings used when creating templates lower in the hierarchy.

Default site templates appear on the Site Defaults page.

Related topics