[Index]
To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com
Overview
Provider administrators and higher have access to a Global Settings customization menu that allows for the configuration of a number of settings across all hierarchies or per individual hierarchy.
This topic describes the tabs on the Global Settings page (default menu: Customizations > Global Settings)
In the Admin Portal, the read-only value below the drop-down is the current setting (True/False), for options:
To change inherited settings, see How to Change Inherited Settings.
Number Inventory Tab
Enforce HCS Dialplan Rules:
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 which does not conform to the HCS rules, this setting should be set to No.
Include the Number Inventory description in all number drop-downs:
This setting 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.
Include the Number Inventory vendor in all number dropdowns:
This setting 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.
Include the Number Inventory type in all number dropdowns:
This setting defines whether number types for the numbers show in number dropdown 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.
Enable Number Inventory Cooling:
This setting 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.
The table describes the options for this setting:
Option | Description |
---|---|
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. |
True | Enabled, at the hierarchy level you're at. 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 | Default. Number inventory cooling is disabled by default. |
Number Inventory Cooling Duration (Days):
When number inventory cooling is enabled (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.
Related Topics
Number Cooling in the Core Feature Guide
Number Cooling Auto Expiry Schedule in the Advanced Configuration Guide
Number Inventory Alerting Tab
These settings allow for alerts to be raised once the number inventory is running low.
Enable Alert on Available Numbers
By default, this setting is set to Inherit. However, it will not inherit the setting from higher up the tree unless it is explicitly set to Yes or No. Inherit in this instance merely means it is not configured. Set this setting to Yes to enable alerting.
Alert Aggregate Level
Select 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:
Data is also included for lower hierarchies - as tables and in CSV format. For details, see:
Email in the Core Feature Guide
Number Inventory Alerts in the Core Feature Guide
Availability Threshold Percentage
Select or enter a percentage available of the total numbers at which point alerts will be raised. Sample percentages are available to choose from. If available numbers drop below this percentage, alerts will be raised.
Enable Email Group
Set this setting to Yes if you wish email alert notifications should be sent to an email group. The email group needs to be available or should be set up.
Alert Email Group
If Enable Email Group is set to Yes, select the email group. For details on setting up email groups, see: Email Groups.
Ignore Hierarchies With No Numbers
If set to True, hierarchy levels with no numbers are not included in reports.
Note
The email alert message also includes an attachment file NumberThreshold.csv that contains the alert report in CSV format. See: Email HTML Templates.
Related Topics
Email in the Core Feature Guide
Number Inventory Alerts in the Core Feature Guide
Webex App Tab
This tab configures the global settings for Webex App.
The table describes the fields on this tab:
Field | Description |
---|---|
Retain a Webex App User when a Subscriber is deleted | Defines whether to delete Webex App user when a subscriber is deleted. Default is No. |
Send notification when the Webex App Refresh Token expires | Defines whether a notification is sent when the Webex App refresh token expires for a specified customer. A SNMP trap and Webex App message is sent to recipients configured in the email group. |
Webex App Refresh Token expires threshold (in seconds) | The max threshold (in seconds) for when to send a SNMP trap to the SNMP (if Send SNMP trap message when the Webex App Refresh Token expires is enabled). The default is 172800 seconds, which is two days. |
Automatically apply default calling behavior on Webex App user data sync | Whether to apply default calling behavior (set up in Customer settings), to new Webex App users synced in to VOSS Automate. Default is No. |
Generate and send Webex App User CSV file via Webex App message | Whether to generate a CSV file on create/update of Webex App user. Default is No. If enabled (Yes), the CSV file is sent via Webex App to a predefined list of recipients. |
Email group containing recipients of the generated Webex App user CSV file | The group of recipients of the Webex App message with the generated CSV file. The email group is set up on the Email Groups menu. |
Send manual Webex App Workspace configuration steps via Webex App message | Whether manual configuration steps (on Webex App Control Hub) are to be sent on create/update of a Webex App workspace. Default is No. If enabled, the steps are sent via a Webex App message. |
Email group containing recipients of the manual Control Hub steps | Email group recipients of the Webex App message containing the manual configuration steps. |
Quick Add Group for Hybrid Calling Workspace Unified CM users | The Quick Add Group to use when creating dummy CUCM users with line and device for Webex App workspace hybrid calling. |
Related Topics
Quick Add Subscriber Group in the Core Feature Guide
Email in the Core Feature Guide
Email Groups in the Core Feature Guide
Create Webex App Service in the Core Feature Guide
Pexip Conference
Retain a Pexip Conference when a Subscriber is deleted
Defines whether the Pexip conference set up from the subscriber interface is to be removed when the subscriber is deleted. By default the setting is inherited from the hierarchy level directly above the current one.
Email Tab
Allow welcome email to be sent to user after Quick Add Subscriber
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.
Related Topics
SMPT Server in the Core Feature Guide
Email in the Core Feature Guide
Phones Tab
This tab configures the global settings of phones for a site.
Note
These settings only apply to phones within the same site; both the re-added phone and the existing phone must be on the same site.
The table describes the phone global settings on this tab:
Field | Description |
---|---|
Delete existing Unassigned Phone when re-adding an identical phone | 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):
|
Retain Desk Phones when Subscriber is deleted | 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:
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. |
Update the Retained Desk Phone with Configuration Template | 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. |
Field | Description |
---|---|
Include additional information in Phone dropdowns | 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). |
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. |
Related Topics
Replace Phone in the Core Feature Guide.
Quick Add Subscriber for CUCM Users in the Core Feature Guide.
Subscriber, Phones tab in the Core Feature Guide
Voicemail Tab
This tab defines settings for voicemail.
Option | Description |
---|---|
Retain a (Cisco) Voicemail Account when a Subscriber is deleted. | Defines whether to retain a Cisco (CUCM) subscriber's voicemail account when the subscriber is deleted. Default is Yes (true). When set to Yes, the CUCM user's voicemail account is retained when the user is deleted and user sync is executed. |
User Tab
When a user is either synced into or added manually on VOSS Automate, these settings apply by default. The settings can however be modified when adding a user from the User Management menu.
User Default Auth Method
The default authentication method to use a user is synced in or added manually. The default is Local (inherited).
Related Topics
User Authentication Methods in the Core Feature Guide.
Flow Through Provisioning Tab
This tab defines options for sync with flow through provisioning.
Option | Description |
---|---|
Enable Move & Flow Through Provisioning | Defines whether move and flow through provisioning is enabled. The default is No. |
Enable Move & Provisioning after Add Sync | Defines whether move and flow through provisioning on add sync is enabled. The default is No. |
Flow Through Provisioning Criteria | Defines the default flow through provisioning criteria applied to a user to create the subscriber at the site and to assign services. |
Related Topics
Flow Through Provisioning in the Core Feature Guide.
Enabled Services Tab
This tab defines the global settings for enabling/disabling services for different vendors, such as Cisco or Microsoft. Options are Inherit, or Yes/No (True/False).
When provisioning services from two or more vendors, the global setting is the first of a number of system verification checks. For example, when the Enable Cisco CUCM global setting is set to Yes (enabled), the administrator can provision a subscriber with new CUCM services (such as a Cisco phone, Jabber, and extension mobility), only if the CUCM device check (server installed), entitlement profile check, and field display policy check all pass the verification check. In the same way, if for example, the Enable Microsoft global setting is set to No (disabled), and all other checks are set to enabled, existing Microsoft services can be viewed but new Microsoft services cannot be provisioned.
Note
By default, for new installs, the global setting for the following services are inherited from higher levels in the hierarchy (Inherit set to True/enabled):
When upgrading to a version of the system that allows multi-vendor and hybrid subscribers, the default setting for services other than these 5 services is Inherit (False). To provision services to new subscribers (added after an upgrade), you will need to enable the vendor service in global settings.
Related Topics
Multi-vendor Subscribers in the Core Feature Guide
Role-based Access for Multi-vendor Subscriber in the Core Feature Guide
Configure Multi-vendor Subscribers in the Core Feature Guide
Hybrid Cisco-Microsoft Management in the Core Feature Guide
Change Inherited Settings
GlobalSettings
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Number Inventory | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enforce HCS Dialplan Rules | If this setting is set to "Yes", then the dialplan workflows will enforce HCS Rules with regards to provisioning Customers, Countries, Sites, etc. By default this is set to "Inherit", which means it takes the value from higher up in the hierarchy tree. If you're unsure, then keep the default. If your deployment uses a custom or specific dialplan which does not conform to the HCS rules, this setting should be set to "No". |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_enforce_hcs_dialplan_rules] field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Include the Number Inventory description in all number dropdowns | If this is set to "Yes", then the description value in the Internal Number Inventory, will show up as additional information in number drop-downs. For example, let's say you had number '1000' with a description of "CEO Internal". When using Quick Add Subscriber, or similar features, and selecting numbers from a drop-down, you'd see an option of "1000 - CEO Internal". |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Include the Number Inventory vendor in all number dropdowns | If this is set to "Yes", then the vendor value in the Internal Number Inventory, will show up as additional information in number drop-downs. For example, let's say you had number '1000' with a vendor of "Cisco". When using Quick Add Subscriber, or similar features, and selecting numbers from a drop-down, you'd see an option of "1000 [Cisco]". |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Include the Number Inventory type in all number dropdowns | If this is set to "Yes", then the type value in the Internal Number Inventory, will show up as additional information in number drop-downs. For example, let's say you had number '1000' with a type of "DirectRouting". When using Quick Add Subscriber, or similar features, and selecting numbers from a drop-down, you'd see an option of "1000 [DirectRouting]". |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Number Inventory Cooling | This setting controls the reserved state of numbers, when a phone/user/service is deleted, and the number no longer associated with that phone/user/service. When this is set to "Yes" it will keep numbers in a reserved state for a duration as set in the "Number Inventory Cooling Duration (Days)" field. Meaning, the number will not appear as available in drop-downs, until the cooling period has expired. By default, this is set to "Inherit". If the value is "No", then numbers become immediately available after deletion/dissociation from a phone/user/service. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_auto_move_ini_into_cooling] field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Number Inventory Cooling Duration (Days) | This setting control the duration of cooling (reservation) days, when the "Enable Number Inventory Cooling" is turned on. By default, this is set to "Inherit". An admin can override this setting, by replacing "Inherit" with a numeric value such as "14", "30", "100" etc |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_cooling_duration] field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Number Inventory Alerting | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enable Alert on Available Numbers | This setting enables the Number alerting feature. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_ini_enable_alert] field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Alert Aggregate Level | This setting control the aggregate level (Provider/Reseller/Customer/Site/LinkedSite). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_ini_alert_aggregate_level] field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Availability Threshold Percentage | This setting control the aggregate threshold percentage with list of intervals every 5%. When the count of internal number inventory drops below this threshold an alert will be generated. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_ini_alert_threshold] field. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Email Group | This setting enables the Number alerting email to group. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_ini_enable_alert_email] field. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Alert Email Group | This setting control the email group to use when sending the alert notification via email. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_ini_alert_email_group] field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Ignore Hierarchies With No Numbers | This setting control if hierarchies with no numbers should be ignored. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_ini_alert_ignore_zero] field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Webex App | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Retain a Webex App User when a Subscriber is deleted. | This setting is used to determine if a Webex App user needs to be deleted when a Subscriber is deleted. The default behaviour is No which means that the Webex App user will be deleted be default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Send notification when the Webex App Refresh Token expires | This setting is a flag to control whether a notification is sent when the Webex App refresh token expires for a specific customer. This would send both SNMP trap as well as a Webex App message to the recipients configured in the email group below. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Email group containing recipients of the Webex App message for token refresh failure | This setting is used to configure the recipients of the Webex App message sent when the token refresh fails. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Webex App Refresh Token expires threshold (in seconds) | This setting controls the max threshold in seconds for when to send a SNMP trap to the SNMP server. The default is 172800 seconds which is 2 days. This setting has no effect if the 'Send SNMP trap message when the Webex App Refresh Token expires' setting is set to false. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Automatically apply default calling behaviour on Webex App user data sync | This setting is used to determine whether the default calling behaviour will be applied to new Webex App users synced into VOSS Automate. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Generate and send Webex App User CSV file via Webex App message | This setting is used to determine if a CSV import file should be generated on creation or modification of a Webex App user. If enabled the CSV file will be sent via a Webex App message to a configured list of recipients. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Email group containing recipients of the generated Webex App user CSV file | This setting is used to configure the recipients of the Webex App message containing the generated CSV file. This must be a valid email group already defined in the portal. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Send manual Webex App Workspace configuration steps via Webex App message | This setting is used to determine whether manual configuration steps is sent on creation or modification of a Webex App workspace. If enabled the steps will be sent via a Webex App message to a configured list of recipients. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Email group containing recipients of the manual Control Hub steps | This setting is used to configure the recipients of the Webex App message containing the manual Control Hub steps. This must be a valid email group already defined in the portal. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Quick Add Group for Hybrid Calling Workspace Unified CM users | This setting determines which Quick Add Group is used when creating dummy Unified CM users for Webex App workspace hybrid calling. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Pexip Conference | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Retain a Pexip Conference when a Subscriber is deleted. | This setting is used to determine if a Pexip Conference needs to be deleted when a Subscriber is deleted. The default behaviour is No which means that the Pexip Conference user will be deleted be default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Group Assigned by FDP |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Allow welcome email to be sent to user after Quick Add Subscriber | This setting controls if an email needs to be sent to a user when added via Quick Add Subscriber. The default value is No. Email Account and HTML Email Template (Quick Add Subscriber) need to be set up. Please refer to documentation for setting up an Email account. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Phones | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Delete existing Unassigned Phone when re-adding an identical Phone | This setting allows an existing Phone, which has no Owner set, to be Deleted if a Phone with the same Name and Product Type is re-added. The default setting is No. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
This setting allows an existing Phone, which has no Owner set, to be Deleted if a Phone with the same Name and Product Type is re-added. The default setting is No. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Retain Desk Phones when Subscriber is deleted | This setting controls whether or not a subscriber's associated Desk Phones should be retained whenever that subscriber gets deleted. If set to true, then phones starting with 'SEPxxx' and 'BATxxx' will not be removed along with the subscriber, but retained instead. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of the 'Retain Desk Phones' field (global_setting_retain_phones_when_delsubscriber) |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Update the Retained Desk Phone with Configuration Template | This setting controls whether retained phones should also be updated with a CFT or not (blank value means no update will occur). Must be valid existing CFT for device/cucm/Phone |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of the 'Update Retained Phone with CFT' field (global_setting_update_retained_phones_with_cft) |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Include additional information in Phone dropdowns | This setting controls additional information displayed Phone dropdowns (QAS & ReplacePhone only). The default setting is No. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Additional information in Phone dropdowns | This setting controls addition information options for Phone dropdowns (QAS & ReplacePhone Only). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Voicemail | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Retain a (Cisco) Voicemail Account when a Subscriber is deleted. | This setting is used to determine if a (Cisco) Voicemail Account needs to be retained when a Subscriber is deleted. The default behaviour is Yes which means that the Voicemail Account will be retained by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
User | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Default Auth Method | This setting control the user's default auth method when created for the first time |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_user_auth_method] field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Map UPN from CUCM User Identity | This setting is used to map the MS UPN from CUCM User Identity instead of using mapping macros on MS import. When set to true, mappings are created when a hybrid service is assigned to a user. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Update Username during datasync | This setting is used to update the existing VOSS username when a new associated user is imported via a sync. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Flow Through Provisioning | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enable Move & Flow Through Provisioning | This setting controls if Move and Flow Through Provisioning is enabled or not. The default setting is No. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Move & Provisioning after Add Sync | This setting controls if Move and Flow Through Provisioning on LDAP Add sync is enabled or not. The default setting is No. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Flow Through Provisioning Criteria | This setting controls the default Flow Through Provisioning Criteria which is applied to the user. Add instances under the Flow Through Provisioning Criteria menu. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_flow_through_provisioning_subscriber_criteria] field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enabled Services | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enable Cisco CUCM | This setting is used to enable Cisco CUCM (Call Manager) services. The default behaviour is Yes which means that the Cisco UC services will be enabled by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Cisco CUCX | This setting is used to enable Cisco CUCX (Unity) services. The default behaviour is Yes which means that the Cisco CUCX services will be enabled by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Cisco WebEx | This setting is used to enable Cisco WebEx services. The default behaviour is No which means that the Cisco WebEx services will be disabled by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Cisco Webex App | This setting is used to enable Cisco Webex Team services. The default behaviour is No which means that the Cisco Webex Team services will be disabled by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable CCX | This setting is used to enable Cisco CCX (Contact Center Express) services. The default behaviour is No which means that the Cisco CCX services will be disabled by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Cisco Broadworks | This setting is used to enable Cisco Broadworks services. The default behaviour is No which means that the Cisco Broadworks services will be disabled by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Microsoft | This setting is used to enable Cisco Microsoft services. The default behaviour is No which means that the Microsoft services will be disabled by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Avaya | This setting is used to enable Avaya services. The default behaviour is No which means that the Avaya services will be disabled by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Pexip | This setting is used to enable Pexip services. The default behaviour is No which means that the Pexip services will be disabled by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Zoom | This setting is used to enable Zoom services. The default behaviour is No which means that the Zoom services will be disabled by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Cisco / Microsoft Hybrid | This setting is used to enable Cisco / Microsoft hybrid services. The default behaviour is No which means that the Cisco/ Microsoft hybrid services will be disabled by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Avaya / Microsoft Hybrid | This setting is used to enable Avaya / Microsoft hybrid services. The default behaviour is No which means that the Avaya / Microsoft hybrid services will be disabled by default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|