Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/1] qmi: support SMS receive on Quectel EC21
Date: Tue, 17 Oct 2017 09:45:10 -0500	[thread overview]
Message-ID: <7f81d809-a990-c8af-df30-9b75337e5be7@gmail.com> (raw)
In-Reply-To: <20171017134134.0d70b32e@lazus.yip>

[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]

On 10/17/2017 06:41 AM, Alexander Couzens wrote:
> Hi Jonas,
> 
>> Could you explain what you are trying to do here?  Why would you
>> clear the SMS storage every time the modem powers up?
>>
>> I also don't see that ofono actually supports deleting messages from
>> the modem's storage... if you know how this is supposed to work,
>> please enlighten me.

oFono does not manage the message store.  The implicit assumption is 
that all SMS messages are delivered immediately without hitting ME/SMS 
storage.  oFono takes care of notifying the history plugin and sending 
the ACK.

For those devices that don't support immediate delivery it is assumed 
that the sms atom driver takes care of the details.  So on startup the 
driver is supposed to grab all messages from the store, notify the core 
and then delete all of them.  Any subsequent messages that are delivered 
to the store, should be notified up to the core and the storage space freed.

See how the atmodem sms driver does this.  E.g. +CMTI delivery vs +CMT

> 
> the Gobi2000 doesn't accept the routes with TRANSFER_AND_ACK nor
> STORAGE_TYPE_NONE.
> 
> Reading out the store is also useful if the modem is receiving any
> SMS while ofono isn't runing. E.g. while booting, the sms would never
> made it to ofono.

This is a weird case as the modem should not be in radio on mode anyway. 
  But yes this is possible...

> 
> I don't know (yet) how the different routes are working in detail. This
> is on my list. But I've faced edge cases when the NV was full, the
> modem rejects receiving any messages, regardless if the modem should
> save it to it.
> 

On an unrelated note, can you guys look at the WIP mbimmodem plugin and 
see if the parsing/building approach taken there is applicable (in some 
modified form) to QMI?  E.g. to simplify the drudgery of building / 
parsing QMI messages.

Regards,
-Denis

  reply	other threads:[~2017-10-17 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 12:20 [PATCH 1/1] qmi: support SMS receive on Quectel EC21 Jonas Bonn
2017-10-16 14:07 ` Alexander Couzens
2017-10-16 14:43   ` Jonas Bonn
2017-10-17  7:16   ` Jonas Bonn
2017-10-17 11:41     ` Alexander Couzens
2017-10-17 14:45       ` Denis Kenzior [this message]
2017-10-17 14:35 ` 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=7f81d809-a990-c8af-df30-9b75337e5be7@gmail.com \
    --to=denkenz@gmail.com \
    --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