All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goetz Issel <g.issel@fh-wolfenbuettel.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] blueZ and SAP
Date: Tue, 20 Jun 2006 23:50:08 +0200	[thread overview]
Message-ID: <44986D90.2090505@fh-wolfenbuettel.de> (raw)
In-Reply-To: <mailman.1467.1150830573.9417.bluez-devel@lists.sourceforge.net>

Hi Mayank,

>
>First of all, please do not reply on individual ids.


sorry for PM, will post here in list again.

 I do get a message back from the mobile phone, of course after first 
sending a message to it..
The response of a 'connect-req' from the phone is:
header:            1100, the response message header is correct, since 
it has the correct MsgID that corresponds to 'connect-resp'

parameter #1:  10010000 ,  meaning that it is the parameterID 
'ConnectionStatus', with parameter value length 1 and the value is 0 (= 
OK, server can fulfill the requirements)

This message is received  from a Nokia 6810 and the MaxMsgSize requested 
in the 'connection-req' was 0x0118. It looks promising so far. I will 
try to get a few more things done now.
When I request an initial MaxMsgSize of 0xff ff the mobile phone 
responds with
header: 1200 , so now 2 parameters in the 'connect-resp' message coming up
parameter #1: 10012000 , connectionStatus  now gives 'Error, Server does 
not support maximum message size'
parameter #2: 00028000 , the server now suggests MaxMsgSize to be 0x800

And... when I request a small MaxMsgSize (ie 0x0001) the SIM server 
returns the expected 'Error, maximum message size by Client is too small' 

In case you decide to work on this subject as well I am interested in a 
bit of team work.

> > first of all I am happy to hear that there is somebody out there working
> > on this too. I thought I was on my own since I never got any helpful
> > response on the list so far.
> >
> > I have been checking the returned values in 2 ways.
> >
> > First I tried to use "read()" on the socket on which I did the "write()"
> > before. I got no response at all. By the way, I am using  Nokia 6810 and
> > a Siemens S65 for testing.
>   
>Hang on, if you do a read() before write(), won't the read block your
>thread? and your control will never reach the write()?
>Or are you using different threads for the read and write?

> > problem. I need to implement the whole sap profile. Panic!
> >
> > If you have any decend code I can use... please help. If you want I can
> > send you the code I have so far.
>   
>No, I did not have any code actually, I just made the RFCOMM connection, and
>I was sending the connect_req etc on this rfcomm device (/dev/rfcomm0). So I
>wrote the connect_req in hex form in a file and then simply did cat file >
>/dev/rfcomm0

>Regards,
>Mayank

Greetings,
Goetz



_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

       reply	other threads:[~2006-06-20 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1467.1150830573.9417.bluez-devel@lists.sourceforge.net>
2006-06-20 21:50 ` Goetz Issel [this message]
2006-06-21  5:48   ` [Bluez-devel] blueZ and SAP Mayank Batra
2006-06-23  4:52     ` Mayank Batra
2006-06-23 20:56 Götz Issel
2006-06-26  3:46 ` Mayank Batra
     [not found] <16b5b416d372.16d37216b5b4@fh-wolfenbuettel.de>
2006-06-20  4:09 ` Mayank Batra

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=44986D90.2090505@fh-wolfenbuettel.de \
    --to=g.issel@fh-wolfenbuettel.de \
    --cc=bluez-devel@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.