From: Andras Domokos <andras.domokos@nokia.com>
To: ofono@ofono.org
Subject: Re: [RFC PATCH 2/3] ssn: add code and call id to notifications
Date: Thu, 24 Feb 2011 13:43:36 +0200 [thread overview]
Message-ID: <4D664468.3090806@nokia.com> (raw)
In-Reply-To: <AANLkTi=XHVW0VteBvk2tkhbdwRdcDdMZmYAesMWSm9VR@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2824 bytes --]
Hi Denis and Sankar,
The call SS notification handling patches hasn't been (fully) applied, I
think we need to do something about it.
Regards,
Andras
On 02/22/2011 02:07 PM, ext Sankar wrote:
> Hi Denis/Andras,
>
> Is this patch applied and available in the GIT?
>
> Regards,
> Sankar.
>
> On Thu, Feb 10, 2011 at 2:42 PM, Andras Domokos
> <andras.domokos(a)nokia.com <mailto:andras.domokos@nokia.com>> wrote:
>
> Hi Denis,
>
>
> On 02/10/2011 05:08 AM, ext Denis Kenzior wrote:
>
> Hi Andras,
>
> diff --git a/include/ssn.h b/include/ssn.h
> index d640cad..ba3701b 100644
> --- a/include/ssn.h
> +++ b/include/ssn.h
> @@ -37,9 +37,10 @@ struct ofono_ssn_driver {
> };
>
> /* SSN notifications (CSSI and CSSU). */
> -void ofono_ssn_cssi_notify(struct ofono_ssn *ssn, int
> code, int index);
> -void ofono_ssn_cssu_notify(struct ofono_ssn *ssn, int
> code, int index,
> - const struct
> ofono_phone_number *number);
> +void ofono_ssn_cssi_notify(struct ofono_ssn *ssn,
> unsigned int id,
> + int code1, int index);
> +void ofono_ssn_cssu_notify(struct ofono_ssn *ssn,
> unsigned int id, int code2,
> + int index, const struct
> ofono_phone_number *number);
>
> int ofono_ssn_driver_register(const struct
> ofono_ssn_driver *d);
> void ofono_ssn_driver_unregister(const struct
> ofono_ssn_driver *d);
>
> Right now I'm not seeing any users (or even potential ones) of
> the SSN
> atom besides voicecall. What do you think of removing the SSN
> atom and
> moving these to the voicecall atom?
>
> Yes, we talked about removing the SSN atom, but I thought I would
> keep it for now, it can be removed any time later, anyways, doesn't
> save much removing it.
>
>
> The only one I'm not sure about is<code2> from 27.007:
> 6 forward check SS message received (can be received
> whenever)
>
> Any idea what this one is about?
>
> Never encountered this message, and I am not sure what is it for.
> A patch for handling this message can be submitted later, if a real
> life case is found for it.
>
> Regards,
> -Denis
>
> Regards,
> Andras
>
> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org <mailto:ofono@ofono.org>
> http://lists.ofono.org/listinfo/ofono
>
>
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5571 bytes --]
next prev parent reply other threads:[~2011-02-24 11:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 10:33 [PATCH 0/3] Voice call SS notifications Andras Domokos
2011-02-09 10:33 ` [RFC PATCH 1/3] call-barring: removed +CSSI type " Andras Domokos
2011-02-10 3:04 ` Denis Kenzior
2011-02-10 8:43 ` Andras Domokos
2011-02-09 10:34 ` [RFC PATCH 2/3] ssn: add code and call id to notifications Andras Domokos
2011-02-10 3:08 ` Denis Kenzior
2011-02-10 9:12 ` Andras Domokos
2011-02-22 12:07 ` Sankar
2011-02-24 11:43 ` Andras Domokos [this message]
2011-02-24 15:43 ` Denis Kenzior
2011-02-24 16:11 ` Andras Domokos
2011-02-24 16:14 ` Denis Kenzior
2011-02-24 16:21 ` Andras Domokos
2011-02-09 10:34 ` [RFC PATCH 3/3] voicecall: handle voice call SS notifications Andras Domokos
-- strict thread matches above, loose matches on Subject: below --
2011-02-28 16:28 [PATCH 0/3] Voice call SS notifications (2nd version) Andras Domokos
2011-02-28 16:28 ` [RFC PATCH 2/3] ssn: add code and call id to notifications Andras Domokos
2011-02-28 22:19 ` 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=4D664468.3090806@nokia.com \
--to=andras.domokos@nokia.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