I don't understand exactly what you mean.
Message doesn't reach the smsc complete.
Kannel code truncates it. It thinks that '0x00' is the end of the message.
That's the problem.
Smsc cannot setup custom character translations for us, so i could send
'0x040' and they give me @.
----- Original Message -----
From: "Richard Crawshaw" <[email protected]>
To: "Πετσούκα Τάνια" <[email protected]>; "Mike Nakos" <[email protected]>
Cc: <[email protected]>
Sent: Friday, May 13, 2011 5:32 PM
Subject: RE: sqlbox greek gsm-7
I understand that '@' should be URL encoded (char code 40, which is the
ASCII code for '@'). We've had similar problems where the bind was
expecting GSM encoding but our Kannel instance was using UTF-8 (which
appears to be Kannel's default). The solution that was implemented was
that our SMSC changed the encoding on the bind. We had to re-bind, but
that wasn't a problem.
Richard
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of ?ets???a ????a
Sent: 13 May 2011 14:30
To: Mike Nakos
Cc: [email protected]
Subject: Re: sqlbox greek gsm-7
From U.G :
"Since @ is translated into 0x00 which will break the SMPP PDU..."
So, maybe the question is " Is there a way to escape 0x00 in message
data??
How do you others, send '@' with utf8 and gsm 7bit?
