Calling not work Huawei E173 firmware 11.X, unlocked, no PIN, Voice: Yes

[Michal]

Hi guys,

I have modem Huawei E173 firmware 11.X, unlocked, no PIN, Voice: Yes. I tried to send and receive SMS to demonstrate that modem is working and actually SMS works OK, I can see logs and results in console. But when I try to call to modem's number, nothing happens just BUSY tone (no message in /var/log/asterisk/messages or asterisk's CLI). No message appears also after setting "core set verbose 3" in asterisk's CLI.

1. What am I doing wrong? Why I cannot see nothing in console after calling to modem's number?
   
2. I am about to create SIP2GSM and GSM2SIP gateway. Could you please point me on right direction?
3. Is there some examples how to route GSM to SIP and SIP to GSM?
4. Why when I commented out audio and data in dongle.conf and leave just imei and imsi modem cannot be detected? According to documentation it should be possible - (you can omit both audio and data together and use imei=123456789012345 and/or imsi=123456789012345).
   

I am using Asterisk 1.8.13.1~dfsg-3 (latest stable Raspbian)

Here is output of DC Unlocker:
DC - Unlocker 2 Client 1.00.1034

Detecting modem :

selection :
manufacturer - Huawei modems
model - Auto detect (recommended)

Found modem         : E173
Model               : Huawei E173
IMEI                : 86...
Serial NR.          : XVABYA9311508962
Firmware            : 11.126.15.00.445
Hardware ver.       : CD1E153M
Voice feature       : enabled
SIM Lock status     : unlocked
Wrong codes entered : 0 (unlock attempts left : 10)

Here is output of chan_dongle:
raspberrypi*CLI> dongle show devices
ID           Group State      RSSI Mode Submode Provider Name  Model      Firmware          IMEI             IMSI             Number       
dongle0      0     Free       10   0    0       O2 - SK        E173       11.126.15.00.445  86...  23...  Unknown      
raspberrypi*CLI> dongle show version

chan_dongle: Huawei 3G Dongle Channel Driver, Version 1.1, Revision 16
Project Home: http://code.google.com/p/asterisk-chan-dongle
Bug Reporting: http://code.google.com/p/asterisk-chan-dongle/issues/list

raspberrypi*CLI> dongle show device settings dongle0
------------- Settings ------------
  Device                  : dongle0
  Audio                   : /dev/ttyUSB0
  Data                    : /dev/ttyUSB1
  IMEI                    : 86...
  IMSI                    : 23...
  Channel Language        : en
  Context                 : dongle0
  Exten                   : +4219...
  Group                   : 0
  RX gain                 : 0
  TX gain                 : 0
  U2Diag                  : -1
  Use CallingPres         : Yes
  Default CallingPres     : Presentation Allowed, Passed Screen
  Auto delete SMS         : Yes
  Disable SMS             : No
  Reset Dongle            : Yes
  SMS PDU                 : Yes
  Call Waiting            : auto
  DTMF                    : relax
  Minimal DTMF Gap        : 45
  Minimal DTMF Duration   : 80
  Minimal DTMF Interval   : 200
  Initial device state    : start

raspberrypi*CLI> dongle show device state dongle0
-------------- Status -------------
  Device                  : dongle0
  State                   : Free
  Audio                   : /dev/ttyUSB0
  Data                    : /dev/ttyUSB1
  Voice                   : Yes
  SMS                     : Yes
  Manufacturer            : huawei
  Model                   : E173
  Firmware                : 11.126.15.00.445
  IMEI                    : 86...
  IMSI                    : 23...
  GSM Registration Status : Registered, home network
  RSSI                    : 10, -119 dBm
  Mode                    : No Service
  Submode                 : No service
  Provider Name           : O2 - SK
  Location area code      : CB86
  Cell ID                 : 2B9F
  Subscriber Number       : Unknown
  SMS Service Center      : +421949909909
  Use UCS-2 encoding      : Yes
  USSD use 7 bit encoding : Yes
  USSD use UCS-2 decoding : No
  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

Here is my dongle.conf:

[general]
interval=15
[defaults]
context=dongle0         ; 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 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=no
language=en                     ; set channel default language
smsaspdu=yes                    ; if 'yes' send SMS in PDU mode, feature implementation incomplete and we strongly recommend say 'yes'
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
callwaiting=auto
disable=no
initstate=start
exten=+4219...
dtmf=relax

[dongle0]
context=dongle0
audio=/dev/ttyUSB0
data=/dev/ttyUSB1
imei=86...
imsi=23...


Thanks a lot!
Michal

[Adrian Sandu]

Just like many before you who don't read before posting .. 

[Adrian Sandu]

ttyUSB0 is usually the ROOT

audio=/dev/ttyUSB1

data=/dev/ttyUSB2

group=0

[Marco Gaiarin]

Mandi! Michal
In chel di` si favelave...

> 4. Why when I commented out audio and data in dongle.conf and leave just imei

> and imsi modem cannot be detected? According to documentation it should be
> possible - (you can omit both audio and data together and use imei=
> 123456789012345 and/or imsi=123456789012345).

It is a common mistakes/trouble, simply your modem expose too much usb
feature, and linux/chan_dongle get confused.

Look at:

https://groups.google.com/forum/?hl=it#!topicsearchin/chan_dongle/authorname$3AGaiarin/chan_dongle/682OWOT-DQQ

for me, it suffices to do an at^udiag=0.

--
Marco ``Gaio'' Gaiarin | LUG Pordenone (http://www.pordenone.linux.it)
P.zza S. Tommaso, 20 | Lilliput BBS (http://bbs.lilliput.linux.it)
Cimpello di Fiume Veneto | Azione Cattolica - Concordia-Pordenone
33080 Pordenone (Italia) | (http://www.accanto.org)
Tel. +39-0434-56-1305 | http://www.gaiarin.it/ ga...@linux.it

[Michal]

Thanks! It worked, now my modem is successfully recognized. But still nothing happens when I am trying to call to modem's number. Why is that?

    -- [dongle0] IMEI 86... IMSI 23... found on data_tty=/dev/ttyUSB2 audio_tty=/dev/ttyUSB1
    -- [dongle0] Trying to connect on /dev/ttyUSB2...
    -- [dongle0] Dongle has connected, initializing...
    -- [dongle0] Dongle initialized and ready

Btw thanks a lot for quick responses, this is really great! You rocks! :)

[Michal]

Ok here the thing:

1. When I do "dongle cmd AT^U2DIAG=0", it disables voice (but modem is recognized)
   
2. So I enabled it again with DC Unlocker and tried voice in Windows - it worked
   
3. But now modem is again not recognized using IMEI or IMSI
4. So I tried to use audio=/dev/ttyUSB2 and data=/dev/ttyUSB1 or audio=/dev/ttyUSB1 and data=/dev/ttyUSB2, but I always get:
       -- [dongle0] Trying to connect on /dev/ttyUSB1...

1. 
       -- [dongle0] Dongle has connected, initializing...
   

1. [Jul 16 13:01:37] ERROR[3905]: chan_dongle.c:433 do_monitor_phone: [dongle0] timedout while waiting 'OK' in response to 'AT'
       -- [dongle0] Error initializing Dongle
       -- [dongle0] Dongle has disconnected
2. I found somewhere that this can be power problem, so I plugged it through supported USB hub, but still same 

So, it's not possible to use voice with Huawei E173? Why you have this modem in supported devices? (http://wiki.e1550.mobi/doku.php?id=requirements) What modem should I buy to use voice and someone tried it and it is working?

Thanks!

[Alejandro Donato]

you can chek it using minicom to get connected directly to ttyUSB data
line and send AT commands to check responses.

AT+CLAC? ie. gives you al modem features, get the huawei AT command
reference manual (google for it) and check all features in your modem.

Some firmwares are blocked to some features, model is not the only
parameter to check, firmware version is important too (it does modem
respond to the channel driver correctly)

U2DIAG is not mandatory, and even, you can set usb_modeswitch to change
modem init at a lower level, with no need to reswitch it at channel
instance.

Thats why modem is supported by the channel, maybe need a little work
from you to get it in the right direction.

Hope this info helps

Alejandro

El 16/07/13 08:09, Michal escribi�:
> Ok here the thing:
>
> 1. When I do "dongle cmd AT^U2DIAG=0", it disables voice (but modem is
> recognized)
> 2. So I enabled it again with DC Unlocker and tried voice in Windows -
> it worked
> 3. But now modem is again not recognized using IMEI or IMSI
> 4. So I tried to use audio=/dev/ttyUSB2 and data=/dev/ttyUSB1 or

> audio=/dev/ttyUSB1 and data=/dev/ttyUSB2, but I always get:
> -- [dongle0] Trying to connect on /dev/ttyUSB1...
> -- [dongle0] Dongle has connected, initializing...
> [Jul 16 13:01:37] ERROR[3905]: chan_dongle.c:433 do_monitor_phone:
> [dongle0] timedout while waiting 'OK' in response to 'AT'
> -- [dongle0] Error initializing Dongle
> -- [dongle0] Dongle has disconnected

> 5. I found somewhere that this can be power problem, so I plugged it

> through supported USB hub, but still same
>
> So, it's not possible to use voice with Huawei E173? Why you have this
> modem in supported devices?
> (http://wiki.e1550.mobi/doku.php?id=requirements) What modem should I
> buy to use voice and someone tried it and it is working?
>
> Thanks!
>

> --
> 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.
>
>

[Michal]

I don't know what I did, but it just started working (maybe I was too quick). Now I cannot reproduce errors that happened, rebooting, setting up things that can mess up another things, but it just works OK. Meanwhile I was able to set up GSM2SIP and SIP2GSM gateway. Cheers! Thanks!

On Tuesday, July 16, 2013 1:27:44 PM UTC+2, Alejandro Donato wrote:

you can chek it using minicom to get connected directly to ttyUSB data
line and send AT commands to check responses.

AT+CLAC? ie. gives you al modem features, get the huawei AT command
reference manual (google for it) and check all features in your modem.

Some firmwares are blocked to some features, model is not the only
parameter to check, firmware version is important too (it does modem
respond to the channel driver correctly)

U2DIAG is not mandatory, and even, you can set usb_modeswitch to change
modem init at a lower level, with no need to reswitch it at channel
instance.

Thats why modem is supported by the channel, maybe need a little work
from you to get it in the right direction.

Hope this info helps

Alejandro

El 16/07/13 08:09, Michal escribi�:

[Giovanni]

Hello,

1) copy and paste the result of lsusb command and please
2) your firmware is 11.126.15.00.445 and the last firmware for E173 is 11.126.85.00.209 please consider the firmware update.

You get the update on this link: www.gbme.com.br/E173Update.rar
for the password to update please send me em PVT the IMEI of modem.

3) your dongle.conf not is good configured use this example:

[dongle0]
context=dongle0
imei=86...

~~~~~~~~~~~~~~~~ 

My last labs test win E303: goo.gl/sOAtB

i have tested with success E153, E156, E3131, E160, E303, E1550, E1553, E173, K3520

Giovanni

2013/7/16 Michal <tr...@mby.sk>

[Michal]

Hi guys,

• What protocol would you suggest to route SMS through SIP and SIP through SMS? SIMPLE or XMPP or something else?

I have started experiencing one way audio - from GSM to SIP I cannot hear anything. It started after few calls (I didn't restart anything or change), so I thought it must be a firewall or something, so I start another computer and it works there. I saw somewhere here that someone is trying to solve one way audio on E173. But in most cases it is SIP UDP problem, so maybe it helps someone sometime :)

Giovanni, I don't want to upgrade, because now everything works for me.

M.

[Marco Gaiarin]

Mandi! Michal
In chel di` si favelave...

> • What protocol would you suggest to route SMS through SIP and SIP through

> SMS? SIMPLE or XMPP or something else?

Look at list archives.

1) as a first try, i've setup a *incoming* gateway via XMPP (really,
gtalk); so every incoming SMS are routed to the gtalk account of mine
and my wife. This easy and works.

2) then, i've setup a ''gateway'' (eg, bidirectional) between the
dongle and my SMS-capable gigaset cordless phone, using asterisk
bultin sms capability.
But the setup is really clumsky, i've hit two major trouble:

a) the SMS support of asterisk (or at least, the gigaset
implementation of the specs ;) depend too much on proper timings, so,
even i've fiddled a bit with delay, some SMS get lost (or at least,
i've to get the time to write a proper queue management to resend
the message that does not get sent on the first try).

b) chan_dongle seems to handle very well sms receiving, but on the
sending part does some mistakes (on charset, on message lenght, ...)
and most of the sms get lost/rejected by the carrier.


So, pratically, it works, but really nothing more then an 'hello world'.

[Michal]

Hi,

I have just finished configuration similar to yours and you are right, it is clumsky. I ended up writing Jabber API on the top of libgammu project. This so far works great. I can call using SIP and simultaneously send SMS. But there is much work ahead :)

M.

[Marco Gaiarin]

Mandi! Michal
In chel di` si favelave...

> I have just finished configuration similar to yours and you are right, it is
> clumsky. I ended up writing Jabber API on the top of libgammu project. This so
> far works great. I can call using SIP and simultaneously send SMS. But there is
> much work ahead :)

So, you are using, on the same box, with the same dongle, gammu and
asterisk at the same time?

Interesting... please, give more detail!

[Alejandro Donato]

As a comment, i have a playSMS box using dongles in coexistence with
asterisk. But it's impossible to make them co-use same modems, just
because both of the systems "monopolize" the modems.

Dongle channel is the best (IMHO) to manage the whole thing, just
because it can perfectly handle SMS. Maybe, an AGI script to process the
data into asterisk, correcting the way they are processed. Or some work,
directly, in the chan code. AT commands and responses are, relatively
easy to be understanded.


El 17/07/13 08:37, Marco Gaiarin escribi�:

[Michal]

Hi guys,

I managed to get working configuration both calls and SMS simultaneously (when calling you can send/receive SMS). Check out my final configuration:

• https://docs.google.com/file/d/0B-k-0CcqRTQcbjF3ZEVCVF9Dc2M/edit?usp=sharing
  

You cannot handle receiving messages using smsd (there is asterisk error message on receive), but this is good enough handled by dongle, thus smsd is just for sending. I tried this configuration many times and it worked like a charm. There is much work on interfaces right now to be good to scale whole thing to real GSM gateway with 16 and more modems.

Thanks for help!

I try to post my progress.

M.

On Thursday, July 18, 2013 2:14:15 AM UTC+2, Alejandro Donato wrote:

As a comment, i have a playSMS box using dongles in coexistence with
asterisk. But it's impossible to make them co-use same modems, just
because both of the systems "monopolize" the modems.

Dongle channel is the best (IMHO) to manage the whole thing, just
because it can perfectly handle SMS. Maybe, an AGI script to process the
data into asterisk, correcting the way they are processed. Or some work,
directly, in the chan code. AT commands and responses are, relatively
easy to be understanded.

El 17/07/13 08:37, Marco Gaiarin escribi�:

[Marco Gaiarin]

Mandi! Michal
In chel di` si favelave...

> I try to post my progress.

...and also the code! ;-)

[Jayanth Acharya]

On Thursday, July 18, 2013 12:00:28 PM UTC+5:30, Michal wrote:

Hi guys,

I managed to get working configuration both calls and SMS simultaneously (when calling you can send/receive SMS). Check out my final configuration:

• https://docs.google.com/file/d/0B-k-0CcqRTQcbjF3ZEVCVF9Dc2M/edit?usp=sharing
  

You cannot handle receiving messages using smsd (there is asterisk error message on receive), but this is good enough handled by dongle, thus smsd is just for sending. I tried this configuration many times and it worked like a charm. There is much work on interfaces right now to be good to scale whole thing to real GSM gateway with 16 and more modems.

Michal,

Just started investigating Asterisk on RaspberryPi (same as you, if I guessed right).

Does your E173 have an extension in it's model# ? Example -- "E173U-1", "E173U-2" or "E173Z-1"
Apparently, the only E173's that work are the ones with the specific Qualcomm chipset.

Wondering if the 'Calling Number ID' is received and logged correctly in all/most cases ?

thanks,
Jay

[Bhagirath Verma]

Dear All

my name is bhagirath verma .from Mojolab Foundation Bhopal Madhya Pradesh India.

[Bhagirath Verma]

how to change prompt dongle configuration