<div dir="ltr">Yes I already have the value I need, and mmcli -i 0 shows it.<div> </div><div>Thanks</div></div><div class="gmail_extra"> <div class="gmail_quote">On Wed, Sep 6, 2017 at 10:45 AM, Aleksander Morgado <<a href="mailto:aleksander@aleksander.es" target="_blank">aleksander@aleksander.es</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey, On Wed, Sep 6, 2017 at 6:22 PM, Nathaniel Haggard <<a href="mailto:natester@gmail.com">natester@gmail.com</a>> wrote: > I'd like to read the IMSI just before assigning APN, but > > ~# mmcli -m 0 --command="AT+CIMI" > error: command failed: > 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unauthorized: Cannot > send AT command to modem: operation only allowed in debug mode' > > and sometimes: > mmcli --command is limited only for when ModemManager runs with --debug. But you should have the IMSI reported in the "SIM object" associated to the modem. E.g. if your SIM object is in index #0, you may already have the value you need in the "mmcli -i 0" output. > ~# qmicli -d /dev/cdc-wdm0 --dms-uim-get-imsi | grep IMSI: | cut -d "'" -f2 > error: couldn't create client for the 'dms' service: CID allocation failed > in the CTL client: Transaction timed out > > other times I get this: > > ~# qmicli -d /dev/cdc-wdm0 --dms-uim-get-imsi > [/dev/cdc-wdm0] UIM IMSI retrieved: > IMSI: '310410874358522' > > > I thought qmi-proxy took care of locking issues. How can I get the IMSI > reliably? > Yes, but you need to explicitly select the proxy usage, by adding "-p" in all your qmicli calls. Otherwise, you're competing with ModemManager in the communication through the cdc-wdm device. -- Aleksander <a href="https://aleksander.es" rel="noreferrer" target="_blank">https://aleksander.es</a> </blockquote></div> </div>