From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 4/8] call-forwarding: class applied is the class given by SS code
Date: Wed, 22 Aug 2012 18:36:53 -0500 [thread overview]
Message-ID: <50356D15.1050609@gmail.com> (raw)
In-Reply-To: <1345652303-12866-4-git-send-email-philippe.nunes@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2366 bytes --]
Hi Philippe,
On 08/22/2012 11:18 AM, Philippe Nunes wrote:
> GCF test cases 31.2.1.6.1/2 are asking to make a query according a specific
> class.
> The default class is applied when no class is specified in the SS code.
> ---
> src/call-forwarding.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/src/call-forwarding.c b/src/call-forwarding.c
> index 91e34c6..7531f07 100644
> --- a/src/call-forwarding.c
> +++ b/src/call-forwarding.c
> @@ -1012,7 +1012,7 @@ static void ss_set_query_cf_callback(const struct ofono_error *error, int total,
>
> static void ss_set_query_next_cf_cond(struct ofono_call_forwarding *cf)
> {
> - cf->driver->query(cf, cf->query_next, BEARER_CLASS_DEFAULT,
> + cf->driver->query(cf, cf->query_next, cf->ss_req->cls,
> ss_set_query_cf_callback, cf);
> }
>
> @@ -1167,6 +1167,16 @@ static gboolean cf_ss_control(int type, const char *sc,
> return TRUE;
> }
>
> + /*
> + * Some modems don't understand all classes very well, particularly
> + * the older models. So if the bearer class is the default, we
> + * just use the more commonly understood value of 7 since BEARER_SMS
> + * is not applicable to CallForwarding conditions according to 22.004
> + * Annex A
> + */
> + if (cls == BEARER_CLASS_SS_DEFAULT)
> + cls = BEARER_CLASS_DEFAULT;
> +
Strictly speaking this is wrong. You cannot modify the cls here as it
is used to generate the reply in cf_ss_control_reply. Since
BEARER_CLASS_SS_DEFAULT != BEARER_CLASS_DEFAULT you will generate the
wrong result.
> cf->ss_req->ss_type = type;
> cf->ss_req->cf_type = cf_type;
> cf->ss_req->cls = cls;
> @@ -1188,16 +1198,6 @@ static gboolean cf_ss_control(int type, const char *sc,
> break;
> }
>
> - /*
> - * Some modems don't understand all classes very well, particularly
> - * the older models. So if the bearer class is the default, we
> - * just use the more commonly understood value of 7 since BEARER_SMS
> - * is not applicable to CallForwarding conditions according to 22.004
> - * Annex A
> - */
> - if (cls == BEARER_CLASS_SS_DEFAULT)
> - cls = BEARER_CLASS_DEFAULT;
> -
> switch (cf->ss_req->ss_type) {
> case SS_CONTROL_TYPE_REGISTRATION:
> string_to_phone_number(sia,&ph);
Regards,
-Denis
next prev parent reply other threads:[~2012-08-22 23:36 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 [this message]
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 ` [PATCH 1/8] ussd: Recover idle state in case of response sending failure Denis Kenzior
2012-08-23 10:30 ` 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=50356D15.1050609@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.