Hi Nikos,

thanks for your reply. This is a dump from my bb logs:

67/00342/O/52/4894890/3311234567////////////0000/130810164028////4/0992/0041004E004F004E0020003300
3300380036003900320036003500380032002000430068006500200065007400E1002000680061006900200069006E00200066006F0074006F003F0020005100750061006E0074006F002000730065006900200061006C0074
0061003F00200052006900630063006100720064006F///1///////020108///49

you are right, this is a unicode message. The correct xser field is 020108
not 020100 (that indicate 7-bit message).

Now, the problem is that kannel when receive this type of message pass it as
is to my sms-service that response with syntax error.

Can i resolve this issue with alt-charset on my smsc configuration?

thanks in advance,

regards

2010/8/16 Nikos Balkanas <[email protected]>

> Hi,
>
> Kannel flags indicate unicode, not even binary. Kannel supports 7-bit, but
> in this case you recive unicode. The Xser field comes also from the SMSc. I
> don't know what the fields of Xser mean, but you can see the actual SMS
> received from bb debug logs to decide for yourself if it is Unicode or
> 7-bit. It is probably Unicode.
>
> If that is the case contact your SMSc and ask them what value they are
> sending for the Xser field. Else post detailed bb logs with the MO
> reception.
>
> BR,
> Nikos
> ----- Original Message ----- From: Emanuele Carbone
> To: [email protected]
> Sent: Monday, August 16, 2010 11:03 AM
> Subject: EMI XSer 02, GSM DCS information
>
>
>
> Hi guys,
>
> i have an issue with EMI protocol for the MO scenario. Sometimes my gateway
> receive message with binary body. When received this type of message, i
> found
>
> flags:-1:2:-1:0:-1 , with coding set to UCS-2, and the XSer field with this
> information, 020100.
>
> In the emi specification 4.0, i found:
>
> Example encoding of XSer Type of service 02, GSM DCS information:
>
> 020100, meaning that the DCS value 00 (0000 0000 binary) is used.
>
> According to the GSM03.38 specification, this means 7-bit default alphabet,
> no
> compression, no message class meaning.
>
> Now, i dont understand if this type of message must be considered as 7-bit,
> and if so, kannel does not support this specification?
>
>
> thanks.
>

Reply via email to