Hi, On 15 February 2010 22:24, Denis Kenzior <[email protected]> wrote: > In everything I've researched I understood that there can't be two concurrent > ussd sessions. The only things that can happen during USSD_STATE_USER_ACTION: > - Network sends a timed out notification or terminates the ussd action > - someone else actually responds to the USSD (other local client has > responded) > > I think we should simply ignore the re-entrant case (which USSD operation are > you canceling? First or second?) until we're told otherwise. However, we > _should_ handle the network termination / other local client has responded > cases. > > Also, it might be a good idea to have a State property that shows the current > USSD request state.
Ok, you're definitely right. This new patch ignores the new USSD if we're in USSD_STATE_USER_ACTION already. I also added a USSDState property as string. Regards
0001-Handle-network-initiated-ussd-requests.patch
Description: Binary data
0003-Subscribe-to-USSD-signals-in-test-script.patch
Description: Binary data
_______________________________________________ ofono mailing list [email protected] http://lists.ofono.org/listinfo/ofono
