Site Defaults#

Overview#

Site defaults provide the default values for several of the tasks performed during onboarding. When creating a site, a site defaults instance is created on the site, having the same name as the new site, and pre-populated with several default values.

For Provider deployments, when creating a Cisco HCS site dial plan, the site defaults on the site are updated with dial-plan-related attributes that are affected by the deployed site dial plan. Any related existing values are overwritten. When the site dial plan is removed, these values are reset (set to empty) in the site defaults.

The Site Defaults Doc (SDD) is useful for managing multi-site, multi-country customers. A SDD allows a Provider administrator (or higher) to define geo-specific information at a site level, allowing multinational sites to stay in sync.

Geo-specific information includes CUCM user-locale and network-locale defaults, as well as the CUC time zone and language defaults.

Site defaults may also be used to include a site for the overbuild, a VOSS Automate process that syncs in users, and which may include moving users to sites (based on model filter criteria chosen for the site defaults), and assigning services to subscribers at the sites (when flow through provisioning is enabled).

Configure Site Defaults#

This procedure displays and updates site defaults.

  1. Log in to VOSS Automate (Admin Portal), as Provider, Reseller, or Customer administrator.

  2. Go to (default menus) Site Management > Defaults to open the Defaults page; then, select the relevant site to open the Defaults[site name] page.

  3. Click through the tabs on the Defaults page to modify site default values - refer to the Defaults Page section below.

  4. Save your changes.

    Note

    • Field descriptions for the tabs on this screen are documented below.

    • Note that the SDD also contains ten custom string fields and ten custom boolean fields, which are, by default, untitled and hidden:

      • custom_string_1 to custom_string_10

      • custom_boolean_1 to custom_boolean_10

      To enable and use these fields, higher-level administrators can modify the field display policy (FDP) for the SDD (at a specific hierarchy). Once the fields are available, designers can reference the fields in custom configuration templates and workflows.

Related Topics

Defaults Page#

On the Defaults page (Site Management > Defaults) you can view and edit a site’s default settings (the site defaults document, or SDD).

You can select the following tabs on this page:

General Defaults Tab#

Option

Default Value

Name

Mandatory. The same name as the site.

Only one instance of site defaults exists for a site.

Default CUCM Device Pool

Cu{CustomerId}Si{SiteId}-DevicePool

Default CUCM Location

Cu{CustomerId}Si{SiteId}-Location

Default CUCM Region

Cu{CustomerId}Si{SiteId}-Region

Default CUCM Date/Time Group

CMLocal

For Provider deployments, choose from the drop-down list.

Default User Locale

The user locale identifies a set of detailed information to support users at the specific location, including language and font. Choose the required user locale from the drop-down list, which contains all user locales available on the CUCM at the selected location.

Default Network Locale

The network locale contains a definition of the tones and cadences that the phones and gateways use at the specific location. Choose the required network locale from the drop-down list, which contains all network locales available on the CUCM at the selected location.

Default User Profile (for User Self Provisioning)

Choose from the drop-down list.

Default CUCM Hunt Pilot Partition

Cu{CustomerId}Si{SiteId}-Feature-PT

Default CUCM Call Pickup Partition

Cu{CustomerId}Si{SiteId}-Feature-PT

Default CUCM Call Park Partition

Cu{CustomerId}Si{SiteId}-Feature-PT

Default CUCM MeetMe Partition

Cu{CustomerId}Si{SiteId}-Feature-PT

Default CUCM Group

Defined via a macro in the CUSTOMER_TEMPLATE and the algorithm chosen for CUCM Group selection, either Least Utilized or Default.

See CUCM Group Selection in the Core Feature Guide for details.

Related Topics

Device Defaults Tab#

Values on the Device Defaults tab are applied to the configuration template associated with adding a subscriber (SubcriberPhonePrePopulate).

Option

Default Value

Default CUCM Phone Product

Cisco 9971

Default CUCM Phone Protocol

SIP

Default CUCM Phone Button Template

Standard 9971 SIP

Default CUCM Phone Security Profile

Cisco 9971 - Standard SIP Non-Secure Profile

Default CUCM Phone Softkey Template

Standard User

Default CUCM Phone SIP Profile

Standard SIP Profile

Default CUCM Phone Presence Group

Standard Presence Group

Default CUCM Phone Common Profile

Standard Common Phone Profile

Default CUCM Phone Line E164 Mask

Enter a E164 mask value that will be applied as a default when devices have not been configured with static values.

Default CUCM Device CSS

Cu{CustomerId}Si{SiteId}-{countryIsoCode}- DP-Emer-CSS

Default CUCM User Subscribe CSS

Internal-CSS

Default CUCM Phone Subscribe CSS

Cu{CustomerId}Si{SiteId}-InternalOnly-CSS

Default CUCM Device Profile Product

Cisco 9971

Default CUCM Device Profile Protocol

SIP

When adding a phone (or when choosing a phone for a subscriber), the phone type you choose must support the protocol you wish to use (SIP or SCCP). If the phone type does not support the protocol, the protocol defaults to the protocol value set up in the site defaults (if the phone type supports the default protocol).

Default CUCM Device Profile Button Template

Standard 9971 SIP

Option

Default Value

Default CUCM Device Profile Line E164 Mask

None. Enter a E164 mask value that will be applied as a default when devices have not been configured with static values.

Default CUCM Device Profile EMCC CSS

None

Default CUCM Remote Destination Profile CSS

None

Default CUCM Remote Destination Profile ReRouting CSS

None

Default CUCM Remote Destination Profile Line E164 Mask

None. Enter a E164 mask value that will be applied as a default when devices have not been configured with static values.

Use National Mask Format

When this check box is selected, the E164 Mask will use the National format of the associated E164 Number.

For example, if the E164 Number has been added in the format +44 1234 5000, and this check box is selected, the E164 Mask on the device will have the International Dialing Code prefix removed e.g. +44, and a ‘0’ will be prefixed to the number e.g. 012345000.

Note:

For Quick Add Subscriber, set the following value in the E164 Mask field of the relevant phone, device profile and remote destination profile configuration template {{ macro.SDD_QAS_E164Number_MCR }}. See the “Reference CUCM Phone Template” CFT for an example configuration.

Line Defaults Tab#

Values on the Line Defaults tab are applied to the configuration template associated with adding a line (line-cft).

Option

Default Value

Default CUCM Line BLF Presence Group

Standard Presence Group

Default CUCM Line Voicemail Profile

None

Default CUCM Line Partition

Default CUCM Line Alternate E164 Partition

None

Default CUCM Line CSS

Cu{CustomerId}Si{SiteId}-InternalOnly-CSS

Default CUCM Line Call Forward CSS

Internal-CSS

Default CUCM Line Call Forward No Answer CSS

Internal-CSS

Default CUCM Line Call Forward All CSS

Internal-CSS

Default CUCM Line Call Forward No Answer Internal CSS

Internal-CSS

Default CUCM Line Call Forward Busy CSS

Internal-CSS

Option

Default Value

Default CUCM Line Call Forward Busy Internal CSS

Internal-CSS

Default CUCM Line Call Forward No Coverage CSS

Internal-CSS

Default CUCM Line Call Forward No Coverage Internal CSS

Internal-CSS

Default CUCM Line Call Forward On Failure CSS

Internal-CSS

Default CUCM Line Call Forward On Failure Internal CSS

Internal-CSS

Default CUCM Line Call Forward Not Registered CSS

Internal-CSS

Default CUCM Line Call Forward Alternate Party CSS

CU1-DummyBlk-CSS

Default CUCM Line Call Forward Secondary CSS

Internal-CSS

User Defaults Tab#

Option

Default Value

Default System User Role

{SiteName}SelfService

Default CUCM User BLF Presence Group

Standard Presence group

Default CUCM Service Profile

None

Default Self-service Language

Choose from the drop-down list of installed Self-service languages. Default is English (en-us).

Note

When selecting the Default System User Role, the selection options include roles where the Hierarchies Allowed list includes sites.

See: Add and Edit Roles.

CUC Defaults Tab#

For more information about the settings on this tab, see:

Cisco Unity Connection Localization

Option

Default Value

Default CUC Phone System

This field is populated by the Voice Mail workflow when a Voice Mail pilot number is associated with a site. Likewise, the field is reset (Empty) when the Voice Mail pilot number is disassociated from a site.

Default CUC Subscriber Template

This field is populated by the Voice Mail workflow when a Voice Mail pilot number is associated with a site. Likewise, the field is reset (Empty) when the Voice Mail pilot number is disassociated from a site.

Default CUC HTML Notification Template

Default_Dynamic_Icons

Default CUC SMPP Provider

None

Default CUC TimeZone

None. Choose from the drop-down list, for example: GMT-05:00-America-New_York. The timezones available in this drop-down are those added in Services > CUC Localization > CUC TimeZone Filters (see cross reference below).

You can also manually enter a valid timezone index value in this field, for example 035 for (GMT-05:00) Eastern Time (US and Canada). Note that the code entered must already be installed on the CUC server associated to this site.

Default CUC Language

None. Choose from the drop-down list, for example: English-US. The languages available in this drop-down are those in Services > CUC Localization > CUC Language Filters (see cross reference below).

You can also manually enter a valid Locale ID (LCID) value for the language in this field, for example 1036 for French - France. Note that the code entered must already be installed on the CUC server associated to this site.

Default Language That Callers Hear

None. Choose from the drop-down list:

  • Inherit Language From Caller

  • Use System Default Language

  • [Use the User Language] e.g. English (United States). See “Default CUC Language” above.

  • [Choice of Languages] e.g. Spanish (Spain Traditional). See “Default CUC Language” above).

HotDial Defaults Tab#

Option

Default Value

Default PLAR CSS

None

Default HotDial TimeZone

None

Overbuild Defaults Tab#

This tab defines how imported objects are moved to the site hierarchy during an overbuild.

Note

The Overbuild Defaults tab in the Site Defaults is accessible only to Provider and Reseller administrators.

Important

It is recommended that you request support from a system integrator for all managed services, Day 2 overbuild projects).

The table describes the settings on this tab:

Field

Description

Include Site for Overbuild

Defines whether the site is included in the overbuild.

Create Internal Number Inventory at Customer

Defines whether to create the internal number inventory only at the site level, or only at the customer level.

When set to True (checkbox selected), the internal number inventory is created only at the customer level, and will be used by all sites belonging to that customer.

The default is False.

CAUTION: If overbuild has already been run for a site and the internal number inventory has been created for the site, if Create Internal Number Inventory is enabled and you run overbuild for the same site, a duplicate set of internal number inventory is created at the customer. The same applies if Create Internal Number Inventory at Customer is enabled when the overbuild is run for the site, if it is then disabled and overbuild is run again, a duplicate set of internal number inventory is created at the site.

Additional Device Pools

By default, if a site is included for overbuild, the Default CUCM Device Pool on the General Defaults tab must match the device pool of phones that have been imported in order for these and their related objects to be moved to the site at which the Site Defaults Doc exists.

The Run Overbuild tool uses the device pool to determine the devices and models to move to the site where the site defaults are defined. You can however add additional device pools, so that more than one device pool from those of the imported phones can be moved to the same site.

Additional device pools are selected from the Device Pool Name drop-down, as instances of the Additional Device Pools group control.

The names of the additional device pools can be renamed to the Default Device Pool name (as defined on the General Defaults tab) if Replace with Default Device Pool is selected.

Overbuild Device Control

Options are:

  • Move all devices - when True, all matching and related imported devices are moved to the site.

  • Limit moved devices - when True, options display to choose devices to import to the site (as on Run Overbuild page)

Move Filter Criteria Tab#

This tab defines the rules the system uses to match users to sites when syncing in users, and to determine whether users should be moved directly to the site as subscribers.

  • The MS 365 Model Filter Criteria model filter criteria you can choose (depending on the user type you’re syncing in, for example, Microsoft, LDAP, CUCM, Cisco Webex), is configured in the Admin Portal, via (default menus):

    • Customizations > Model Filter Criteria, or in:

    • Flow Through Provisioning Configuration > Model Filter Criteria

  • The Move by Number check box (unchecked by default) is used for MS Teams users. When checked:

    • it requires that all numbers are pre-loaded

    • only if the synced-in MS Teams user’s LineUri matches a pre-loaded internal number at a site, will user data be moved to that site

    • current users at customer level will be moved to the site during Overbuild (if the Include Site for Overbuild check box is enabled on the Overbuild Defaults Tab).

    • MS Teams users will be moved directly to the site during MS Teams user sync.

Note

The order of processing of these two options are:

  1. MS 365 Model Filter Criteria is processed first if it is selected and the filter exists.

  2. Move by Number is processed second.

In other words, when a user’s details match the model filter criteria, the system will move the user according to the filter criteria. Otherwise, the system will attempt to move the user by number. If neither option is applicable, the user is not moved and remains at the current hierarchy.

Related Topics

MS Teams Tab#

Important

From release 21.4-PB2 onwards, License Management has been removed and is no longer used to control the logic with managing licenses. VOSS Automate will honor any license-related configuration in the Configuration Templates and related Workflows. This includes Quick Subscriber, Quick Offboard Subscriber, associated Quick Add Groups and general Subscriber Management.

It is advised that administrators evaluate their current Configuration Templates and ensure that if any licensing logic exists in the templates, that this is correct as it will be applied when invoked.

Also see the Licensing Users for MS Teams and Teams Phone by Group Membership topic in the Core Feature Guide.

The table describes settings on this tab:

Option

Description

Enterprise Voice

Defines whether to provision MS Teams users with the Enterprise Voice service.

MS Teams Direct Routing

Defines whether MS Teams Direct Routing is disabled on the PBX or in the SBC.

Default Tenant Dial Plan

Defines the default tenant dial plan for the site. For details, see Configure Microsoft Tenant Dialplan in the Core Feature Guide.

Default MS Teams Policies

These drop-downs allow you to choose the MS Teams policies to use as defaults in the SDD.

Policies are synced in to VOSS Automate from MS Teams.

Choosing a default policy for a site in the SDD automatically assigns the policy to subscribers at the site. When creating a subscriber via Quick Subscriber, the SDD is used, but you can also edit the configuration template for the Quick Add Group (QAG) to use a policy different to the SDD, or you can edit a subscriber directly to choose a different policy for that subscriber.

Note that Teams Upgrade Policy is read-only in the Admin Portal as (at the time of writing) it is deprecated in the Teams online portal.

See Introduction to Microsoft Teams Policies in the Core Feature Guide

Default Calling Line Identity

Default Usage Location

The country for default usage.

Webex Tab#

The table describes settings on this tab:

Option

Description

Webex Location ID

The Webex location to which the site is mapped. Webex locations, numbers and users with location ID matching this site, will be synced to it.

Webex App - Use Organization’s Domain

Displays only when:

  • The entitlement profile allows the Webex App service

  • A Webex App server is configured

  • The subscriber and Webex App user have the same email address

  • Subscriber does not already have Jabber clients

  • CUCM calling behavior is not yet configured for the Webex App user

Enabling this option hides the following field: Webex App - UC Manager Profile

Default (when displayed) is unchecked (clear).

When enabled, Webex App provisioning via QAS refers to values generated via the following named macros in the device/spark/User configuration template (CFT):

  • SDD_WtCallBehaviourUcManagerProfile

  • SDD_WtUseOrgDomain

When the CFT with these macros is chosen for the QAS, the QAS uses site default values to provision Webex App (the macros allow QAS to determine whether the user has a Jabber client and whether CUCM calling behavior is configured).

Webex App - UC Manager Profile

Displays only when the following checkbox is clear (not selected): Webex App - Use Organization’s Domain

Choose the UC Manager profile from the drop-down.

Options in the drop-down are the UC manager profiles added via UC Manager Profile (device/spark/CallingProfile).
For Webex Location ID, also see Webex Locations.

Related Topics