gammu-smsd-odbc man page
gammu-smsd-odbc — gammu-smsd(1) backend using ODBC abstraction layer to use any supported database as a message storage
New in version 1.29.92.
ODBC backend stores all data in any database supported by ODBC, which parameters are defined by configuration (see gammu-smsdrc for description of configuration options).
For tables description see gammu-smsd-tables.
This backend is based on gammu-smsd-sql.
On Microsoft Windows, Gammu uses native ODBC, on other platforms, unixODBC can be used.
Due to limits of the ODBC interface, Gammu can not reliably detect which SQL engine it is connected to.
In most cases this can be solved by setting SQL setting to correct dialect.
If that fails, you can also tweak the SQL queries to work in used SQL server, see SQL Queries for more details. Still you should set SQL to closest matching SQL dialect.
Before running gammu-smsd you need to create necessary tables in the database. You can use examples given in database specific backends parts of this manual to do that.
You specify data source name (DSN) as Host in gammu-smsdrc. The data source is configured depending on your platform.
Please remember that SMSD might be running in different context than your user (separate account on Linux or as as service on Windows), so the ODBC DSN needs to be configured as system wide in this case (system DSN on Windows or in global configuration on Linux).
On Microsoft Windows, you can find instructions on Microsoft website: https://support.microsoft.com/kb/305599
For unixODBC this is documented in the user manual: http://www.unixodbc.org/doc/UserManual/
Prior to starting SMSD you have to create tables it will use. Gammu ships SQL scripts for several databases to do that:
[smsd] service = sql driver = odbc host = dsn_of_your_database sql = sql_variant_to_use user = username password = password
- SEE ALSO:
Michal Čihař <email@example.com>
2009-2015, Michal Čihař <firstname.lastname@example.org>