From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [HFP] New Methods/Signals.
Date: Tue, 18 Dec 2007 19:14:07 +0100 [thread overview]
Message-ID: <1198001647.8050.183.camel@aeonflux> (raw)
In-Reply-To: <1197984959.21252.31.camel@greatbear>
Hi Alok,
> some new Methods/Signals are required for HFP in the audio service. Here
> are the ones needed as of now.
are they using the org.bluez.audio.Headset interface or are they meant
to be in a org.bluez.audio.Handsfree interface?
> Method:
> void CallSetup(uint16 value)
>
> Used to send "callsetup" indicator value to the HF.
>
> Signal:
> void TerminateCall()
>
> This signal is sent when an ongoing call is terminated.
>
>
> An appropriate method name would be IndicateCall(), But thats already
> used for Alerting(RING) the Headset/HFP.
In case they are in the audio.Headset interface, then use SetupCall. Can
we use strings to express the value parameter?
> Is it possible to use Alert() instead of IndicateCall() to RING the
> headset/HF and use IndicateCall to send "callsetup" indicator?
We can't change the API. Only a move to BlueZ 4.x could change the API.
> The headset method implementations start with hs_* . Should the hf
> methods prepend hf_ to them for distinguishing them from headset
> methods ?
Sure.
Regards
Marcel
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-12-18 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 13:35 [Bluez-devel] [HFP] New Methods/Signals Alok
2007-12-18 18:14 ` Marcel Holtmann [this message]
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=1198001647.8050.183.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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