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/.
Harald Welte laforge at gnumonks.orgHi Gullik, On Tue, Feb 12, 2019 at 08:05:54PM +0100, Gullik Webjorn wrote: > I think it would be useful to snoop the IMSI or pass it downstream from MSC, > at least for debugging / logging purposes. I am lucky to just try ONE phone at the time... Sure. It's simply not been a priority for anyone working on the code so far :/ We'd be very happy to receive and merge related patches. The most "proper" way to do it in line with the specs is to implement the "Common ID" procedure where the MSC informs the BSC of the IMSI very early after establishing the SCCP connection. If that's implemented in both OsmoMSC and OsmoBSC, it would work reliably at least for this most common use case. -- - Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)