- Product Manual
- Introduction
- Installation Guide
- User Guide
- Developers Guide
- Tutorials
- ASP SMS API
- PHP SMS API
- HTTP SMS API
- Send message
- Receive message
- Billing methods
- Urlencode
- Select operator
- Operate with single message
- Query the addressbook
- Operations with message folders
- Examples
- User handling
- Service Provider Connection Handling
- Reporting API
- Dynamic SMPP parameters
- SQL SMS API
- C# SMS API
- AJAX SMS API
- Delphi SMS API
- Cpp SMS API
- Java SMS API
- VB.NET SMS API
- Python SMS API
- Perl SMS API
- TCL/TK SMS API
- Coldfusion SMS API
- VB 6 SMS API
- Examples and Solutions
- Appendix
- SMS FAQ
- Feature list
- Commercial Information
- Search
Ozeki brings you outstanding
SMS Gateway technology. Use our SMS Server products on Windows,Linux, or Android
C# SMS API
Developers can use our C# SMS API to send SMS from C#.Net. The C# SMS API comes with full source code
PHP SMS API
The ozeki PHP SMS gateway software can be used to send SMS from PHP and to receive SMS usig PHP on your website
SMPP SMS Gateway
SMS service providers use our SMPP gateway solution, that offers a high performance SMPP server and SMPP client gateway with amazing routing capabilities
HTTP SMS API - service provider connection selection
This guide gives information on how you can select an attached GSM Modem or IP SMS service provider connection when you send a message using the HTTP API.
Static routing
In most cases you would use the outgoing routing table to control which connection should be used for an outgoing message. The outgoing routing table can be configured to make the decision based on sending user account, message content, sender and recipient phone number. When a message is being sent, it is matched against the (regular expression) pattern stored in the outgoing routing table. The pattern can match the sending user account, message content, sender and recipient phone number. If the pattern matches the outgoing message, the appropriate rule is applied to decide which GSM modem or IP SMS connection should be used to send the message.
Dynamic routing
If you do not want to use static routes defined in the outgoing routing table, you have to enable the "Allow routing table override." feature on the "Advanced" tab of the user "Configuration form" (Figure 1).
After this option is enabled you can define the serviceprovider name in the HTTP request to specify which GSM modem or IP SMS service provider connection should be used to send the message. (The service provider name is configured in the configuration form of the GSM Modem or IP SMS Service provider connection.) To send a message through a specific modem or IP SMS connection you have to include the "serviceProvider" optional parameter in your request (Figure 2).
Example HTTP request for sending an SMS using GSMModem1:
http://127.0.0.1:9501/httpapi?action=sendMessage&username=admin&password=abc123& recipient=06203105366&messageData=hello&serviceProvider=GSMModem1
More information
- HTTP SMS API - Overview
- HTTP SMS API - sendmessage method
- HTTP SMS API - receivemessage method
- HTTP SMS API - billing method
- HTTP SMS API - SMS service provider connection selection
- HTTP SMS API - Operate with single message
- How to query the addressbook in Ozeki NG SMS Gateway
- Operations with message folders in HTTP SMS API
- HTTP SMS API Examples
- User handling via HTTP API
- Service provider connection handling via HTTP API
- HTTP API for the Reporting function of Ozeki NG SMS Gateway
- Dynamic SMPP parameters via HTTP
- FAQ of the Ozeki NG SMS Gateway