From: James Courtier-Dutton <James@superbug.co.uk>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: jbarre <jbarre@biarritx.dyndns.org>, bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [Fwd: Re: [Asterisk-Dev] New Bounty: Bluetooth Phone Support]
Date: Fri, 01 Oct 2004 09:40:12 +0100 [thread overview]
Message-ID: <415D17EC.4040609@superbug.co.uk> (raw)
In-Reply-To: <1096617904.5403.11.camel@notepaq>
Marcel Holtmann wrote:
> Hi Jerome,
>
>
>>The Asterisk-Dev list is talking about bt... ounce again...
>>
>>Since I'm (really) not an expert in this kind of stuff, I would like to
>>have your opinion.
>>
>>Here is a copy of my last reply to this list.
>>
>>Note: I'm not in the bluez-devel list. Too much mail... :-(
>>
>>Please don't forget to add my email address to your reply.
>
>
> as long as there are no mobile phones with cordless telephony (CTP)
> support I think it makes no sense to think about the integration into a
> PBX. You will be hit by the restrictions of the headset/handsfree
> profiles, because they are designed for a different approach. However,
> what you first need is correct ALSA-SCO-Bluetooth integration.
>
> Regards
>
> Marcel
>
Just a bit of advice. If anyone does any contributions to Asterisk, for
those contributions to be accepted, one has to sign over one's copyright
to a single Asterisk developer.
So, if one wishes to keep copyright over one's work, do not contribute
to Asterisk.
James
next prev parent reply other threads:[~2004-10-01 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 18:01 [Bluez-devel] [Fwd: Re: [Asterisk-Dev] New Bounty: Bluetooth Phone Support] jbarre
2004-10-01 8:05 ` Marcel Holtmann
2004-10-01 8:40 ` James Courtier-Dutton [this message]
2004-10-01 10:21 ` Lars Grunewaldt
2004-10-05 14:50 ` jbarre
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=415D17EC.4040609@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jbarre@biarritx.dyndns.org \
--cc=marcel@holtmann.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