Dongle crash every night

Question

Dongle crash every night

rlzmaxx opened this issue 7 years ago · comments

Hi,

I managed to configure and make incoming/ outgoing calls, however, I have a stability issue because of every day the dongle crash and the State: GSM not registered GSM Registration Status: Not registered, but searching. After doing a "dongle reset dongle0" the modem register fine to the network without a problem and remain connected up to 12 hours (office hours).

There is some way to check logs to see the reason why the dongle is crashing? Or any way to solve this issue?

Thanks!

raspbx*CLI> dongle show device state dongle0
-------------- Status -------------
Device : dongle0
State : GSM not registered
Audio : /dev/ttyUSB1
Data : /dev/ttyUSB2
Voice : Yes
SMS : Yes
Manufacturer : huawei
Model : E160
Firmware : 11.609.10.02.432
IMEI : 3547640311XXXXX
IMSI : 2142200033XXXXX
GSM Registration Status : Not registered, but searching
RSSI : 13, -87 dBm
Mode : WCDMA
Submode : WCDMA
Provider Name : NONE
Location area code : B33
Cell ID : 926A
Subscriber Number : +346420XXXXX
SMS Service Center : +346422XXXXX
Use UCS-2 encoding : Yes
USSD use 7 bit encoding : No
USSD use UCS-2 decoding : Yes
Tasks in queue : 0
Commands in queue : 0
Call Waiting : Disabled
Current device state : start
Desired device state : start
When change state : now
Calls/Channels : 0
Active : 0
Held : 0
Dialing : 0
Alerting : 0
Incoming : 0
Waiting : 0
Releasing : 0
Initializing : 0

After "dongle reset dongle0"

raspbx*CLI> dongle show device state dongle0
-------------- Status -------------
Device : dongle0
State : Free
Audio : /dev/ttyUSB1
Data : /dev/ttyUSB2
Voice : Yes
SMS : Yes
Manufacturer : huawei
Model : E160
Firmware : 11.609.10.02.432
IMEI : 3547640311XXXXX
IMSI : 2142200033XXXXX
GSM Registration Status : Registered, roaming
RSSI : 12, -89 dBm
Mode : WCDMA
Submode : WCDMA
Provider Name : movistar
Location area code : B33
Cell ID : E74B
Subscriber Number : +346420XXXXX
SMS Service Center : +346422XXXXX
Use UCS-2 encoding : Yes
USSD use 7 bit encoding : No
USSD use UCS-2 decoding : Yes
Tasks in queue : 0
Commands in queue : 0
Call Waiting : Disabled
Current device state : start
Desired device state : start
When change state : now
Calls/Channels : 0
Active : 0
Held : 0
Dialing : 0
Alerting : 0
Incoming : 0
Waiting : 0
Releasing : 0
Initializing : 0

bg111 · Answer 1 · Fri May 12 2017 00:55:34 GMT+0800 (China Standard Time)

Its not crash.
This problems caused maybe by network maybe by SIM maybe by dongle itself.
I think you should monitor dongles for this state and reset with help of external scripts for example.
In public chan_dongle watchdog functons not implemented.

rlzmaxx · Answer 2 · Fri May 12 2017 01:05:22 GMT+0800 (China Standard Time)

I can trace from Network side and I am not seeing Location update from the dongle's IMSI. So that why seems the dongle is not trying to register in the network. Ruben Lezama El 11 may. 2017 18:55, "bg111" <notifications@github.com> escribió:

…

Its not crash. This problems caused maybe by network maybe by SIM maybe by dongle itself. I think you should monitor dongles for this state and reset with help of external scripts for example. In public chan_dongle watchdog functons not implemented. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#246 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AbS2a15eKTuJngPJZRAXUD6nzphha-ARks5r4z2IgaJpZM4NXqiM> .

VGBLTSK · Answer 3 · Fri May 12 2017 02:35:36 GMT+0800 (China Standard Time)

rlzmaxx, bg111 is right. There might be a whole bunch of factors making your dongle loose a network.
Try to check the network signal first. You may use AT+CSQ AT command and see what your dongle responses. It might be a bad sim card as well. If you have an option to test with a different one - it is definitely worth of checking. Your forlorn hope might be a script to check dongle state put on cron and triggered every 5-10 mins. In the event that your dongle lost a network you may want to use this https://gist.github.com/x2q/5124616 tool to reset it. This is what I have for those cases when my USB dongles become inaccessible due to the lack of power after some power spikes.
It goes like this:

You can reset USB bus via this C program. https://gist.github.com/x2q/5124616

Download C code from github

wget -c --no-check-certificate https://gist.githubusercontent.com/x2q/5124616/raw/3f6e5f144efab2bc8e9d02b95b8301e1e0eab669/usbreset.c -O usbreset.c
Compile C code as usbreset
cc usbreset.c -o usbreset
Give execute permission to program
chmod +x usbreset
List your USB devices via lsusb command
lsusb
You should see USB device entries in your output and check device you want to reset for.

Bus 002 Device 003: ID 0fe9:9010 DVICO

Run usbreset program with arguments

sudo ./usbreset /dev/bus/usb/002/003

Cheers.

bg111 · Answer 4 · Fri May 12 2017 02:45:12 GMT+0800 (China Standard Time)

It is not USB issue

VGBLTSK · Answer 5 · Fri May 12 2017 03:02:41 GMT+0800 (China Standard Time)

He said that reset was useful. Since it works why not giving it a try?

rlzmaxx · Answer 6 · Fri May 12 2017 03:50:19 GMT+0800 (China Standard Time)

Yes, resetting worked,I think I will implement some script to track dongle registration state and in case it is not registered , execute the reset. Thank you. Ruben Lezama El 11 may. 2017 21:02, "VGBLTSK" <notifications@github.com> escribió:

…

He said that reset was useful. Since it works why not giving it a try? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#246 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AbS2a1JC8FRsgxWLMjl6RvvEhVvWmBgWks5r41tSgaJpZM4NXqiM> .

donaldf26 · Answer 7 · Sun Jul 30 2017 21:58:27 GMT+0800 (China Standard Time)

Ruben, Did you manage to implement any script that you could share here.
I have this script but I got issues getting to work, Can someone please fine tune this. Thanks

#!/bin/sh
#asterisk -rvx "dongle show devices" | grep -c "Free"
#asterisk -rvx "dongle show devices" | grep -c "NONE"
/usr/sbin/asterisk -rvx "dongle show device state dongle0" | grep -c "GSM not registered"
date >> /var/log/asterisk/dongle0-status.log
/usr/sbin/asterisk -rvx "dongle show device state dongle0" >> /var/log/asterisk/dongle0-status.log
if [ $? -eq 1 ]
#if [ $? == 0 ]
then
date >> /var/log/asterisk/dongle0-running.log
/usr/sbin/asterisk -rvx "dongle show device state dongle0" >> /var/log/asterisk/dongle0-running.log
exit 0
else
date >> /var/log/asterisk/dongle0-down.log
/usr/sbin/asterisk -rvx "dongle show device state dongle0" >> /var/log/asterisk/dongle0-down.log
date >> /var/log/asterisk/dongle0-reset.log
/usr/sbin/asterisk -rvx "dongle reset dongle0"
exit 1
fi

rlzmaxx · Answer 8 · Sun Jul 30 2017 23:47:00 GMT+0800 (China Standard Time)

Hi, I haven't applied the script since the modem became estable in other location. It wasn't a problem of the modem itself, it was something more related to the network. Ruben Lezama El 30 jul. 2017 3:58 p. m., "donaldf26" <notifications@github.com> escribió:

…

Ruben, Did you manage to implement any script that you could share here. I have this script but I got issues getting to work, Can someone please fine tune this. Thanks #!/bin/sh #asterisk -rvx "dongle show devices" | grep -c "Free" #asterisk -rvx "dongle show devices" | grep -c "NONE" /usr/sbin/asterisk -rvx "dongle show device state dongle0" | grep -c "GSM not registered" date >> /var/log/asterisk/dongle0-status.log /usr/sbin/asterisk -rvx "dongle show device state dongle0" >> /var/log/asterisk/dongle0-status.log if [ $? -eq 1 ] #if [ $? == 0 ] then date >> /var/log/asterisk/dongle0-running.log /usr/sbin/asterisk -rvx "dongle show device state dongle0" >> /var/log/asterisk/dongle0-running.log exit 0 else date >> /var/log/asterisk/dongle0-down.log /usr/sbin/asterisk -rvx "dongle show device state dongle0" >> /var/log/asterisk/dongle0-down.log date >> /var/log/asterisk/dongle0-reset.log /usr/sbin/asterisk -rvx "dongle reset dongle0" exit 1 fi — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#246 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AbS2a6B6A8i0Hi2MI7c1Xzy2eHOewvc8ks5sTIwFgaJpZM4NXqiM> .

Syavick · Answer 9 · Thu May 31 2018 05:10:03 GMT+0800 (China Standard Time)

donaldf26: Corrected your script. It works now!

#!/bin/bash
if /usr/sbin/asterisk -rx "dongle show device state dongle0" | grep -c "GSM not registered" >> /dev/null
then
date >> /var/log/asterisk/dongle0-down.log
/usr/sbin/asterisk -rx "dongle show device state dongle0" >> /var/log/asterisk/dongle0-down.log
date >> /var/log/asterisk/dongle0-reset.log
/usr/sbin/asterisk -rx "dongle reset dongle0"
else
date >> /var/log/asterisk/dongle0-running.log
/usr/sbin/asterisk -rx "dongle show device state dongle0" >> /var/log/asterisk/dongle0-running.log
fi

Alexey · Answer 10 · Wed Aug 07 2019 19:44:17 GMT+0800 (China Standard Time)

Hi
Sorry from my english :-)

I have also a problem and not find in internet possible dongle state's...
My dongle can have state Free (is OK), GSM not registered and Active1.
Often dongle not work and have state Active... Surely in time no active calls in CLI :-)

And i change first string in your script:
if /usr/sbin/asterisk -rx "dongle show device state dongle0" | grep "State" |grep -cv "Free" >> /dev/null

Syavick · Answer 11 · Wed Aug 07 2019 21:02:37 GMT+0800 (China Standard Time)

It's good to add to cron daily rebooting of server with asterisk. This script don't always help me if server is running for more than 1 week.

lo0 · Answer 12 · Mon Sep 30 2019 18:55:50 GMT+0800 (China Standard Time)

Hello everyone!
I've had a similar problem and here is how I solved it:
Ifno:
OS: Debian 10
Asterisk 13.28.1
Dongle: Huawei e1552
Firmware: 11.608.12.00.00

Connect to modem via minicom
Check the registration status of the device (AT+CGREG?) and got +CGREG: 0,5 (Registered, non-home network)

Results of network registration status commans,
0,0 – not registered, MT is not currently searching a new operator to register to
0,1 – Registered, home network
0,2 – Searching
0,3 – Registration denied
0,5 – Registered, non-home network

Call from another phone to my modem
Answer voice call using AT command ATA
After 20-30 sec I hear noises and disconnect
Check the registration status of the device and got 0,2 – Searching

So, Then I changed my mobile operator (with network status: 0,1 – Registered, home network) and the problem is gone.