From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH v2] ussd: Recover idle state in case of response sending failure
Date: Thu, 23 Aug 2012 13:03:05 -0500 [thread overview]
Message-ID: <50367059.9050406@gmail.com> (raw)
In-Reply-To: <1345739265-3080-2-git-send-email-philippe.nunes@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
Hi Philippe,
On 08/23/2012 11:27 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 | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/src/ussd.c b/src/ussd.c
> index 74888b2..21e0164 100644
> --- a/src/ussd.c
> +++ b/src/ussd.c
> @@ -414,6 +414,18 @@ void ofono_ussd_notify(struct ofono_ussd *ussd, int status, int dcs,
> return;
> }
>
> + if (status == OFONO_USSD_STATUS_TERMINATED&&
> + (ussd->state == USSD_STATE_IDLE ||
> + ussd->state == USSD_STATE_USER_ACTION)) {
This check makes no sense, why bother checking for ussd->state ==
USSD_STATE_IDLE?
> + ussd_change_state(ussd, USSD_STATE_IDLE);
> +
> + if (ussd->pending == NULL)
> + return;
> +
> + reply = __ofono_error_not_supported(ussd->pending);
> + goto out;
> + }
> +
I would handle it just like the 'Not Supported' case but with a new
__ofono_error_network_terminated error reply. Or perhaps re-use
__ofono_error_canceled.
> if (status == OFONO_USSD_STATUS_NOT_SUPPORTED) {
> ussd_change_state(ussd, USSD_STATE_IDLE);
>
Regards,
-Denis
next prev parent reply other threads:[~2012-08-23 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 16:27 [PATCH v2] call-forwarding: class applied is the class given by SS code Philippe Nunes
2012-08-23 16:27 ` [PATCH v2] ussd: Recover idle state in case of response sending failure Philippe Nunes
2012-08-23 18:03 ` Denis Kenzior [this message]
2012-08-24 9:15 ` 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=50367059.9050406@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.