Contents

Database Connections

Database connections are important, because they allow a campaign to select a contact list, without specifying any details concerning the location of that file. To make this connection, Dialer makes use of a Universal Data Link (UDL) connection.

Since Interaction Dialer reads and updates campaign tables using UDL, UDL files must be defined before contact lists or campaigns are configured in Dialer. A UDL file encapsulates everything that a DBMS server needs to know to integrate with an application such as Interaction Dialer. More specifically, UDL connections provide a software layer that an application (such as Dialer) can use to communicate with a DBMS. The Central Campaign server uses UDL to connect to OLE DB data sources, such as the contact list, which are under control of a DBMS. Each UDL defines data sources in a generic way that allows conforming applications to work with data.

You cannot define UDL connections in Dialer Manager. Fortunately UDL files are easy to create, using Microsoft's Data Link Properties utility. See Create a UDL File.
Dialer does not support ODBC connections. Dialer uses OLE DB providers.
Any number of campaigns can share the same connection. Campaigns can use different connections but don't need to in most cases. The Default Connection is commonly used for all campaigns.

Default Connection

A default database connection object is created when Interaction Dialer is installed. It is called [Default Connection]. In many cases, [Default Connection] provides all of the database connectivity that a call center needs to run campaigns. While each campaign might use a separate contact list table, typically these tables are stored in only one database. If this is the case, the Default Connection may be used exclusively. You cannot delete the default connection object, but you can modify it or define your own custom connection settings.