Linux bluetooth development
 help / color / mirror / Atom feed
From: "Szilágyi Szilveszter" <sszilveszter@citromail.hu>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] problems syncing with bluetooth on multisync: evolution/blueotooth plugin
Date: Tue, 17 May 2005 09:54:18 +0200	[thread overview]
Message-ID: <4289A32A.1040907@citromail.hu> (raw)
In-Reply-To: <1116313073.10074.8.camel@linux.site>

maybe your bluez-pin path is not correct in /etc/bluetooth/hcid.conf

@localhost:~$ whereis bluepin
bluepin: /usr/bin/bluepin

/etc/bluetooth/hcid.conf
    # PIN helper
 >>>    pin_helper /usr/bin/bluepin;

Tamer Higazi írta:

>Hi! 
>Everytime I want to synchronize with multisync: bluetooth/evolution2
>plugins, the cell phone ask me for a password, i type one and receive a
>error on the screen: "connection failed". 
>
>I use as operating system SuSE Linux 9.3 Pro
>
>Is it perhaps the configuration?! 
>
>
>For any help
>
>Thank you 
>
>
>SuSE Linux 9.3 preconfigures the configuration like this for rfcomm: 
>
>-f /etc/bluetooth/rfcomm.conf bind all
>
>and inside the rfcomm.conf 
>
>#
># RFCOMM configuration file.
>#
># $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $
>#
>
>rfcomm0 {
>        # Automatically bind the device at startup
>        bind no;
>
>        # Bluetooth address of the device
>        device 11:22:33:44:55:66;
>
>        # RFCOMM channel for the connection
>        channel 1;
>
>        # Description of the connection
>        comment "Example Bluetooth device";
>}
>
>the result by quering the phone: 
>
>Browsing 00:E0:03:65:64:94 ...
>Service Name: Hands-Free Audio Gateway
>Service RecHandle: 0x10000
>Service Class ID List:
>  "Handfree Audio Gateway" (0x111f)
>  "Generic Audio" (0x1203)
>Protocol Descriptor List:
>  "L2CAP" (0x0100)
>  "RFCOMM" (0x0003)
>    Channel: 1
>Language Base Attr List:
>  code_ISO639: 0x454e
>  encoding:    0x6a
>  base_offset: 0x100
>Profile Descriptor List:
>  "Handfree Audio Gateway" (0x111f)
>    Version: 0x0101
>
>Service Name: OBEX File Transfer
>Service RecHandle: 0x10001
>Service Class ID List:
>  "OBEX File Transfer" (0x1106)
>Protocol Descriptor List:
>  "L2CAP" (0x0100)
>  "RFCOMM" (0x0003)
>    Channel: 10
>  "OBEX" (0x0008)
>Language Base Attr List:
>  code_ISO639: 0x454e
>  encoding:    0x6a
>  base_offset: 0x100
>Profile Descriptor List:
>  "OBEX File Transfer" (0x1106)
>    Version: 0x0100
>
>Service Name: SyncMLClient
>Service RecHandle: 0x10002
>Service Class ID List:
>  "Error: This is UUID-128" (0x00000002-0000-1000-8000-0002ee000002)
>Protocol Descriptor List:
>  "L2CAP" (0x0100)
>  "RFCOMM" (0x0003)
>    Channel: 11
>  "OBEX" (0x0008)
>Language Base Attr List:
>  code_ISO639: 0x454e
>  encoding:    0x6a
>  base_offset: 0x100
>Profile Descriptor List:
>  "Error: This is UUID-128" (0x00000002-0000-1000-8000-0002ee000002)
>    Version: 0x0100
>
>Service Name: Nokia OBEX PC Suite Services
>Service RecHandle: 0x10003
>Service Class ID List:
>  "Error: This is UUID-128" (0x00005005-0000-1000-8000-0002ee000001)
>Protocol Descriptor List:
>  "L2CAP" (0x0100)
>  "RFCOMM" (0x0003)
>    Channel: 12
>  "OBEX" (0x0008)
>Language Base Attr List:
>  code_ISO639: 0x454e
>  encoding:    0x6a
>  base_offset: 0x100
>Profile Descriptor List:
>  "Error: This is UUID-128" (0x00005005-0000-1000-8000-0002ee000001)
>    Version: 0x0100
>
>Service Name: OBEX Object Push
>Service RecHandle: 0x10004
>Service Class ID List:
>  "OBEX Object Push" (0x1105)
>Protocol Descriptor List:
>  "L2CAP" (0x0100)
>  "RFCOMM" (0x0003)
>    Channel: 9
>  "OBEX" (0x0008)
>Language Base Attr List:
>  code_ISO639: 0x454e
>  encoding:    0x6a
>  base_offset: 0x100
>Profile Descriptor List:
>  "OBEX Object Push" (0x1105)
>    Version: 0x0100
>
>Service Name: Dial-Up Networking
>Service RecHandle: 0x10005
>Service Class ID List:
>  "Dialup Networking" (0x1103)
>Protocol Descriptor List:
>  "L2CAP" (0x0100)
>  "RFCOMM" (0x0003)
>    Channel: 2
>Language Base Attr List:
>  code_ISO639: 0x454e
>  encoding:    0x6a
>  base_offset: 0x100
>Profile Descriptor List:
>  "Dialup Networking" (0x1103)
>    Version: 0x0100
>
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by Oracle Space Sweepstakes
>Want to be the first software developer in space?
>Enter now for the Oracle Space Sweepstakes!
>http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
>_______________________________________________
>Bluez-users mailing list
>Bluez-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-users
>  
>


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-05-17  7:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17  6:57 [Bluez-users] problems syncing with bluetooth on multisync: evolution/blueotooth plugin Tamer Higazi
2005-05-17  7:54 ` Szilágyi Szilveszter [this message]
2005-05-17 11:06   ` Tamer Higazi
2005-05-17 11:29     ` Marcel Holtmann
2005-05-17 12:45       ` Tamer Higazi
2005-05-17 12:55         ` Marcel Holtmann
2005-05-17 19:44           ` Tamer Higazi
2005-05-17 21:52             ` Marcel Holtmann
2005-05-18  8:03               ` Tamer Higazi
2005-05-18  9:06                 ` Marcel Holtmann
2005-05-18 10:49                   ` Tamer Higazi
2005-05-18 11:07                     ` Marcel Holtmann
2005-05-18 12:06                       ` Tamer Higazi
2005-05-18 12:14                         ` Marcel Holtmann
2005-05-17 13:38         ` Szilágyi Szilveszter
2005-05-17 11:34     ` Szilágyi Szilveszter

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=4289A32A.1040907@citromail.hu \
    --to=sszilveszter@citromail.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox