Now that kannel uses UTF-8 characters in order to receive SMS contents to be delivered, I'm evaluating optional billings at smsc...
so, if with version 1.4.1 of kannel I would have written: http://localhost:14000/cgi-bin/sendsms?text=%E8 in order to send out the character "รจ" (which is iso-8859-1) with version 1.4.3 I have to write: http://localhost:14000/cgi-bin/sendsms?text=%C3%A8 as %C3%A8 is the UTF-8 rappresentation of the %E8 If I'm sending standard text 160 character MT SMS, each char is 7 bit and for each 160 chars I get billed for 1 SMS. I'm expecting kannel to send to the smsc only the correct characters converted in the right encoding (based on coding= and charset= variables) and not using UTF-8 by default, is that correct ? Recap: I'm I correct when saying that kannel will use for internal/external communication UTF-8 chars but for smsc communication the encoding is what is set via coding/charset ? -- Julien Buratto
