From: Neil Jerram <neil@ossau.homelinux.net>
To: ofono@ofono.org
Subject: Re: Handling AT command with no response
Date: Fri, 16 Mar 2012 21:16:25 +0000 [thread overview]
Message-ID: <87vcm4b61i.fsf@neil-laptop.ossau.uklinux.net> (raw)
In-Reply-To: <87zkbgb66n.fsf@neil-laptop.ossau.uklinux.net>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
Neil Jerram <neil@ossau.homelinux.net> writes:
> Hi there,
>
> Is there a way in oFono of sending an AT command and not waiting for any
> response?
>
> Specifically, AT+VTS doesn't give any response according to 27.007, and
> this appears to be true in practice for the Option HSO modem (GTM601).
>
> Thanks,
> Neil
Here's the relevant log:
Mar 16 19:55:51 gta04 daemon.info ofonod[1102]: App: < \r\n+CLCC: 1,0,0,0,0,"02083627267",129\r\n\r\nOK\r\n
Mar 16 19:55:52 gta04 daemon.info ofonod[1102]: App: > AT+CLCC\r
Mar 16 19:55:52 gta04 daemon.info ofonod[1102]: App: < \r\n+CLCC: 1,0,0,0,0,"02083627267",129\r\n\r\nOK\r\n
Mar 16 19:55:52 gta04 daemon.info ofonod[1102]: App: > AT+VTS=2\r
Mar 16 19:56:00 gta04 daemon.debug connmand[1098]: src/rtnl.c:rtnl_message() buf 0xbecd99dc len 128
Mar 16 19:56:00 gta04 daemon.debug connmand[1098]: src/rtnl.c:rtnl_message() NEWROUTE len 128 type 24 flags 0x0000 seq 0
Mar 16 19:56:24 gta04 daemon.info ofonod[1102]: App: < \r\nNO CARRIER\r\n\r\n_OSIGQ: 13,0\r\n
Mar 16 19:56:24 gta04 daemon.debug ofonod[1102]: src/voicecall.c:tone_request_cb() command failed with error: Unknown error type
Mar 16 19:56:24 gta04 daemon.debug ofonod[1102]: src/network.c:ofono_netreg_strength_notify() strength 41
i.e. tone_request_cb is only called when the call ends.
next prev parent reply other threads:[~2012-03-16 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 21:13 Handling AT command with no response Neil Jerram
2012-03-16 21:16 ` Neil Jerram [this message]
2012-03-16 21:31 ` Denis Kenzior
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=87vcm4b61i.fsf@neil-laptop.ossau.uklinux.net \
--to=neil@ossau.homelinux.net \
--cc=ofono@ofono.org \
/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