FW: MM v1.4.6/Telit HE910-D SMS question

[Highland, Glenn]

Actually the AT+CNMI? query response of 0,0,0,0,0 means the new SMS messages should be 
stored in the SIM, but the indications of their reception will not be issued.  I would
imagine the AT+CMGL command would list the messages if it is sent over the secondary
channel (assuming the primary is currently assigned to PPP traffic).

Wednesday, September 02, 2015 10:50 AM, Dan Williams wrote:

> On Wed, 2015-09-02 at 17:03 +0200, Aleksander Morgado wrote:
> > On Wed, Sep 2, 2015 at 4:53 PM, Highland, Glenn <Glenn.Highland at digi.com> wrote:
> > >
> > > Aleksander suggested that I propose the change below to the mailing list.
> > >
> > > Essentially we're encountering a problem with SMS notifications not being received
> > > by the application from ModemManager v1.4.6 (and v1.4.10 for that matter).  This
> > > is using a Telit HE910-D that has two USB endpoints (in our case ttyACM0 and
> > > ttyACM3).
> > > 
> > > The Telit HE910-D needs to be configured with the AT+CNMI=2,1,2,1,0 command on
> > > both the primary and secondary ports as confirmed by Telit Support.  Currently
> > > that command is performed only on the primary port, which is reserved for PPP
> > > I/O after connection to the provider network.  The secondary port's New
> > > Message Indication configuration remains at 0,0,0,0 which (in summary) causes
> > > the modem to discard inbound messages without storing them.  Hence ModemManager
> > > does not get notified of a newly-received SMS.
> > >
> > > Does an update to mm-broadband-modem.c seem reasonable to everyone?
> >
> > The specific suggestion I'm doing is to run the CNMI settings command
> > in both the primary and the secondary ports for all AT-based modems,
> > not just in the primary port - but don't fail the operation if setting
> > it in the secondary port fails (e.g. for the case where secondary port
> > is a very limited or not-fully-functional AT interpreter).

> That sounds like the right approach to me...

> Dan