Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [RFC] voice call API changes (proposal)
Date: Mon, 31 Jan 2011 13:58:40 -0600	[thread overview]
Message-ID: <4D471470.5050100@gmail.com> (raw)
In-Reply-To: <f05c513a9ca1d1a296a8e1dfc6af633e2fb058a1.1296474033.git.Andras.Domokos@nokia.com>

[-- Attachment #1: Type: text/plain, Size: 4055 bytes --]

Hi Andras,

On 01/31/2011 05:56 AM, Andras Domokos wrote:
> Here is a proposal for expanding the VoiceCallManager interface with 
> call related Supplementary Services signals, and the VoiceCall
> interface with new properties.
> 
> ---
>  doc/call-barring-api.txt     |   10 ----------
>  doc/voicecall-api.txt        |   15 +++++++++++++++
>  doc/voicecallmanager-api.txt |   21 +++++++++++++++++++++
>  3 files changed, 36 insertions(+), 10 deletions(-)
> 
> diff --git a/doc/call-barring-api.txt b/doc/call-barring-api.txt
> index 41ae4b1..1534494 100644
> --- a/doc/call-barring-api.txt
> +++ b/doc/call-barring-api.txt
> @@ -37,16 +37,6 @@ Signals		PropertyChanged(string property, variant value)
>  			Signal is emitted whenever a property has changed.
>  			The new value is passed as the signal argument.
>  
> -		IncomingBarringInEffect()
> -
> -			Signal is emitted when a call is made and an
> -			incoming call barring supplementary service is in use.
> -
> -		OutgoingBarringInEffect()
> -
> -			Signal is emitted when a call is made and an
> -			outgoing call barring supplementary service is in use.
> -
>  Properties	string VoiceIncoming [readwrite]
>  
>  			Contains the value of the barrings for the incoming
> diff --git a/doc/voicecall-api.txt b/doc/voicecall-api.txt
> index 047b8cb..e7276a3 100644
> --- a/doc/voicecall-api.txt
> +++ b/doc/voicecall-api.txt
> @@ -145,3 +145,18 @@ Properties	string LineIdentification [readonly]
>  
>  			Contains the indication if the voice call is an
>  			emergency call or not.
> +
> +		boolean Forwarded
> +
> +			Contains the indication whether the voice call is a
> +			forwarded call or not.
> +

So just to clarify, this is usually set on a local Incoming / Waiting
call, correct?

> +		boolean RemoteHold
> +
> +			Contains the indication whether the voice call has been
> +			put on hold by the remote party or not.
> +

This one is rather tricky, since AT modems do not report the index of
the call.  So the only way you can report this is if you have only a
single call active or your modem supports this properly (I know ISI does).

> +		boolean Waiting
> +
> +			Contains the indication whether the outgoing voice call
> +			is waiting or not.

And this is for a local dialing / alerting call.  Correct?

> diff --git a/doc/voicecallmanager-api.txt b/doc/voicecallmanager-api.txt
> index 2bf9ded..bbd80db 100644
> --- a/doc/voicecallmanager-api.txt
> +++ b/doc/voicecallmanager-api.txt
> @@ -144,6 +144,27 @@ Signals		CallAdded(object path, dict properties)
>  			Signal is emitted whenever a property has changed.
>  			The new value is passed as the signal argument.
>  
> +		UnconditionalForwardingInEffect
> +
> +			Signal is emitted when a call is made and unconditional
> +			call forwarding supplementary service is active.

This is for a local dialing / alerting call.  Correct?

> +
> +		ConditionalForwardingInEffect
> +
> +			Signal is emitted when a call is made and some of the
> +			conditional call forwarding supplementary services are
> +			active.
> +

Same as above?

> +		IncomingBarringInEffect()
> +
> +			Signal is emitted when a call is made and an
> +			incoming call barring supplementary service is in use.
> +

For local outgoing calls telling that the remote side has incoming
barring active?

> +		OutgoingBarringInEffect()
> +
> +			Signal is emitted when a call is made and an
> +			outgoing call barring supplementary service is in use.
> +

And this one telling you that local outgoing barring is active?

>  Properties	array{string} EmergencyNumbers [readonly]
>  
>  			Contains the list of emergency numbers recognized

Generally I'm fine with these but please document them a bit more
clearly, and we might have to pick names that make a bit more sense.

Other than that, you're missing the mpty join indications that Pekka had
in his earlier proposal.  These suffer from the same problem as RemoteHold.

Regards,
-Denis

  reply	other threads:[~2011-01-31 19:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1296474033.git.Andras.Domokos@nokia.com>
2011-01-31 11:56 ` [RFC] voice call API changes (proposal) Andras Domokos
2011-01-31 19:58   ` Denis Kenzior [this message]
2011-02-01 15:43     ` Andras Domokos
2011-02-01 15:54       ` Denis Kenzior
2011-02-02  7:51         ` Andras Domokos
2011-02-02 15:32           ` Denis Kenzior
2011-02-02 18:16             ` [RFC] voicecall API changes (proposal 2) Andras Domokos
2011-02-02 20:01               ` Denis Kenzior
2011-02-03 10:53                 ` Andras Domokos
2011-02-03 16:29                   ` Denis Kenzior
2011-02-07 11:18                     ` [RFC] voicecall API changes (proposal v3) Andras Domokos
2011-02-07 16:38                       ` Denis Kenzior
2011-02-07 17:07                         ` Andras Domokos
2011-02-07 17:09                         ` Andras Domokos
2011-02-07 19:39                           ` Denis Kenzior
2011-02-08  8:55                             ` Andras Domokos

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=4D471470.5050100@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