- Product Manual
- Installation Guide
- User Guide
- Developers Guide
- Examples and Solutions
- 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
Two way SMS system - Ozeki NG
When we are talking about two way SMS system we usually refer to systems, that can submit messages to mobile users and can process SMS messages sent by mobile users.
The SMS technology does not provide any way to check if an incoming message is
a reply to a previously sent SMS or not. The reason for this is that there is no
such thing as a session identifier or discussion identifier in the SMS protocol
data unit (PDU). All message are independent from each other and are treated
as a single entity.
The only thing you can do is rely on keywords included in the message text, or if you are lucky and you use IP SMS connection and your SMS service provider supports long codes, you can include some extra digits in the sender telephone number to identify the sent message.
Although the SMS technology does not provide any way to check if an incoming message is a reply to a previously sent SMS or not, you can work around this issue, by putting in a keyword into the message text itself. You can tell the person who replies to the message to include that keyword in the message text. If you use a unique keyword for a submitted message and the keyword is included in the response, you can tell which message does the response message belong to. The problem with this approach is that the mobile user might forget to include the keyword in the message text.
The good news is that in some networks long codes are allowed to be used as
telephone numbers. A long code is a telephone number that has a postfix. E.g.:
+36201234678888, where 8888 is the postfix appended to
the standard telephone number +3620123467.
Long codes can be used through IP SMS connections in some networks. In these
networks the recipient (e.g.: +3620123467) will receive messages sent to any
telephone number that start with +3620123467. For example if an SMS message is
sent to +36201234678888 or to +36201234679999999, the
receiver, that has a phone number of +3620123467 will receive both. If you
can use a long code as the sender telephone number, because your network
supports it, you can include a message identifier
in the tail of the sender telephone number. This way if a reply comes back
to the long telephone number, you can tell which originally submitted message
it belongs to.
The problem with this approach that only a very limited number of Mobile Networks allow long code telephone number formats.
If two autoresponding systems start to communicate with each other a message loop can occur. Information on this can be found at: https://ozekisms.com/p_2203-the-sms-message-loop-threat.html. This loop can create huge telephone bills for both parties in the loop. Luckily Ozeki NG SMS Gateway has built in message loop prevention. It does not allow message submission to the same telephone number with the same text more then 10 times per hour.
Are there any threats with autoresponding systems? Can I query a database and return data in a response SMS?Yes.
The best way to do this is to setup an autoreply database user in Ozeki NG SMS Gateway. More information about this can be found at: https://ozekisms.com/p_2392-sms-autoreply-from-database.html
To create such a service, you need to use the WAP Push message type, that
allows you to send a webpage link to a cellphone. The cellphone can
automatically read this link and can open a webpage.
To create this service, please use the Autoreply easy user built into Ozeki NG.
You can send automatic reply message with Ozeki NG SMS gateway. It is also possible to query the reply based on a keyword of the incoming SMS message. FOr this purpose, you can use Autoreply user or autoreply database user.
- 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
- Hardware and software requirements
- 2.2 Network requirements
- Ozeki SMS Gateway - General information about the software
- Message types
- Delivery reports
- GSM modem
- SQL to SMS
- HTTP to SMS gateway
- E-mail to SMS and SMS to E-mail forwarding
- Autoreply database
- Performance and scalability
- Problem resolution
- Cost control and usage statistics
- Trial version of the SMS Gateway
- Commercial questions
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