search

machtudong / asterisk-chan-dongle

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

Error: Incoming caller with blocked ID #163

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. GSM-Caller with blocked ID

What is the expected output? What do you see instead?
- ERROR[XXXXX] at_response.c:992 at_response_clcc: [dongle0] can't parse CLCC 
line '+CLCC: 1,1,4,0,0,"",,"",'

What version of the product are you using? On what operating system?
- https://github.com/jstasiak/asterisk-chan-dongle/archive/asterisk11.zip, r35; 
raspbx

Please provide any additional information below.
- I added support for blocked IDs for incoming calls.
- Instead of only a error msg in the log-file of the incoming call the missing 
number will be changed to "Blocked Caller ID" and so it can be forwarded to SIP

Enjoy!

at_parse.c:
601,606d600
+               else // add block id support
+               {
+                       *number = "Blocked Caller ID";
+                       return 0;
+               }

Original issue reported on code.google.com by mark.bau...@project-run.com on 20 Jan 2014 at 12:58

Attachments:

GoogleCodeExporter commented 9 years ago 
1) empty number does't mean blocked 
caller may be hidden or none

2) real caller number also may be "Blocked Caller ID" in native :)  yes yes :))

3) can replace empty caller to any usefull string (include localized)  in 
application software for example, not inside channel driver (i think its bad 
place)

Original comment by bg_...@mail.ru on 29 Apr 2014 at 8:02