Handling received SMS
aleksander at aleksander.es
Mon Feb 13 16:09:58 UTC 2017
On Mon, Feb 13, 2017 at 3:37 PM, Colin Helliwell
<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.
>> Thanks, I'll try to get that patched into my 1.6.4 version that I'm using currently.
> Could you take a minute to point me in the direction of mm_parse_uint_list() please? Added in somewhere subsequent to 1.6.4 I presume
More information about the ModemManager-devel