Return-Path: Date: Wed, 28 Jan 2009 13:25:04 +0200 From: Johan Hedberg To: linux-bluetooth@vger.kernel.org Subject: Re: Disconnect eSCO link from Command line Message-ID: <20090128112504.GA22536@localhost> References: <20090128082323.GA8865@jh-x301> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-bluetooth-owner@vger.kernel.org List-ID: On Wed, Jan 28, 2009, sreevani medhahal wrote: > > On Wed, Jan 28, 2009, sreevani medhahal wrote: > >> After the headset has created the eSCO link. The Profile Tuning > >> Suite asks for Closing the Audio Connection from AG. Is there any > >> command line utiility to disable the eSCO link & not the service level > >> connection(ACL).[The eSCO link is visible on giving hcitool con ] > > > > You can do that by calling the Stop D-Bus method call on the > > org.bluez.Headset interface of the corresponding device object. You can > > e.g. use the test/test-telephony python script for this: > > ./test-telephony stop > > > The above method does not close the eSCO link ,because the > sco_connect_cb has reported connection timed out. but the hcitool con > still lists the eSCO link. > I have another query bluez4.2x is compatible with which linux kernel > version. does it have any strict requirement that it works best only > if the kernel version is >= 2.6.27 . You might want to try Marcel's bluetooth-testing tree. I think that issue might be fixed by the following patch: http://git.kernel.org/?p=linux/kernel/git/holtmann/bluetooth-testing.git;a=commitdiff;h=d7461bfbd48bb76a1126a4f05bb16e4bb0187d31 Johan