|
Customer update: 23 April 2010
|
Mobile Payments
SMS Gateway Services
MIS
MAP
|
SMS Gateway Services |
Automatic MT Message Concatenation
The Dialogue SMS API now supports automatic splitting of Bulk MT message submissions longer than 160 characters into concatenated messages. These messages are then seamlessly reassembled by the handset into a single long message. A long message may consist of up-to 255* individual messages “stitched together”
Please note that this functionality is not available for SMPP submissions (as the protocol is limited to a maximum of 255 characters per message).
Also note that each concatenated part is chargeable as an individual message.
In order to take advantage of this feature, you can either:
- Add an extra parameter to HTTP submissions (please see latest version of “Dialogue SMS Gateway API” section 1.4) or
- Contact support@dialogue.net to enable fully automatic message concatenation for your API account organiser. Any Bulk MT submission over 160 characters will be automatically concatenated. Automatic MO concatenated message reassembly can also be enabled for your account.
* Dependant on operator and handset support.
SMS API support for GSM extended characters
Dialogue SMS Gateway API now offers the full range of characters supported by handsets (the GSM 03.38 character set) in MT submissions.
In order to easily submit € the default character encoding of the SMS API has been changed from iso-8859-1/latin1 to iso-8859-15/latin9.
For customers that require characters in GSM 03.38 alphabet that are not available in iso-8859-15/latin9 (e.g. Greek alphabet characters) provision has been made to allow customers to submit mobile terminated messages to Dialogue using GSM 03.38 alphabet.
Please refer to the latest version of the “Dialogue SMS Gateway API”, Appendix 4 and “Dialogue SMS Gateway SMPP API”, section 4 for further information on GSM extended characters support.
SMPP transceiver session support
The SMPP API now supports the BIND_ TRANSCEIVER PDU for the creation of bi-directional SMPP sessions. This means that customers now have the option of creating a single TRANSCEIVER session instead of separate TRANSMITTER and RECEIVER sessions.
For further information please download the latest copy of the SMPP API Guide.
|