> > 00 in GSM to latin1 ==> decimal 64 (the @ symbol). > 64 in GSM to latin1 ==> decimal 161 (the inverted !)
I have a similar problem, when I send this: (test2 @ eden dva tri) ... [19] DEBUG: data_coding: 0 = 0x00000000 ... [19] DEBUG: data: 74 65 73 74 32 20 00 20 test2 . [19] DEBUG: data: 65 64 65 6e 0d 0a 64 76 eden..dv [19] DEBUG: data: 61 0d 0a 74 72 69 a..tri ... I receive only "test2" on my mobile and nothing after the "@" If I send with alt-dcs=1: [19] DEBUG: data_coding: 241 = 0x000000f1 ... [19] DEBUG: data: 74 65 73 74 20 40 20 65 test @ e [19] DEBUG: data: 64 65 6e 0d 0a 64 76 61 den..dva [19] DEBUG: data: 0d 0a 74 72 69 ..tri I get the inverted exclamation point (!). Is this a bug in my SMSC?? And what is data_coding=241?? Acording to the SMPP 3.4 spec. data_coding=0 is SMSC default, how can I set-up a specific data_coding? Also if I set alt-charset="iso-8859-1" I get: [6] DEBUG: data_coding: 0 = 0x00000000 ... [6] DEBUG: data: 74 65 73 74 33 20 40 20 test3 @ [6] DEBUG: data: 65 64 65 6e 0d 0a 64 76 eden..dv [6] DEBUG: data: 61 0d 0a 74 72 69 a..tri Any clues? I'm using kannel-cvs-20030626. -- Damjan Georgievski jabberID: [EMAIL PROTECTED]
