Hello Alexander Thanks for getting back.
I see what you are saying, and I am with you on the fact that alt_charset option is a SMSC option. But in deciding if this is a bug or not, consider the fact that if a user configures alt_charset = ISO-8759-1, and then encodes data using ISO-8759-1 charset (setting coding = 0), he expects the data to be passed through to the SMSC transparently. But what happens is that Kannel replaces all characters in ISO-8759-1 that are not in GSM 03.38 by "?". And this is because of the code that I pointed out. If I disable that code, things come out OK. Sanjay On 9/21/2010 6:05 PM, Alexander Malysh wrote: > HI, > > no it's not a bug IMO. in extract_msgdata_part_by_coding we don't convert > anything.we just use > gsm03.38 covert function to be able to count message length because equal > which charset smsc operator > accept message will be transported via ss7 and there is only gsm03.38 apply > (ok may be issue here with cdma/tdma). > > alt_charset is SMSC module option and only tell SMSC module to send message > body in this charset. > > Thanks, > Alexander Malysh > > Am 21.09.2010 um 15:10 schrieb Sanjay Bhandari: > >> >> Can anyone shed light on this? >> >> In file sms.c function extract_msgdata_part_by_coding(), it filters on >> the GSM 03.38 charset. This basically results in characters not in the >> GSM charset to be replaced by "?". >> >> But this happens with no consideration to the alt_charset config setting >> in the "group = smsc". So, basically, if someone sets the alt_charset to >> something other than GSM 03.38, none of the characters not in GSM 03.38 >> make it through. >> >> Why is this? Is this not a problem? >> >> >
