SMS receive behaviour

Daniel danielvaz at gmail.com
Fri Jan 22 07:31:43 PST 2016


Glenn, Thank you for your fast answer. I am using ModemManager 1.4.2

I will try to test the earliest version of ModemManager.

Is there some kind of workaround without upgrading the ModemManager version?

Thanks

On Fri, Jan 22, 2016 at 1:15 PM, Highland, Glenn <Glenn.Highland at digi.com>
wrote:

>
>
>
>
> *From:* ModemManager-devel [mailto:
> modemmanager-devel-bounces at lists.freedesktop.org] *On Behalf Of *Daniel
> *Sent:* Friday, January 22, 2016 7:20 AM
> *To:* modemmanager-devel at lists.freedesktop.org
> *Subject:* SMS receive behaviour
>
>
>
> Hi all,
>
>
>
> What is the supposed behavior when the modem device receives a SMS? The
> message org.freedesktop.ModemManager1.Modem.Messaging.Added will be emitted
> on dbus?
>
>
>
> I am using the MMQt in order to handle SMSs in an embedded device. Sending
> SMS it's ok.
>
> But when I sent a message to the device, and I use the dbus-monitor in
> order to see if the ModemManager sends the signal Added() there is no
> traffic on dbus until I "reset" the modem using:
>
> (disabling)
>
> # mmcli -m 0 -d
>
> (enabling) and after
>
> # mmcli -m 0 -e
>
>
>
> all messages that were sent to device will be received at same time and
> the signals are emitted in the dbus, as follows:
>
>
>
> signal sender=:1.3 -> dest=(null destination) serial=197
> path=/org/freedesktop/ModemManager1/
>
> Modem/0; interface=org.freedesktop.ModemManager1.Modem.Messaging;
> member=Added
>
>   object path "/org/freedesktop/ModemManager1/SMS/5"
>
>   boolean true
>
>
>
> Am I missing something?
>
> How I can debug the process of receiving a SMS?
>
>
>
> Follow some hardware info:
>
>
> root at ts-imx6-s:~# mmcli -m 0
>
>
>
> /org/freedesktop/ModemManager1/Modem/0 (device id
> '3fba001a3e3ce5ffefda417609400ad882ef3c7f')
>
>  -------------------------
>
>  Hardware |   manufacturer: 'Telit'
>
>           |          model: 'HE910-EUD'
>
>           |       revision: '12.00.224'
>
>           |      supported: 'gsm-umts'
>
>           |        current: 'gsm-umts'
>
>           |   equipment id: '354043052132539'
>
>  -------------------------
>
>  System   |         device:
> '/sys/devices/soc0/soc.1/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb2/2-1'
>
>           |        drivers: 'cdc_acm'
>
>           |         plugin: 'Generic'
>
>           |   primary port: 'ttyACM3'
>
>           |          ports: 'ttyACM3 (at), ttyACM0 (at)'
>
>  -------------------------
>
>  Numbers  |           own : 'unknown'
>
>  -------------------------
>
>  Status   |           lock: 'none'
>
>           | unlock retries: 'unknown'
>
>           |          state: 'connected'
>
>           |    power state: 'on'
>
>           |    access tech: 'umts'
>
>           | signal quality: '42' (recent)
>
>  -------------------------
>
>  Modes    |      supported: 'allowed: 2g, 3g; preferred: none'
>
>           |        current: 'allowed: 2g, 3g; preferred: none'
>
>  -------------------------
>
>  Bands    |      supported: 'unknown'
>
>           |        current: 'unknown'
>
>  -------------------------
>
>  IP       |      supported: 'ipv4, ipv6, ipv4v6'
>
>  -------------------------
>
>  3GPP     |           imei: '354043052132539'
>
>           |  enabled locks: 'none'
>
>           |    operator id: '72410'
>
>           |  operator name: 'VIVO'
>
>           |   subscription: 'unknown'
>
>           |   registration: 'home'
>
>  -------------------------
>
>  SIM      |           path: '/org/freedesktop/ModemManager1/SIM/0'
>
>
>
>  -------------------------
>
>  Bearers  |          paths: '/org/freedesktop/ModemManager1/Bearer/0'
>
> *[>] Daniel: What version of ModemManager are you running?  This looks
> eerily similar to a problem with the Telit HE910 family*
>
> *that we ran into which is fixed in ModemManager v1.4.12.  In our case
> when the HE910 switched into data mode on the primary*
>
> *channel it wasn’t sending the SMS notifications over the secondary,
> because the HE910 required the AT commands to enable*
>
> *SMS notifications be performed on the secondary as well.  The v1.4.12
> updates include a fix for that implemented by N. Stevens *
>
> *(a co-worker of mine).  We’d sometimes get the notifications on the
> primary right after start-up, and then nothing afterward.*
>
>
>
> Thanks in advance.
>
> Best regards.
>
> --
>
> Daniel Vaz
>



-- 
Daniel Vaz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/modemmanager-devel/attachments/20160122/9d3b7a74/attachment-0001.html>


More information about the ModemManager-devel mailing list