- Product Manual
- Introduction
- Installation Guide
- User Guide
- Developers Guide
- Examples and Solutions
- Appendix
- A - Terms and definitions
- B - References
- C - Message types
- Introduction
- OTA bitmap
- Operator logo I.
- Operator logo II.
- Ringtone
- J4a - RTX ringtone format
- J4b - RTTL ringtone format
- Wappush
- Binary XML
- VCard
- VCalendar
- Special SMS Message Indication
- Bookmark
- MMS:XML
- WAP Browser Settings
- SyncML settings
- OMA OTA Settings
- USSD
- Special SMS Message Indication
- Picture message
- D - Database connection strings
- E - SMS alphabet
- F - GSM error codes
- G - SMSC settings
- H - MMSC settings
- I - GSM operators
- J - SMPP providers
- K - GSM modems, phones
- L - Error codes
- M - Country codes
- O - SMPP Error codes
- W - Wireshark Capture
- 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
Mobile message type specification - Ringtone SMS
(SMS message type, SMS message format)
Introduction
Ringtones are little melodies and tunes created to give a unique sound to the GSM phone when the phone is ringing. Ringtones can be composed with an appropriate editor and they can be sent as SMS messages.
Support for operator logos in Ozeki NG - SMS GatewayWhen a ringtone is sent as an SMS message, it is represented as a bitstream. This bitstream can be pictured as a set of hexadecimal numbers.
For example:024A3A51D195CDD004001B20550590610560558550548540820849900000
The bit string contains the following sections:
| 00000010 | <command-length> Number of command parts present |
| 01001010 | <ringing-tone-programming> Command part 1 (with filler bit) |
| 0011101 | <sound> Command part 2 |
| 001 | <basic song type> |
| 0100 | <song title length> 4 characters (ISO-8859-1) |
| 01110100 | the first character T |
| 01100101 | the second character E |
| 01110011 | the third character S |
| 01110100 | the fourth character T |
| 00000001 | <song sequence length> 1 song pattern |
| 000 | <pattern header> pattern header ID |
| 00 | <pattern id> A-part |
| 0000 | <loop value> no loop |
| 00001101 | <pattern specifier> <length of the new pattern> 13 pattern instructions |
| 100 | <tempo instruction id> |
| 10000 | <beats per minute> 160 (i.e., length of 1/4 note = 0,38 sec.) |
| 001 | <note instruction id> |
| 0101 | <note value> note E |
| 010 | <note duration> � note |
| 00 | <note duration specifier> no special duration |
| 001 | <note instruction id> |
| 0110 | <note value> note F |
| 010 | <note duration> � note |
| 00 | <note duration specifier> no special duration |
| 001 | <note instruction id> |
| 1000 | <note instruction> note G |
| 010 | <note duration> � note |
| 00 | <note duration specifier> no special duration |
| 001 | <note instruction id> |
| 0101 | <note value> note E |
| 100 | <note duration> 1/16 note |
| 00 | <note duration specifier> no special duration |
| 001 | <note instruction id> |
| 0101 | <note value> note E |
| 011 | <note duration>1/8 note |
| 00 | <note duration specifier> no special duration |
| 001 | <note instruction id> |
| 0101 | <note value> note E |
| 010 | <note duration> � note |
| 00 | <note duration specifier> no special duration |
| 001 | <note instruction id> |
| 0101 | <note value> note E |
| 001 | <note duration> � note |
| 00 | <note duration specifier> no special duration |
| 001 | <note instruction id> |
| 0101 | <note value> note E |
| 000 | <note duration> full note |
| 00 | <note duration specifier> no special duration |
| 010 | <scale instruction id> |
| 00 | <note scale> Scale-1 (i.e., note A is 440 Hz) |
| 001 | <note instruction id> |
| 0000 | <note value> pause |
| 010 | <note duration> � note |
| 00 | <note duration specifier> no special duration |
| 010 | <scale instruction id> |
| 01 | <note scale> Scale-2 (i.e., note A is 880 Hz), default |
| 001 | <note instruction id> |
| 1001 | <note value> Gis ' i.e. As ' |
| 000 | <note duration> full note |
| 00 | <note duration specifier> no special duration |
| 0000000 | filler bits |
| 00000000 | <command end> end of the ringing tone data |
Sending a ringtone in SMS
To send a ringtone message with Ozeki NG - SMS Gateway, you need to specify a message type which tells the software that the message body contains a ringtone. To send the above example, you would use the following message type: SMS:RINGTONE. In this case, the message type is made up of two sections. The first section tells the message server that this is an SMS message. This way only the service providers supporting this type of SMS will be considered to deliver the message. The second section is used by the service provider to use the ringtone encoder. This encoder will create the protocol data unit (PDU) that will be sent as an SMS message.
Example:
If you use
the Database user to send and receive
SMS messages with Ozeki NG - SMS Gateway,
you can use the following SQL statement to send a ringtone message:
insert into ozekimessageout (receiver,msgtype,msg,status) values ('+36205222245',
'SMS:RINGTONE','024A3A51D195CDD004001B20550590610560558550548540820849900000','send');
More information
- Introduction to mobile message types
- Mobile message type specification - OTA bitmap SMS
- Mobile message type specification - Operator logo SMS, XML
- Mobile message type specification - Operator logo SMS, binary
- Mobile message type specification - WAP Push SMS
- Mobile message type specification - Binary SMS XML
- Mobile message type specification - VCard SMS
- Mobile message type specification - VCalendar SMS
- Introduction to SMS Message Indication
- Mobile message type specification - Webpage link, SMS
- Multimedia Message MMS
- Mobile message type specification - OTA Browser settings SMS
- Mobile message type specification - OTA SyncML settings SMS
- Mobile message type specification
- How to send an USSD Message
- Mobile message type specification - WAP Push SL SMS
- Mobile message type specification - Picture message