- Product Manual
- Introduction
- Installation Guide
- User Guide
- Developers Guide
- Examples and Solutions
- Appendix
- SMS FAQ
- 1.1 SMS basics
- 1.2 Why is SMS so successful?
- 1.3 Example applications of SMS messaging
- 1.4 SMS number formats
- 1.5 Mobile message types
- 1.6 SMSC
- 1.7 SMS Gateway
- 1.8 Two way SMS systems
- 2.1 Prerequisites
- 2.2 Network requirements
- 2.3 General Information
- 2.4 Message routing
- 2.5 Message types
- 2.6 Delivery reports
- 3.1 GSM modem
- 3.2 SMPP
- 3.3 CIMD2
- 3.4 UCP/EMI
- 3.5 HTTP
- 3.6 SMTP
- 4.1 API
- 4.2 SQL to SMS
- 4.3 HTTP to SMS
- 4.4 E-mail to SMS
- 4.5 Autoreply database
- 5.1 Performance
- 5.2 Logging
- 5.3 Errors
- 5.4 Reporting
- 6.1 Trial version
- 6.2 Licensing
- 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 to SMS gateway
If I uninstall a user named "AAA", then try to create a new user also named "AAA" the system tells me "AAA" already exists, even if it has been uninstalled. How do I delete these uninstalled users definitively?
When you delete a user, it is marked as deleted by the
system. The reason it is not deleted permanently at run time is due to the
internal architecture of the gateway.
You have to restart the
service in Start, Control Panel, Administrative Tools, Services to have the
user removed permanently.
Why are changes in the physical configuration files are not reflected in the web Admin interface?
Configuration files are read when the service is
started.
For performance reasons, configuration information is
stored in memory. You need to restart the Ozeki NG SMS Gateway service in
Start, Control Panel, Administrative Tools, Services in order to have your
configuration changes applied.
Why sometimes do I get a message from my HTTP client user that says that it could not resolve the name corresponding to the URL it is calling?
Your internet connection might be down, or your DNS
server might not return a response to a DNS query.
In most cases,
this problem
happens if your DNS server is temporarily out of service. You can add your
hostname to the C:\WINDOWS\system32\drivers\etc\hosts file to work around
this problem. This file is checked for the hostname entry before a DNS
resolution happens. If the file contains the IP address for the searched
hostname, the IP address in the file is used and no DNS lookup is performed.
I am using the HTTP Client user. Some SMS request messages are served by HTTP queries which are very slow. We see that if the reply from the website takes to long the reply is an empty messages. Is there a way of increasing the time for the http client user to wait longer for a reply from the website?
Yes. You can increase the HTTP submit response timeout.
This setting can be adjusted in the "HTTP Connection" tab of the "HTTP User"
configuration form. The default HTTP timeout value is 30 seconds. This means that
if an SMS comes in it is forwarded instantly to a webpage through HTTP. By
default
When I am sending an SMS message through HTTP API, the "+" sign in the content of SMS and in the phone number are not forwarded to Ozeki NG SMS Gateway. How can I solve this issue?
It happens, because you have forgotten to encode the phone number and SMS message. You need to send the HTTP Request in encoded format, and the Ozeki NG SMS Gateway will decode it.
More information
- SMS basics
- Why is SMS so successful?
- Example applications of SMS messaging
- SMS number formats
- SMS and MMS message types
- Short Message Service Center (SMSC)
- SMS Gateway
- Two way SMS system - Ozeki NG
- Hardware and software requirements
- 2.2 Network requirements
- Ozeki SMS Gateway - General information about the software
- Routing
- Message types
- Delivery reports
- GSM modem
- SMPP
- CIMD2
- UCP/EMI
- HTTP
- SMTP
- API
- SQL to SMS
- E-mail to SMS and SMS to E-mail forwarding
- Autoreply database
- Performance and scalability
- Logging
- Problem resolution
- Cost control and usage statistics
- Trial version of the SMS Gateway
- Commercial questions
Most popular
If you are insterested in how to setup automated SMS notifications, you should apply one of the following configurations:
SMS through HTTP requests
SMS from E-mail
SMS from the command line
SMS using txt files
If you are a software developer you can proceed to adding SMS functionality to your source code by clicking on one of the following links:
PHP SMS example
C# SMS example
ASP SMS example
SQL SMS example
Delphi SMS example
If you would like to send and receive SMS messages from MS Office applications, please check out the following links:
Send SMS from MS Excel
Send SMS from MS Outlook
Check out Ozeki SMS Client