Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chan_dongle sometimes loses 3G dongle connection #48

Open
oooo1 opened this issue Oct 22, 2017 · 5 comments
Open

chan_dongle sometimes loses 3G dongle connection #48

oooo1 opened this issue Oct 22, 2017 · 5 comments
Labels
help wanted

Comments

@oooo1
Copy link

oooo1 commented Oct 22, 2017

Asterisk 13.12 with Huawei E367 and the last this chan_dongle version is installed at Ubuntu 14.04 x64.

Time to time, Asterisk chan_dongle lose 3G dongle connection.
That is 'dongle show devices' sows 'Not connected' .

The worst thing in the situation that there are not any useful messages in Asterisk messages log.
Only:
[Oct 22 12:53:50] ERROR[11786] chan_dongle.c: [Huawei7] Lost connection to Dongle

Sometimes such message is appeared:
[Oct 20 08:55:45] WARNING[8356][C-0000001b] channel.c: [Dongle/HuaweiTl25667-0100000017] Don't know how to indicate condition 22
[Oct 20 08:55:52] ERROR[11786] at_response.c: [HuaweiTl25667] Receive NO CARRIER
In the case, after this message dongle continued working.

Firstly, I thought that the reason is autosuspend - no any incoming / outgoing calls were made within 12 hours.
But ls /dev shows all devices: audio, data and someelse device for this dongle.

Sendind sms from minicom was successfull.
That is minicom -D /dev/dongle_data and
AT+CMGF=1
AT+CMGS="+..................."
Test.
<ctrl+z>
passed successfully.

Helps only Asterisk reload command.
What and where are reasons of sudden disconnection at ?
@gamba47
Copy link

gamba47 commented Oct 23, 2017

Some times this is a power issue, please connect your dongle directly to your motherboard. Avoid use of usb hubs at least for this test.

First of all try to detect on "dmesg" if you see any disconection or changes on devs
Take a look at this #37

Best regards.

gamba47

@oooo1
Copy link
Author

oooo1 commented Oct 29, 2017 •
edited
Loading

I thought so firstly.
But I have 7 port USB haub with connected external power supply.
And mainly it was happended after some non using time but seldom it was after 30-60 minutes after using.
I thought that the reason is autosuspend.
But as I wrote modem is disconnected in Asterisk only (chan_dongle) , not disconnected from system at all.
In the time I can send sms, for example, using minicom.

@oooo1
Copy link
Author

oooo1 commented Nov 11, 2017 •
edited
Loading

I set up power/control="on" and power/autosuspend="-1" for port occupied by dongle (such as 2-1.1.1)
Reboot the server.
I have 4.2.0-42-generic kernel.
And after about 17 hours I got "dongle lost connection" at log.
And dongle show device state MySuperDongle gave out the following:

 Device                  : MySuperDongle 
  State                   : Not connected Start scheduled
  Audio                   : /dev/ModemAudioPort
  Data                    : /dev/ModemDataPort
  Voice                   : No
  SMS                     : No
  Manufacturer            :
  Model                   :
  Firmware                :
  IMEI                    :
  IMSI                    :
  GSM Registration Status : Unknown
  RSSI                    : 0, <= -113 dBm
  Mode                    : No Service
  Submode                 : No service
  Provider Name           : NONE
  Location area code      :
  Cell ID                 :
  Subscriber Number       : Unknown
  SMS Service Center      :
  Use UCS-2 encoding      : No
  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    : stop
  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

And it is up after 10 minutes.
So, is it normal behaviour to lost registration or connection for 10 minutes ?

@wdoekes wdoekes changed the title Time to time dongle disconnection from Asterisk chan_dongle. chan_dongle sometimes loses 3G dongle connection Mar 5, 2018
@wdoekes
Copy link
Owner

wdoekes commented Mar 5, 2018

I'm sorry, this is not something I can debug. Feel free to discuss this issue further here. If you come up with more clues I may be able to fix something for you.

@CpServiceSpb
Copy link

So, discovery dongle by imei and imsi don; t work on CubieTruck (armv7l architecture) .
Ports must be specified exactly.

shalzz pushed a commit to shalzz/asterisk-chan-dongle that referenced this issue Apr 23, 2022
@spacedream @shalzz
# This is a combination of 54 commits.
69b112f 
# This is the 1st commit message:

Create DONATIONS.txt
# This is the commit message wdoekes#2:

Update README.md
# This is the commit message wdoekes#3:

Update DONATIONS.txt
# This is the commit message wdoekes#4:

Update DONATIONS.txt
# This is the commit message wdoekes#5:

Update DONATIONS.txt
# This is the commit message wdoekes#6:

Update chan_quectel.h
# This is the commit message wdoekes#7:

Update README.md
# This is the commit message wdoekes#8:

Update cpvt.h
# This is the commit message wdoekes#9:

Add files via upload
# This is the commit message wdoekes#10:

Delete DONATIONS.txt
# This is the commit message wdoekes#11:

Update README.md
# This is the commit message wdoekes#12:

Update README.md
# This is the commit message wdoekes#13:

Update README.md
# This is the commit message wdoekes#14:

Add files via upload
# This is the commit message wdoekes#15:

Update README.md
# This is the commit message wdoekes#16:

Update README.md
# This is the commit message wdoekes#17:

Update README.md
# This is the commit message wdoekes#18:

Update README.md
# This is the commit message wdoekes#19:

Update README.md
# This is the commit message wdoekes#20:

Update README.md
# This is the commit message wdoekes#21:

Update README.md
# This is the commit message wdoekes#22:

Update README.md
# This is the commit message wdoekes#23:

Add files via upload

Added Simcom support
# This is the commit message wdoekes#24:

Update README.md
# This is the commit message wdoekes#25:

Update README.md
# This is the commit message wdoekes#26:

Added support for Quectel UAC configuration
# This is the commit message wdoekes#27:

Conf file when using UAC
# This is the commit message wdoekes#28:

Update README.md
# This is the commit message wdoekes#29:

Update README.md
# This is the commit message wdoekes#30:

Quectel CREG correction

chan_dongle code assumes 4 parameters in response to command and 3 for URC. However quectel provides 5 and 4 respectively. This fix helps pass on correct status of registration.
# This is the commit message wdoekes#31:

No force registration status

Due to CREG parse issues, earlier registration status was always kept on, now will show unregistered if not connected to network
# This is the commit message wdoekes#32:

Create readme.md
# This is the commit message wdoekes#33:

For compilation with openwrt sdk
# This is the commit message wdoekes#34:

Support for openwrt sdk compilation
# This is the commit message wdoekes#35:

Fix for lac and cell id

Ref IchthysMaranatha#6
Post fix values may have a trailing double quote for quectel devices
# This is the commit message wdoekes#36:

Updated call ids for simcom

Add call termination for call ids 1 and 2
# This is the commit message wdoekes#37:

comment for simcom audio

Added default audio port for simcom in comment
# This is the commit message wdoekes#38:

Integrated ALSA support for UAC

Integrated driver for ALSA added, no need for bridging additional Asterisk ALSA channel when using UAC mode. Please use non-ALSA integrated branch if there is no need for UAC and you wish to avoid alsa dependency when compiling and running
# This is the commit message wdoekes#39:

Update COPYRIGHT.txt

Attribute copyright for alsa code copied from chan_alsa.c https://github.com/asterisk/asterisk/blob/master/channels/chan_alsa.c
# This is the commit message wdoekes#40:

Update README.md
# This is the commit message wdoekes#41:

Conf file with UAC device support
# This is the commit message wdoekes#42:

UAC mode conf file
# This is the commit message wdoekes#43:

Added alsa-lib for compilation
# This is the commit message wdoekes#44:

Delete Makefile.in
# This is the commit message wdoekes#45:

alsa-lib dependency addition
# This is the commit message wdoekes#46:

Fix for simcom audio issues with immediate answer in dialplan
# This is the commit message wdoekes#47:

Note for Quectel serial audio

Added remark to disable gps messages
# This is the commit message wdoekes#48:

Added note for Pi users
# This is the commit message wdoekes#49:

Quectel creg formatting fix

Removed trailing double quotes in reporting lac/cid
# This is the commit message wdoekes#50:

add gitattributes
# This is the commit message wdoekes#51:

Send DTMF using AT command

Corrected at command for dtmf generation
# This is the commit message wdoekes#52:

Fix for busy on call rejection for simcom

For those who receive 'busy' additionally on call rejection when dialling out. Author only receives 'no carrier' on rejection. Reported and solved by @mpmc here IchthysMaranatha#22
# This is the commit message wdoekes#53:

Removal of redundant closetty
# This is the commit message wdoekes#54:

Update busy fix for call rejection

Updated fix as submitted by @mpmc here IchthysMaranatha#22
Author does not receive busy response on call rejection
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@wdoekes @oooo1 @gamba47 @CpServiceSpb