[Index]
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.
Settings are enabled or disabled using a drop-down and can be one of 3 values:
The following tabs are available:
Number Inventory
Include the Number Inventory description in all number drop-downs: when the Number Inventory is managed from the Number Management menu, descriptions can be added to the numbers (for example, "CEO number"). Default = No.
This setting controls the display where the number is listed on a form drop-down. The description will be displayed if the setting is Yes.
Enable Number Inventory Cooling:
Default = False (not enabled).
Choose Yes from the drop-down to enable number cooling. If the inherited value is set to True, number cooling is already enabled.
See "Number Cooling" for more information.
Number Inventory Cooling Duration (Days):
Default = 30 days.
If you want to choose a different value from the inherited value, then enter the required number of cooling duration days in this field.
Webex Teams
GlobalSettings
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
Number Inventory | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Include the Number Inventory description in all number dropdowns | This setting controls the lines dropdowns in the GUI. The default value is No which means no description will be appended to the list. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Number Inventory Cooling |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_auto_move_ini_into_cooling] field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Number Inventory Cooling Duration (Days) |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Current value of [global_setting_cooling_duration] field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Webex Teams | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Retain a Webex Teams User when a Subscriber is deleted. | This setting is used to determine if a Webex Teams user needs to be deleted when a Subscriber is deleted. The default behaviour is No which means that the Webex Teams user will be deleted be default. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Send SNMP trap message when the Webex Teams Refresh Token expires. | This setting is a flag to control if a SNMP trap message should be send to the SNMP server. The default settion is No which means no message will be send. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Webex Teams 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 Teams Refresh Token expires' setting is set to false. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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 send 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. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Flow Through Provisioning | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enable Flow Through Provisioning | This setting controls if Flow Through Provisioning is enabled ot not. The default setting is No. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Provisioning after LDAP Add Sync | This setting controls if Flow Through Provisioning on LDAP Add sync is enabled ot not. The default setting is No. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Provisioning after LDAP Update Sync | This setting controls if Flow Through Provisioning on LDAP Update sync is enabled ot not. The default setting is No. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Provisioning after LDAP Delete Sync | This setting controls if Flow Through Provisioning on LDAP Delete sync is enabled ot not. The default setting is No. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Provisioning Workflow to execute after LDAP Add Sync | This setting stores the Flow Through Provisioning PWF name to execute when LDAP Add sync executes. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Provisioning Workflow to execute after LDAP Update Sync | This setting stores the Flow Through Provisioning PWF name to execute when LDAP Update sync executes. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Provisioning Workflow to execute after LDAP Delete Sync | This setting stores the Flow Through Provisioning PWF name to execute when LDAP Delete sync executes. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Quick Add Subscriber CFT to use | This setting stores the Flow Through Provisioning QAS CFT name to use adding a Subscriber. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
The current resolved value for this setting at the current hierarchy. |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Update of LDAP User after Flow Through Provisioning | This setting controls if the LDAP User is allowed to be updated after Flow Through Provisioning. The default setting is No. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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. |
|