Registry Settings

By default, will return -1 in this scenario.

By default, excludes the retry fields.

Users may change the base set of dialing outcome codes to comply with legacy reporting needs. This registry value allows users to change the abandoned call outcome value from the default value (7).

Users may change the base set of dialing outcome codes to comply with legacy reporting needs. This registry value allows users to change the Agent-specific callback failure due to agent not logged in call outcome value from the default value (32).

Data is only discarded if campaign is still being run.

When set to

• 0 only completed records are purged
• 1 all records are purged

Previously, the Audit table would only purge old records if they had been marked as completed, which can cause slow start up issues as the audit table grows with large data sets.

Users may change the base set of dialing outcome codes to comply with legacy reporting needs. This registry value allows users to change the busy call outcome value from the default value (1).

Softdial CallGem™ doesn't care, but Softdial Campaign Manager™ does. Default is 0 (Local Time). Set to 1 for UTC.

Some users require the ability to process callbacks outside of the compliance call expiry time. With the default setting of 1, calls are limited by call expiry time

From V10.6.670 - if not set, defaults to 1 (ON). If filters are set on the campaign, it will include those filters in the "cleaning" statement e.g. Campaign with filter to pick up records with Contact_ID < 100, will only clean records with Contact_ID <100.

Only ever set this registry value if you have campaigns with overlapping data sets i.e. where the selection criteria for more than one campaign includes the same rows in the same tables.

Some ODBC driver implementations will continue to use broken connections, therefore generating ODBC socket timeout errors. Setting this to 1 forces full closure of the ODBC connection to the database, including any socket connection for the underlying driver.

The default delay (60) allows a further 60 seconds for cleanup to complete.

Limiting the size of this rowset enables customers to open campaigns on very large tables a lot quicker than otherwise possible. The number of rows should be greater than the number of fresh rows to be dialled in a single day on the largest campaign that a tenant runs. A simple rule of thumb for this value would be to take the peak agent count on the largest campaign and multiply by 1200 to give a value.

WARNING: When configuring this value in the registry editor please make sure to select a decimal value rather than hexadecimal. 100,000h is 1,048,576 in base 10. At the time of writing opening a cursor on a 500,000 row table may take 25 seconds for the server to cache the index information for 500,000 rows. By limiting to 200,000 rows this would reduce load times to 10 seconds.

When running an inbound campaign, Softdial Campaign Manager™ needs to interrogate the primary table structure. This is done by opening a rowset cursor and iterating over the column definitions.

A value of 0 does not limit the row count.

There is not wide adoption of the ISO SQL2008 standard for limiting row counts with the syntax FETCH FIRST N ROWS ONLY. The default value of 0 tells Softdial Campaign Manager™ not to modify SELECT statements to limit the row count. This provides for backwards compatibility.

Other legal values are:

• 1 - MS SQL Server, Sybase
• 2 - MySQL
• 3 - PostgreSQL
• 4 - DB2
• 5 - Oracle

Other relational databases that are ISO SQL 2008 conformant should set this value to 4. A single Softdial Campaign Manager™instance can connect to multiple different databases, although in practice this rarely happens. If using Softdial Campaign Manager™ to connect to 2 different DBMS, you should contact Sytel Support for advice.

* From V10.6.393 - default setting changed from 0 to 1 from .

The default value is 00 (UK). This value is also used if the registry key is not present.

For international dialing, set this value to either

• + (if supported by the network equipment), or
• the required international prefix (e.g. 011 for USA, 0011 for Australia).

Altering retry data during a campaign run produces inconsistencies between audit and contact databases.

The default is 5 characters, to be consistent with US zip codes. For other territories with post coding schemes and multiple timezones, this should be set to the number of characters in the longest possible postal code.

Valid values are:

Valid values as ODBCRecordsetType above.

From V10.6.263 - now a tenant level configuration.

Default value of 0 means that periodic cursor reload is disabled.

With long cursor open times this may be reduced.

Overdue retries get purged from cache after a configurable amount of time. This setting allows a minimum number of retries to be cached in order to ensure there is always data available to deliver to Softdial CallGem™.

If your database is updated with fresh data in real-time during the shift, you may need to alter the reload frequency to prevent number starvation at end-of-list.

For MS SQL, they are normally set to SQL_FLOAT which can lead to rounding errors in MySQL.

Set this to <empty> for older versions of Oracle.

When the DB runs out, then the next detection of a cache runout will result in automatic stopping of campaign.

From V10.6.478 - the maximum number of digits supported is 18.

If set, the <UseDoInPreview> setting in the Softdial Telephony Gateway™ config.xml file must also be enabled.

Also makes the Agentless option visible in the Windows and Web clients. To enable, add this key and set to 1.