Inbound USSD response detection issue

[GoogleCodeExporter]

Inbound USSD response detected lately with incorrect status.

please take a look at logs.

Thanks

Device : wavecom fastrack m1306b

Original issue reported on code.google.com by meher.g...@gmail.com on 17 Dec 2012 at 4:48

Attachments:

• logSMSLib.txt

[GoogleCodeExporter]

I modified the AModemDriver.java like this :

AsyncEvents event = 
getGateway().getATHandler().processUnsolicitedEvents(buffer.toString());
                if (event == eventResponse && eventResponse == AsyncEvents.USSDRESPONSE) { getAsyncNotifier().setEvent(event, buffer.toString()); } <------- ADDED this line 
                if (event == eventResponse && eventResponse != AsyncEvents.NOTHING) { return buffer.toString(); }
                if ((event == AsyncEvents.INBOUNDMESSAGE) || (event == AsyncEvents.INBOUNDSTATUSREPORTMESSAGE) || (event == AsyncEvents.INBOUNDCALL)) getAsyncNotifier().setEvent(event, buffer.toString()); <---- modified this line 
                return getResponse();

Original comment by meher.g...@gmail.com on 17 Dec 2012 at 9:11

[GoogleCodeExporter]

Guys i'm waiting for real solution to my problem ...thanks for any help 
suggested.

Original comment by meher.g...@gmail.com on 17 Dec 2012 at 9:13

[GoogleCodeExporter]

Hello,

USSD handling has problems. I can't help you with this, as I have no way to 
test USSD commands.

Better ask at the discussion group.

Original comment by admin@smslib.org on 27 Dec 2012 at 12:28

• Changed state: Closed

[GoogleCodeExporter]

I fixed the problem by myself as showed above .. but I think users have to 
manage the smslib code to handle USSD responses theirself as I think it depends 
on the Modem model.
Thank you anyway :) thanks for this lib.

Original comment by meher.g...@gmail.com on 27 Dec 2012 at 1:31