Hi,
Can someone tell me how to set the bluetooth voice settings when using sco
and what to set it to?
My hcidump shows voice setting as (0x03|0x0025) - what does this mean? Also,
the hcidump shows that a connection is created for DM* and DH* packet types:
for sco, should this not be HV* packet types?
Any help is greatly appreciated.
Khaled
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Brad, Marcel, Steven,
I've decided to go ahead with the kernel upgrade (unless of course you guys
advise me not to) because:
1. I think asterisk will require snd-bt-sco given my recent experience
trying to troubleshoot sound settings for asterisk; asterisk does try to
acces /dev/dsp on the machine...
2. the sco packets from the hcidump call trace change with voice input at
either end of the call (from the softphone and from the deskphone), despite
there being no sound at either end, I am optimistic that I can achieve
two-way audio should I have snd-bt-sco in the kernel.
Brad, when you said I should rebuild the kernel with a newer version, you
said:
>You'll have to rebuild sco_bt_snd too.
How can I do this? I have never done this before...
Kind Regards
Khaled
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Brad
> Midgley
> Sent: 08 December 2005 15:18
> To: [email protected]
> Subject: Re: [Bluez-users] Bluetooth Voice Setting
>
>
> Khaled
>
> What I'm saying is asterisk either connects to (eg) /dev/dsp1 or the
> alsa device, invoking snd-bt-sco which sends/receives over bluetooth
> sockets OR asterisk sends and receives over bluetooth sockets without
> bothering with snd-bt-sco. Have a look at the code or ask the
> asterisk guy.
>
> Brad
>
> > If I am trying to use voip, then wouldn't the application
> (asterisk) require
> > the snd_bt_sco module? Perhaps this is why I am not getting any
> sound (as
> > shown in the hcidump output of my last message).
> > Is this a sensible assumption because I am using a softphone that is
> > connected to the machine configured as a handsfree headset via voip?
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Khaled
What I'm saying is asterisk either connects to (eg) /dev/dsp1 or the
alsa device, invoking snd-bt-sco which sends/receives over bluetooth
sockets OR asterisk sends and receives over bluetooth sockets without
bothering with snd-bt-sco. Have a look at the code or ask the asterisk guy.
Brad
> If I am trying to use voip, then wouldn't the application (asterisk) require
> the snd_bt_sco module? Perhaps this is why I am not getting any sound (as
> shown in the hcidump output of my last message).
> Is this a sensible assumption because I am using a softphone that is
> connected to the machine configured as a handsfree headset via voip?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Brad,
If I am trying to use voip, then wouldn't the application (asterisk) require
the snd_bt_sco module? Perhaps this is why I am not getting any sound (as
shown in the hcidump output of my last message).
Is this a sensible assumption because I am using a softphone that is
connected to the machine configured as a handsfree headset via voip?
Kind Regards
Khaled
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Brad
> Midgley
> Sent: 08 December 2005 14:56
> To: [email protected]
> Subject: Re: [Bluez-users] Bluetooth Voice Setting
>
>
> Khaled
>
> > My next step now is to upgrade the kernel to one of the 2.6.14
> kernel. But
> > before I do...
>
> I should say that upgrading the kernel is only useful if your asterisk
> stuff needs the snd-bt-sco module. If it just transfers audio direct to
> the bluetooth layer, then it isn't likely to help.
>
> Brad
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Marcel, Brad, Steven,
I have come across some more information: I am getting sco packets on a
second system setup (this time with mandrake 9.2) with the exact setup. I
have noticed one important thing: when I speak into my desk phone (the
receiving phone) I get various characters appearing in the empty
'............' lines; the more I speak, the more characters appear, if I
dont speak, only a few appear. This is only for the outgoing sco packets (<
SCO); the incoming sco packets (> SCO) never show any of these characters.
What does this mean? Am I getting one way audio? Then why can I not hear at
the other end (the handsfree end)?
Any ideas?
< SCO data: handle 43 dlen 48
0000: 40 fc 80 fc 80 fc 20 fc 20 fc 00 fd 60 fd 60 fd @..... . ...`.`.
0010: c0 fd 60 fd 80 fc 80 fc 40 fc 20 fc c0 fc 20 fd ..`.....@. ... .
0020: a0 fc 80 fc a0 fc c0 fc 20 fd 40 fd 40 fd 20 fd ........ .@.@. .
< SCO data: handle 43 dlen 48
0000: e0 fc 40 fc 60 fc 80 fc 60 fc 80 fc 80 fc 60 fc ..@.`...`.....`.
0010: a0 fc 80 fc 40 fc 60 fc 80 fc 80 fc 80 fc 20 fc ....@.`....... .
0020: 80 fb 40 fb c0 fb 60 fc c0 fc c0 fc 80 fc 40 fc ..@...`.......@.
< SCO data: handle 43 dlen 48
0000: 20 fc 20 fc 20 fc 20 fc 20 fc 60 fc 20 fc 00 fc . . . . .`. ...
0010: 20 fc 60 fc a0 fc c0 fc a0 fc 20 fc 00 fc 80 fb .`....... .....
0020: 00 fc 40 fc 60 fc a0 fc a0 fc 80 fc a0 fc e0 fc ..@.`...........
< SCO data: handle 43 dlen 48
0000: c0 fc e0 fc 20 fd 20 fd 80 fd 60 fd a0 fc 20 fc .... . ...`... .
0010: 60 fc a0 fc c0 fc 20 fd e0 fc 80 fc c0 fc c0 fc `..... .........
0020: c0 fc c0 fc 60 fc 00 fc 00 fc 00 fc 20 fc 20 fc ....`....... . .
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
< SCO data: handle 43 dlen 48
0000: c0 fb c0 fb 00 fc 80 fc e0 fc 00 fd 00 fd e0 fc ................
0010: e0 fc 00 fd a0 fc 80 fc e0 fc a0 fc c0 fb c0 fb ................
0020: 20 fc 60 fc c0 fc e0 fc 20 fd 80 fd 40 fd 40 fd .`..... ...@.@.
< SCO data: handle 43 dlen 48
0000: 60 fd 60 fd a0 fd 80 fd 00 fd 20 fd e0 fc 60 fc `.`....... ...`.
0010: 60 fc 20 fd a0 fd 80 fd a0 fd e0 fd c0 fd e0 fd `. .............
0020: 60 fd 60 fd c0 fd c0 fd 20 fd 20 fd 20 fd e0 fc `.`..... . . ...
< SCO data: handle 43 dlen 48
0000: e0 fc 00 fd e0 fc e0 fc 20 fd 20 fd 40 fd 40 fd ........ . .@.@.
0010: 60 fd 80 fd a0 fd 60 fd 40 fd c0 fc a0 fc c0 fc `.....`.@.......
0020: 20 fd 00 fd 80 fc a0 fc c0 fc a0 fc a0 fc a0 fc ...............
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
< SCO data: handle 43 dlen 48
0000: c0 fc c0 fc 20 fd 00 fd 80 fc 80 fc 60 fd 20 fd .... .......`. .
0010: 80 fc e0 fc 80 fd 60 fd 80 fc 40 fc 80 fc c0 fc ......`...@.....
0020: a0 fc 80 fc 80 fc c0 fc 40 fc 00 fc 40 fc 40 fc ........@...@.@.
< SCO data: handle 43 dlen 48
0000: 60 fc a0 fc a0 fc 80 fc 80 fc 80 fc 40 fc 00 fc `...........@...
0010: 20 fc e0 fc 00 fd 00 fd 20 fd c0 fc a0 fc a0 fc ....... .......
0020: c0 fc a0 fc e0 fc e0 fc 80 fc a0 fc e0 fc 20 fd .............. .
< SCO data: handle 43 dlen 48
0000: 00 fd a0 fc 80 fc e0 fc 40 fd e0 fc 80 fc c0 fc ........@.......
0010: 20 fd 60 fd 40 fd 00 fd 00 fd 20 fd 00 fd e0 fc .`.@..... .....
0020: e0 fc 00 fd 60 fd 20 fd c0 fc 80 fc c0 fb 00 fc ....`. .........
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
< SCO data: handle 43 dlen 48
0000: 40 fc 60 fc 80 fc a0 fc 40 fc 00 fc 00 fc 00 fc @.`.....@.......
0010: c0 fb 80 fb c0 fb 00 fc 20 fc 00 fc c0 fb c0 fb ........ .......
0020: 40 fc 20 fc c0 fb 00 fc 20 fc 20 fc 40 fc 40 fc @. ..... . .@.@.
< SCO data: handle 43 dlen 48
0000: 60 fc a0 fc c0 fb 00 fb c0 fb 20 fc c0 fb c0 fb `......... .....
0010: 20 fc c0 fb 40 fb 80 fb c0 fb 20 fc a0 fc c0 fc ...@..... .....
0020: 80 fc 40 fc 20 fc 20 fc 40 fc 00 fc 00 fc 60 fc ..@. . .@.....`.
< SCO data: handle 43 dlen 48
0000: 40 fc 00 fc 20 fc e0 fc 40 fd e0 fc 20 fd 00 fd @... ...@... ...
0010: c0 fc 80 fc 60 fc 40 fc 40 fc 00 fc 00 fc c0 fb ....`.@.@.......
0020: c0 fb c0 fb 80 fb 00 fc 20 fc 40 fc 00 fd 00 fd ........ .@.....
< SCO data: handle 43 dlen 48
0000: 80 fc e0 fc 00 fd c0 fc 20 fc 20 fc 60 fc 00 fc ........ . .`...
0010: 40 fb 80 fb c0 fb c0 fb 80 fb 40 fb c0 fb 20 fc @.........@... .
0020: 40 fc a0 fc 20 fd 20 fd c0 fc 20 fc 00 fc 00 fc @... . ... .....
> ACL data: handle 40 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 9 fcs 0x3e
0000: 0d 0a 45 52 52 4f 52 0d 0a ..ERROR..
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
< SCO data: handle 43 dlen 48
0000: 00 fc 00 fc 00 fc c0 fb c0 fb 80 fb 80 fb 00 fc ................
0010: a0 fc 80 fc a0 fc e0 fc e0 fc c0 fc 80 fc 40 fc ..............@.
0020: 20 fc 60 fc 20 fc 00 fc 40 fb 40 fb c0 fb c0 fb .`. ...@.@.....
< SCO data: handle 43 dlen 48
0000: c0 fa 80 fa 80 fb c0 fb c0 fb c0 fb 80 fb 80 fb ................
0010: 80 fb 00 fb 00 fb c0 fb 00 fc 80 fb 40 fb 00 fb ............@...
0020: 40 fb 00 fc 00 fc 20 fc 40 fc c0 fb c0 fb 40 fc @..... .@.....@.
< SCO data: handle 43 dlen 48
0000: 60 fc 00 fc c0 fb c0 fb c0 fb 20 fc 60 fc 00 fc `......... .`...
0010: 00 fc 20 fc 20 fc 20 fc 60 fc 80 fc 80 fc 60 fc .. . . .`.....`.
0020: 40 fc c0 fb c0 fb 00 fc 20 fc 00 fc c0 fb 00 fc @....... .......
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 14 fcs 0x3e
0000: 0d 0a 2b 43 49 45 56 3a 20 31 2c 30 0d 0a ..+CIEV: 1,0..
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 40 flags 0x02 dlen 15
L2CAP(d): cid 0x0040 len 11 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 7 fcs 0xe4
0000: 41 54 2b 43 48 55 50 AT+CHUP
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
< SCO data: handle 43 dlen 48
0000: 40 fc a0 fc c0 fc 00 fd 00 fd e0 fc c0 fc a0 fc @...............
0010: c0 fc a0 fc c0 fc a0 fc 80 fc c0 fc 40 fd 40 fd ............@.@.
0020: 00 fd 40 fd 00 fd a0 fc c0 fc e0 fc e0 fc 40 fd ..@...........@.
< HCI Command: Disconnect (0x01|0x0006) plen 3
handle 43 reason 0x13
Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
Disconnect (0x01|0x0006) status 0x00 ncmd 1
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 43 reason 0x16
Reason: Connection Terminated by Local Host
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> SCO data: handle 43 dlen 48
0000: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0010: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
0020: fe ff fe ff fe ff fe ff fe ff fe ff fe ff fe ff ................
> ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> HCI Event: Max Slots Change (0x1b) plen 3
handle 40 slots 5
> ACL data: handle 40 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 6 fcs 0x3e
0000: 0d 0a 4f 4b 0d 0a ..OK..
> ACL data: handle 40 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 0 dlci 26 pf 1 ilen 0 fcs 0x67
< ACL data: handle 40 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 0 dlci 26 pf 1 ilen 0 fcs 0x4d
< ACL data: handle 40 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 0 dlci 0 pf 1 ilen 0 fcs 0x9c
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 40 reason 0x13
Reason: Remote User Terminated Connection
Kind Regards
Khaled
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Khaled
> My next step now is to upgrade the kernel to one of the 2.6.14 kernel. But
> before I do...
I should say that upgrading the kernel is only useful if your asterisk
stuff needs the snd-bt-sco module. If it just transfers audio direct to
the bluetooth layer, then it isn't likely to help.
Brad
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Marcel, Steven, Brad
My next step now is to upgrade the kernel to one of the 2.6.14 kernel. But
before I do...
I have noticed that sometimes, when I start asterisk, after initialising a
bluetooth link to the phone, there is an incoming sco link...note that
usually, only an acl link is created at this point and an sco when a call is
initiated. But reoccuringly, usually the first time I run asterisk, an
incoming sco link is attempted to be created. This sco link lasts for about
2/3 seconds before it dies.
Please look at the following extract from asterisk atrtup (debug enabled)
and then the hcidump -X -V output for this event (unfortunately I couldn't
access all of the hcidump since I couldn't scroll up the terminal window far
enough!)
1. Asterisk -vvvvvvvvvvc:
Asterisk Ready.
*CLI> Dec 8 11:21:42 NOTICE[4515]:
/usr/src/chan_bluetooth/chan_bluetooth.c:2041 try_connect: Initial
ised bluetooth link to device Nokia6310i
[AG] Nokia6310i < AT+BRSF=23
[AG] Nokia6310i > ERROR
Dec 8 11:21:42 DEBUG[4515]: /usr/src/chan_bluetooth/chan_bluetooth.c:1658
ag_brsf_response: Bluetooth
features: ERROR
[AG] Nokia6310i < AT+CIND=?
Dec 8 11:21:42 DEBUG[4515]: /usr/src/chan_bluetooth/chan_bluetooth.c:1504
ag_unsol_cind: CIND: 1=call
Dec 8 11:21:42 DEBUG[4515]: /usr/src/chan_bluetooth/chan_bluetooth.c:1504
ag_unsol_cind: CIND: 2=serv
ice
Dec 8 11:21:42 DEBUG[4515]: /usr/src/chan_bluetooth/chan_bluetooth.c:1514
ag_unsol_cind: CIND: 3=call
_setup
[AG] Nokia6310i > +CIND:
("call",(0,1)),("service",(0,1)),("call_setup",(0-3))
[AG] Nokia6310i > OK
[AG] Nokia6310i < AT+CIND?
Dec 8 11:21:42 DEBUG[4515]: /usr/src/chan_bluetooth/chan_bluetooth.c:386
set_cind: CIND 1 set to 0
Dec 8 11:21:42 DEBUG[4515]: /usr/src/chan_bluetooth/chan_bluetooth.c:386
set_cind: CIND 2 set to 1
Dec 8 11:21:42 NOTICE[4515]: /usr/src/chan_bluetooth/chan_bluetooth.c:417
set_cind: Audio Gateway Nok
ia6310i got signal
Dec 8 11:21:42 DEBUG[4515]: /usr/src/chan_bluetooth/chan_bluetooth.c:1539
ag_unsol_cind: CIND IND 3 s
et to 0 [0]
[AG] Nokia6310i > +CIND: 0,1,0
[AG] Nokia6310i > OK
[AG] Nokia6310i < AT+CMER=3,0,0,1
Dec 8 11:21:42 DEBUG[4515]: /usr/src/chan_bluetooth/chan_bluetooth.c:2265
handle_incoming_sco: Incoming SCO socket
Dec 8 11:21:42 DEBUG[4515]: /usr/src/chan_bluetooth/chan_bluetooth.c:2295
handle_incoming_sco: SCO Connect from Nokia6310i
Dec 8 11:21:42 DEBUG[4516]: /usr/src/chan_bluetoot
h/chan_bluetooth.c:522 sco_thread: SCO thread started on fd 25, pid 4516
Dec 8 11:21:42 DEBUG[4515]: /usr/src/chan_bluetooth/chan_bluetooth.c:2315
handle_incoming_sco: SCO: 2
5, HCIHandle=43, MUT=64
[AG] Nokia6310i > OK
[AG] Nokia6310i < AT+CLIP=1
[AG] Nokia6310i > OK
[AG] Nokia6310i < AT+CGMI=?
[AG] Nokia6310i > OK
[AG] Nokia6310i < AT+CGMI
[AG] Nokia6310i > Nokia
[AG] Nokia6310i > OK
-----------------The Disconnect below (hcidump -X -V) happens here after 2/3
seconds---------------------------------------
Dec 8 11:21:47 ERROR[4516]: /usr/src/chan_bluetooth/chan_bluetooth.c:586
sco_thread: SCO connection error: Connection reset by peer
(errno 104)
Dec 8 11:21:47 DEBUG[4516]: /usr/src/chan_bluetooth/chan_bluetooth.c:619
sco_thread: SCO thread stopped
2. hcidump -X -V when asterisk -vvvvvvvvvc is run:
00 ................
< SCO data: handle 43 dlen 48
0000: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
0010: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
0020: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
< SCO data: handle 43 dlen 48
0000: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
0010: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
0020: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
< SCO data: handle 43 dlen 48
0000: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
0010: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
0020: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
< SCO data: handle 43 dlen 48
0000: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
0010: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
0020: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
> SCO data: handle 43 dlen 48
0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> SCO data: handle 43 dlen 48
0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> SCO data: handle 43 dlen 48
0000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
.
.
. This repeats untill:
.
.
< SCO data: handle 43 dlen 48
0000: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
0010: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
0020: 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f ................
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 43 reason 0x13
Reason: Remote User Terminated Connection
> HCI Event: Max Slots Change (0x1b) plen 3
handle 40 slots 5
> HCI Event: Mode Change (0x14) plen 6
status 0x00 handle 40 mode 0x02 interval 800
Mode: Sniff
Please remember this happens very very occassionally...most of the time
there is no incoming sco connection untill a call is made.
The disconnect is automatic and happens almost immediately. Any ideas on
this guys? Why would the phone try to create an sco link before a call once,
and thereafter only initiate an sco link at an active call, but then with no
hcidump trace of sco packets unlike here?
Should I continue with a kernel upgrade? Also, I cannot see sco_bt_snd
anywhere in the system...do I need this and for what?
Finally, does it matter whether I use OSS or alsa?
Kind Regards
Khaled
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Brad
> Midgley
> Sent: 07 December 2005 16:51
> To: [email protected]
> Subject: Re: [Bluez-users] Bluetooth Voice Setting
>
>
> Khaled
>
> > **[root@mdk10-voipgsm root]# uname -r
> > 2.6.3-7mdk (Mandrake 10)
>
> this could be a problem. If you can, use something newer like 2.6.14.
> You'll have to rebuild sco_bt_snd too.
>
> Brad
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Khaled
> **[root@mdk10-voipgsm root]# uname -r
> 2.6.3-7mdk (Mandrake 10)
this could be a problem. If you can, use something newer like 2.6.14.
You'll have to rebuild sco_bt_snd too.
Brad
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Marcel, Brad, Steven,
> > You might also want to check the output of
> /proc/bus/usb/devices and make
> > sure the device has registered its isochronous endpoints correctly.
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.3-7mdk ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:03.2
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.3-7mdk ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:03.1
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 22/900 us ( 2%), #Int= 1, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.3-7mdk ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:03.0
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a12 ProdID=0001 Rev= 3.73
C:* #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=200mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
I: If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
I dont really know how to interpret this.
> and that the kernel driver includes support for it "modinfo hci_usb"
> must show an isoc parameter for most recent Linux kernels. What kernel
> are you using?
>
I am using: 2.6.3-7mdk (mandrake 10)
[root@mdk10-voipgsm root]# modinfo hci_usb
author: Maxim Krasnyansky <[email protected]>
description: Bluetooth HCI USB driver ver 2.4
license: GPL
vermagic: 2.6.3-7mdk 586
depends: usbcore,bluetooth
alias: usb:v0A5Cp2033dl*dh*dc*dsc*dp*ic*isc*ip*
alias: usb:v08FDp0001dl*dh*dc*dsc*dp*ic*isc*ip*
alias: usb:v*p*dl*dh*dcE0dsc01dp01ic*isc*ip*
alias: usb:v0BDBp1002dl*dh*dc*dsc*dp*ic*isc*ip*
alias: usb:v044Ep3002dl*dh*dc*dsc*dp*ic*isc*ip*
alias: usb:v04BFp030Adl*dh*dc*dsc*dp*ic*isc*ip*
I am not sure what you mean by isoc parameter...
Regards
Khaled
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Steven, Brad,
Thanks for your help Steven; Brad do you have any ideas?
I am using asterisk and Theo Zourzouvillys' chan_bluetooth module to
integrate voip and gsm. I understand that Theo's code may not be fully
functioning but there are people out there (most of whom are/have been on
the bluez-users list) who have managed at least one-way audio transfer in
this setup. I haven't achieved this yet and so my efforts continue.
I believe there are seniors out there who have actually fully implemented
theo's project to the extent that it works occassionally!
If what you are saying Steven is correct then it would seem the
chan_bluetooth module is at fault - BUT even then, why do I not get even
unidirectional sound? There is more to it...
I would be grateful for any help from you guys.
Kind Regards
Khaled
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Steven
> Singer
> Sent: 07 December 2005 16:06
> To: [email protected]
> Subject: Re: [Bluez-users] Bluetooth Voice Setting
>
>
> Khaled wrote:
> > I have just checked hcidump again: when in an active call there
> is no output
> > on hcidump -X -V, the last trace is:
> >
> > > ..+CIEV: 3,3..
> > > ..+CIEV: 1,1..
> > > ..+CIEV: 3,0..
> >
> > The trace holds on this for as long as the call is active, then once the
> > destination (dialled phone) is hung up, still nothing happens
> untill about 5
> > seconds later when the call on the mobile phone dissappears, at
> which point
> > the next line in the trace (ERROR) appears:
> >
> > > ..ERROR..
> > > ..+CIEV: 1,0..
>
> Right. This looks like a perfectly normal connection and a perfectly
> normal disconnection (in response to a remote hangup). As far as all
> the signalling is concerned at all protocol levels on both sides, the
> SCO link was up and running normally in the bit in the middle.
>
> The problem is therefore something to do with getting the SCO data out
> of the module and into your app. You haven't said which app and which
> version of that app you're using.
>
> Anyway, this all looks more like Brad's department than mine :-) Maybe
> you have to run some command to get the USB subsystem to start polling
> the isochronous endpoints.
>
> > Output from hciconfig -a:
> [...]
> > HCI Ver: 1.1 (0x1) HCI Rev: 0x175 LMP Ver: 1.1 (0x1)
> LMP Subver: 0x175
> > Manufacturer: Cambridge Silicon Radio (10)
> [...]
> > Output from hciconfig hcio revision:
> [...]
> > HCI 14.7
>
> That's very old firmware. You might want to consider upgrading to version
> 16.4 or later. I don't think SCO over USB is completely broken in 14.7,
> it's just that there were a set of bug fixes between 14.7 and 16.4. I
> suspect 14.7 works sufficiently well to get some noises out of the
> system.
>
> Brad might know if anyone has successfully got SCO over USB working with
> BlueZ and 14.7 CSR firmware.
>
> You might also want to check the output of /proc/bus/usb/devices and make
> sure the device has registered its isochronous endpoints correctly.
>
> > Any thoughts? I was wondering why then in the trace, is there
> references to
> > SCO? see below:
> [...]
> >> HCI Event: Connect Complete (0x03) plen 11
> > status 0x00 handle 43 bdaddr 00:0E:6D:34:BD:B1 type SCO encrypt 0x01
>
> This means that a SCO connection was formed at the baseband. It says
> nothing about where the SCO data is going (or even whether there's any
> SCO data flowing across the link).
>
> Specifically, it does not say whether the USB isochronous endpoints are
> even being polled.
>
> - Steven
> --
>
>
> This message has been scanned for viruses by BlackSpider
> MailControl - http://www.blackspider.com
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Steven,
> You might also want to check the output of /proc/bus/usb/devices and make
> sure the device has registered its isochronous endpoints correctly.
and that the kernel driver includes support for it "modinfo hci_usb"
must show an isoc parameter for most recent Linux kernels. What kernel
are you using?
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Khaled wrote:
> I have just checked hcidump again: when in an active call there is no output
> on hcidump -X -V, the last trace is:
>
> > ..+CIEV: 3,3..
> > ..+CIEV: 1,1..
> > ..+CIEV: 3,0..
>
> The trace holds on this for as long as the call is active, then once the
> destination (dialled phone) is hung up, still nothing happens untill about 5
> seconds later when the call on the mobile phone dissappears, at which point
> the next line in the trace (ERROR) appears:
>
> > ..ERROR..
> > ..+CIEV: 1,0..
Right. This looks like a perfectly normal connection and a perfectly
normal disconnection (in response to a remote hangup). As far as all
the signalling is concerned at all protocol levels on both sides, the
SCO link was up and running normally in the bit in the middle.
The problem is therefore something to do with getting the SCO data out
of the module and into your app. You haven't said which app and which
version of that app you're using.
Anyway, this all looks more like Brad's department than mine :-) Maybe
you have to run some command to get the USB subsystem to start polling
the isochronous endpoints.
> Output from hciconfig -a:
[...]
> HCI Ver: 1.1 (0x1) HCI Rev: 0x175 LMP Ver: 1.1 (0x1) LMP Subver: 0x175
> Manufacturer: Cambridge Silicon Radio (10)
[...]
> Output from hciconfig hcio revision:
[...]
> HCI 14.7
That's very old firmware. You might want to consider upgrading to version
16.4 or later. I don't think SCO over USB is completely broken in 14.7,
it's just that there were a set of bug fixes between 14.7 and 16.4. I
suspect 14.7 works sufficiently well to get some noises out of the
system.
Brad might know if anyone has successfully got SCO over USB working with
BlueZ and 14.7 CSR firmware.
You might also want to check the output of /proc/bus/usb/devices and make
sure the device has registered its isochronous endpoints correctly.
> Any thoughts? I was wondering why then in the trace, is there references to
> SCO? see below:
[...]
>> HCI Event: Connect Complete (0x03) plen 11
> status 0x00 handle 43 bdaddr 00:0E:6D:34:BD:B1 type SCO encrypt 0x01
This means that a SCO connection was formed at the baseband. It says
nothing about where the SCO data is going (or even whether there's any
SCO data flowing across the link).
Specifically, it does not say whether the USB isochronous endpoints are
even being polled.
- Steven
--
This message has been scanned for viruses by BlackSpider MailControl - http://www.blackspider.com
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Brad, Steven,
Further information:
I have just checked hcidump again: when in an active call there is no output
on hcidump -X -V, the last trace is:
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 33 2c 33 0d i....+CIEV:
3,3.
0010: 0a 3e .>
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 31 2c 31 0d i....+CIEV:
1,1.
0010: 0a 3e .>
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 33 2c 30 0d i....+CIEV:
3,0.
0010: 0a 3e
The trace holds on this for as long as the call is active, then once the
destination (dialled phone) is hung up, still nothing happens untill about 5
seconds later when the call on the mobile phone dissappears, at which point
the next line in the trace (ERROR) appears:
> ACL data: handle 40 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 0]
0000: 69 ef 13 0d 0a 45 52 52 4f 52 0d 0a 3e i....ERROR..>
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 31 2c 30 0d i....+CIEV:
1,0.
0010: 0a 3e .>
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 0]
0000: 6b ef 05 0d 0a e4 k.....
< ACL data: handle 40 flags 0x02 dlen 15
L2CAP(d): cid 0x0040 len 11 [psm 0]
0000: 6b ef 0f 41 54 2b 43 48 55 50 e4 k..AT+CHUP.
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 0]
0000: 6b ef 05 0d 0a e4
Regards
Khaled
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Khaled
> Sent: 07 December 2005 15:06
> To: [email protected]
> Subject: RE: [Bluez-users] Bluetooth Voice Setting
>
>
> Hi Brad,
>
> > Run "hciconfig hci0 revision" as root and show us the output.
> >
> > Also see http://bluetooth-alsa.sourceforge.net/index.html#help
> >
>
> Some more information:
>
> **bluez packages were downloaded from the website
>
>
> **[root@mdk10-voipgsm root]# hcitool info 00:0e:6d:34:bd:b1
> Requesting information ...
> BD Address: 00:0e:6d:34:bd:b1
> Device Name: Nokia6310i
> LMP Version: 1.1 (0x1) LMP Subversion: 0x23b
> Manufacturer: Nokia Mobile Phones (1)
> Features: 0xbf 0x28 0x21 0x00 0x00 0x00 0x00 0x00
> <3-slot packets> <5-slot packets> <encryption>
> <slot offset>
> <timing accuracy> <role switch> <sniff mode> <SCO link>
> <HV3 packets> <CVSD> <flow control (MB)
>
> **[root@mdk10-voipgsm root]# uname -r
> 2.6.3-7mdk (Mandrake 10)
>
> **
>
> [root@mdk10-voipgsm root]# hcitool con
> Connections:
> < ACL 00:0E:6D:7A:B1:FA handle 40 state 1 lm MASTER
> #When asterisk
> is started and 6310i is initialised
> [root@mdk10-voipgsm root]# hcitool con
> Connections:
> > SCO 00:0E:6D:34:BD:B1 handle 46 state 1 lm SLAVE
> #When a call is
> made from the soft phone
> < ACL 00:0E:6D:34:BD:B1 handle 43 state 1 lm MASTER ENCRYPT
> [root@mdk10-voipgsm root]# hcitool con
> Connections:
> < ACL 00:0E:6D:34:BD:B1 handle 43 state 1 lm MASTER
> ENCRYPT #After
> hangup of soft phone
>
>
>
> Kind Regards
>
> Khaled
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Brad,
> Run "hciconfig hci0 revision" as root and show us the output.
>
> Also see http://bluetooth-alsa.sourceforge.net/index.html#help
>
Some more information:
**bluez packages were downloaded from the website
**[root@mdk10-voipgsm root]# hcitool info 00:0e:6d:34:bd:b1
Requesting information ...
BD Address: 00:0e:6d:34:bd:b1
Device Name: Nokia6310i
LMP Version: 1.1 (0x1) LMP Subversion: 0x23b
Manufacturer: Nokia Mobile Phones (1)
Features: 0xbf 0x28 0x21 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <sniff mode> <SCO link>
<HV3 packets> <CVSD> <flow control (MB)
**[root@mdk10-voipgsm root]# uname -r
2.6.3-7mdk (Mandrake 10)
**
[root@mdk10-voipgsm root]# hcitool con
Connections:
< ACL 00:0E:6D:7A:B1:FA handle 40 state 1 lm MASTER #When asterisk
is started and 6310i is initialised
[root@mdk10-voipgsm root]# hcitool con
Connections:
> SCO 00:0E:6D:34:BD:B1 handle 46 state 1 lm SLAVE #When a call is
made from the soft phone
< ACL 00:0E:6D:34:BD:B1 handle 43 state 1 lm MASTER ENCRYPT
[root@mdk10-voipgsm root]# hcitool con
Connections:
< ACL 00:0E:6D:34:BD:B1 handle 43 state 1 lm MASTER ENCRYPT #After
hangup of soft phone
Kind Regards
Khaled
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Steven
> They're not SCO packets. They're RFCOMM packets. There are no SCO
> packets on the trace.
>
> At the AT command level, the sequence is (with explanation):
>
> < \r\nATD0208xxxxx13;\r\n ; dial number (I've x'd out the number)
> > \r\nOK\r\n ; ok, will do
> > \r\n+CIEV: 3,2\r\n ; outgoing call setup in progress
> [SCO link created at HCI]
> > \r\n+CIEV: 3,3\r\n ; remote party alerted
> > \r\n+CIEV: 1,1\r\n ; call active
> > \r\n+CIEV: 3,0\r\n ; no longer in call setup (now in call)
> > \r\nERROR\r\n ; something went wrong
> > \r\n+CIEV: 1,0\r\n ; call inactive
> < \r\nAT+CHUP\r\n. ; hangup
> [SCO link disconnect started at HCI]
> > \r\nOK\r\n ; ok
> [SCO link disconnect completes at HCI]
>
> It's worth noting that the local device splits AT messages across
> multiple RFCOMM frames. This is perfectly legal as RFCOMM is a byte
> stream not a packet stream so packet boundaries are meaningless [1].
>
> The key message is the "+CIEV: 1,0" from the other side. This indicates
> that the call has been dropped. The spec seems to imply that this in
> itself is sufficient for headset to know that the call has been
> dropped and that the AT+CHUP message is used only when the headset
> wants to initiate the disconnection. However, by this point the call
> is already down so it can't hurt.
>
> Presumably the preceeding "ERROR" indication is related. Unfortunately,
> it's not possible to tell what went wrong. All the spec says is:
>
> * ERROR
>
> Standard error indication code. It shall be issued on detection of
> any syntax, format or procedure error condition. [...]
>
> Everything before the ERROR message exactly matches the reference
> message sequence chart in the spec.
>
> There are no SCO packets in the trace. Ar you sure your module is set
> to route SCO over HCI (as opposed to over a PCM port). hciconfig
> revision should tell you. You should also do hciconfig -a.
> It may be that the other side has got upset that the SCO link is up
> and it's connected to the remote side, but there has been no SCO data.
I am as sure as I can be given my being novice...
Output from hciconfig -a:
hci0: Type: USB
BD Address: 00:09:DD:10:29:78 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:45869 acl:1418 sco:0 events:2018 errors:0
TX bytes:27530 acl:1445 sco:0 commands:252 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0)'
Class: 0x200404
Service Classes:
Device Class: Audio/Video, Device conforms to the Headset profile
HCI Ver: 1.1 (0x1) HCI Rev: 0x175 LMP Ver: 1.1 (0x1) LMP Subver:
0x175
Manufacturer: Cambridge Silicon Radio (10)
Output from hciconfig hcio revision:
hci0: Type: USB
BD Address: 00:09:DD:10:29:78 ACL MTU: 192:8 SCO MTU: 64:8
HCI 14.7
Chip version: BlueCore02-External (ES2)
Max key size: 56 bit
SCO mapping: HCI
Any thoughts? I was wondering why then in the trace, is there references to
SCO? see below:
> HCI Event: Connect Request (0x04) plen 10
bdaddr 00:0E:6D:34:BD:B1 class 0x000000 type SCO
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
bdaddr 00:0E:6D:34:BD:B1 role 0x01
Role: Slave
> HCI Event: Command Status (0x0f) plen 4
Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 43 bdaddr 00:0E:6D:34:BD:B1 type SCO encrypt 0x01
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
handle 43 ptype 0x00e0
Packet type: HV1 HV2 HV3
Kind Regards
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Khaled,
Run "hciconfig hci0 revision" as root and show us the output.
Also see http://bluetooth-alsa.sourceforge.net/index.html#help
Brad
Steven Singer wrote:
> There are no SCO packets in the trace. Ar you sure your module is set
> to route SCO over HCI (as opposed to over a PCM port). hciconfig
> revision should tell you. You should also do hciconfig -a.
>
> It may be that the other side has got upset that the SCO link is up
> and it's connected to the remote side, but there has been no SCO data.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Khaled wrote:
> From the following I understand that once the SCO link is established (when
> a phone call is made), HV3 SCO packets are transmitted with voice data, but
> then what do the subsequent mean? I assume they are incoming HV3 packets?
They're not SCO packets. They're RFCOMM packets. There are no SCO
packets on the trace.
At the AT command level, the sequence is (with explanation):
< \r\nATD0208xxxxx13;\r\n ; dial number (I've x'd out the number)
> \r\nOK\r\n ; ok, will do
> \r\n+CIEV: 3,2\r\n ; outgoing call setup in progress
[SCO link created at HCI]
> \r\n+CIEV: 3,3\r\n ; remote party alerted
> \r\n+CIEV: 1,1\r\n ; call active
> \r\n+CIEV: 3,0\r\n ; no longer in call setup (now in call)
> \r\nERROR\r\n ; something went wrong
> \r\n+CIEV: 1,0\r\n ; call inactive
< \r\nAT+CHUP\r\n. ; hangup
[SCO link disconnect started at HCI]
> \r\nOK\r\n ; ok
[SCO link disconnect completes at HCI]
It's worth noting that the local device splits AT messages across
multiple RFCOMM frames. This is perfectly legal as RFCOMM is a byte
stream not a packet stream so packet boundaries are meaningless [1].
The key message is the "+CIEV: 1,0" from the other side. This indicates
that the call has been dropped. The spec seems to imply that this in
itself is sufficient for headset to know that the call has been
dropped and that the AT+CHUP message is used only when the headset
wants to initiate the disconnection. However, by this point the call
is already down so it can't hurt.
Presumably the preceeding "ERROR" indication is related. Unfortunately,
it's not possible to tell what went wrong. All the spec says is:
* ERROR
Standard error indication code. It shall be issued on detection of
any syntax, format or procedure error condition. [...]
Everything before the ERROR message exactly matches the reference
message sequence chart in the spec.
There are no SCO packets in the trace. Ar you sure your module is set
to route SCO over HCI (as opposed to over a PCM port). hciconfig
revision should tell you. You should also do hciconfig -a.
It may be that the other side has got upset that the SCO link is up
and it's connected to the remote side, but there has been no SCO data.
- Steven
[1] Although it should be worth noting that certain very old headset/
Audio gateway implementations incorrectly expected AT commands to
come in a single RFCOMM frame. This doesn't appear to be anything
to do with what's happening here, I mention it merely for future
reference.
--
This message has been scanned for viruses by BlackSpider MailControl - http://www.blackspider.com
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Brad, Marcel,
Any ideas on the hcidump output I am getting?
Thanks for your help Marcel.
Kind Regards
Khaled
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Marcel
> Holtmann
> Sent: 07 December 2005 12:27
> To: [email protected]
> Subject: RE: [Bluez-users] Bluetooth Voice Setting
>
>
> Hi Khaled,
>
> > > > > if you wanna emulate a headset then you need to add
> Headset profile
> > > > > records and not Headset Audio Gateway records.
> > > >
> > > > I mean to use the handsfree profile, so that I can speak into
> > > my computer
> > > > through a headset (earphone and mic), sorry if I was
> unclear earlier.
> > >
> > > if you wanna use a headset with your computer you don't
> really need any
> > > additional service records.
> >
> > But why dont I get any sound at the computer? Is there
> something to do with
> > the sound settings on my computer? it uses alsa and is
> functional already -
> > do I need to do anything specific for this purpose?
> >
> > From the following I understand that once the SCO link is
> established (when
> > a phone call is made), HV3 SCO packets are transmitted with
> voice data, but
> > then what do the subsequent mean? I assume they are incoming
> HV3 packets?
> > Then the local host gives up the reserved bandwidth for sco and
> disconnects?
> > But then why does it the error 0x13 and remote user disconnects message?
> > Were there any packets transmitted at all? Why the "i....ERROR..>"?
>
> I have no idea. Maybe Brad can answer this.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Khaled,
> > > > if you wanna emulate a headset then you need to add Headset profile
> > > > records and not Headset Audio Gateway records.
> > >
> > > I mean to use the handsfree profile, so that I can speak into
> > my computer
> > > through a headset (earphone and mic), sorry if I was unclear earlier.
> >
> > if you wanna use a headset with your computer you don't really need any
> > additional service records.
>
> But why dont I get any sound at the computer? Is there something to do with
> the sound settings on my computer? it uses alsa and is functional already -
> do I need to do anything specific for this purpose?
>
> From the following I understand that once the SCO link is established (when
> a phone call is made), HV3 SCO packets are transmitted with voice data, but
> then what do the subsequent mean? I assume they are incoming HV3 packets?
> Then the local host gives up the reserved bandwidth for sco and disconnects?
> But then why does it the error 0x13 and remote user disconnects message?
> Were there any packets transmitted at all? Why the "i....ERROR..>"?
I have no idea. Maybe Brad can answer this.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Marcel,
> > > if you wanna emulate a headset then you need to add Headset profile
> > > records and not Headset Audio Gateway records.
> >
> > I mean to use the handsfree profile, so that I can speak into
> my computer
> > through a headset (earphone and mic), sorry if I was unclear earlier.
>
> if you wanna use a headset with your computer you don't really need any
> additional service records.
But why dont I get any sound at the computer? Is there something to do with
the sound settings on my computer? it uses alsa and is functional already -
do I need to do anything specific for this purpose?
>From the following I understand that once the SCO link is established (when
a phone call is made), HV3 SCO packets are transmitted with voice data, but
then what do the subsequent mean? I assume they are incoming HV3 packets?
Then the local host gives up the reserved bandwidth for sco and disconnects?
But then why does it the error 0x13 and remote user disconnects message?
Were there any packets transmitted at all? Why the "i....ERROR..>"?
---EXTRACT---
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
status 0x00 handle 43 ptype 0x0080
Packet type: HV3
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 33 2c 33 0d i....+CIEV:
3,3.
0010: 0a 3e .>
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 31 2c 31 0d i....+CIEV:
1,1.
0010: 0a 3e .>
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 33 2c 30 0d i....+CIEV:
3,0.
0010: 0a 3e .>
> ACL data: handle 40 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 0]
0000: 69 ef 13 0d 0a 45 52 52 4f 52 0d 0a 3e i....ERROR..>
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 31 2c 30 0d i....+CIEV:
1,0.
0010: 0a 3e .>
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 0]
0000: 6b ef 05 0d 0a e4 k.....
< ACL data: handle 40 flags 0x02 dlen 15
L2CAP(d): cid 0x0040 len 11 [psm 0]
0000: 6b ef 0f 41 54 2b 43 48 55 50 e4 k..AT+CHUP.
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 0]
0000: 6b ef 05 0d 0a e4 k.....
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 0]
0000: 69 ff 01 03 22 i..."
< HCI Command: Disconnect (0x01|0x0006) plen 3
handle 43 reason 0x13
Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
Disconnect (0x01|0x0006) status 0x00 ncmd 1
> ACL data: handle 40 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 0]
0000: 69 ef 0d 0d 0a 4f 4b 0d 0a 3e i....OK..>
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 43 reason 0x16
Reason: Connection Terminated by Local Host
---EXTRACT---
Kind Regards
Khaled
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Kahled,
> > > > > Would you not expect to see '> SCO' lines in the hcidump output
> > > > given that I
> > > > > am (trying to) use SCO for voice transfer? Like you said in
> > one of the
> > > > > archives, hcidump shows payload of the SCO packets over hci?
> > > >
> > > > The Headset and Headfree profiles specify when the SCO
> > channel has to be
> > > > opened. Maybe your connection is not in that state. Post the output of
> > > > hcidump, so we can see what's going on.
> > >
> > > This is when the bluetooth phone is initialised:
> >
> > if you wanna emulate a headset then you need to add Headset profile
> > records and not Headset Audio Gateway records.
>
> I mean to use the handsfree profile, so that I can speak into my computer
> through a headset (earphone and mic), sorry if I was unclear earlier.
if you wanna use a headset with your computer you don't really need any
additional service records.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Marcel Holtmann wrote:
> ... Use "hcidump -X -V" as stated almost everywhere in the
> mailing list archives.
We should have a FAQ for these mailing lists. Here's my first draft:
Q1) I have ...
A1) Use hcidump -X -V.
Q2) But I haven't told you ...
A2) Use hcidump -X -V.
Q3) But you don't know ...
A3) Use hcidump -X -V.
:-)
- Steven
--
This message has been scanned for viruses by BlackSpider MailControl - http://www.blackspider.com
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Marcel,
> > > > Would you not expect to see '> SCO' lines in the hcidump output
> > > given that I
> > > > am (trying to) use SCO for voice transfer? Like you said in
> one of the
> > > > archives, hcidump shows payload of the SCO packets over hci?
> > >
> > > The Headset and Headfree profiles specify when the SCO
> channel has to be
> > > opened. Maybe your connection is not in that state. Post the output of
> > > hcidump, so we can see what's going on.
> >
> > This is when the bluetooth phone is initialised:
>
> if you wanna emulate a headset then you need to add Headset profile
> records and not Headset Audio Gateway records.
I mean to use the handsfree profile, so that I can speak into my computer
through a headset (earphone and mic), sorry if I was unclear earlier.
I have done sdptool add hf to add the handsfree profile:
Service Name: Handsfree
Service RecHandle: 0x10002
Service Class ID List:
"Handsfree" (0x111e)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0101
One thing I have noticed is that Handsfree is reffered to as 0x111e; I need
to use 0x111f which is the handsfree audio gateway profile as advertised on
my mobile. Is this an incompatibility issue?
The service on the mobile of interest is:
Service Name: Voice Gateway
Service RecHandle: 0x10005
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 13
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0100
Thus I have specified channel 13 under rfcomm (only this channel registers
my machine as a headset to my mobile phone).
Any thoughts? When I do sdptool local browse:
[root@mdk10-voipgsm root]# sdptool browse local
Browsing FF:FF:FF:00:00:00 ...
Service Name: Voice Gateway
Service RecHandle: 0x10000
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 5
Profile Descriptor List:
"Handfree Audio Gateway" (0x111f)
Version: 0x0100
Service Name: Voice Gateway
Service RecHandle: 0x10001
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 6
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0100
Service Name: Handsfree
Service RecHandle: 0x10002
Service Class ID List:
"Handsfree" (0x111e)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0101
Isn't this correct?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Khaled,
> > > Would you not expect to see '> SCO' lines in the hcidump output
> > given that I
> > > am (trying to) use SCO for voice transfer? Like you said in one of the
> > > archives, hcidump shows payload of the SCO packets over hci?
> >
> > The Headset and Headfree profiles specify when the SCO channel has to be
> > opened. Maybe your connection is not in that state. Post the output of
> > hcidump, so we can see what's going on.
>
> This is when the bluetooth phone is initialised:
if you wanna emulate a headset then you need to add Headset profile
records and not Headset Audio Gateway records.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Marcel,
> > Would you not expect to see '> SCO' lines in the hcidump output
> given that I
> > am (trying to) use SCO for voice transfer? Like you said in one of the
> > archives, hcidump shows payload of the SCO packets over hci?
>
> The Headset and Headfree profiles specify when the SCO channel has to be
> opened. Maybe your connection is not in that state. Post the output of
> hcidump, so we can see what's going on.
This is when the bluetooth phone is initialised:
[root@mdk10-voipgsm root]# hcidump -X -V
HCI sniffer - Bluetooth packet analyzer ver 1.27
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> HCI Event: Command Complete (0x0e) plen 6
Read Voice Setting (0x03|0x0025) ncmd 1
status 0x00 voice setting 0x0060
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:0E:6D:34:BD:B1 ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 40 bdaddr 00:0E:6D:34:BD:B1 type ACL encrypt 0x00
< ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
handle 40 policy 0x0f
Link policy: RSWITCH HOLD SNIFF PARK
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Command Complete (0x0e) plen 6
Write Link Policy Settings (0x02|0x000d) ncmd 1
status 0x00 handle 40
> HCI Event: Max Slots Change (0x1b) plen 3
handle 40 slots 5
> ACL data: handle 40 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
Connection successful
< ACL data: handle 40 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 1024
> HCI Event: QoS Setup Complete (0x0d) plen 21
status 0x00 handle 40 flags 0
Service type: 1
Token rate: 0
Peak bandwith: 0
Latency: -1
Delay variation: -1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 16
> ACL data: handle 40 flags 0x01 dlen 16
> ACL data: handle 40 flags 0x01 dlen 8
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 28
MTU 32772 QoS 0x01 (Best effort)
< ACL data: handle 40 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 40 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
< ACL data: handle 40 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 40 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 26 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 1019 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 16
> ACL data: handle 40 flags 0x01 dlen 2
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 26 frame_type 0 credit_flow 14 pri 7 ack_timer 0
frame_size 324 max_retrans 0 credits 0
< ACL data: handle 40 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 26 pf 1 ilen 0 fcs 0xe7
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:0E:6D:34:BD:B1
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:0E:6D:34:BD:B1 key 802C4CACA4F2F18E1942747328FEFAE5
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:0E:6D:34:BD:B1
> HCI Event: Encrypt Change (0x08) plen 4
status 0x00 handle 40 encrypt 0x01
> ACL data: handle 40 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 26 pf 1 ilen 0 fcs 0x2c
< ACL data: handle 40 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 26 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 7
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0041
< ACL data: handle 40 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 26 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 1 b2 0 b3 0 len 7
< ACL data: handle 40 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 26 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 1 b2 0 b3 0 len 7
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 0
< ACL data: handle 40 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
Success
< ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 4
> ACL data: handle 40 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
Success
> ACL data: handle 40 flags 0x02 dlen 17
L2CAP(d): cid 0x0041 len 13 [psm 1]
SDP SS Req: tid 0x178 len 0x8
pat uuid-16 0x111e (Handsfree)
max 255
cont 00
< ACL data: handle 40 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 len 14 [psm 1]
SDP SS Rsp: tid 0x178 len 0x9
count 1
handle 0x10001
cont 00
> ACL data: handle 40 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): RPN CMD: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 26 br 7 db 3 sb 0 p 0 pt 0 xi 0 xo 0
rtri 0 rtro 0 rtci 0 rtco 0 xon 17 xoff 19 pm 0x006f
< ACL data: handle 40 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): RPN RSP: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 26 br 7 db 3 sb 0 p 0 pt 0 xi 0 xo 0
rtri 0 rtro 0 rtci 0 rtco 0 xon 17 xoff 19 pm 0x3f7f
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 26 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 1 len 3
< ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 1 ilen 0 fcs 0xf8 credits 33
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 40 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 10 fcs 0xe4
0000: 41 54 2b 42 52 53 46 3d 32 33 AT+BRSF=23
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 21
L2CAP(d): cid 0x0041 len 17 [psm 1]
SDP SA Req: tid 0x179 len 0xc
handle 0x10001
max 255
aid(s) 0x0311 (unknown)
cont 00
< ACL data: handle 40 flags 0x02 dlen 14
L2CAP(d): cid 0x0041 len 10 [psm 1]
SDP SA Rsp: tid 0x179 len 0x5
count 2
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0041
< ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0041
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 9 fcs 0x3e
0000: 0d 0a 45 52 52 4f 52 0d 0a ..ERROR..
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 40 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 9 fcs 0xe4
0000: 41 54 2b 43 49 4e 44 3d 3f AT+CIND=?
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0041
< ACL data: handle 40 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 0
< ACL data: handle 40 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
Success
< ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 78
L2CAP(d): cid 0x0040 len 74 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 70 fcs 0x3e
0000: 0d 0a 2b 43 49 4e 44 3a 20 28 22 63 61 6c 6c 22 ..+CIND:
("call"
0010: 2c 28 30 2c 31 29 29 2c 28 22 73 65 72 76 69 63
,(0,1)),("servic
0020: 65 22 2c 28 30 2c 31 29 29 2c 28 22 63 61 6c 6c
e",(0,1)),("call
0030: 5f 73 65 74 75 70 22 2c 28 30 2d 33 29 29 0d 0a
_setup",(0-3))..
0040: 0d 0a 4f 4b 0d 0a ..OK..
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 40 flags 0x02 dlen 16
L2CAP(d): cid 0x0040 len 12 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 8 fcs 0xe4
0000: 41 54 2b 43 49 4e 44 3f AT+CIND?
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
Success
> ACL data: handle 40 flags 0x02 dlen 31
L2CAP(d): cid 0x0041 len 27 [psm 1]
SDP SS Req: tid 0x17a len 0x16
pat uuid-128 00005555-0000-1000-8000-0002ee000001
max 255
cont 00
< ACL data: handle 40 flags 0x02 dlen 14
L2CAP(d): cid 0x0041 len 10 [psm 1]
SDP SS Rsp: tid 0x17a len 0x5
count 0
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0041
< ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0041
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 30
L2CAP(d): cid 0x0040 len 26 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 22 fcs 0x3e
0000: 0d 0a 2b 43 49 4e 44 3a 20 30 2c 31 2c 30 0d 0a ..+CIND:
0,1,0..
0010: 0d 0a 4f 4b 0d 0a ..OK..
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 40 flags 0x02 dlen 23
L2CAP(d): cid 0x0040 len 19 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 15 fcs 0xe4
0000: 41 54 2b 43 4d 45 52 3d 33 2c 30 2c 30 2c 31
AT+CMER=3,0,0,1
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 40 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 6 fcs 0x3e
0000: 0d 0a 4f 4b 0d 0a ..OK..
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 40 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 9 fcs 0xe4
0000: 41 54 2b 43 4c 49 50 3d 31 AT+CLIP=1
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 40 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 6 fcs 0x3e
0000: 0d 0a 4f 4b 0d 0a ..OK..
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 40 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 9 fcs 0xe4
0000: 41 54 2b 43 47 4d 49 3d 3f AT+CGMI=?
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 40 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 6 fcs 0x3e
0000: 0d 0a 4f 4b 0d 0a ..OK..
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 40 flags 0x02 dlen 15
L2CAP(d): cid 0x0040 len 11 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 7 fcs 0xe4
0000: 41 54 2b 43 47 4d 49 AT+CGMI
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 40 flags 0x02 dlen 23
L2CAP(d): cid 0x0040 len 19 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 15 fcs 0x3e
0000: 0d 0a 4e 6f 6b 69 61 0d 0a 0d 0a 4f 4b 0d 0a
..Nokia....OK..
> HCI Event: Mode Change (0x14) plen 6
status 0x00 handle 40 mode 0x02 interval 800
Mode: Sniff
This is when a call is active (when a call is made) NOTE: when the call is
terminated, the ACL connection is terminated and then automatically
reconnected so at the end of the following output, the above may be
repeated.
[root@mdk10-voipgsm root]# hcidump -X -V
HCI sniffer - Bluetooth packet analyzer ver 1.27
device: hci0 snap_len: 1028 filter: 0xffffffff
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 0]
0000: 6b ef 05 0d 0a e4 k.....
< ACL data: handle 40 flags 0x02 dlen 23
L2CAP(d): cid 0x0040 len 19 [psm 0]
0000: 6b ef 1f 41 54 44 30 32 30 38 31 31 34 31 30 31
k..ATD0208114101
0010: 33 3b e4 3;.
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 0]
0000: 6b ef 05 0d 0a e4 k.....
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Mode Change (0x14) plen 6
status 0x00 handle 40 mode 0x00 interval 0
Mode: Active
> ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 0]
0000: 69 ff 01 03 22 i..."
> ACL data: handle 40 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 0]
0000: 69 ef 0d 0d 0a 4f 4b 0d 0a 3e i....OK..>
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 33 2c 32 0d i....+CIEV:
3,2.
0010: 0a 3e .>
> HCI Event: Connect Request (0x04) plen 10
bdaddr 00:0E:6D:34:BD:B1 class 0x000000 type SCO
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
bdaddr 00:0E:6D:34:BD:B1 role 0x01
Role: Slave
> HCI Event: Command Status (0x0f) plen 4
Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 43 bdaddr 00:0E:6D:34:BD:B1 type SCO encrypt 0x01
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
handle 43 ptype 0x00e0
Packet type: HV1 HV2 HV3
> HCI Event: Max Slots Change (0x1b) plen 3
handle 40 slots 1
> HCI Event: Command Status (0x0f) plen 4
Change Connection Packet Type (0x01|0x000f) status 0x00 ncmd 1
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
status 0x00 handle 43 ptype 0x0080
Packet type: HV3
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 33 2c 33 0d i....+CIEV:
3,3.
0010: 0a 3e .>
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 31 2c 31 0d i....+CIEV:
1,1.
0010: 0a 3e .>
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 33 2c 30 0d i....+CIEV:
3,0.
0010: 0a 3e .>
> ACL data: handle 40 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 0]
0000: 69 ef 13 0d 0a 45 52 52 4f 52 0d 0a 3e i....ERROR..>
> ACL data: handle 40 flags 0x02 dlen 22
L2CAP(d): cid 0x0040 len 18 [psm 0]
0000: 69 ef 1d 0d 0a 2b 43 49 45 56 3a 20 31 2c 30 0d i....+CIEV:
1,0.
0010: 0a 3e .>
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 0]
0000: 6b ef 05 0d 0a e4 k.....
< ACL data: handle 40 flags 0x02 dlen 15
L2CAP(d): cid 0x0040 len 11 [psm 0]
0000: 6b ef 0f 41 54 2b 43 48 55 50 e4 k..AT+CHUP.
< ACL data: handle 40 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 0]
0000: 6b ef 05 0d 0a e4 k.....
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 0]
0000: 69 ff 01 03 22 i..."
< HCI Command: Disconnect (0x01|0x0006) plen 3
handle 43 reason 0x13
Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
Disconnect (0x01|0x0006) status 0x00 ncmd 1
> ACL data: handle 40 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 0]
0000: 69 ef 0d 0d 0a 4f 4b 0d 0a 3e i....OK..>
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 43 reason 0x16
Reason: Connection Terminated by Local Host
> HCI Event: Max Slots Change (0x1b) plen 3
handle 40 slots 5
> ACL data: handle 40 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 0]
0000: 69 53 01 67 iS.g
< ACL data: handle 40 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 0]
0000: 69 73 01 4d is.M
< ACL data: handle 40 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 0]
0000: 03 53 01 fd .S..
< ACL data: handle 40 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 40 packets 1
> ACL data: handle 40 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 0]
0000: 01 53 01 9c .S..
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 40 reason 0x13
Reason: Remote User Terminated Connection
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:0E:6D:34:BD:B1 ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 41 bdaddr 00:0E:6D:34:BD:B1 type ACL encrypt 0x00
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
handle 41 policy 0x0f
Link policy: RSWITCH HOLD SNIFF PARK
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Command Complete (0x0e) plen 6
Write Link Policy Settings (0x02|0x000d) ncmd 1
status 0x00 handle 41
> HCI Event: Max Slots Change (0x1b) plen 3
handle 41 slots 5
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
Connection successful
< ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 1024
> HCI Event: QoS Setup Complete (0x0d) plen 21
status 0x00 handle 41 flags 0
Service type: 1
Token rate: 0
Peak bandwith: 0
Latency: -1
Delay variation: -1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 16
> ACL data: handle 41 flags 0x01 dlen 16
> ACL data: handle 41 flags 0x01 dlen 8
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 28
MTU 32772 QoS 0x01 (Best effort)
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 26 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 1019 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 16
> ACL data: handle 41 flags 0x01 dlen 2
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 26 frame_type 0 credit_flow 14 pri 7 ack_timer 0
frame_size 324 max_retrans 0 credits 0
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 26 pf 1 ilen 0 fcs 0xe7
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:0E:6D:34:BD:B1
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:0E:6D:34:BD:B1 key 802C4CACA4F2F18E1942747328FEFAE5
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:0E:6D:34:BD:B1
> HCI Event: Encrypt Change (0x08) plen 4
status 0x00 handle 41 encrypt 0x01
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 26 pf 1 ilen 0 fcs 0x2c
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 26 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 7
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0041
< ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 26 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 1 b2 0 b3 0 len 7
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 26 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 1 b2 0 b3 0 len 7
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 0
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
Success
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 4
> ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
Success
> ACL data: handle 41 flags 0x02 dlen 17
L2CAP(d): cid 0x0041 len 13 [psm 1]
SDP SS Req: tid 0x17b len 0x8
pat uuid-16 0x111e (Handsfree)
max 255
cont 00
> ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): RPN CMD: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 26 br 7 db 3 sb 0 p 0 pt 0 xi 0 xo 0
rtri 0 rtro 0 rtci 0 rtco 0 xon 17 xoff 19 pm 0x006f
< ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): RPN RSP: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 26 br 7 db 3 sb 0 p 0 pt 0 xi 0 xo 0
rtri 0 rtro 0 rtci 0 rtco 0 xon 17 xoff 19 pm 0x3f7f
< ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 len 14 [psm 1]
SDP SS Rsp: tid 0x17b len 0x9
count 1
handle 0x10001
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 26 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 1 ilen 0 fcs 0xf8 credits 33
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 10 fcs 0xe4
0000: 41 54 2b 42 52 53 46 3d 32 33 AT+BRSF=23
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 21
L2CAP(d): cid 0x0041 len 17 [psm 1]
SDP SA Req: tid 0x17c len 0xc
handle 0x10001
max 255
aid(s) 0x0311 (unknown)
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(d): cid 0x0041 len 10 [psm 1]
SDP SA Rsp: tid 0x17c len 0x5
count 2
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0041
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0041
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 9 fcs 0x3e
0000: 0d 0a 45 52 52 4f 52 0d 0a ..ERROR..
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 41 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 9 fcs 0xe4
0000: 41 54 2b 43 49 4e 44 3d 3f AT+CIND=?
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0041
< ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 0
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
Success
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 78
L2CAP(d): cid 0x0040 len 74 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 70 fcs 0x3e
0000: 0d 0a 2b 43 49 4e 44 3a 20 28 22 63 61 6c 6c 22 ..+CIND:
("call"
0010: 2c 28 30 2c 31 29 29 2c 28 22 73 65 72 76 69 63
,(0,1)),("servic
0020: 65 22 2c 28 30 2c 31 29 29 2c 28 22 63 61 6c 6c
e",(0,1)),("call
0030: 5f 73 65 74 75 70 22 2c 28 30 2d 33 29 29 0d 0a
_setup",(0-3))..
0040: 0d 0a 4f 4b 0d 0a ..OK..
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 41 flags 0x02 dlen 16
L2CAP(d): cid 0x0040 len 12 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 8 fcs 0xe4
0000: 41 54 2b 43 49 4e 44 3f AT+CIND?
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
Success
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 2
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 31
L2CAP(d): cid 0x0041 len 27 [psm 1]
SDP SS Req: tid 0x17d len 0x16
pat uuid-128 00005555-0000-1000-8000-0002ee000001
max 255
cont 00
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(d): cid 0x0041 len 10 [psm 1]
SDP SS Rsp: tid 0x17d len 0x5
count 0
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0041
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0041
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 30
L2CAP(d): cid 0x0040 len 26 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 22 fcs 0x3e
0000: 0d 0a 2b 43 49 4e 44 3a 20 30 2c 31 2c 30 0d 0a ..+CIND:
0,1,0..
0010: 0d 0a 4f 4b 0d 0a ..OK..
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 41 flags 0x02 dlen 23
L2CAP(d): cid 0x0040 len 19 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 15 fcs 0xe4
0000: 41 54 2b 43 4d 45 52 3d 33 2c 30 2c 30 2c 31
AT+CMER=3,0,0,1
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 41 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 6 fcs 0x3e
0000: 0d 0a 4f 4b 0d 0a ..OK..
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 41 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 9 fcs 0xe4
0000: 41 54 2b 43 4c 49 50 3d 31 AT+CLIP=1
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 41 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 6 fcs 0x3e
0000: 0d 0a 4f 4b 0d 0a ..OK..
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 41 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 9 fcs 0xe4
0000: 41 54 2b 43 47 4d 49 3d 3f AT+CGMI=?
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 41 flags 0x02 dlen 14
L2CAP(d): cid 0x0040 len 10 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 6 fcs 0x3e
0000: 0d 0a 4f 4b 0d 0a ..OK..
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
< ACL data: handle 41 flags 0x02 dlen 15
L2CAP(d): cid 0x0040 len 11 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 7 fcs 0xe4
0000: 41 54 2b 43 47 4d 49 AT+CGMI
< ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0040 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 26 pf 0 ilen 2 fcs 0xe4
0000: 0d 0a ..
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 1 ilen 0 fcs 0x22 credits 3
> ACL data: handle 41 flags 0x02 dlen 23
L2CAP(d): cid 0x0040 len 19 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 26 pf 0 ilen 15 fcs 0x3e
0000: 0d 0a 4e 6f 6b 69 61 0d 0a 0d 0a 4f 4b 0d 0a
..Nokia....OK..
> HCI Event: Mode Change (0x14) plen 6
status 0x00 handle 41 mode 0x02 interval 800
Mode: Sniff
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Khaled,
> > > I was curious because I am not getting any sound through my machine
> > > (configured as a headset - 0x200404 device class).
> > > Also there are no service classes defined when I do hciconfig
> > -a (as shown
> > > below).
> >
> > this is now the class of device. You are mixing things up here.
>
> I understand but should there not be some services defined also - I dont
> remember any of the example hciconfig -a outputs on the net without service
> classes
it is not a requirement. However maybe the decoding code in hciconfig is
incomplete.
> > > Although a headset icon appears on my 6310i and I get no sound
> > at the actual
> > > mobile phone (because the headset is connected), I still cannot
> > hear or say
> > > anything that can be heard from my computer.
> > > Therefore, I am trying to study the hcidump output but its
> > almost impossible
> > > to interpret.
> >
> > No it is not. Use "hcidump -X -V" as stated almost everywhere in the
> > mailing list archives.
>
> Apologies Marcel - I should have told you before: I am using -X -V and as
> the list archives suggest, I am in the process of reviewing the BT
> specifications to help interpret the output. At first sight it is very
> confusing.
>
> Would you not expect to see '> SCO' lines in the hcidump output given that I
> am (trying to) use SCO for voice transfer? Like you said in one of the
> archives, hcidump shows payload of the SCO packets over hci?
The Headset and Headfree profiles specify when the SCO channel has to be
opened. Maybe your connection is not in that state. Post the output of
hcidump, so we can see what's going on.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Marcel,
> > > > Can someone tell me how to set the bluetooth voice settings
> > > when using sco
> > > > and what to set it to?
> > > > My hcidump shows voice setting as (0x03|0x0025) - what does
> > > this mean? Also,
> > > > the hcidump shows that a connection is created for DM* and DH*
> > > packet types:
> > > > for sco, should this not be HV* packet types?
> > >
> > > you don't need to worry about it. The packet types and the
> voice setting
> > > are not related (from the HCI viewpoint). If you wanna know details
> > > about it, look at the HCI part of the Bluetooth
> specification. The value
> > > is a bitmask and it is explained in detail there.
> > >
> >
> > I was curious because I am not getting any sound through my machine
> > (configured as a headset - 0x200404 device class).
> > Also there are no service classes defined when I do hciconfig
> -a (as shown
> > below).
>
> this is now the class of device. You are mixing things up here.
I understand but should there not be some services defined also - I dont
remember any of the example hciconfig -a outputs on the net without service
classes
> > Although a headset icon appears on my 6310i and I get no sound
> at the actual
> > mobile phone (because the headset is connected), I still cannot
> hear or say
> > anything that can be heard from my computer.
> > Therefore, I am trying to study the hcidump output but its
> almost impossible
> > to interpret.
>
> No it is not. Use "hcidump -X -V" as stated almost everywhere in the
> mailing list archives.
Apologies Marcel - I should have told you before: I am using -X -V and as
the list archives suggest, I am in the process of reviewing the BT
specifications to help interpret the output. At first sight it is very
confusing.
Would you not expect to see '> SCO' lines in the hcidump output given that I
am (trying to) use SCO for voice transfer? Like you said in one of the
archives, hcidump shows payload of the SCO packets over hci?
Regards
Khaled
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Khaled,
> > > Can someone tell me how to set the bluetooth voice settings
> > when using sco
> > > and what to set it to?
> > > My hcidump shows voice setting as (0x03|0x0025) - what does
> > this mean? Also,
> > > the hcidump shows that a connection is created for DM* and DH*
> > packet types:
> > > for sco, should this not be HV* packet types?
> >
> > you don't need to worry about it. The packet types and the voice setting
> > are not related (from the HCI viewpoint). If you wanna know details
> > about it, look at the HCI part of the Bluetooth specification. The value
> > is a bitmask and it is explained in detail there.
> >
>
> I was curious because I am not getting any sound through my machine
> (configured as a headset - 0x200404 device class).
> Also there are no service classes defined when I do hciconfig -a (as shown
> below).
this is now the class of device. You are mixing things up here.
> Although a headset icon appears on my 6310i and I get no sound at the actual
> mobile phone (because the headset is connected), I still cannot hear or say
> anything that can be heard from my computer.
> Therefore, I am trying to study the hcidump output but its almost impossible
> to interpret.
No it is not. Use "hcidump -X -V" as stated almost everywhere in the
mailing list archives.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Marcel
> > Can someone tell me how to set the bluetooth voice settings
> when using sco
> > and what to set it to?
> > My hcidump shows voice setting as (0x03|0x0025) - what does
> this mean? Also,
> > the hcidump shows that a connection is created for DM* and DH*
> packet types:
> > for sco, should this not be HV* packet types?
>
> you don't need to worry about it. The packet types and the voice setting
> are not related (from the HCI viewpoint). If you wanna know details
> about it, look at the HCI part of the Bluetooth specification. The value
> is a bitmask and it is explained in detail there.
>
I was curious because I am not getting any sound through my machine
(configured as a headset - 0x200404 device class).
Also there are no service classes defined when I do hciconfig -a (as shown
below).
Although a headset icon appears on my 6310i and I get no sound at the actual
mobile phone (because the headset is connected), I still cannot hear or say
anything that can be heard from my computer.
Therefore, I am trying to study the hcidump output but its almost impossible
to interpret.
I have hcidump output, which I can send should you wish to view it.
hciconfig -a:
hci0: Type: USB
BD Address: 00:09:DD:10:29:78 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:45230 acl:1413 sco:0 events:2002 errors:0
TX bytes:27314 acl:1440 sco:0 commands:243 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0)'
Class: 0x200404
Service Classes:
Device Class: Audio/Video, Device conforms to the Headset profile
HCI Ver: 1.1 (0x1) HCI Rev: 0x175 LMP Ver: 1.1 (0x1) LMP Subver:
0x175
Manufacturer: Cambridge Silicon Radio (10)
hci0: Type: USB
BD Address: 00:09:DD:10:29:78 ACL MTU: 192:8 SCO MTU: 64:8
HCI 14.7
Chip version: BlueCore02-External (ES2)
Max key size: 56 bit
SCO mapping: HCI
sdptool browse local:
Browsing FF:FF:FF:00:00:00 ...
Service Name: Voice Gateway
Service RecHandle: 0x10000
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 5
Profile Descriptor List:
"Handfree Audio Gateway" (0x111f)
Version: 0x0100
Service Name: Voice Gateway
Service RecHandle: 0x10001
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 6
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0100
sdptool search --bdaddr 00:0E:6D:34:BD:B1 0x111f:
Class 0x111F
Searching for 0x111f on 00:0E:6D:34:BD:B1 ...
Service Name: Voice Gateway
Service RecHandle: 0x10005
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 13
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0100
I have set the channel to be used as channel 13 given the above search
result; this connects the phone to the headset.
Kind Regards.
Khaled
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Khaled,
> Can someone tell me how to set the bluetooth voice settings when using sco
> and what to set it to?
> My hcidump shows voice setting as (0x03|0x0025) - what does this mean? Also,
> the hcidump shows that a connection is created for DM* and DH* packet types:
> for sco, should this not be HV* packet types?
you don't need to worry about it. The packet types and the voice setting
are not related (from the HCI viewpoint). If you wanna know details
about it, look at the HCI part of the Bluetooth specification. The value
is a bitmask and it is explained in detail there.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users