Error parsing incoming message about asterisk-chan-dongle HOT 24 CLOSED

[deleted comment]

message has OA TOA field = 0xD0 

error in pdu_parse_number() 

Hi!

Any update on this bug?

Thank you!

Issue 42 has been merged into this issue.

TYPE OF NR. :   Alpha (acc. to TS 03.38)

Anything new here. I also have this bug.

I am also getting same error. Any news about this bug?

[May 15 16:17:06] WARNING[8201]: at_response.c:1204 at_response_cmgr: [dongle0] 
Error parsing incoming message '+CMGR: 0,,... ' at possition 36: Can't parse OA
[May 15 16:18:28] WARNING[6596]: at_response.c:1204 at_response_cmgr: [dongle0] 
Error parsing incoming message '+CMGR: 0,,...' at possition 38: Can't parse OA
[May 15 16:18:40] WARNING[6591]: at_response.c:1204 at_response_cmgr: [dongle0] 
Error parsing incoming message '+CMGR: 0,,...' at possition 48: Can't parse OA
....
please some one , little help, point direction

Hi, this happens because Chan dongle doesn't have support dor alphabetical 
addresses (eg TS 03.38), and the type of address descriptor in the pdu is 
probably D0 .
if you still want to get the rest of the message   just modify pdu.c
from this:
                   digit = pdu_code2digit(pdu[0][1]);
                                if(digit <= 0)
                                        return -1;
                                *number++ = digit;
                                digit = pdu_code2digit(pdu[0][0]);
                                if(digit < 0 || (digit == 0 && (syms != 2 || (digits & 0x1) == 0)) || (digit!=16))
                                        return -1;
                                *number++ = digit;
to this:
 digit = pdu_code2digit(pdu[0][1]);
                             /*   if(digit <= 0)
                                        return -1;*/
                                *number++ = digit;
                                digit = pdu_code2digit(pdu[0][0]);
                               /* if(digit < 0 || (digit == 0 && (syms != 2 || (digits & 0x1) == 0)) || (digit!=16))
                                        return -1;*/
                                *number++ = digit;

This is just commenting those if and increasing the pointer to force the 
parsing of the rest of the message.
compile, unload->load chan dongle in asterisk and try it.
This is not really a solution but at least it is a workaround.

p.d i'm attaching my chan_dongle.so (compiled for debian lenny and tested with 
asterisk 1.8.3.3)  to save you the trouble, it also contains a fix to be able 
to send messages to short codes (eg message to 2266 to subscribe by sms to a 
service // https://code.google.com/p/asterisk-chan-dongle/issues/detail?id=21 ) 
and also additional dongle models in pdiscovery.c that i have tested

pdiscovery.c:   { 0x12d1, 0x1001, { 2, 1, /* 0 */ } },      /* E1550 and generic */
pdiscovery.c:   { 0x12d1, 0x1465, { 2, 1, /* 0 */ } },      /* K3520 */
pdiscovery.c:   { 0x12d1, 0x140c, { 3, 2, /* 0 */ } },      /* E17xx */
pdiscovery.c:   { 0x12d1, 0x1436, { 4, 3, /* 0 */ } },      /* E1750 */
pdiscovery.c:   { 0x12d1, 0x1506, { 1, 2, /* 0 */ } },      /* E171  */

Regards.

Hi everybody.
I propose attached patch as a solution to this problem. With it, chan_dongle 
can decode alphanumeric TP-OA and some other types of TP-PID.
I also attached some cases, which I used for testing.

good work, patch works for me. Can you add this patch in the main version of 
chan-dongle?

Hi, I also applyed this patch, but still don't work.

here is my error:

[Aug  7 15:12:42] WARNING[13044] at_response.c: [dongle0] Error parsing 
incoming message '+CMGR: 0,,86
069183950805F1040691839577340031807051210280505479D95DA7BBDF207718240F8FEBEE3A28
DD0ECF41B51BCB0603ADDD2E9035CC5687DDEF391D44B7BFCF20F1DB2D7EBB4162F95B1D06A5E7F4
F4B80C92DD5CB09C4B068BCD5C' at possition 42: Unhandled PID value, only SMS 
supported


is this related to this bug?

Best regards, 
Franjo

Is possible to view original PDU message in dialpaln, so I can use custom 
(external) PDU decoder?

THANKS   this is good patch also working for me
i have applied patch to this version
chan_dongle: Huawei 3G Dongle Channel Driver, Version 1.1, Revision 14

very good  thanks for patch

is it possible to send sms message   with special characters  like  (,) or (@) 
or others  can anyone help  me  ????????????????????

Glad I found this forum, I have same problem.

My Problem is also that the from address contains alfabetical characters: like 
this
#Mabcda>14:11 UITGESCH 01 Rick

[2013-12-16 08:50:00] WARNING[3002]: at_response.c:1207 at_response_cmgr: 
[dongle0] Error parsing incoming message '+CMGR: 0,,41
07911356131313F60400803900312161809475401FA3E6DB4D9FB7C33E184E57B38188C522139474
8240B018485A769701' at possition 34: Can't parse length of OA

So I think you found a solution/patch, please can you let me know how to apply 
it.
Which commands to make the patch work, please ?

Can it also deal with # and > ?

thanks a lot!

i have applied this patch this way 
1.    download patch 
2.go to source off patch  for example i have source chan_dongle  in 
  /usr/src/chan_dongle-1.1.r14

cd /usr/src/chan_dongle-1.1.r14

i have downloaded this patch in Downloads folder
patch  <  /root/Downloads/chan-dongle-alphanumeric-pdu.patch

3. make
4. make install
5.  asterisk  -r
6.  core restart now 
   and u have done

Thanks so much.
It was precompiled, so I could not so it, but now I get help from here:

https://sourceforge.net/p/raspbx/discussion/bugreports/thread/e721a550/

hi sorry to bother but this patch chan-dongle-alphanumeric-pdu.patch still not 
working on Number that didnot in International Format. Something like 99999

but on Sender As Letters, itw worked. such as "INDOSAT".

I think because the OA field is empty, I have same problem :
WARNING[4425]: at_response.c:1207 at_response_cmgr: [dongle1] Error parsing 
incoming message '+CMGR: 0,,43
07911356131313F6040080390041400280641180222358CC56C3C960B219CC07C3E968345035493D
16A7432408160349CBEE32' at possition 34: Can't parse length of OA

Can someone smart adjust the code and let us know, please?

It's been a while. Any progress with this kind of issue? My error is:

WARNING[3592]: at_response.c:1207 at_response_cmgr: [dongle0] Error parsing 
incoming message '+CMGR: 0,,43
07915389080003F124068171002600F1511050127063801ED9775D0E8287E7F3FB5B4E0681463119
4E064ACF41301CAC269B01' at possition 44: Unsupported DCS value

I was bitten by this same bug as well. Too bad it is taking so long to merge 
this patch.