From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/8] ussd: Recover idle state in case of response sending failure
Date: Wed, 22 Aug 2012 18:02:56 -0500 [thread overview]
Message-ID: <50356520.9090109@gmail.com> (raw)
In-Reply-To: <1345652303-12866-1-git-send-email-philippe.nunes@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
Hi Philippe,
On 08/22/2012 11:18 AM, Philippe Nunes wrote:
> GCF test case 31.8.1.2.3 is rejecting the user response.
> Any subsequent USSD notification are not handled because USSD is always in
> state user-action.
> ---
> src/ussd.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/src/ussd.c b/src/ussd.c
> index 74888b2..0ad4f61 100644
> --- a/src/ussd.c
> +++ b/src/ussd.c
> @@ -414,6 +414,10 @@ void ofono_ussd_notify(struct ofono_ussd *ussd, int status, int dcs,
> return;
> }
>
> + if (status == OFONO_USSD_STATUS_TERMINATED&&
> + ussd->state == USSD_STATE_IDLE)
> + return;
> +
> if (status == OFONO_USSD_STATUS_NOT_SUPPORTED) {
> ussd_change_state(ussd, USSD_STATE_IDLE);
>
How about you simply handle the TERMINATED notification properly here and
> @@ -595,9 +599,11 @@ static void ussd_response_callback(const struct ofono_error *error, void *data)
> struct ofono_ussd *ussd = data;
> DBusMessage *reply;
>
> - if (error->type != OFONO_ERROR_TYPE_NO_ERROR)
> + if (error->type != OFONO_ERROR_TYPE_NO_ERROR) {
> DBG("ussd response failed with error: %s",
> telephony_error_to_str(error));
> + ussd_change_state(ussd, USSD_STATE_IDLE);
> + }
>
> if (error->type == OFONO_ERROR_TYPE_NO_ERROR) {
> ussd_change_state(ussd, USSD_STATE_RESPONSE_SENT);
Take out this chunk.
Regards,
-Denis
next prev parent reply other threads:[~2012-08-22 23:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 16:18 [PATCH 1/8] ussd: Recover idle state in case of response sending failure Philippe Nunes
2012-08-22 16:18 ` [PATCH 2/8] stkagent: '+' is considered as a digit Philippe Nunes
2012-08-22 22:55 ` Denis Kenzior
2012-08-23 15:53 ` Philippe Nunes
2012-08-23 18:15 ` Denis Kenzior
2012-08-22 16:18 ` [PATCH 3/8] call-forwarding: return specific errors for SS query Philippe Nunes
2012-08-22 23:18 ` Denis Kenzior
2012-08-22 16:18 ` [PATCH 4/8] call-forwarding: class applied is the class given by SS code Philippe Nunes
2012-08-22 23:36 ` Denis Kenzior
2012-08-23 15:30 ` Philippe Nunes
2012-08-23 18:32 ` Denis Kenzior
2012-08-22 16:18 ` [PATCH 5/8] call-barring: Return specific errors for SS query Philippe Nunes
2012-08-22 23:19 ` Denis Kenzior
2012-08-22 16:18 ` [PATCH 6/8] call-barring: class applied is the class given by SS code Philippe Nunes
2012-08-22 16:18 ` [PATCH 7/8] call-settings: Return specific errors for SS query Philippe Nunes
2012-08-22 23:19 ` Denis Kenzior
2012-08-22 16:18 ` [PATCH 8/8] call-settings: class applied is the class given by SS code Philippe Nunes
2012-08-22 23:41 ` Denis Kenzior
2012-08-22 23:02 ` Denis Kenzior [this message]
2012-08-23 10:30 ` [PATCH 1/8] ussd: Recover idle state in case of response sending failure Philippe Nunes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50356520.9090109@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox