Re: [PATCH] [RfC] doc: Proposed Set Up Call api.

[Marcel Holtmann <marcel@holtmann.org>]

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

Hi Andrew,

> The normal sequence for call setup is:
> 
> * Modem asks user for confirmation using icon1 / alphaId1.
> * User confirms
> * Modem starts dialling, screen displays icon2 / alphaId2,
> * Call is connected, modem replies to the proactive command, screen
>   keeps displaying icon2 / alphaId2 until the phone call is over.
> ---
>  doc/stk-api.txt       |   11 +++++++++++
>  doc/voicecall-api.txt |   11 +++++++++++
>  2 files changed, 22 insertions(+), 0 deletions(-)
> 
> diff --git a/doc/stk-api.txt b/doc/stk-api.txt
> index 2e863a9..dcb8e2b 100644
> --- a/doc/stk-api.txt
> +++ b/doc/stk-api.txt
> @@ -189,6 +189,17 @@ Methods		byte RequestSelection(string title, byte icon_id,
>  
>  			Possible Errors: [service].Error.SimToolkit.GoBack
>  
> +		boolean ConfirmCallSetup(string information, byte icon_id)
> +
> +			Asks the agent to request user to confirm an
> +			outgoing call setup.  If confirmed, the next new
> +			outgoing call reported by VoiceCallManager will
> +			have the Information and Icon properties set to
> +			inform the user.  Hanging up before the call is
> +			connected will cause EndSession reply to be sent.
> +
> +			Possible Errors: [service].Error.SimToolkit.EndSession
> +
>  		void Cancel()
>  
>  			Asks the agent to cancel any ongoing operation in
> diff --git a/doc/voicecall-api.txt b/doc/voicecall-api.txt
> index 59e3568..f0ba316 100644
> --- a/doc/voicecall-api.txt
> +++ b/doc/voicecall-api.txt
> @@ -114,3 +114,14 @@ Properties	string LineIdentification [readonly]
>  			stamped when the call enters the "active" state.
>  			Client applications can use this to infer somewhat
>  			reliable call duration information.
> +
> +		string Information [readonly, optional]
> +
> +			Contains information related to the call for the
> +			user.  Currently this property is set for calls
> +			initiated by SIM Toolkit applications.
> +
> +		byte Icon [readonly, optional]
> +
> +			Icon identifier to be used instead of or together
> +			with the text information.

I would be fine with this. At least for an initial attempt to implement
this. We need to see how far we get from here. If it doesn't work out
then we have to get back to the drawing board.

Regards

Marcel