Hello to all. I have a problem with the messages encoding going from my ESME through opensmppbox.
I don't have access to source code of application, but I need to make it able to send and receive messages to SMSC. ESME don't really have a lot of options to configure connection, it doesn't send enquire_link etc. So I use Kannel as a SMS Proxy. The problem is that SMSC accept only messages in UCS-2 or UTF-16BE encoding (without BOM). My ESME, based on characters used in message use 2 encoding type. Messages send from ESME have different encoding according to characters that exist in message itself. If message written with only latin characters, encoding is pure latin-1 (ISO-8859-1) Example: "Hello" = << 48 65 6C 6C 6F >> If only message contains one non-ASCII character it fall to UTF-16 LE with BOM Example: "Hello テ" = << FF FE 48 00 65 00 6C 00 6C 00 6F 00 20 00 C630 >> SMSC side accept only UCS-2 or UTF-16 BE which for previous examples should look like this: "Hello" ==>> 00 48 00 65 00 6C 00 6C 00 6F "Hello テ" ==>> 00 48 00 65 00 6C 00 6C 00 6F 00 20 30 C6 Can I configure Kannel to recode messages of two different formats to UTF-16 BE and how it can be done? Also alt-charset in smsc group doesn't help when I send messages with non ASCII characters from my ESME. my configurations: kannel 1.4.4 debian 7 group = smsc smsc = smpp smsc-id = SMSCSim smsc-admin-id = smscsim throughput = 1.0 alt-charset = "UTF-16LE" log-file = "/var/log/kannel/SMSCSim.log" log-level = 0 dead-start = false host = 192.168.2.49 port = 5018 transceiver-mode = true interface-version = 34 smsc-username = XXXXXX smsc-password = XXXXXX system-type = VMA # service-type = VMA #what the option my-number means? my-number = 223344 max-pending-submits = 10 reconnect-delay = 5 enquire-link-interval = 270 connection-timeout = 300 wait-ack = 60 wait-ack-expire = 0x02 source-addr-ton = 2 source-addr-npi = 1 dest-addr-ton = 2 dest-addr-npi = 1 bind-addr-ton = 2 bind-addr-npi = 1 msg-id-type = 0x03 esm-class = 3 Thanks, Yegor
