[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SV: [bluetooth-dev] l2cap config cmf question
The stack should work as you have described but it doesn't at the moment :). We will have to add a timer as well to be able to terminate the configuration negotiation if it hasn't succeed in maximum 120 seconds as stated in the specifications. Feel free to send me a patch and I'll include it in the next release.
> -----Ursprungligt meddelande-----
> Från: Peter Fredriksson [mailto:firstname.lastname@example.org]
> Skickat: den 18 september 2001 15:55
> Till: email@example.com
> Ämne: [bluetooth-dev] l2cap config cmf question
> Hi all,
> I have a question about the handling of l2ca_config_cmf.
> I am trying to make a RFCOMM connect to a device that is not
> using the
> OpenBT stack.
> When the stack gets an a l2cap_config_response with
> unacceptable parameters
> from a remote device it just deletes the connection. Is this
> really the way
> it should work? Should it not try again with the received
> parameters if
> they are ok for the stack?
> I dont know if it is mandatory in the BT spec but it seems to
> make the
> stack more interoperable against other bluetooth stacks.
> To unsubscribe from this list: send the line "unsubscribe
> bluetooth-dev" in
> the body of a message to firstname.lastname@example.org
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to email@example.com