Search the manual:

Overview Quick start Download Manual How to buy FAQ Contact Us
OZEKI NG SMS Gateway - Product Guide

Multiple keywords Contents | SearchOutbound routing

Home > Product Manual > User Guide > Configuration > Inbound Routing > SQL routing

SMS Gateway SMS Gateway Home

  Product Manual
  Introduction
  SMS technology
  Installation Guide
  User Guide
  Quick Start Guide
  User Interface
  Configuration
  Inbound Routing
  Multiple keywords
  SQL routing
  Outbound routing
  SQL logging
  Source routing
  Sender address
  Content manipulation
  Charset handling
  Client software
  Administrator's guide
  Developers Guide
  Examples and Solutions
  Appendix
  FAQ
  Feature list
  Commercial Information
  Search
 



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

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 GSM modem.

If you want to set static routes, in the Ozeki SMS Gateway, you can use the Inbound routing and Outbound routing tables.



Next page: Outbound routing
Copyright © 2000 - 2013 Ozeki Informatics Ltd.
All rights reserved

Software PBX for Windows | VoIP SDK   |   Legal information   |   Privacy policy   |   Terms of use
Please, address your inquiries to info@ozekisms.com