PM325 by LG cell phone - pairing failed

Bluez-users Carl K 2 participants 7 messages Jun 9, 2006 Bluetooth drivers

Share & tools

Carl K

author

2006-06-09 06:32 UTC #0 lore raw

I am trying to pair my phone to my ubuntu/dapper laptop .

carl@asus17:~$ lsusb

Bus 003 Device 002: ID 044e:3001 Alps Electric Co., Ltd UGTZ4 Bluetooth

carl@asus17:~$ cat /etc/bluetooth/pin
1234
carl@asus17:~$ sudo /etc/init.d/bluez-utils start

On the phone: menu, bluetooth, add new, Searching and Pairing, it shows asus17-0, I select that, phone prompts "Enter PIN code", I enter 1234<Next> and within a second get "pairing failed"

guessing because of this:

Jun  9 00:37:42 localhost gconfd (root-7749): starting (version 2.14.0), 
pid 7749 user 'root'
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only 
configuration source at position 0
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readwrite:/root/.gconf" to a writable configuration source at 
position 1
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only 
configuration source at position 2
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readonly:/var/lib/gconf/debian.defaults" to a read-only 
configuration source at position 3
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readonly:/var/lib/gconf/defaults" to a read-only configuration 
source at position 4
Jun  9 00:38:42 localhost gconfd (root-7749): GConf server is not in 
use, shutting down.
Jun  9 00:38:42 localhost gconfd (root-7749): Exiting

Jun  9 01:03:08 localhost hcid[8572]: Bluetooth HCI daemon
Jun  9 01:03:08 localhost hcid[8572]: Can't get system message bus name: 
Connection ":1.15" is not allowed to own the service "org.bluez" due to 
security policies in the configuration file
Jun  9 01:03:08 localhost hcid[8572]: Starting security manager 0
Jun  9 01:03:08 localhost sdpd[8577]: Bluetooth SDP daemon

I probably need to file a bug report with ubuntu, but I would like to get some feedback from the experts so that the report has some useful info.

Or do I need to be doing something else?

Carl K

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Marcel Holtmann

maintainer

2006-06-09 07:08 UTC #1 lore raw

Hi Carl,

Quoted 43 lines

I am trying to pair my phone to my ubuntu/dapper laptop .

carl@asus17:~$ lsusb

Bus 003 Device 002: ID 044e:3001 Alps Electric Co., Ltd UGTZ4 Bluetooth

carl@asus17:~$ cat /etc/bluetooth/pin
1234
carl@asus17:~$ sudo /etc/init.d/bluez-utils start

On the phone: menu, bluetooth, add new, Searching and Pairing, it shows asus17-0, I select that, phone prompts "Enter PIN code", I enter 1234<Next> and within a second get "pairing failed"

guessing because of this:

Jun  9 00:37:42 localhost gconfd (root-7749): starting (version 2.14.0), 
pid 7749 user 'root'
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only 
configuration source at position 0
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readwrite:/root/.gconf" to a writable configuration source at 
position 1
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only 
configuration source at position 2
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readonly:/var/lib/gconf/debian.defaults" to a read-only 
configuration source at position 3
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readonly:/var/lib/gconf/defaults" to a read-only configuration 
source at position 4
Jun  9 00:38:42 localhost gconfd (root-7749): GConf server is not in 
use, shutting down.
Jun  9 00:38:42 localhost gconfd (root-7749): Exiting

Jun  9 01:03:08 localhost hcid[8572]: Bluetooth HCI daemon
Jun  9 01:03:08 localhost hcid[8572]: Can't get system message bus name: 
Connection ":1.15" is not allowed to own the service "org.bluez" due to 
security policies in the configuration file
Jun  9 01:03:08 localhost hcid[8572]: Starting security manager 0
Jun  9 01:03:08 localhost sdpd[8577]: Bluetooth SDP daemon

Quoted 2 lines

I probably need to file a bug report with ubuntu, but I would like to get some feedback from the experts so that the report has some useful info.

for the "security policies" error you should really file a bug report with Ubuntu. For the rest show us the output of "hcidump -X -V" while you are trying to pair. I suspect that you PIN help isn't called properly.

Regards

Marcel

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Carl K

author

2006-06-09 08:02 UTC #2 lore raw

Quoted 46 lines · Marcel Holtmann

Hi Carl,

Quoted 43 lines

I am trying to pair my phone to my ubuntu/dapper laptop .

carl@asus17:~$ lsusb

Bus 003 Device 002: ID 044e:3001 Alps Electric Co., Ltd UGTZ4 Bluetooth

carl@asus17:~$ cat /etc/bluetooth/pin
1234
carl@asus17:~$ sudo /etc/init.d/bluez-utils start

On the phone: menu, bluetooth, add new, Searching and Pairing, it shows asus17-0, I select that, phone prompts "Enter PIN code", I enter 1234<Next> and within a second get "pairing failed"

guessing because of this:

Jun  9 00:37:42 localhost gconfd (root-7749): starting (version 2.14.0), 
pid 7749 user 'root'
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only 
configuration source at position 0
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readwrite:/root/.gconf" to a writable configuration source at 
position 1
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only 
configuration source at position 2
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readonly:/var/lib/gconf/debian.defaults" to a read-only 
configuration source at position 3
Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
"xml:readonly:/var/lib/gconf/defaults" to a read-only configuration 
source at position 4
Jun  9 00:38:42 localhost gconfd (root-7749): GConf server is not in 
use, shutting down.
Jun  9 00:38:42 localhost gconfd (root-7749): Exiting

Jun  9 01:03:08 localhost hcid[8572]: Bluetooth HCI daemon
Jun  9 01:03:08 localhost hcid[8572]: Can't get system message bus name: 
Connection ":1.15" is not allowed to own the service "org.bluez" due to 
security policies in the configuration file
Jun  9 01:03:08 localhost hcid[8572]: Starting security manager 0
Jun  9 01:03:08 localhost sdpd[8577]: Bluetooth SDP daemon

Quoted 6 lines

Quoted 3 lines
I probably need to file a bug report with ubuntu, but I would like to get some feedback from the experts so that the report has some useful info.
for the "security policies" error you should really file a bug report with Ubuntu.

will do.

Quoted 4 lines

For the rest show us the output of "hcidump -X -V" while you are trying to pair. I suspect that you PIN help isn't called properly.

HCI sniffer - Bluetooth packet analyzer ver 1.28
device: hci0 snap_len: 1028 filter: 0xffffffff

Quoted 1 line

HCI Event: Connect Request (0x04) plen 10

    bdaddr 08:00:37:03:EF:36 class 0x400204 type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 08:00:37:03:EF:36 role 0x01
    Role: Slave

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1

Quoted 1 line

HCI Event: Connect Complete (0x03) plen 11

    status 0x00 handle 42 bdaddr 08:00:37:03:EF:36 type ACL encrypt 0x00

< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
handle 42 policy 0x0f
Link policy: RSWITCH HOLD SNIFF PARK

Quoted 1 line

HCI Event: Page Scan Repetition Mode Change (0x20) plen 7

    bdaddr 08:00:37:03:EF:36 mode 1

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 6

    Write Link Policy Settings (0x02|0x000d) ncmd 1
    status 0x00 handle 42

< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
handle 42 ptype 0xcc18
Packet type: DM1 DM3 DM5 DH1 DH3 DH5

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

    Change Connection Packet Type (0x01|0x000f) status 0x00 ncmd 1

Quoted 1 line

HCI Event: Connection Packet Type Changed (0x1d) plen 5

status 0x00 handle 42 ptype 0xcc18
Packet type: DM1 DM3 DM5 DH1 DH3 DH5

Quoted 1 line

HCI Event: Max Slots Change (0x1b) plen 3

handle 42 slots 5

Quoted 1 line

HCI Event: PIN Code Request (0x16) plen 6

    bdaddr 08:00:37:03:EF:36
< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
    bdaddr 08:00:37:03:EF:36 len 4 pin '1234'

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 10

    PIN Code Request Reply (0x01|0x000d) ncmd 1
    status 0x00 bdaddr 08:00:37:03:EF:36

Quoted 1 line

HCI Event: Link Key Notification (0x18) plen 23

    bdaddr 08:00:37:03:EF:36 key 7ECC0F84F68E851175F204130B4E561A type 0

Quoted 1 line

HCI Event: Disconn Complete (0x05) plen 4

status 0x00 handle 42 reason 0x13
Reason: Remote User Terminated Connection

Quoted 1 line

HCI Event: Connect Request (0x04) plen 10

    bdaddr 08:00:37:03:EF:36 class 0x400204 type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 08:00:37:03:EF:36 role 0x01
    Role: Slave

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1

Quoted 1 line

HCI Event: Connect Complete (0x03) plen 11

    status 0x00 handle 43 bdaddr 08:00:37:03:EF:36 type ACL encrypt 0x00

< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
handle 43 policy 0x0f
Link policy: RSWITCH HOLD SNIFF PARK

Quoted 1 line

HCI Event: Page Scan Repetition Mode Change (0x20) plen 7

    bdaddr 08:00:37:03:EF:36 mode 1

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 6

    Write Link Policy Settings (0x02|0x000d) ncmd 1
    status 0x00 handle 43

< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
handle 43 ptype 0xcc18
Packet type: DM1 DM3 DM5 DH1 DH3 DH5

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

    Change Connection Packet Type (0x01|0x000f) status 0x00 ncmd 1

Quoted 1 line

HCI Event: Connection Packet Type Changed (0x1d) plen 5

status 0x00 handle 43 ptype 0xcc18
Packet type: DM1 DM3 DM5 DH1 DH3 DH5

Quoted 1 line

HCI Event: Max Slots Change (0x1b) plen 3

handle 43 slots 5

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 12

    L2CAP(s): Connect req: psm 1 scid 0x0044
< ACL data: handle 43 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0044 result 0 status 0
      Connection successful

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 43 packets 1

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 20

    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 8
      MTU 256 FlushTO 65535
< ACL data: handle 43 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0044 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0044 flags 0x00 clen 0

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 43 packets 1

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 43 packets 1

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 14

    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 22

    L2CAP(d): cid 0x0040 len 18 [psm 1]
        SDP SSA Req: tid 0x0 len 0xd
          pat uuid-16 0x1108 (Headset)
          max 240
          aid(s) 0x0001 (SrvClassIDList)
          cont 00
< ACL data: handle 43 flags 0x02 dlen 14
    L2CAP(d): cid 0x0044 len 10 [psm 1]
        SDP SSA Rsp: tid 0x0 len 0x5
          count 2
          cont 00

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 43 packets 1

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 12

    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0044
< ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0044

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 43 packets 1

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 12

    L2CAP(s): Connect req: psm 1 scid 0x0045
< ACL data: handle 43 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0045 result 0 status 0
      Connection successful

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 43 packets 1

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 20

    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 8
      MTU 256 FlushTO 65535
< ACL data: handle 43 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0045 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0045 flags 0x00 clen 0

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 43 packets 1

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 43 packets 1

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 14

    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 22

    L2CAP(d): cid 0x0040 len 18 [psm 1]
        SDP SSA Req: tid 0x0 len 0xd
          pat uuid-16 0x111e (Handsfree)
          max 240
          aid(s) 0x0001 (SrvClassIDList)
          cont 00
< ACL data: handle 43 flags 0x02 dlen 14
    L2CAP(d): cid 0x0045 len 10 [psm 1]
        SDP SSA Rsp: tid 0x0 len 0x5
          count 2
          cont 00

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 43 packets 1

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 12

    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0045
< ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0045

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

handle 43 packets 1

Quoted 1 line

HCI Event: Disconn Complete (0x05) plen 4

status 0x00 handle 43 reason 0x13
Reason: Remote User Terminated Connection

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Marcel Holtmann

maintainer

2006-06-09 08:07 UTC #3 lore raw

Hi Carl,

Quoted 8 lines

Quoted 4 lines
For the rest show us the output of "hcidump -X -V" while you are trying to pair. I suspect that you PIN help isn't called properly.
HCI sniffer - Bluetooth packet analyzer ver 1.28
device: hci0 snap_len: 1028 filter: 0xffffffff
Quoted 1 line
HCI Event: Connect Request (0x04) plen 10
    bdaddr 08:00:37:03:EF:36 class 0x400204 type ACL

So the phone established the connection to you.

Quoted 26 lines

< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 08:00:37:03:EF:36 role 0x01
    Role: Slave
Quoted 1 line
HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
Quoted 1 line
HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 42 bdaddr 08:00:37:03:EF:36 type ACL encrypt 0x00
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
handle 42 policy 0x0f
Link policy: RSWITCH HOLD SNIFF PARK
Quoted 1 line
HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
    bdaddr 08:00:37:03:EF:36 mode 1
Quoted 1 line
HCI Event: Command Complete (0x0e) plen 6
    Write Link Policy Settings (0x02|0x000d) ncmd 1
    status 0x00 handle 42
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
handle 42 ptype 0xcc18
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
Quoted 1 line
HCI Event: Command Status (0x0f) plen 4
    Change Connection Packet Type (0x01|0x000f) status 0x00 ncmd 1
Quoted 1 line
HCI Event: Connection Packet Type Changed (0x1d) plen 5
status 0x00 handle 42 ptype 0xcc18
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
Quoted 1 line
HCI Event: Max Slots Change (0x1b) plen 3
handle 42 slots 5
Quoted 1 line
HCI Event: PIN Code Request (0x16) plen 6

Quoted 8 lines

    bdaddr 08:00:37:03:EF:36
< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
    bdaddr 08:00:37:03:EF:36 len 4 pin '1234'

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 10

    PIN Code Request Reply (0x01|0x000d) ncmd 1
    status 0x00 bdaddr 08:00:37:03:EF:36

Quoted 1 line

HCI Event: Link Key Notification (0x18) plen 23

    bdaddr 08:00:37:03:EF:36 key 7ECC0F84F68E851175F204130B4E561A type 0

the pairing itself works. You get a valid link key.

Quoted 3 lines

Quoted 1 line
HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 42 reason 0x13
Reason: Remote User Terminated Connection

Then it disconnects. That is strange.

Quoted 50 lines

Quoted 1 line
HCI Event: Connect Request (0x04) plen 10
    bdaddr 08:00:37:03:EF:36 class 0x400204 type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 08:00:37:03:EF:36 role 0x01
    Role: Slave
Quoted 1 line
HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
Quoted 1 line
HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 43 bdaddr 08:00:37:03:EF:36 type ACL encrypt 0x00
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
handle 43 policy 0x0f
Link policy: RSWITCH HOLD SNIFF PARK
Quoted 1 line
HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
    bdaddr 08:00:37:03:EF:36 mode 1
Quoted 1 line
HCI Event: Command Complete (0x0e) plen 6
    Write Link Policy Settings (0x02|0x000d) ncmd 1
    status 0x00 handle 43
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
handle 43 ptype 0xcc18
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
Quoted 1 line
HCI Event: Command Status (0x0f) plen 4
    Change Connection Packet Type (0x01|0x000f) status 0x00 ncmd 1
Quoted 1 line
HCI Event: Connection Packet Type Changed (0x1d) plen 5
status 0x00 handle 43 ptype 0xcc18
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
Quoted 1 line
HCI Event: Max Slots Change (0x1b) plen 3
handle 43 slots 5
Quoted 1 line
ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0044
< ACL data: handle 43 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0044 result 0 status 0
      Connection successful
Quoted 1 line
HCI Event: Number of Completed Packets (0x13) plen 5
handle 43 packets 1
Quoted 1 line
ACL data: handle 43 flags 0x02 dlen 20
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 8
      MTU 256 FlushTO 65535
< ACL data: handle 43 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0044 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0044 flags 0x00 clen 0
Quoted 1 line
HCI Event: Number of Completed Packets (0x13) plen 5
handle 43 packets 1
Quoted 1 line
HCI Event: Number of Completed Packets (0x13) plen 5
handle 43 packets 1
Quoted 1 line
ACL data: handle 43 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
Quoted 1 line
ACL data: handle 43 flags 0x02 dlen 22

Quoted 11 lines

    L2CAP(d): cid 0x0040 len 18 [psm 1]
        SDP SSA Req: tid 0x0 len 0xd
          pat uuid-16 0x1108 (Headset)
          max 240
          aid(s) 0x0001 (SrvClassIDList)
          cont 00
< ACL data: handle 43 flags 0x02 dlen 14
    L2CAP(d): cid 0x0044 len 10 [psm 1]
        SDP SSA Rsp: tid 0x0 len 0x5
          count 2
          cont 00

It looks for you being a headset and this will obviously fail.

Quoted 31 lines

Quoted 1 line
HCI Event: Number of Completed Packets (0x13) plen 5
handle 43 packets 1
Quoted 1 line
ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0044
< ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0044
Quoted 1 line
HCI Event: Number of Completed Packets (0x13) plen 5
handle 43 packets 1
Quoted 1 line
ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0045
< ACL data: handle 43 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0045 result 0 status 0
      Connection successful
Quoted 1 line
HCI Event: Number of Completed Packets (0x13) plen 5
handle 43 packets 1
Quoted 1 line
ACL data: handle 43 flags 0x02 dlen 20
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 8
      MTU 256 FlushTO 65535
< ACL data: handle 43 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0045 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0045 flags 0x00 clen 0
Quoted 1 line
HCI Event: Number of Completed Packets (0x13) plen 5
handle 43 packets 1
Quoted 1 line
HCI Event: Number of Completed Packets (0x13) plen 5
handle 43 packets 1
Quoted 1 line
ACL data: handle 43 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
Quoted 1 line
ACL data: handle 43 flags 0x02 dlen 22

Quoted 11 lines

    L2CAP(d): cid 0x0040 len 18 [psm 1]
        SDP SSA Req: tid 0x0 len 0xd
          pat uuid-16 0x111e (Handsfree)
          max 240
          aid(s) 0x0001 (SrvClassIDList)
          cont 00
< ACL data: handle 43 flags 0x02 dlen 14
    L2CAP(d): cid 0x0045 len 10 [psm 1]
        SDP SSA Rsp: tid 0x0 len 0x5
          count 2
          cont 00

Second try with handsfree and this will fail, too.

Quoted 11 lines

Quoted 1 line
HCI Event: Number of Completed Packets (0x13) plen 5
handle 43 packets 1
Quoted 1 line
ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0045
< ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0045
Quoted 1 line
HCI Event: Number of Completed Packets (0x13) plen 5
handle 43 packets 1
Quoted 1 line
HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 43 reason 0x13
Reason: Remote User Terminated Connection

So since you are not emulating a headset or handsfree unit, this is not the way to go.

Regards

Marcel

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Carl K

author

2006-06-09 08:27 UTC #4 lore raw

Quoted 4 lines · Marcel Holtmann

So since you are not emulating a headset or handsfree unit, this is not the way to go.

arg - I was going to ask if it mattered which direction the pairing was done for a given profile. I guess it does. Now to try the other direction.

Here is my cut/paste bug report about the "security policies" error:

https://launchpad.net/distros/ubuntu/+source/bluez-utils/+bug/49105

Carl K

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Marcel Holtmann

maintainer

2006-06-09 08:40 UTC #5 lore raw

Hi Carl,

Quoted 5 lines

Quoted 2 lines
So since you are not emulating a headset or handsfree unit, this is not the way to go.
arg - I was going to ask if it mattered which direction the pairing was done for a given profile. I guess it does. Now to try the other direction.

for the pairing the direction doesn't matter all. You have a valid link key and that is enough.

For using a service of your phone it does matter. If you wanna connect to DUN for dialup into the Internet then you don't wanna play with the headset support of your phone.

Regards

Marcel

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Carl K

author

2006-06-09 09:38 UTC #6 lore raw

Quoted 10 lines · Marcel Holtmann

Hi Carl,
Quoted 6 lines
Quoted 3 lines
So since you are not emulating a headset or handsfree unit, this is not the way to go.
arg - I was going to ask if it mattered which direction the pairing was done for a given profile. I guess it does. Now to try the other direction.

Quoted 7 lines

for the pairing the direction doesn't matter all. You have a valid link key and that is enough.
For using a service of your phone it does matter. If you wanna connect to DUN for dialup into the Internet then you don't wanna play with the headset support of your phone.

To use DUN don't I have to pair first?

I seem to have done whatever I need to do, because I am not talking to it via minicom:

at&v1
&C: 1; &D: 2; &F: 0; E: 1; L: 1; M: 0; Q: 0; V: 1; X: 4; Z: 0; S0: 0
S10: 14; S11: 95; S3: 13; S4: 10; S5: 8; S6: 2; S7: 45; S8: 2; S9: 6 +FCLASS: 0; +CFG: ""; +FCC: 0,1,0,0,0,0,0,0; +FIS: 0,1,0,0,0,0,0,0 +CDR: 0; +CDS: 0,1,2048,6; +CFC: 0; +CQD: 10; +CRC: 0; +CRM: 2; +TEST: 0 +CTA: 60; +CXT: 0; +DR: 0; +DS: 3,0,2048,6; +EB: 1,0,30; +EFCS: 1 +ER: 0; +ES: 3,0,2; +ESR: 1; +ETBM: 1,1,20; +FAA: 0; +FAP: 0,0,0 +FBO: 0; +FBU: 0; +FCQ: 1,0; +FCR: 0; +FCT: 1E; +FEA: 0; +FFC: 0,0,0,0 +FHS: 0; +FIE: 0; +FIP: 0; +FLI: ""; +FLO: 2; +FLP: 0; +FMS: 0 +FNR: 0,0,0,0; +FNS: ""; +FPA: ""; +FPI: ""; +FPP: 0; +FPR: 8; +FPS: 1 +FPW: ""; +FRQ: 0,0; +FRY: 0; +FSA: ""; +FSP: 0; +ICF: 3,3; +IFC: 2,2 +ILRR: 0; +IPR: 115200; +MA: ; +MR: 0; +MS: ; +MV18R: 0; +MV18S: 0,0,0 +CMUX: C,2

I don't have a modem to call, so I tried calling my cell phone. I think it rebooted the phone?

Carl K

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users