asterisk users - Aug 2009 - Problems using chan_sebi and Huawei E169G

Hi,

Having seen the messages on the dev list a couple of weeks ago about chan_sebi I
thought I would try to get it going on my system.

I am using 1.6.1.4 so I first upgraded the driver to work with 1.6. I think it
is mostly correct and the bit I have wrong shouldn't be causing me the
problems I am seeing. If your are interested my chan_sebi 1.4 to 1.6 patch is at
http://www.mycrofters.com/sites/default/files/chan_sebi.diff .

The USB modem is a Huawei E169G.

When I load the driver I get the expected responses

[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT+CGSN
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [3530xxxxxxxxxxx]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT+CPIN?
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [+CPIN: READY]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT^CARDLOCK?
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [^CARDLOCK: 2,10,0]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT+CLIP=1
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT+CREG?
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [+CREG: 0,1]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT+COPS=3,0
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT+COPS?
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [+COPS: 0,0,"FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF",0]
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT+CNUM
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [+CME ERROR: invalid characters in text string+CNUM:
"","07xxxxxxxxx",129]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT+CLVL=5
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT^DDSETEX=2
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT^CVOICE=?
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [^CVOICE:(0)]
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT+CMGF=1;+CPMS="ME","ME","ME";+CNMI=1,1,0,1,0
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [+CPMS: 1,23,1,23,1,23]
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
]Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT+CSCA="+447973100973",145
[Aug 27 13:22:27] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
    -- Modem Device huawei1 initialised and ready.

The response to the +COPS command gives the FFFFF response as my modem does not
seem to know the network names. I also needed to increase the storage size for
this field to prevent data corruption.

The problem is I can't dial out or accept incoming calls.

    -- Executing [3000 at home:2] Dial("SIP/martin-007ab0c8",
"sebi/huawei1/07xxxxxxxxx,20,T") in new stack
[Aug 27 13:25:30] DEBUG[572]: chan_sebi.c:534 modem_call: Calling
huawei1/07xxxxxxxxx on Sebi/huawei1-b64c
]Aug 27 13:25:30] DEBUG[572]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT^DDSETEX=2
    -- Called huawei1/07xxxxxxxxx
[Aug 27 13:25:30] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]
]Aug 27 13:25:31] DEBUG[560]: chan_sebi.c:853 data_write: data_write() (huawei1)
[ATD07xxxxxxxxx;
[Aug 27 13:25:31] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [ERROR]
[Aug 27 13:25:36] DEBUG[572]: chan_sebi.c:561 modem_hangup: Hanging up device
huawei1.
]Aug 27 13:25:36] DEBUG[572]: chan_sebi.c:853 data_write: data_write() (huawei1)
[AT+CHUP
  == Spawn extension (home, 3000, 2) exited non-zero on
'SIP/martin-007ab0c8'
[Aug 27 13:25:36] DEBUG[499]: chan_sebi.c:773 modem_devicestate: Checking device
state for device huawei1
[Aug 27 13:25:36] DEBUG[560]: chan_sebi.c:1011 do_monitor_phone: data_read()
(huawei1) [OK]

If I connect to the USB modem with minicom and issue the ATDxxxxxxx; command
with a semicolon at the end to signify a voice call I get the same error
response.

Could someone else with this type of USB modem tell me if that command should
work in minicom?

Thanks
Martin

Martin Stubbs wrote:
> Hi,
> 
> 
> If I connect to the USB modem with minicom and issue the ATDxxxxxxx;
command with a semicolon at the end to signify a voice call I get the same error
response.
> 
> Could someone else with this type of USB modem tell me if that command
should work in minicom?
> 

I had exactly this problem with a 3UK E169, in the end after trying a 
million and one things (including crossflashing to various different 
providers), I replaced it with an unlocked Vodafone UK one. (apparently 
vodafone ES ones work fine as well, I also have what I think is a german 
vodafone one, that works).

Thanks for the patch, I also have a little addition that allows the 
dongle to roam. (very simple change but essential on the network I am 
using it on).

Do you know if there's anywhere set up that people can collaborate on this?