From: Jussi Kangas <jussi.kangas@tieto.com>
To: ofono@ofono.org
Subject: Re: [PATCH] call-forwarding: fix for showing call forwarding states
Date: Fri, 18 Mar 2011 14:53:52 +0200 [thread overview]
Message-ID: <1300452832.2707.78.camel@jussi-desktop> (raw)
In-Reply-To: <4D82221D.3070401@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]
Hi,
On Thu, 2011-03-17 at 17:00 +0200, Denis Kenzior wrote:
> Hi Jussi,
>
> >>
> >> So correct me if I'm wrong, but I don't think we can do that. the
> >> current cf_conditions implementation stores all conditions, which could
> >> be unrelated to voice; and if my interpretation of 22.004 is correct you
> >> can have something like this:
> >>
> >> Activate CFB for all services to Number 1
> >> Activate CFU for Data services to Number 2
> >>
> >> Which results in cf_conditions[CALL_FORWARDING_TYPE_UNCONDITIONAL] not
> >> being NULL and you reporting CFB for voice incorrectly.
> >>
> >> You are probably safer using is_cfu_enabled() function.
> >
> > As far as I know scenario you describe cannot happen with oFono. There
> > is no data related conditions in the call forwarding API. Sure, you can
> > set data forwarding on using SS API, but I don't see how data forwarding
> > states could be shown in call forwarding API when all states in API
> > start with word "voice". Also according to comments in code fax and data
> > are not supported.
> >
>
> It can. oFono stores _all_ conditions in its lists. However, it
> filters them when reporting the conditions in get_properties or signals.
> This is why is_cfu_enabled function looks the way it does. So a
> scenario like this is fully possible. Not to mention that the CFs are
> queried for all services by default.
All right. I have no access to network that would support data
forwarding or my modem does not support it so I cannot verify this in
practice. But I think problem can be avoided by changing the line
if (cf->cf_conditions[CALL_FORWARDING_TYPE_UNCONDITIONAL] == NULL) {
to
if (!is_cfu_enabled(cf, NULL)) {
Of course little bit optimization would be good to avoid second calling
of this method later in function. Moving the setting of status variable
above these and using it when checked if UNCONDITIONAL is on instead of
is_cfu_enabled seems to be working nicely.
Br,
-Jussi
next prev parent reply other threads:[~2011-03-18 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 10:27 [PATCH] call-forwarding: fix for showing call forwarding states Jussi Kangas
2011-03-11 22:48 ` Denis Kenzior
2011-03-14 13:47 ` Jussi Kangas
2011-03-17 3:34 ` Denis Kenzior
2011-03-17 8:25 ` Jussi Kangas
2011-03-17 15:00 ` Denis Kenzior
2011-03-18 12:53 ` Jussi Kangas [this message]
2011-03-18 16:39 ` Denis Kenzior
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=1300452832.2707.78.camel@jussi-desktop \
--to=jussi.kangas@tieto.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