Hello, I have a general question concerning 8-bit messages over HTTP using Kannel 1.4.3 with its internal sendsms CGI. Referring to Julien Buratto´s Characters, Kannel & MT SMS document, Kannel uses UTF-8 internally and binary SMS should be encoded using single byte characters with an argument coding=1.
Does Kannel forward a binary payload correct when using "raw" url-encoding? (unclear to me is how Kannel treats double byte character sets e.g. internally) Everything seems to work fine analysing the PDU but the SME seems to ignore messages somehow. The following URL was invoked by a JAVA application, forced to an CIMD2 SMSC: http://localhost:13013/cgi-bin/sendsms?username=cimd2conc&password=cimd2concPwd&from=%2B49XXX&to=%2B46XXX&dlr-mask=31&dlr-url=http%3A%2F%2Flocalhost%3A8080%2Fkannelservlet%3Fid%3D30269438300001%26dlrstatus%3D%25d%26senton%3D%25t%26sender%3D%25q%26receiver%3D%25Q%26smscid%3D%25i%26smsid%3D%25I%26dlrreply%3D%25A%26foreignid%3D%25F%26senduser%3D%25n%26messagecharset%3D%25C%26originatingsmsc%3D%25f&coding=1&alt-dcs=1&mclass=2&priority=2&udh=%06%05%04%C0%32%C0%32&text=%00%00%14%00%0A%06%0A%0D%2E%09%31%02%00%00%CC%9C%5F%01%FF%FF%FF%FF%00 Some important parameters needs explanation (needed by the receiving SME) alt-dcs=1 TP-DCS: FX mclass=2 TP-DCS: X6 --> F6 priority=2 not really needed (coding=1 msg will be preferred) udh=%06%05%04%C0%32%C0%32 --> holds ports, works fine text=%00%00%14%00%0A%06%0A%0D%2E%09%31%02%00%00%CC%9C%5F%01%FF%FF%FF%FF%00 --> original binary payload, processed by the JAVA app: 000014000A060A0D2E0931020000CC9C5F01FFFFFFFF00 I will be glad if somebody have comments, suggestions, experiences or even doubts - how this could work at all. Thanks, Ben
