RE: SMPP: data_coding (deliver_sm)

> -----Original Message-----
> From: Alan McNatty [mailto:[email protected]]

> If I receive a message from a smsc in say ucs2, from what I can see in
> smsc_smpp.c pdu_to_msg the msg data always gets converted from gsm to
> latin1 regardless of source charset. Although the data coding is
> recorded it doesn't seem to make any difference to the msg 
> decoding. In
> this way there is potential for some characters from the 
> source message
> to be lost. 
> 
> Is this an accurate assessment? Anyone else experiencing this problem
> (ie chars that vanish from MO messages)? What about having a 
> translation
> scheme for each data_coding (usc2_to_latin, etc with gsm_to_latin1 the
> default obviously. Potentially a smsc configuration directive could be
> useful to force a data_coding for broken smsc.

Yep - the logic as you described it seems to be how Kannel handles things. I have not had a chance to recieve unicode data through an SMPP SMSC, but that would seem to be problematic. we don't need to transcode from UCS2, as Kannel should send unicode text as UCS2 to the application (as all other drivers do), we simply should not use gsm_to_latin1 on UCS2 encoded message as that can mangle some characters.

--
Oded Arbel
m-Wise mobile solutions
[email protected]

+972-9-9581711 (116)
+972-67-340014

::..
If you lie to the compiler, it will get its revenge. 
	-- Henry Spencer