Re: [dongle] Receive NO CARRIER / Outcall not possible

1,500 views
Skip to first unread message

Paco Gil

unread,
Feb 24, 2013, 1:52:43 PM2/24/13
to chan_...@googlegroups.com
can you call the usual way? I mean, using a sip peer or using originate command...  Anyway, maybe E303 is not supported by chan_dongle :(


On Sun, Feb 24, 2013 at 1:54 PM, Gregor <ma...@gregorfischer.com> wrote:
Hi,


I try to make an outcall by writing the following spoolfile to /var/spool/asterisk/outgoing on my Raspberry Pi running Wheezy.

Channel: Dongle/dongle0/+43xxxxxxx
Application: Playback
Data: hello-world
Priority: 1
MaxRetries: 0
RetryTime: 15
WaitTime: 4


The result (error) is always the same:

[Feb 23 23:44:58] ERROR[8598]: at_response.c:1807 at_response: [dongle0] Receive NO CARRIER
[Feb 23 23:44:58] NOTICE[1135]: pbx_spool.c:353 attempt_thread: Call failed to go through, reason (8) Congestion (circuits busy)
[Feb 23 23:44:58] NOTICE[1135]: pbx_spool.c:356 attempt_thread: Queued call to Dongle/dongle0/+43xxxxxxxx expired without completion after 0 attempts
[Feb 23 23:45:00] ERROR[8598]: chan_dongle.c:433 do_monitor_phone: [dongle0] timedout while waiting 'OK' in response to 'ATD'


The reason therefore seem to be the state of the dongle:

-------------- Status -------------
  Device                  : dongle0
  State                   : Free
  Audio                   : /dev/ttyUSB1
  Data                    : /dev/ttyUSB2
  Voice                   : Yes
  SMS                     : Yes
  Manufacturer            : huawei
  Model                   : E303
  Firmware                : 21.157.01.00.801
  IMEI                    : 868988012327604
  IMSI                    : 232017521007530
  GSM Registration Status : Registered, home network
  RSSI                    : 18, -114 dBm
  Mode                    : No Service
  Submode                 : No service
  Provider Name           : A1
  Location area code      : "426B"
  Cell ID                 : "299B"
  Subscriber Number       : Unknown
  SMS Service Center      : 002B003400330036003
  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


But it's not that the dongle is not working at all. I succeeded to send SMS via the console:

raspberrypi*CLI> dongle sms dongle0 +43664xxxxxxx "test message from asterisk"

[Feb 24 12:55:01] NOTICE[2042]: at_response.c:257 at_response_ok: [dongle0] Successfully sent SMS message 0x1ebe230




I tried to change the mode of the dongle with AT^SYSCFG command. But the error remains.





This is my dongle.conf file

[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=dongle-incomming                ; context for incoming calls, SMS and USSD
group=0                         ; calling group
rxgain=0                        ; increase the incoming volume; may be negative
txgain=0                        ; increase the outgoint volume; may be negative
autodeletesms=no               ; auto delete incoming sms  GREGOER yes > no
resetdongle=no                ; reset dongle during initialization with ATZ command GREGOER yes > no
u2diag=-1                       ; set ^U2DIAG parameter on device (0 = disable everything except modem function) 
; -1 not use ^U2DIAG command
usecallingpres=yes              ; use the caller ID presentation or not
callingpres=allowed_passed_screen ; set caller ID presentation. By default use default network settings
disablesms=yes                   ; disable of SMS reading from device when received. Enable this option to disable GREGOER no > yes
; sms reception. Use smsaspdu=yes to avoid problem when SMS is too long in TEXT mode.
smsaspdu=yes                    ; if 'yes' send SMS in PDU mode.
language=de                    ; set channel default language GREGOER en > de
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                      ; if 'yes' no load this device and just ignore this section
exten=+43xxxx              ; exten for start incoming calls, only in case of Subscriber Number not available!,
; also set to CALLERID(dnid)

dtmf=relax ; control of incoming DTMF detection, possible values:
;   off    - off DTMF tone detection, voice data passed to asterisk unaltered
;              use this value for gateways or if you do not use IVR in diaplan
;   inband - do DTMF tones detection
;   relax  - like inband but with relaxdtmf option
;  default is 'relax' for backward compatibility




; dongle required settings
[dongle0]
audio=/dev/ttyUSB1              ; tty port for audio connection;        
data=/dev/ttyUSB2              ; tty port for AT commands; 

; or you can omit both audio and data parameters and use imei=123456789012345 and/or imsi=612849384756451
; imei and imsi must contain exactly 15 digits !
        ;  imei/imsi discovery is available on Linux only

imei=868988012327604
imsi=232017521007530
; if you set audio and data parameter together with imei and/or imsi, audio and data is used.
; you can use both imei and imsi together. In this case exact match by imei and imsi is required.



lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard


ls /dev/ttyUSB*
/dev/ttyUSB0  /dev/ttyUSB1  /dev/ttyUSB2


lsmod
Module                  Size  Used by
ppp_deflate             3828  0
zlib_deflate           21863  1 ppp_deflate
zlib_inflate           15631  1 ppp_deflate
bsd_comp                5247  0
ppp_async               7217  0
crc_ccitt               1465  1 ppp_async
ppp_generic            25057  3 ppp_async,bsd_comp,ppp_deflate
slhc                    5600  1 ppp_generic
snd_bcm2835            12808  0
snd_pcm                74834  1 snd_bcm2835
snd_seq                52536  0
snd_timer              19698  2 snd_seq,snd_pcm
snd_seq_device          6300  1 snd_seq
snd                    52489  5 snd_seq_device,snd_timer,snd_seq,snd_pcm,snd_bcm2835
snd_page_alloc          4951  1 snd_pcm
option                 16816  2
usb_wwan               12102  1 option
usbserial              34545  6 usb_wwan,option
sr_mod                 13030  0
cdrom                  38147  1 sr_mod


dmesg | grep ttyUSB
[    7.468104] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB0
[    7.596786] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB1
[    7.722359] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB2



dmesg
...
[    3.284620] usb 1-1.3: New USB device found, idVendor=12d1, idProduct=1506
[    3.297338] usb 1-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber          =0
[    3.307663] usb 1-1.3: Product: HUAWEI Mobile
[    3.314974] usb 1-1.3: Manufacturer: HUAWEI
[    3.333490] scsi0 : usb-storage 1-1.3:1.4
[    3.349198] scsi1 : usb-storage 1-1.3:1.5
[    4.193042] udevd[141]: starting version 175
[    4.334104] scsi 0:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ          : 0 ANSI: 2
[    4.383150] scsi 1:0:0:0: Direct-Access     HUAWEI   SD Storage       2.31 PQ          : 0 ANSI: 2
[    4.434592] sd 1:0:0:0: [sda] Attached SCSI removable disk
[    4.754310] sr0: scsi-1 drive
[    4.760254] cdrom: Uniform CD-ROM driver Revision: 3.20
[    4.834064] sr 0:0:0:0: Attached scsi CD-ROM sr0
[    6.877667] usbcore: registered new interface driver usbserial
[    7.076764] USB Serial support registered for generic
[    7.137269] usbcore: registered new interface driver usbserial_generic
[    7.253167] usbserial: USB Serial Driver core
[    7.270108] USB Serial support registered for GSM modem (1-port)
[    7.362710] option 1-1.3:1.0: GSM modem (1-port) converter detected
[    7.468104] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB0
[    7.543281] option 1-1.3:1.2: GSM modem (1-port) converter detected
[    7.596786] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB1
[    7.670268] option 1-1.3:1.3: GSM modem (1-port) converter detected
[    7.722359] usb 1-1.3: GSM modem (1-port) converter now attached to ttyUSB2
[    7.793133] usbcore: registered new interface driver option
...



Could anyone please help me on that?

-Gregor


--
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/groups/opt_out.
 
 

Gregor

unread,
Jul 7, 2013, 2:38:23 PM7/7/13
to chan_...@googlegroups.com
Hi Aron,
Thank you very much for the tipp. How can I upgrade my dongle firmware?
br gregor
Reply all
Reply to author
Forward
0 new messages