Vincent Bernat <[email protected]> writes: > ❦ 24 janvier 2016 22:19 +0100, Bjørn Mork <[email protected]> : > >>> I am being "denied" by 3GPP. What could be the cause? MCC and MNC are >>> correct. >> >> Sorry, I'm totallt lost here. AFAICS, you get the NwError code '19' here: >> >> 07:00:00:80:5C:00:00:00:00:00:00:00:01:00:00:00:00:00:00:00:A2:89:CC:33:BC:BB:8B:4F:B6:B0:13:3E:C2:AA:E6:DF:09:00:00:00:30:00:00:00:13:00:00:00:06:00:00:00:01:00:00:00:20:00:00:00:01:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:02:00:00:00 >> >> which is decoded to (without the header): >> >> >> MBIM_CID_REGISTER_STATE (9) >> InformationBuffer [48]: >> NwError: 19 () >> RegisterState: 6 (MBIMRegisterStateDenied) >> RegisterMode: 1 (MBIMRegisterModeAutomatic) >> AvailableDataClasses: 0x00000020 LTE >> CurrentCellularClass: 0x00000001 GPRS >> ProviderId: [0] <none> >> ProviderName: [0] <none> >> RoamingtText: [0] <none> >> RegistrationFlag: 0x00000002 > > Which utility did you use to decode?
A very primitive perl script I used for testing before libmbim was available. It has a bit too hackish UI to be generally useful, I believe. >> But I cannot find that code defined anywhere. It is not listed in the >> MBIM spec, and it is not listed in 3GPP TS 24.008, AFAICS. Very weird. >> >> Did you force the modem to a non-LTE network here? If so, then maybe it >> helps to let it register in the LTE network? > > I tried with Windows 10, got the same result. Then, I put the SIM on a > phone and it worked without a problem. The phone doesn't support LTE > thought. Then, I tried again on Windows and it worked. Then, again on > Linux and it didn't work. In fact, I didn't get a denied, but a loop in > the registration: > > Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> > enabling) > Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed > (unknown -> registering) > Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed > (registering -> home) > Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> > registered) > Simple connect started... > Simple connect state (4/8): Wait to get fully enabled > Simple connect state (5/8): Register > Simple connect state (6/8): Bearer > Simple connect state (7/8): Connect > Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> > connecting) > Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed > (home -> unknown) > Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed > (unknown -> registering) > Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed > (registering -> home) > Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed > (home -> unknown) > Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed > (unknown -> registering) > Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed > (registering -> home) > Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed > (home -> unknown) > > So, I tried to connect manually with: > > mmcli -m 1 --simple-connect="apn=internet,ip-type=ipv4" --verbose > > And it worked just fine. mmcli -b 2 showed me that I got an IP > address. Then, I did disconnect (-b 2 -x), then I tried again with > NM. And it worked. > > Does the 3GPP registration include the ip-type? I think I have put ipv4 > too for Windows 10 on my second try. > > I suppose that I'll have to investigate a bit more. New firmware, new > bugs. ;-) I wonder if you might just have been "lucky" and hit some unrelated network error? The closest defined codes are 17 - "Network failure" and 22 - "Congestion". Bjørn _______________________________________________ ModemManager-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
