Model: view/GlobalSettings

When enabled, dial plan workflows enforce HCS Rules when provisioning Customers, Countries, Site and so on. Default = Inherit.

If your deployment uses a custom or specific dial plan that does not conform to the HCS rules, this setting should be set to No (False).

Defines whether descriptions for the numbers (which can be added when the number inventory is managed via the Number Management menu), display along with the numbers in the drop-down lists. For example, let's say you have a number and its description as follows: 1000 - CEO Internal. When this setting is enabled (Yes), both the number (1000) and its description displays in the lists (when using features such as Quick Add Subscriber).

The default is No.

Defines whether vendor names for the numbers show in number dropdown as an option.

For example, a number 982017206 (which is from Microsoft vendor) will display as 982017206 [Microsoft] in the drop-down list.

Defines whether number types for the numbers show in number drop-down as an option.

For example, a number 982017206 (which is from Microsoft vendor and is of type OperatorConnect will display as 982017206 [OperatorConnect] in the drop-down list.

Defines the availability of numbers in the system when a phone, subscriber, or service associated with the number is deleted, and the number is no longer associated with these entities. Options are:

• Inherit:

  When set to True, number inventory cooling is enabled or disabled based on the setting defined for number inventory cooling at a higher level in the hierarchy.

• Yes (True)

  Enabled at the current hierarchy. Numbers associated with deleted entities are kept in a cooled state for a specified number of days (based on the value defined in the Number Inventory Cooling Duration (Days) field.

  Numbers in a cooled state are unavailable in the system until the cooling period end date is reached, unless they are manually released before the "end cooling period" end date.

• False (No)

  Default. Number inventory cooling is disabled by default.

When number inventory cooling is enabled (Yes/True), this field defines the period (number of days) the number is kept in a cooled state and unavailable for association with a phone user, or service.

The default is 30 days.

Choose a hierarchy level at which the aggregate of available numbers should be calculated (Provider, Reseller, Customer, Site), and displayed in the body of the alert.

The shown data in the body for this hierarchy level is:

• Hierarchy node name
• Hierarchy node type
• Hierarchy full path
• Total numbers available
• Total numbers
• Total percent available

Data is also included for lower hierarchies (as tables and in CSV format). For details, see the following topics:

• Email in the Core Feature Guide
• Number Inventory Alerts in the Core Feature Guide

Defines whether an email is sent to a user when added via Quick Add Subscriber. The default is No.

When set to Yes, and a SMTP server is set up (via the Apps Management menu), then selecting the option to send an email when using Quick Add Subscriber, a welcome email is sent to the new subscriber.

Defines whether to delete an existing, unassigned phone (a phone without an owner), when re-adding a phone with the same name and product type (duplicate phone).

Default is Inherit (No, inherited from the hierarchy above), which triggers a transaction failure if you try adding a duplicate phone, for example, in a QuickAddSubscriber bulk load or when updating a subscriber.

When set to Yes, a system check verifies whether the phone exists and/or if it is already assigned (whether ownerUserName field is populated):

• If the phone exists and is assigned to a different subscriber, the transaction fails.
• If the phone exists and is unassigned, the existing phone is deleted, the phone is re-added, and is assigned to the subscriber you're adding or updating.
• If the phone exists and is already assigned to the subscriber you're working with. The system performs an update.

Defines whether a subscriber's associated desk (hard) phones (phones prefixed with SEP or BAP) are deleted or retained when that subscriber is deleted.

When set to Yes:

• The deleted subscriber's hard phones are retained.
• The deleted subscriber's soft phones (such as Jabber devices) are deleted.
• An additional field displays (Update the Retained Desk Phone with Configuration Template), which allows you to define whether retained phones are updated via a CFT once the subscriber is deleted.

Default is Inherit (set to No).

This setting defines hard phone delete/retain behavior for any method of deleting a subscriber, for example, delete subscriber via the Subscribers list view, or delete subscriber in LDAP import, purge or sync (where delete or purge mode is automatic).

You can view the hard phones associated with the subscriber on the Phones tab in Subscriber settings.

This field displays only when Retain Desk Phones when Subscriber is deleted is set to Yes (True).

Defines whether to update retained hard phones via a configuration template (CFT) when the associated subscriber is deleted.

This feature ships with a default CFT (RemoveOwnerFromPhoneCFT), which clears the phone's Owner User ID if the phone is retained when deleting the associated subscriber. You can choose a different CFT for the update step, if required.

Options are Yes, No, Inherit. Default is Inherit (inherited from the hierarchy above)

Set to Yes to enable. You will need to save this update then refresh the tab to display an additional configuration field (Additional information in Phone dropdowns).

Options are Yes, No, Inherit. Default is Inherit.

Additional information options are Description, First Line, and Description + First Line.

The default, Description, means that the phone description (if defined) displays in the phone selection drop-downs on the Replace Phone configuration screen (Existing Phone tab, Device Name drop-down), and on the Quick Add Subscriber screen, allowing you to search by phone description when choosing a phone from the drop-down.

In the same way, when the additional information option is set to either First Line or Description + First Line, you can search for or choose phones based on this criteria.

The default authentication method to use when a user is synced in or added manually.

The default is Local (inherited).

Maps the Microsoft Azure UserPrincipalName (UPN) attribute to CUCM userIdentity attribute - used in Cisco-Microsoft hybrid configurations where the same user ID is on every user account (MS Teams, CUCM, etc.).

If enabled, the CUCM user's userIdentity attribute is used for the import of MS teams CsOnlineUser and MS 365 Msol user instances.

The default is No (inherited).

Defines the user groups (one or more) that admins will not be allowed to assign to subscribers.

This is to prevent subscribers being incorrectly assigned elevated permissions to system resources that are reserved for users in the groups you specify here.

Fill out the user group names in a colon-separated format, for example, Standard CUCM SuperUser:MyGroupName

Enables/disables Cisco CUCM services. The default is Yes.

When set to Yes, allows an admin user to provision a subscriber with new CUCM services, such as a Cisco phone, Jabber, and Extension Mobility, provided the server is installed, and the entitlement profile and field display policy pass a verification check.

Enables/disables Cisco/Microsoft hybrid services. The default is No.

When enabled, VOSS Automate allows for provisioning users and services from both Cisco and Microsoft devices, and makes available an admin user parent menu called Hybrid Cisco-Microsoft Management, and associated access profiles. For details, see Hybrid Cisco-Microsoft Management in the Core Feature Guide.

Specifies the hierarchy level up to which Quick Add Groups will be searched for. The default is Provider level. (sys and hcs levels are not available.)

When a lookup level is set, selections of available QAGs will be restricted upwards to this lookup level.