Cinterion bug? (Re: Handling received SMS)

Colin Helliwell colin.helliwell at ln-systems.com
Tue Feb 14 08:11:37 UTC 2017


> On 13 February 2017 at 09:48 Aleksander Morgado <aleksander at aleksander.es> wrote:
> 
> On Mon, Feb 13, 2017 at 9:13 AM, <colin.helliwell at ln-systems.com> wrote:
> 
> > All I'm seeing in the logs is "+CIEV: message,1".
> > Checking back through the logs for unsolicited event setups, I also see
> > [src/mm-broadband-modem.c:5888]
> > set_messaging_unsolicited_events_handlers(): (ttyMux0) Setting messaging
> > unsolicited events handlers
> > [src/mm-port-serial.c:1347] _close_internal(): (ttyMux0) device open count
> > is 1 (close)
> > [src/mm-iface-modem-messaging.c:867] enable_unsolicited_events_ready():
> > Couldn't enable unsolicited events: 'SMS settings don't accept [2,1]
> > 
> > '
> > 
> > That inner error message seems to originate in the Cinterion plugin's
> > messaging_enable_unsolicited_events (). From what I can make out, that
> > function is looking for a supported mode in the response to "AT+CNMI=?".
> > Doing this from the command line gives the response " +CNMI:
> > (0-3),(0,1),(0,2,3),(0,2),(1) ". Furthermore a "AT+CNMI=2" also from the
> > command line - which I think the plugin would have otherwise tried to do
> > if it had found the mode - does give an OK response.
> 
> The +CNMI=? parser didn't expect the "range" format given for the
> 
>  field. I've fixed that in git master now.
> 

'Fraid I'm not geared up to log bug or supply patch, but I think there's a bug in 
messaging_enable_unsolicited_events() of plugins/cinterion/mm-broadband-modem-cinterion.c :
Line 215 (on Master) should be an 'else if' ?


More information about the ModemManager-devel mailing list