Hi, actually this mostly depends not on Kannel, but on various SMPP versions used by mobile providers. The problem is that they do not follow the standard, character sets and encodings if concrete.
My tests showed that this is rarely true to show everything in the phone correctly when using normal encoding (passing no coding or coding=0 for sendsms CGI wrapper) and sending ASCII '@' (0x40) inside the text. Kannel recodes it into 0x00 according to GSM character set, but SMPP often does another conversation which really shouldn't be done. As the result, phone often shows some unprintable character or all the text starting with the of '@' in the message is cut off. Or, as you said, message becomes garbage. As a workaround, instead of '@' you could pass 0xA1 (text=blabla%A1) and according to the GSM charset Kannel will convert it to 0x40 which hereby in GSM character is reversed 'i', but in ASCII again '@'. A possibility exists that at least for certain characters your provider's SMPP expects them in ASCII (or latin1 or similar) form and it will do the conversation to the GSM charset itself. That's stupid but it's true. regards, Dziugas Baltrunas On Thu, 13 May 2004, Navjot Singh wrote: > what;s the coding parameters that you use? > > >-----Original Message----- > >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > >Behalf Of Aftab Rashid > >Sent: Thursday, May 13, 2004 10:00 AM > >To: [EMAIL PROTECTED] > >Subject: "@" Handling > > > > > >Hi, > >We are using Kannel with SMPP protocol. The problem is when a user type > >@ in the text message, the whole message becomes a garbage message. > > > >How to handle @ in the messages? > > > > > >Regards, > > > >Aftab > > > > > > >
