I'm trying to figure out how to send different data encodings from Kannel 1.5.0 over SMPP. The SMPP Spec lists the following options for data_coding field:
0 0 0 0 0 0 0 0 SMSC Default Alphabet 0 0 0 0 0 0 0 1 IA5(CCITTT.50)/ASCII(ANSIX3.4) 0 0 0 0 0 0 1 0 Octet unspecified (8-bit binary) 0 0 0 0 0 0 1 1 Latin1(ISO-8859-1) 0 0 0 0 0 1 0 0 Octet unspecified (8-bit binary) 0 0 0 0 0 1 0 1 JIS(X0208-1990) 0 0 0 0 0 1 1 0 Cyrllic(ISO-8859-5) 0 0 0 0 0 1 1 1 Latin/Hebrew (ISO-8859-8) 0 0 0 0 1 0 0 0 UCS2(ISO/IEC-10646) ... and some others. To initiate MT messages, we're using the sendsms http interface on smsbox (the one here: http://www.kannel.org/download/1.5.0/userguide-1.5.0/userguide.html#AEN4623). It looks like the only relevant parameter into the sendsms is the "coding" parameter, which can only be 0, 1, or 2. "0" causes data_coding 0, 1 causes 4, and 2 causes 8. I don't see a way to set data_coding to 3, for example, in order to do Latin-1. Another thing is that only 0 causes the message text to get encoded from UTF-8 (input encoding from http) into the correct encoding. For example, sending the UTF-8 data with coding=2 does not re-encode the message into USC-2, but just sends your UTF-8 bytes as if they were UCS-2 but sending utf8 data with coding=0 does re-encode them into GSM. These things seem to me to be incorrect behavior, however given the wide use of kannel I figured I should make sure I'm not missing something obvious before I draft a patch to attempt to fix them. Am I missing something?
