From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] problems establishing connection to Cellular phone
Date: Mon, 14 Mar 2005 13:13:28 +0100 [thread overview]
Message-ID: <1110802408.629.3.camel@pegasus> (raw)
In-Reply-To: <1110802026.9167.11.camel@tux>
Hi Tamer,
> Thank you very much for the quick answer. I appreciate your help very
> much for solving my problem (specially because I am such a newbie).
> About the dbus, I installed it and get the bluez-pin package installed
> successfully.
>
> 1st) I run up the Bluetooth-stick with the command:
> hciconfig auth noscan nosecmgr noencrypt
don't do anything like this. Simply start hcid and using "auth" means
security mode 3. You don't want this.
> and tried to connect to the mobile phone with the result (after entering
> on the phone a PIN):
> Can't create connection: Input/output error
>
> Before creating a connection I run the sniffer command:
> hcidump -X -V
>
> program and received this result during the test:
>
> HCI sniffer - Bluetooth packet analyzer ver 1.18
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Create Connection (0x01|0x0005) plen 13
> bdaddr 00:E0:03:65:64:94 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: Link Key Request (0x17) plen 6
> bdaddr 00:E0:03:65:64:94
> < HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6
> bdaddr 00:E0:03:65:64:94
> > HCI Event: Command Complete (0x0e) plen 10
> Link Key Request Negative Reply (0x01|0x000c) ncmd 1
> status 0x00 bdaddr 00:E0:03:65:64:94
> > HCI Event: PIN Code Request (0x16) plen 6
> bdaddr 00:E0:03:65:64:94
> < HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
> bdaddr 00:E0:03:65:64:94 len 4 pin '1234'
> > HCI Event: Command Complete (0x0e) plen 10
> PIN Code Request Reply (0x01|0x000d) ncmd 1
> status 0x00 bdaddr 00:E0:03:65:64:94
> > HCI Event: Connect Complete (0x03) plen 11
> status 0x05 handle 41 bdaddr 00:E0:03:65:64:94 type ACL encrypt 0x00
> Error: Authentication Failure
The PIN code you supply is "1234". You must enter the same on your
phone.
> 2nd) About the mobilephone itself I can give you informations i
> requested with the tool hcitool info 00:E0:03:65:64:94:
>
> hcitool info 00:E0:03:65:64:94
> Requesting information ...
> BD Address: 00:E0:03:65:64:94
> Device Name: Yo-Tamer
> LMP Version: 1.1 (0x1) LMP Subversion: 0x382
> Manufacturer: Cambridge Silicon Radio (10)
> Features: 0xbf 0xfe 0x0f 0x00 0x00 0x00 0x00 0x00
> <3-slot packets> <5-slot packets> <encryption> <slot
> offset>
> <timing accuracy> <role switch> <sniff mode> <RSSI>
> <channel quality> <SCO link> <HV2 packets> <HV3 packets>
> <u-law log> <A-law log> <CVSD> <paging scheme> <power
> control>
> <transparent SCO>
What kind of phone is this?
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-03-14 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 2:17 [Bluez-users] problems establishing connection to Cellular phone Tamer Higazi
2005-03-14 10:21 ` Marcel Holtmann
2005-03-14 12:07 ` Tamer Higazi
2005-03-14 12:13 ` Marcel Holtmann [this message]
2005-03-14 20:40 ` Tamer Higazi
2005-03-14 20:59 ` Marcel Holtmann
2005-03-25 8:01 ` Tamer Higazi
2005-03-25 11:45 ` Marcel Holtmann
2005-03-16 0:47 ` Fredy P.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1110802408.629.3.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.