[dongle0] timedout while waiting 'OK' in response to 'AT+COPS?'

1,579 views
Skip to first unread message

Israel Padron

unread,
May 14, 2014, 7:33:33 AM5/14/14
to chan_...@googlegroups.com
Hello,

I´m triying to setup 10 Huawei K3765 with chan_dongle and asterisk 11.9.0 on a Raspberry Pi B model. After plug 3 modem, I start receiving those warnings on console:

[dongle0] timedout while waiting 'OK' in response to 'AT+COPS?'

The modems goes offline and online, and also asterisk console freezes some seconds.

My chan_dongle configuration is:

[general]

interval=15                     ; Number of seconds between trying to connect to devices

;------------------------------ JITTER BUFFER CONFIGURATION --------------------------
;jbenable = yes                 ; Enables the use of a jitterbuffer on the receiving side of a
                                ; Dongle channel. Defaults to "no". An enabled jitterbuffer will
                                ; be used only if the sending side can create and the receiving
                                ; side can not accept jitter. The Dongle channel can't accept jitter,
                                ; thus an enabled jitterbuffer on the receive Dongle side will always
                                ; be used if the sending side can create jitter.

;jbforce = no                   ; Forces the use of a jitterbuffer on the receive side of a Dongle
                                ; channel. Defaults to "no".

;jbmaxsize = 200                ; Max length of the jitterbuffer in milliseconds.

;jbresyncthreshold = 1000       ; Jump in the frame timestamps over which the jitterbuffer is
                                ; resynchronized. Useful to improve the quality of the voice, with
                                ; big jumps in/broken timestamps, usually sent from exotic devices
                                ; and programs. Defaults to 1000.

;jbimpl = fixed                 ; Jitterbuffer implementation, used on the receiving side of a Dongle
                                ; channel. Two implementations are currently available - "fixed"
                                ; (with size always equals to jbmaxsize) and "adaptive" (with
                                ; variable size, actually the new jb of IAX2). Defaults to fixed.

;jbtargetextra = 40             ; This option only affects the jb when 'jbimpl = adaptive' is set.
                                ; The option represents the number of milliseconds by which the new jitter buffer
                                ; will pad its size. the default is 40, so without modification, the new
                                ; jitter buffer will set its size to the jitter value plus 40 milliseconds.
                                ; increasing this value may help if your network normally has low jitter,
                                ; but occasionally has spikes.

;jblog = no                     ; Enables jitterbuffer frame logging. Defaults to "no".
;-----------------------------------------------------------------------------------

[defaults]
; now you can set here any not required device settings as template
;   sure you can overwrite in any [device] section this default values

context=from-trunk-dongle       ; context for incoming calls
group=0                         ; calling group
rxgain=0                        ; increase the incoming volume; may be negative
txgain=0                        ; increase the outgoint volume; may be negative
autodeletesms=yes               ; auto delete incoming sms
resetdongle=yes                 ; reset dongle during initialization with ATZ command
u2diag=-1                       ; set ^U2DIAG parameter on device (0 = disable everything except modem function) ; -1 not us$
usecallingpres=yes              ; use the caller ID presentation or not
callingpres=allowed_passed_screen ; set caller ID presentation          by default use default network settings
disablesms=no                   ; disable of SMS reading from device when received
                                ;  chan_dongle has currently a bug with SMS reception. When a SMS gets in during a
                                ;  call chan_dongle might crash. Enable this option to disable sms reception.
                                ;  default = no

language=es                     ; set channel default language
smsaspdu=yes                    ; if 'yes' send SMS in PDU mode, feature implementation incomplete and we strongly recommend$
mindtmfgap=45                   ; minimal interval from end of previews DTMF from begining of next in ms
mindtmfduration=80              ; minimal DTMF tone duration in ms
mindtmfinterval=200             ; minimal interval between ends of DTMF of same digits in ms

callwaiting=auto                ; if 'yes' allow incoming calls waiting; by default use network settings
                                ; if 'no' waiting calls just ignored
disable=no                      ; OBSOLETED by initstate: if 'yes' no load this device and just ignore this section

initstate=start                 ; specified initial state of device, must be one of 'stop' 'start' 'remote'
                                ;   'remove' same as 'disable=yes'

exten=+1234567890               ; exten for start incoming calls, only in case of Subscriber Number not available!, also set$

dtmf=relax                      ; control of incoming DTMF detection, possible values:


[dongle0]
imei=35XXXXXXXXXXXXX

[dongle1]
imei=35XXXXXXXXXXXXX

[dongle2]
imei=35XXXXXXXXXXXXX

[dongle3]
imei=35XXXXXXXXXXXXX

[dongle4]
imei=354232040710569

[dongle5]
imei=35XXXXXXXXXXXXX

[dongle6]
imei=35XXXXXXXXXXXXX

[dongle7]
imei=35XXXXXXXXXXXXX

[dongle8]
imei=35XXXXXXXXXXXXX

[dongle9]
imei=35XXXXXXXXXXXXX

Any idea, how to make 10 dongles work same time without disconnects/freezes?

Thanks in advance,
Israel.

Ajmi Nessim

unread,
May 14, 2014, 7:48:47 AM5/14/14
to chan_...@googlegroups.com

Hey,

Try to use an external usb hub with a power supplier.
It should fix the problem.

Best regards

--
You received this message because you are subscribed to the Google Groups "dongle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chan_dongle...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

jorge montero

unread,
May 14, 2014, 7:54:19 AM5/14/14
to chan_...@googlegroups.com
Hello Israel,

It is good have news about you.

We talk about it, a few months ago, a few people feel the same with raspbery, normaly it is a problem about power, but with raspberry it is like a problem with USB hub.

Please try your configuration with a "big" computer :- )

ehh, que te echamos de menos por estas tierras ;-)

Best regards.

Jorge.


--
You received this message because you are subscribed to the Google Groups "dongle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chan_dongle...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Un saludo.

Jorge Montero

jan.be...@gmail.com

unread,
May 15, 2014, 5:44:20 AM5/15/14
to chan_...@googlegroups.com
I have almost the same problem but my RPi(Rev B) works correct up to 3 modems. After attaching 4 modem, devices in /dev/ are created and sytem works. After adding dongle in asterisk, system is unstable, temporarily freezing, modems timedout ...

I have 2 powered USB hubs and i have tryied all combination (all dongles in hub1, 2; split dongles into both hubs; hubs paralel, serial,..) without success.

I have heard about some USB issues in Raspberry but I dont known that these are responsible

My config with 3 modems
RPi Rev B
modems Huawei K3765
Linux raspbx 3.12.19+

root@raspbx1:~# lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 012: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 005: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
Bus 001 Device 006: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 001 Device 008: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
Bus 001 Device 011: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 010: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem


root@raspbx1:~# dmesg |grep -i dwc
[    0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708.boardrev=0xd bcm2708.serial=0x142187b8 smsc95xx.macaddr=B8:27:EB:21:87:B8 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 dwc_otg.fiq_enable=1 dwc_otg.fiq_fix_enable=0 dwc_otg.fiq_fsm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
[    1.425570] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    1.879318] WARN::dwc_otg_hcd_init:1042: FIQ DMA bounce buffers: virt = 0xdec14000 dma = 0x5ec14000 len=9024
[    1.891740] dwc_otg: Microframe scheduler enabled
[    1.912334] dwc_otg bcm2708_usb: DWC OTG Controller
[    1.918631] dwc_otg bcm2708_usb: new USB bus registered, assigned bus number 1
[    1.927352] dwc_otg bcm2708_usb: irq 32, io mem 0x00000000
[    1.961293] usb usb1: Product: DWC OTG Controller
[    1.967363] usb usb1: Manufacturer: Linux 3.12.19+ dwc_otg_hcd
[    1.992407] dwc_otg: FIQ enabled
[    1.992426] dwc_otg: NAK holdoff enabled
[    1.992436] dwc_otg: FIQ split-transaction FSM disabled
[    1.992454] Module dwc_common_port init
[    2.402336] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    2.932418] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    3.272375] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
[    3.442469] usb 1-1.2: new high-speed USB device number 5 using dwc_otg
[    3.792481] usb 1-1.3: new high-speed USB device number 6 using dwc_otg
[    4.242428] usb 1-1.3.1: new full-speed USB device number 7 using dwc_otg
[    4.442404] usb 1-1.3.1: new high-speed USB device number 8 using dwc_otg
[    4.822539] usb 1-1.3.4: new full-speed USB device number 9 using dwc_otg
[    5.002424] usb 1-1.3.4: new high-speed USB device number 10 using dwc_otg

I am realy interestng in this issue.

Jan

Dne středa, 14. května 2014 13:54:19 UTC+2 jorge montero napsal(a):

Israel Padron

unread,
May 15, 2014, 6:51:30 AM5/15/14
to chan_...@googlegroups.com
Hey Jorge!!

Nice to see you around! I´m using powered 10 port USB Hub, so I think you are right about the problem being from the raspberry. I was looking for a small portable solution, this is why I choose the raspberry, also I have raspberry working for another project (litecoin mining) working with 20 Usb Gridseed per raspberry,

Pronto volveré a la madre patria, para finales de año ya estaré por aquí!  ;)

Un abrazo,
Israel Padrón. 

Jan Benda

unread,
May 21, 2014, 5:16:21 AM5/21/14
to chan_...@googlegroups.com
yet my asterisk version

root@raspbx1:/etc/asterisk# asterisk -rx "core show version"
Asterisk 11.9.0 built by root @ raspbx on a armv6l running Linux on 2014-05-05 18:57:34 UTC



--
You received this message because you are subscribed to a topic in the Google Groups "dongle" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/chan_dongle/Vrqt_jM3rII/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chan_dongle...@googlegroups.com.

isa...@gmail.com

unread,
Jun 2, 2018, 11:40:01 AM6/2/18
to dongle
I was using x86 computer. And things are all the same.  I have only got 5 dongles


Israel Padron於 2014年5月15日星期四 UTC+8下午6時51分30秒寫道:

boaky...@gmail.com

unread,
Jun 22, 2018, 11:20:15 AM6/22/18
to dongle
Connected to Asterisk 11.19.0 currently running on localhost (pid = 1663)
localhost*CLI>
    -- [dongle0] Trying to connect on /dev/ttyUSB2...
    -- [dongle0] Dongle has connected, initializing...
[2018-06-22 14:18:58] ERROR[7427]: chan_dongle.c:436 do_monitor_phone: [dongle0] timedout while waiting 'OK' in response to 'AT'
    -- [dongle0] Error initializing Dongle
    -- [dongle0] Dongle has disconnected

Please any help?
Reply all
Reply to author
Forward
0 new messages