Dongle failed to respond to AT command sometimes in time short time interval

[GoogleCodeExporter]

Dongle is working fine but sometimes it automatically shows message that 
failed to respond AT while waiting ok.... something like this
and dongle reloads automatically and works fine.
but during this time if any call comes, call fail because reload or dongle 
unavailable during reload.

Kindly tell me if dongle does not have any problem ie. i can make and receive 
calls, then why it reloads after a time interval showing the mentioned error?

I am using centos 6.3.
and device Huawei 1 x E173, 2 x E1731, 1 x E180 (total 4 dongle)

Original issue reported on code.google.com by o...@w3host.in on 22 Oct 2012 at 8:23

[GoogleCodeExporter]

Give me message(s) exactly 

Original comment by bg_...@mail.ru on 21 Nov 2012 at 8:34

[GoogleCodeExporter]

logs:
[Dec 18 16:39:10] ERROR[5522] at_response.c: [dongle5] Received unexpected 'OK'
[Dec 18 16:39:20] ERROR[4197] pdiscovery.c: [dongle6 discovery] failed to get 
valid response from /dev/ttyUSB8 in 500 msec
[Dec 18 16:39:20] ERROR[4567] at_response.c: [dongle4] Received unexpected 'OK'
[Dec 18 16:39:21] ERROR[4197] pdiscovery.c: [dongle6 discovery] failed to get 
valid response from /dev/ttyUSB11 in 500 msec
[Dec 18 16:43:53] ERROR[5885] chan_dongle.c: [dongle6] Lost connection to Dongle
[Dec 18 16:43:58] ERROR[5928] at_response.c: [dongle6] Getting IMSI number 
failed
[Dec 18 16:44:03] ERROR[5593] at_response.c: [dongle7] Received unexpected 'OK'
[Dec 18 16:44:11] ERROR[4197] pdiscovery.c: [dongle6 discovery] failed to get 
valid response from /dev/ttyUSB2 in 500 msec
[Dec 18 16:53:56] ERROR[4567] at_response.c: [dongle4] Error sending hangup for 
call idx 1
[Dec 18 17:03:44] ERROR[5929] chan_dongle.c: [dongle6] Lost connection to Dongle
[Dec 18 17:03:51] ERROR[5593] at_response.c: [dongle7] Received unexpected 'OK'
[Dec 18 17:04:02] ERROR[5593] chan_dongle.c: [dongle7] timedout while waiting 
'OK' in response to 'AT'
[Dec 18 17:05:16] ERROR[6015] at_queue.c: [dongle6] Error write command 'AT' 
expected response 'OK' length 3, cancel
[Dec 18 17:05:16] ERROR[6015] chan_dongle.c: [dongle6] Lost connection to Dongle
[Dec 18 17:05:57] ERROR[6045] chan_dongle.c: [dongle6] Lost connection to Dongle
[Dec 18 17:11:19] ERROR[6072] at_queue.c: [dongle6] Error write command 'AT' 
expected response 'OK' length 3, cancel
[Dec 18 17:11:19] ERROR[6072] chan_dongle.c: [dongle6] Lost connection to Dongle

dongle.conf:
context=dongle-incoming
group=1
rxgain=0
txgain=0
autodeletesms=yes
resetdongle=yes
u2diag=-1
usecallingpres=yes
callingpres=allowed_passed_screen
disablesms=no
language=ru
smsaspdu=yes
mindtmfgap=45
mindtmfduration=80
mindtmfinterval=200
callwaiting=yes
disable=no
initstate=start
dtmf=relax
[dongle4]
imei=123456789012345
....

kernel: Linux 3.5.7-gentoo #5 SMP PREEMPT Thu Dec 13 11:02:19 EET 2012 x86_64 
AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AuthenticAMD GNU/Linux

kernel config in attached file

Already tried USB hub with external power, but with no effect.

Original comment by justwhis...@gmail.com on 18 Dec 2012 at 3:38

Attachments:

• .config

[GoogleCodeExporter]

Model E173, firmware 11.126.16.04.174

Original comment by justwhis...@gmail.com on 18 Dec 2012 at 3:46

[GoogleCodeExporter]

On another server/asterisk/chan_dongle version same problem. Seems to be 
hardware problem.

Original comment by justwhis...@gmail.com on 20 Dec 2012 at 3:52

[GoogleCodeExporter]

i think this is hardware problems like 1.1 USB, bad power etc

turn off chan_dongle, use minicom/screen or other for direct access to ports 
and 
also look to your dmesg/kernel.log 

Original comment by bg_...@mail.ru on 28 Dec 2012 at 6:08

[GoogleCodeExporter]

get write rights for /var/lock/*
your asterisk use same port twice one for handle device and  second for 
discovery others (try discovery)

Original comment by bg_...@mail.ru on 27 Apr 2013 at 3:47

• Changed state: WontFix