incoming sms message with utf8 (üöä...)

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. if received sms with utf8 letter (üöä)
2.
3. "temm ä lol ü lol ö lol"

What is the expected output? What do you see instead?
[dongle0] Got SMS from +4917XXXXXX47: 'temm { lol ~ lol | lol '
    -- Executing [sms@dongle-incoming:1] Set("Local/sms@dongle-incoming-ffcd;1", "sms=temm { lol ~ lol | lol ") in new stack
[Jun  6 15:40:55] WARNING[1294]: pbx.c:1355 pbx_exec: The application delimiter 
is now the comma, not the pipe.  Did you forget to convert your dialplan?  
(Set(sms=temm { lol ~ lol | lol ))
    -- Auto fallthrough, channel 'Local/sms@dongle-incoming-ffcd;1' status is 'UNKNOWN'

What version of the product are you using? On what operating system?
Debian 6 
Kernel 2.6.32-5-686

Model K3520     
Firmware 11.314.21.31.00     
Please provide any additional information below.

Original issue reported on code.google.com by dafredm...@gmail.com on 6 Jun 2011 at 1:58

GoogleCodeExporter commented 9 years ago

first, UCS2 -> utf8 decoding based in iconv() library call, please check your 
system locale.

second, can use ${SMS_BASE64} for avoid special chars problems in dialplan.

Original comment by bg_...@mail.ru on 11 Jun 2011 at 8:15

GoogleCodeExporter commented 9 years ago

I found a secound bug. When i write more then 160 letter, the sms US not 
readable...

Original comment by dafredm...@gmail.com on 11 Jun 2011 at 9:18

GoogleCodeExporter commented 9 years ago

TODO: replace iconv() usage  with GSM alphabet

Original comment by bg_...@mail.ru on 14 Aug 2011 at 6:54

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

are there any news on this issue? I have the same problem and can't figure out 
how to read the combined sms.

Original comment by pdittr...@gmail.com on 30 Oct 2011 at 12:59

GoogleCodeExporter commented 9 years ago

ive got the same issue not beeing able to read sms longer than 160chars with 
chan_dongle v1.1.14 and a E1550 (11.608.13.00.47) on asterisk 1.8.13 
(debian/kernel 3.2.0).

also tried to set default smsaspdu=yes as recommended but that didnt work out.

extensions.conf:
exten => sms,1,Verbose(Incoming SMS from ${CALLERID(num)} to ${DONGLENAME} 
${BASE64_DECODE(${SMS_BASE64})})

log:
Got SMS from +43660xxxxxxx: 'GQAPCEA\_GQAJS]A`CCeS]OKANYKSGQAR]AHKeA
e}QAtkADKg_eOK]Y@nK]]gAHSeAdKGQiARgiAn}eIARGQANKe]AJegiAj[ArPg`@heKMMK]Y@HSeKWiA
B[AeiAHKgAKgGQKQK]gu@$_iK]ik'
-- Executing [sms@default:1] Verbose("Local/sms@default-16b5;1", "Incoming SMS 
from +43660xxxxxxx GQAPCEA\_GQAJS]A`CCeS]OKANYKSGQAR]AHKeA
e}QAtkADKg_eOK]Y@nK]]gAHSeAdKGQiARgiAn}eIARGQANKe]AJegiAj[ArPg`@heKMMK]Y@HSeKWiA
B[AeiAHKgAKgGQKQK]gu@$_iK]ik") in new stack
Incoming SMS from +43660xxxxxxx GQAPCEA_GQAJS]A`CCeS]OKANYKSGQAR]AHKeA
e}QAtkADKg_eOK]Y@nK]]gAHSeAdKGQiARgiAn}eIARGQANKe]AJegiAj[ArPg`@heKMMK]Y@HSeKWiA
B[AeiAHKgAKgGQKQK]gu@$_iK]ik

Original comment by vchr...@gmail.com on 20 Dec 2012 at 1:55

GoogleCodeExporter commented 9 years ago

I'm also having errors where the SMS is coming in as garbage :

KiA [CuS]OYsAX_oAFCYYAdCiKAL_eA*  AP S@B]IA&CkISA eCEAP S@^]A(CYWgQCoWY@ 
SCYATfhjTdn`F@h_AfkEgGeSEKAB]sAHCsAr_kAXSWKQFQCeOKgu@$g]@nV@hCqS@ SgG_k]iARgAl

and

BYSIAL_eAb@HCs]

Original comment by shak...@shakeelahmad.net on 24 Oct 2013 at 2:33

GoogleCodeExporter commented 9 years ago

Is there a locale that will workaround this issue?

Original comment by rossen.a...@gmail.com on 26 Apr 2014 at 5:40

GoogleCodeExporter commented 9 years ago

Any update? I encountered the same problem that received long sms in rubbish.

Original comment by woei...@gmail.com on 25 Nov 2014 at 2:37

antirek / asterisk-chan-dongle

incoming sms message with utf8 (üöä...) #8