Dongle (without voice support) wont connect after running dongle callwaiting

[GoogleCodeExporter]

What steps will reproduce the problem?
1. On a dongle that does not have voice support
2. Run dongle callwaiting (by mistake)
3. Check the state, or just wait on the cli

What is the expected output? What do you see instead?
It should try report failed. And should allow to disable that command. But 
instead I keep getting this error every 15 seconds
[Jun  6 12:07:23] ERROR[20432]: chan_dongle.c:433 do_monitor_phone: [dongle0] 
timedout while waiting 'OK' in response to 'AT'

What version of the product are you using? On what operating system?
Ubuntu 12.04, Asterisk 1.8

Please provide any additional information below.
1) I tried to unplug and plug the device, nothing
2) I tried to reset the dongle, nothing
3) I tried to reload the dongle, nothing
4) I tried "dongle callwaiting disable dongle0", it reported "dongle disabled". 
Basically a catch 22 on this one.
5) I tried to commend out the following configuration lines from dongle.conf 
autodeletesms=yes, usecallingpres=yes, callingpres=allowed_passed_screen, 
callwaiting=auto
6) I tried to change value of callwaiting to yes, no 

None of the above got me rid of my mistake.

Original issue reported on code.google.com by jsiddha...@mcruiseon.com on 6 Jun 2013 at 6:40

[GoogleCodeExporter]

Ok, I also write a guide that can not be dried cats in a microwave.

I think problems in your dongle (modem, firmware?) or USB, not in chan_dongle 
code.

Original comment by bg_...@mail.ru on 30 Jul 2013 at 7:39

• Changed state: WontFix

[GoogleCodeExporter]

I Had the same problems on both dongles:
[Jun  6 12:07:23] ERROR[20432]: chan_dongle.c:433 do_monitor_phone: [dongle0] 
timedout while waiting 'OK' in response to 'AT'
it was connected with USB-hub, but then I switched it directly to 
Asterisk-server and all CLI became without red strings. If you haven't usbhub I 
recomend to play with different usbports.

Original comment by maxi...@simplio.com on 18 Nov 2013 at 5:58