Routing at the SQL level
If you setup an SQL to SMS gateway configuration, you might want to
control which SMSC connection or GSM modem is used to send out your SMS
messages. In other words you may ask is it possible to drive the least
cost routing function when we are presenting SMS messages to Ozeki via
the SQL Server table method? Ideally there would be something we could
write into the table, without having to load all the recipients into Ozeki.
The answer is yes, you can do it. To control which service provider connection
or GSM modem you wish to send out the messages at the SQL level, you need to do the following:
1.) Configure the Database user to enable "Allow routing table override" in the
"Advanced" tab of the Database user configuration form.
2.) The next step is to provide a unique "Service provider name" fore each
service provider connection. For example if you use two GSM modems, you can
enter "Modem1" into the "Service provider name:" field in the configuration form
of the GSM modem connection for the first modem and "Modem2" for the second
modem. Of course you can choose any name you like.
3.) After applying these settings when you insert an SMS message into the
ozekimessageout database table, all you have to do is set the "operator" field
to "Modem1" if you wish to send out the message on the first GSM modem. You can
enter "Modem2" into this field if you wish to send out the message on the second
If you want to set static routes, in the Ozeki SMS Gateway, you can
use the Inbound routing and Outbound routing tables.