Setup FoxPro
for storing call records

In this chapter you can learn how to configure the Ozeki Phone System XE to be able to store call records using a FoxPro database server. You will be provided with the installation steps, the configuration details such as the database connection string, database connection type, and with the recommended database table layout.

To be able to store calling information to a FoxPro database, you need to configure the Call reporter SQL API in the Ozeki Phone System XE in the following way.

During the configuration you have the chances to use OleDb or Odbc connection types.

In case of the OleDb connection you need to choose OleDb type:

OleDb

Connection string for OleDb connection:

Provider=any oledb provider's name;OledbKey1=someValue;OledbKey2=someValue;

If you use Odbc connection type, you need to select Odbc connection type:

Odbc

Connection string for Odbc driver:

Driver={Microsoft Visual FoxPro Driver};SourceType=DBC;SourceDB=c:myvfpdb.dbc; Exclusive=No;NULL=NO;Collate=Machine;BACKGROUNDFETCH=NO;DELETED=NO;

The database connection string has to be modified to match your database.

The connection string and the connection type should be entered on the Call Reporter SQL API configuration form.


Figure 5 - Specifying the connection string for the FoxPro database

In the following figure you can see the SQL templates tab of the Call reporting API. Here, you need to provide the SQL queries that will store the main changes of the calls (e.g. when a call started, forwarded or finished).


Figure 6 - Specifying the SQL queries

After the Call Reporter SQL API has been configured in the Ozeki Phone System XE, the only thing left to do is to create the database tables for Call Reporter SQL API. We recommend you to use the following table layout: 

-- -----------------------------------------------------
-- Table `OzekiPBX`.`ozpbxcalls`
-- -----------------------------------------------------
CREATE TABLE `ozpbxcalls` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `starttime` datetime DEFAULT NULL,
  `source` varchar(150) DEFAULT NULL,
  `callerid` varchar(150) DEFAULT NULL,
  `dialed` varchar(150) DEFAULT NULL,
  `destination` varchar(150) DEFAULT NULL,
  `duration` int(10) DEFAULT NULL,
  `callstate` varchar(150) DEFAULT NULL,
  `recordurl` varchar(150) DEFAULT NULL,
  PRIMARY KEY (`id`)
)

If you have any questions or need assistance, please contact us at info@ozekiphone.com.

Dig deeper!
People who read this also read...

More information