This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Lennart Müller mueller.lennart at googlemail.comHi Holger, > IANAL, regarding the token auth, you might find a way instead of sending > the MM Auth Reject to omit the LU Accept and schedule a LU Reject after > the SMS is sent? I think a phone can only receive SMS after it successfully registered itself at the network? > Did the user accidently end in your network and thanks to > a broken phone stayed in it, but didn't read the SMS that is on the > lock-screen of his fruit phone? He saw it - thats the reason why he blame us. I think his home network was not reachable and so his phone simply tried to "roam" into our network. The configured reject cause is: location updating reject cause 11 So in my understanding, after kicking out the phone, it should not try to automatically register to our network again until switched off or manually selecting our network, and instead simply switch back to the home network. Probable instead of switching back, it stayed offline - until a power cycle as I heard. > Did the "nice' guy open a ticket with the > fruit company too? Certainly not - "This never happened elsewhere - it must be your network!". Regards, Lennart