Re: [dongle] USSD on E153u-1

[Paco Gil]

On Tue, Oct 25, 2011 at 07:44, joseph <klas...@gmail.com> wrote:

Hullo,

Please advise on how to send ussd on e153u-1 of the form
*100*1234567890123#

tried: dongle ussd dongle1 *100*1234567890123#

Expected response is an sms, instead a ussd response is received,
contents below:

2011-10-24 17:53:56 - dongle1:

Where is content of ussd?

 

Details of install:

chan_dongle: Huawei 3G Dongle Channel Driver, Version 1.1, Revision 10
Asterisk 1.6.2.20
Linux hostname 2.6.35-28-generic-pae #50-Ubuntu

dongle1 E153 fw 11.609.18.00.342

Thanks, Joseph

[Paco Gil]

On Tue, Oct 25, 2011 at 08:25, joseph mpora <klas...@gmail.com> wrote:

On 25 October 2011 09:20, Paco Gil <pag...@gmail.com> wrote:

On Tue, Oct 25, 2011 at 07:44, joseph <klas...@gmail.com> wrote:

Hullo,

Please advise on how to send ussd on e153u-1 of the form
*100*1234567890123#

tried: dongle ussd dongle1 *100*1234567890123#

Expected response is an sms, instead a ussd response is received,
contents below:

2011-10-24 17:53:56 - dongle1:

Where is content of ussd?

Thats the response recorded in the /var/log/asterisk/ussd.txt; just that.

chan_dongle does not log any response to any txt. Please check your dialplan... and also paste console output when any ussd is received.

[Paco Gil]

you answered yourself:

dongle ussd dongle1 *100*1234567890123#

On Tue, Oct 25, 2011 at 10:11, joseph mpora <klas...@gmail.com> wrote:

dongle ussd dongle1 *100*1234567890123#

[Maarten Bezemer]

On Tue, 25 Oct 2011, joseph mpora wrote:

> this is from the asterisk cli:
>
> dongle ussd dongle1 *100*42658712447593#
> [dongle1] USSD queued for send with id 0x9ceef08
> -- [dongle1] Successfully sent USSD 0x9ceef08
> [dongle1] Got USSD type 2 'USSD Terminated by network': ''

In the past, I've played a bit with such a dongle, and when accessing it
from minicom, it errored out on 'simple' AT+CUSD requests. Then, I had the
idea to try to encode the USSD request (using PDU encoding) and then the
results were as expected.
So, this may as well be an encoding issue.
I don't have this stick any more, so I can't do any further testing.
Didn't test it with chan_dongle back then.

> when the same is typed using a mobile handset, the response is an sms (with
> amount loaded and current balance)

Every provider I know of that uses *something# to show and/or top-up
balance (with *something*top-up-code# only when topping up) sends the
reply back as USSD message. Not as SMS. Having a USSD without a response
is very unusual. At least something like "please wait to receive sms"
would be appropriate in such cases.
However, some handy's present the USSD response in the same way as an
incoming SMS. So maybe it's a bug in your perception ;-)

HTH...

--
Maarten

[bg]

dongle may have UCS-2 or 7bit USSD encoding.
check how dongle report model and also check this model listed in
'7bit models' list