MaxSok / asterisk-chan-dongle

Automatically exported from code.google.com/p/asterisk-chan-dongle
Other
0 stars 0 forks source link

Прием SMS #72

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
При получении SMS появляется ошибка и СМС не 
доходит.

[Mar 30 19:00:59] WARNING[19062]: at_response.c:1204 at_response_cmgr: 
[dongle0] Error parsing incoming message '+CMGR: 0,,97
0791947106004034040C9194713900303341002130039100558059D6B75B076A86D36CF11BEF024D
D365103A2C2EBB413490BB5C2F839CE1315A9E1EA3E96537C805D2D6DBA0A0585E3797DDA0FB1ECD
2EBB41D37419244ED3E965906845CBC56EB9190C069BCD6622' at possition 50: Unhandled 
PID value, only SMS supported

chan_dongle: Huawei 3G Dongle Channel Driver, Version 1.1, Revision 10

Asterisk 10.2.1

Original issue reported on code.google.com by nikolaus...@gmail.com on 30 Mar 2012 at 5:05

GoogleCodeExporter commented 9 years ago
And whats you can see instead ?

Original comment by bg_...@mail.ru on 1 Apr 2012 at 7:17

GoogleCodeExporter commented 9 years ago
I only see an error message. 
http://twit88.com/home/utility/sms-pdu-encode-декоде here I can decrypt 
the message

Original comment by nikolaus...@gmail.com on 1 Apr 2012 at 7:22

GoogleCodeExporter commented 9 years ago
this message has PID value equal 41.

Original comment by bg_...@mail.ru on 13 May 2012 at 8:02

GoogleCodeExporter commented 9 years ago
chan_dongle: Huawei 3G Dongle Channel Driver, Version 1.1, Revision 35
asterisk 1.8

[dongle0] Error parsing incoming message '+CMGR: 0,,157
079...D35D' at possition 47: Unhandled PID value, only SMS supported

Original comment by leont...@gmail.com on 29 Nov 2013 at 11:00

GoogleCodeExporter commented 9 years ago
is there a solution?

I get a very similar error

WARNING[3265]: at_response.c:1207 at_response_cmgr: [dongle0] Error parsing 
incoming message '+CMGR: 0,,43
07915389080003F124068171002600F1511050024303801ED9775D0E8287E7F3FB5B4E068146B39B
0C074ACF41B15BAC068301' at possition 44: Unsupported DCS value

Original comment by ivant...@gmail.com on 5 Jan 2015 at 6:39