hey guys, I must be doing something silly in my kannel use/config.  However, this is 
what happens:
 
When I send from a handset to my operator assigned shortcode the character "@", it 
comes to kannel and I see the message in the kannel.log debug output as being of hex 
value '00'.  When it reaches kannel's access.log, it is now showing up as an inverted 
exclimation mark.  It is also passed onto our web service as an inverted exclimation 
mark.  At first I was confused by this mapping, but a quick look at how a GSM -> latin 
conversion works, one realizes that Kannel appears to be converting the data TWICE.
 
00 in GSM to latin1 ==> decimal 64 (the @ symbol).
64 in GSM to latin1 ==> decimal 161 (the inverted !)
 
A similar problem seems to be occuring when I use kannel to send to my handset.  In 
order for an @ symbol to appear on the handset, I need to send it decimal 161, as it 
appears to go from latin1 -> gsm twice.
 
What can I do to alleviate this?
 
Thanks,
 
Bryce

Reply via email to