public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@iki.fi>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Re: rfcomm and a freezing SE t610
Date: Fri, 09 Jul 2004 00:11:07 +0300	[thread overview]
Message-ID: <20040708211107.GE2581@nalle> (raw)
In-Reply-To: <20040708205303.GD2581@nalle>

On Thu, Jul 08, 2004 at 11:53:03PM +0300, Mikko wrote:
> Is the phone only one to blame? Is there a way to send some more hangup
> messages to the phone and hope that it catches them and stops the GPRS
> and rfcomm connections? 

*doink*, as usual I found a way immediately after sending the question
out: add more PPP hangup characters.

Now, my hangup chat script seems to have enough (more than just one pair
of) \K's and +++ATH's:
exec /usr/sbin/chat -V -s -S    \
ABORT           "BUSY"          \
ABORT           "ERROR"         \
ABORT           "NO DIALTONE"   \
""              "\K"            \
""              "\K"            \
""              "\K"            \
""              "+++ATH"        \
""              "+++ATH"        \
""              "+++ATH"        

Now the t610 seems to work as it should.

-Mikko


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2004-07-08 21:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-08 20:53 [Bluez-users] rfcomm and a freezing SE t610 Mikko Rapeli
2004-07-08 21:11 ` Mikko Rapeli [this message]

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=20040708211107.GE2581@nalle \
    --to=mikko.rapeli@iki.fi \
    --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