6682 SMS Gateway - SQL logging, MySQL table layout

Search the manual:

Overview

OZEKI NG SMS Gateway - Product Guide

Contents | Search

Home > Product Manual > User Guide > Configuration > SQL logging > MySQL table layout

Advanced traffic queries

Administrator's guide

Developers Guide

Examples and Solutions

Appendix

FAQ

Feature list

Commercial Information

Contact Us!

If you wish to get further information, do not hesitate to contact us!

E-mail: info@ozekisms.com

If you have a technical question, please submit a support request on-line.

Callcenter developers
If you are working on telephone solutions, please check out the Ozeki VoIP SIP SDK.
It can be used to create:

Webphone solutions:
- Adobe Flash video phone
- Silverlight video phone
- Web to web calls
- Web to VoIP calls

Custom SIP clients:
- Silverlight SIP VoIP client
- Flash SIP VoIP client
- C# .net SIP VoIP client
- ASP .net SIP VoIP client
- Web based SIP VoIP client

Custom VoIP solutions:
- VoIP SIP softphones
- VoIP call center clients
- VoIP IVR systems
- VoIP predictive dialer systems
- VoIP auto dialer systems
- VoIP call assistant
- VoIP call recording systems
- VoIP intercom solutions

SQL Reporting in the SMS Gateway - Database layout (MySQL)

This page gives you the database connection information and the database layout if you want to setup SQL reporting in a MySQL database server. SQL reporting makes it possible to keep track of all incoming and outgoing messages in the system regardless of who sent it.

To setup SQL reporting with MySQL, you need to install the MySQL ODBC v5 driver.
You can find information on how to install this driver in the MySQL ODBC v5 installation guide.

The database connection type, you should choose is:

Odbc

The database connection string you should use is:

Driver={MySQL ODBC 5.1 Driver};Server=127.0.0.1;Database=ozekisms;User=ozeki;Password=abc123;Option=4;

The recommended database table layout for SQL reporting into a MySQL database contains two database tables called outbox and inbox. Their definitions are displayed in the following section.

CREATE TABLE outbox ( id int not null auto_increment primary key, username varchar(30), msgtype varchar(160), msgid varchar(60), callbackid varchar(255), sender varchar(30), receiver varchar(30), msgsubject varchar(1024), msgdata text, acceptedfordeliverytime datetime, deliveredtonetworktime datetime, deliveredtohandsettime datetime, operator varchar(30), route varchar(30), status varchar(130), errormessage varchar(1024), cost varchar(10), INDEX(msgid) ) charset=utf8; CREATE TABLE inbox ( id int not null auto_increment primary key, username varchar(30), msgtype varchar(160), msgid varchar(60), sender varchar(30), receiver varchar(30), msgsubject varchar(1024), msgdata text, senttime datetime, receivedtime datetime, operator varchar(30) ) charset=utf8;

If you want to change these table definitions to support your requirements, do not forget to review (and change if necessary) the SQL templates that are configured in the server preferences form.

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