help_documentation
Σύνολο εγγραφών στον πίνακα: 1581
| help_id | help_title | help_text |
|---|---|---|
| settings-user_hide_realtime_enabled | Enable User Hide RealTime | <QXZ>This setting allows a User Modify setting to be changed to allow a user to be hidden from all managers in the Real-Time Report. Default is 0 for disabled.</QXZ> |
| settings-manual_auto_next | Enable Manual Dial Auto Next | <QXZ>This setting allows the campaign setting to be enabled forcing a manual dial after X seconds in a manual or inbound manual dial mode. Default is 0 for disabled.</QXZ> |
| settings-manual_dial_validation | Enable Manual Dial Validation | <QXZ>This setting if set to 1 will allow you to enable the Manual Dial Validation feature on a per-campaign basis. If set to 2 the Manual Dial Validation feature will be forced as enabled on all campaigns on the system. The default is 0 for disabled.</QXZ> |
| settings-contacts_enabled | Contacts Enabled | <QXZ>This setting enables the Contacts sub-section in Admin which allows a manager to add modify or delete contacts in the system that can be used as part of a Custom Transfer in a campaign where an agent can search for contacts by first name last name or office number and then select one of many numbers associated with that contact. This feature is often used by operators or in switchboard functions where the user would need to transfer a call to a non-agent phone. Default is 0 for disabled.</QXZ> |
| settings-call_menu_qualify_enabled | Call Menu Qualify Enabled | <QXZ>This setting enables the option in Call Menus to put a SQL qualification on the people that hear that call menu. For more information on how that feature works, view the help for Call Menus. Default is 0 for disabled.</QXZ> |
| settings-alt_ivr_logging | Call Menu Alt DTMF Logging | <QXZ>This setting enables the option in Call Menus to log the DTMF responses to an alternate database table. This can be used in addition to the default DTMF lead logging option. Default is 0 for disabled.</QXZ> |
| settings-allow_ip_lists | Allow IP Lists | <QXZ>This setting allows the IP Lists admin section to be used, as well as the User Group options for web access whitelists and the System Settings option for a system-wide web blacklist. Default is 0 for disabled.</QXZ> |
| settings-system_ip_blacklist | System IP Blacklist | <QXZ>If Allow IP Lists above are enabled, this option will allow you to set an IP List as a blacklist for IP addresses that are not able to access the web resources of this system. Default DISABLED.</QXZ> |
| settings-level_8_disable_add | Level 8 Disable Add | <QXZ>This setting if enabled will prevent any level 8 user from adding or copying any record in the system, no matter what their user settings are. Excluded from these restrictions are the ability to add DNC and Filter Phone Groups numbers and the Add a New Lead page. Default is 0 for disabled.</QXZ> |
| settings-script_remove_js | Script Text Remove JS | <QXZ>This setting if enabled will remove any javascript that is included in the script text for a script. This is considered a security feature to prevent cross-site scripting, or XSS. Default is 1 for enabled.</QXZ> |
| settings-admin_list_counts | Admin List Counts Link | <QXZ>This setting gives you the option to display list counts by clicking on the -show lists leads counts- link at the top of the Lists listing and the Campaign modify screens. Default is 1 for enabled.</QXZ> |
| settings-allow_emails | Allow Emails | <QXZ>This is where you can set whether this system will be able to receive inbound emails in addition to phone calls.</QXZ> |
| settings-allow_chats | Allow Chats | <QXZ>This is where you can set whether this system will be able to receive incoming chats in addition to phone calls, as well as allow agent-to-agent and agent-to-manager chatting.</QXZ> |
| settings-chat_timeout | Chat Timeout | <QXZ>This is where you can set how long a customer chat can stay alive after the customer has navigated away from or closed their chat window. When the timeout is reached the chat is closed.</QXZ> |
| settings-chat_url | Chat URL | <QXZ>This is the location where you have placed the chat web pages for customer use.</QXZ> |
| settings-agent_push_events | Agent Push Events | <QXZ>This setting will enable the sending of events from agent screens to the URL defined below. Default is 0 for disabled.</QXZ> |
| settings-agent_push_url | Agent Push URL | <QXZ>If Agent Push Events are enabled above, this is the URL that the events will be sent to. The variables that you can use within the URL are --A--user--B--, --A--event--B--, --A--message--B--, --A--lead_id--B--. Since this function uses AJAX, it must reference a local script on the web server. If you want to reference an external web address then you should use the get2post.php script that can be found in the extras directory.</QXZ> |
| settings-log_recording_access | Log Recording Access | <QXZ>This option if enabled allows the logging of user access to call recordings. It also requires the User setting Access Recordings to be set to 1 to allow a user to access call recordings. Default is 0 for disabled.</QXZ> |
| settings-recording_buttons | Recording Buttons Type | <QXZ>This option allows you to choose the appearance of the recording buttons on the agent screen. START_STOP will show a START RECORDING button if the call is not recording and a STOP RECORDING button when the call is recording. The RECORDING option will show a red NOT RECORDING button if the call is not recording and a green RECORDING button when the call is recording. If NOGAP is part of the option, then the space below the recording button will be removed. If 2xHEIGHT is part of the option, then the recording button will be double the height. Default is START_STOP.</QXZ> |
| settings-mute_recordings | Allow Mute Recordings | <QXZ>This option if enabled allows you to enable the MUTE RECORDING button on the agent screen by campaign and-or user. This feature is only tested with systems running Asterisk 13. You should not mute recordings for more than 15 minutes at a time. Default is 0 for disabled.</QXZ> |
| settings-enable_auto_reports | Enable Automated Reports | <QXZ>This option if enabled allows you access to the Automated Reports section where you can set up reports to run at scheduled times and be delivered by email or FTP. Default is 0 for disabled.</QXZ> |
| settings-first_login_trigger | First Login Trigger | <QXZ>This setting allows for the initial configuration of the server screen to be shown to the administrator when they first log into the system.</QXZ> |
| settings-require_password_length | User Password Minimum Length | <QXZ>If set above 0, this setting will require that user passwords, phone and server passwords, and system settings default passwords be at least this minimum length of characters when those records settings are modified on the Modify pages. The most important factor in password security is the length of the password, and user passwords in this system can be up to 100 characters in length. Default is 0 for disabled.</QXZ> |
| settings-two_factor_auth_hours | Two-Factor Admin Auth Hours | <QXZ>Two-Factor-Authentication, 2FA for short, adds a required second step to the login process through a method other than a password, such as an Email, Phone Call or Text-Message -SMS-. This 2FA Admin Auth Hours field is where you define the number of hours each auth will last for a web admin user, or until the user logs out. 2FA can also be enabled for agent screen logins using the setting below. Default is 0 for 2FA disabled. WARNING, if you enable this without properly configuring the 2FA settings container below, you will lock all users out of the admin web screens, and a System Administrator will have to fix your system. Also, you will need to configure each user email and-or mobile phone number for all active web admin users.</QXZ> |
| settings-two_factor_auth_agent_hours | Two-Factor Agent Auth Hours | <QXZ>Two-Factor-Authentication, 2FA for short, adds a required second step to the login process through a method other than a password, such as an Email, Phone Call or Text-Message -SMS-. This 2FA Agent Auth Hours field is where you define the number of hours each auth will last for agent screen users. 2FA can also be enabled for admin logins using the setting above this one. Default is 0 for 2FA disabled. WARNING, if you enable this without properly configuring the 2FA settings container below, you will lock all users out of the agent web screens, and a System Administrator will have to fix your system. Also, you will need to configure each user email and-or mobile phone number for all active agent screen users.</QXZ> |
| settings-two_factor_container | Two-Factor Auth Config Container | <QXZ>Must be a valid 2FA_SETTINGS Container Type for 2FA to work. For more information on the settings that can be used in that container, please see the -2FA_TWO_FACTOR_AUTHENTICATION.txt- document.</QXZ> |
| settings-user_account_emails | User Login Link Emails Allowed | <QXZ>The feature will allow you to click on a link from the User Modify page to send an email to an agent with a shortcut URL web address that will allow them to more easily log in to the agent screen. You can select options to send these emails with or without the user password included. Default is DISABLED.</QXZ> |
| settings-phone_defaults_container | Default Phones Settings Container | <QXZ>This feature allows you to use a settings container of the type PHONE_DEFAULTS to pre-load numerous settings into the phone creation form and create new phones with these values pre-set. Refer to the PHONE_DEFAULTS settings container for an example of a container with all available settings that can be pre-set. Default is ---DISABLED---.</QXZ> |
| settings-default_phone_registration_password | Default Phone Registration Password | <QXZ>This is the default registration password used when new phones are added to the system. Default is test.</QXZ> |
| settings-default_phone_login_password | Default Phone Login Password | <QXZ>This is the default phone web login password used when new phones are added to the system. Default is test.</QXZ> |
| settings-default_server_password | Default Server Password | <QXZ>This is the default server password used when new servers are added to the system. Default is test.</QXZ> |
| settings-report_default_format | Report Default Format | <QXZ>Determines whether the reports will default to display in text or html format. Default is TEXT.</QXZ> |
| settings-slave_db_server | Secondary Database Server | <QXZ>If you have a MySQL secondary, or replicating, database server then enter the local IP address for that server here. This option is currently only used by the selected reports in the next option and has nothing to do with automatically configuring MySQL primary-secondary replication. Default is empty for disabled.</QXZ> |
| settings-reports_use_slave_db | Reports to use Secondary DB | <QXZ>This option allows you to select the reports that you want to have use the MySQL secondary database as defined in the option above instead of the master database that your live system is running on. You must set up the MySQL secondary replication before you can enable this option. Default is empty for disabled.</QXZ> |
| settings-custom_reports_use_slave_db | Custom Reports to use Secondary DB | <QXZ>This option allows you to select the custom reports that you want to have use the MySQL secondary database as defined in the option above instead of the master database that your live system is running on. You must set up the MySQL secondary replication before you can enable this option. Default is empty for disabled.</QXZ> |
| settings-default_field_labels | Default Field Labels | <QXZ>These fields allow you to set the name as it will appear in the agent interface as well as the administrative modify lead page. Default is empty which will use the hard-coded defaults in the agent interface. For the first 19 fields, which are form entry fields, you can also set a label to ---HIDE--- to hide both the label and the field. Another option for most fields is ---READONLY--- which will display but not allow an agent to modify the field. One more option for most fields is ---REQUIRED--- which will force an agent to populate that field on all calls before being able to hang up and disposition each call. For the REQUIRED option to work, the campaign must have Allow Required Fields enabled.</QXZ> |
| settings-admin_screen_colors | Admin Screen Colors | <QXZ>This feature allows you to set different color schemes and logo for the administrative web screens. These can be defined in the Screen Colors section. Default is default, for the standard blue screen colors</QXZ> |
| settings-agent_screen_colors | Agent Screen Colors | <QXZ>This feature allows you to set different color schemes and logo for the agent screen. These can be defined in the Screen Colors section. Default is default, for the standard blue screen colors</QXZ> |
| settings-agent_chat_screen_colors | Agent Chat Screen Colors | <QXZ>This feature allows you to set the different colors that are used for the users chatting within the internal chat window in the agent screen. These can be defined in the Screen Colors section, and only the five standard and three alternate colors are used. Default is default, for a standard set of eight colors</QXZ> |
| settings-label_hide_field_logs | Hide Label in Call Logs | <QXZ>If a label is set to ---HIDE--- then the agent call logs, if enabled on the campaign, will still show the field and data unless this option is set to Y. Default is N.</QXZ> |
| settings-qc_features_active | QC Features Active | <QXZ>This option allows you to enable or disable the QC or Quality Control features. Default is 0 for inactive.</QXZ> |
| settings-qc_claim_limit | QC Claim Limit | <QXZ>This option allows you to put a limit on the number of QC records an agent can claim for themselves without finishing them. Default is 3.</QXZ> |
| settings-qc_expire_days | QC Expire Days | <QXZ>This option allows you to limit the number of days an unclaimed QC call will be available to claim and evaluate. Default is 3 days.</QXZ> |
| settings-default_webphone | Default Webphone | <QXZ>If set to 1, this option will make all new phones created have Set As Webphone set to Y. Default is 0.</QXZ> |
| settings-webphone_systemkey | Webphone System Key | <QXZ>If your system or provider requires it, this is where the System Key for the webphone should be entered in. Default is empty.</QXZ> |
| settings-default_codecs | Default Codecs | <QXZ>You can define a comma delimited list of codecs to be set as the default codecs for all systems. Options for codecs include ulaw, alaw, gsm, g729, speex, g722, g723, g726, ilbc, opus, slin, g719,... Default is empty.</QXZ> |
| settings-custom_dialplan_entry | Custom Dialplan Entry | <QXZ>This field allows you to enter in any dialplan elements that you want for all of the asterisk servers, the lines will be added to the default context.</QXZ> |
| settings-reload_dialplan_on_servers | Reload Dialplan On Servers | <QXZ>This option allows you to force a reload of the dialplan on all Asterisk servers in the cluster. If you made changes in the Custom Dialplan Entry above you should set this to 1 and submit to have those changes go into effect on the servers.</QXZ> |
| settings-noanswer_log | No-Answer Log | <QXZ>This option will log the auto-dial calls that are not answered to a separate table. Default is N.</QXZ> |
| settings-did_agent_log | DID Agent Log | <QXZ>This option will log the inbound DID calls along with an in-group and user ID, if applicable, to a separate table. Default is N.</QXZ> |