2005-07-21 15:54:57

by Victor Shcherbatyuk

[permalink] [raw]
Subject: [Bluez-users] rfcomm connection fails

Hello Marcel,

Have some weird rfcomm connect problem. Have 2 devices from the same
batch, 1 phone; trying to open a rfcomm channel form a device to the
phone. For one device it succeeds for another fails (phone forces
disconnect). hcidump logs are attached.
Looks like the phone (SVP500, Windows Mobile) says DISC after exchanging
MSC's for one of the devices, while for the other it succeeds. I can not
find definitions for b1,b2,b3, len parameters and it looks as it is only
the difference between the devices. Does it look ok or there is
something wrong about it?

Success MSC:
dlci 14 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 0 b3 0 len 5
Failure MSC:
dlci 4 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 15

Kind regards,
Victor.

hciconfig -a:
hci0: Type: UART
BD Address: 00:13:6C:BF:63:58 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING
RX bytes:16220 acl:357 sco:0 events:273 errors:0
TX bytes:9670 acl:133 sco:0 commands:42 errors:0
Features: 0xff 0xff 0x8f 0x78 0x18 0x18 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: HOLD SNIFF PARK
Link mode: MASTER
Name: 'TomTom RIDER'
Class: 0x200408
Service Classes:
Device Class: Audio/Video, Hands-free
HCI Ver: 1.2 (0x2) HCI Rev: 0x639 LMP Ver: 1.2 (0x2) LMP Subver:
0x639
Manufacturer: Cambridge Silicon Radio (10)


This e-mail message contains information which is confidential and may be privileged. It is intended for use by the addressee only. If you are not the intended addressee, we request that you notify the sender immediately and delete or destroy this e-mail message and any attachment(s), without copying, saving, forwarding, disclosing or using its contents in any other way. TomTom N.V., TomTom International BV or any other company belonging to the TomTom group of companies will not be liable for damage relating to the communication by e-mail of data, documents or any other information.


Attachments:
success.txt (6.62 kB)
success.txt
failure.txt (6.06 kB)
failure.txt
Download all attachments