Hi All I've bumped against this issue again. The SMSC I'm trying to send to has latin1 default and data coding 1 is GSM 7 bit. Is there any way to instruct kannel on which data coding to use?
On Mon, Jul 22, 2013 at 11:46 AM, Wayne Gemmell <[email protected]> wrote: > Hi > > I am also having an issue with this. Any suggestions from the experts? > > > On Tue, Jul 9, 2013 at 11:47 AM, Niel Smith <[email protected] > > wrote: > >> >> Is there anyway to directly specify the data_coding manually (via http) >> without kannel trying to be intelligent and build the data_coding? >> >> This topic has been raised 10,000x in the past, but cannot find a >> solution that does not involve patching bearerbox. >> >> In short: >> >> 1. The SMSC I'm using does not use GSM / IA5 as the default SMSC >> alphabet (latin1). >> 2. They fragment (concat) messages on anything larger than 140 >> characters on their side, and charging for it. >> 3. Sending with data_coding = 0 and GSM alphabet causes garbage >> inside the messages. >> 4. The data_coding must be precisely 1 to send 7bit. >> >> I've tried all the combinations of mwi,coding,alt-dcs, but that always >> produces a data_coding with the message class and MWI bits set. eg >> >>> 2013-07-09 11:36:42 [3177] [7] DEBUG: data_coding: 216 = 0x000000d8 >>> >> >> >> Any ideas? >> > >
