>Code that was working back in July isn't working, and our IT > folks gave us new SIMs from T-Mobile. Here in the USA, T-Mobile has > instituted a requirement that a SIM be bound to a specific IMEI. I am > using the ModemSimple.connect call to connect, and I keep getting a timeout.
If you are on a business account or certain MVNO this may be true. If you're APN really is fast.t-mobile.com though, then there is no IMEI locking. I'd ask your IT dept to confirm your APN first off. On Fri, Oct 21, 2022 at 1:11 AM Aleksander Morgado < aleksande...@chromium.org> wrote: > Hey, > > > After something of a hiatus induced by work priorities, I am back to my > > project that uses ModemManager and a "glue" program to tell it to > > connect. Code that was working back in July isn't working, and our IT > > folks gave us new SIMs from T-Mobile. Here in the USA, T-Mobile has > > instituted a requirement that a SIM be bound to a specific IMEI. I am > > using the ModemSimple.connect call to connect, and I keep getting a > timeout. > > > > Using mmcli, I run this command and also get a timeout: > > > > $ mmcli -m 0 --simple-connect='apn=fast.t-mobile.com,ip-type=ipv4v6' > > > > My boss is getting the same thing with a different modem and SIM. Both > > SIMs have allegedly been paired with the IMEI in T-Mobile's records. > > > > Does anyone know if simple-connect still works with T-Mobile in the USA? > > > > Yes, it works. There are daily tests running automatic connections to > T-Mobile and other major carriers in the USA and other countries. > > Are you sure the "fast.t-mobile.com" APN should be used? Maybe your > new SIM cards require a different one like e.g. "wholesale"? > > What is the output of "mmcli -m a"? > > Also, try adding --timeout=300 to the --simple-connect call. > > -- > Aleksander >