Jernas Solutions Ozeki NG SMS Gateway: Development Overview Presented by: Milen Nikolov Manager, Products & Services A subsidiary of International Development Company [IDC] http://www.idcuae.com
The Big Picture OzekiNG SMS Gateway Service Provider/SMSC API Adaptors Encapsulator Queue Applications C++,C#,ASP,PHP, AJAX, … HTTP methods SQL queries Databases Oracle, MSSQL, Sybase, Postgre, MySQL, etc E-mail Servers SMTP/POP3 Sendmail, Qmail, MS Exchange, etc TEXT Files
Users and Applications User Type Description Standard user User account for accessing the OzekiNG management interface or for sending/receiving SMS messages using the built-in web interface E-mail user Automated user, implementing two-way SMS/E-mail gateway service using POP3 and SMTP Autoreply user A user for automatic reply and message routing based on sender address or message content SMPP user This user account enables other devices to connect to the OzekiNG, turning the software into a SMSC Database user A user account that periodically polls a database for incoming/outgoing messages File user A user account that processes text files as means for sending and receiving messages HTTP Client user A translator, converting mobile communication into HTTP GET and HTTP POST methods.
Two database tables: ozekimessageout and ozekimessagein
A database user account and a connector [ODBC or ADO]
Incoming Messages: Table Fields Field Description Example id This distinguishes incoming messages from each other. Every id has to be different. 1, 2, 3, ... sender This is the phone number of the sender of the message. +36441234567, 06459876543 receiver This is the phone number of the recipient of the message. +36441234567, 06459876543 msg This is the text of the message. This is a message text. senttime This is the time of sending the message. 2007-04-23 10:02:13 receivedtime This is the time of receiving the message. 2007-04-23 10:02:13 operator This denotes which service provider connection was used to receive the message. Vodafone1 msgtype This denotes the type of the message. SMS:TEXT, SMS:WAPPUSH, ...
Outgoing Messages: Table Fields Column name Description Example id This distinguishes outgoing messages from each other. Every id has to be different 1, 2, 3, ... sender This is the phone number of the sender of the message +36441234567, 06459876543 receiver This is the phone number of the recipient of the message +36441234567, 06459876543 msg This is the text of the message This is a message text. senttime This is the time of sending the message 2007-04-23 10:02:13 receivedtime This is the time of receiving the message 2007-04-23 10:02:13 operator This denotes which service provider connection is to be used to send out the message. The default is ANY ANY; Vodafone1 msgtype This denotes the type of the message, default SMS:TEXT SMS:TEXT, SMS:WAPPUSH, … status This denotes the status of the message. send, sending, sent, notsent, delivered, undelivered
Message Status Field Status Description send The message has been inserted into the database table (ozekimessageout), but not yet processed by Ozeki NG. This is the status to be specified when inserting a new message. sending The message has been processed by Ozeki NG, and inserted into the Database user's Outbox folder, where it is waiting to be sent out. sent The message has been sent out to the SMS Center of a specified service provider, which has accepted the message for delivery. notsent The message has not been sent out to the SMS Center of a specified service provider. Some error has caused the sending to fail. delivered The specified service provider has reported that the message has been delivered to the recipient. undelivered The specified service provider has reported that the delivery of the message to the recipient has failed.
How to send SMS messages using ASP,ASP .NET, C# and other languages
HTTP API: The Idea OzekiNG SMS Gateway Service Provider/SMSC WWW Server Encapsulator Queue Application C++,C#,ASP,PHP, AJAX, … HTTP POST http://127.0.0.1:9501/ozeki? action =SendMessage&u sername =user& password =pass& recipient =050XXXXXXX& messageData =hello
HTTP Fields Parameter Description Values Example action Mandatory field, specifying the API command sendMessage action=sendMessage originator Optional field. Specifies the sender identity/number, URL encoded An alphanumeric sender address, or telephone number. Encoded in UTF8 originator=%2B36201112222 recipient Mandatory field, specifying the recipient phone number. Must be URL encoded Comma separated telephone numbers in local or international number format recipient=%2B36201234567 messageType Optional field, defining the type of SMS message There are more than 20 possible message types messageType=SMS:TEXT messageData Specifies the text or the data of the SMS message. Mandatory The value must be encoded in UTF8 and must be URL encoded messageData=Hello+World _charset_ Specifies the charset of the encoded data (if not specified UTF-8 will be assumed). Optional. utf-8 windows-1250 iso-8859-1 iso-8859-2 _charset_=iso-8859-2 serviceProvider The name of the service provider connection to use Must match the string from the configuration serviceProvider=Etisalat