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/.
Ivan Kluchnikov Ivan.Kluchnikov at fairwaves.ruHi Holger, Thank you for patch review. can you please give a general introduction of that feature? Describe when > one would want to use it. The basic idea is to support roaming-based network sharing. So subscribers of different operators can roam seamlessly in our network. For that purpose we should be able to check a subscriber's IMSI to identify the virtual network the IMSI belongs to. On the first stage to achieve seamless roaming we should be able to set network name for each supported virtual network. In future we plan to add more configuration parameters for virtual network: - auth policy (which could solve http://projects.osmocom.org/issues/1647) - location updating reject cause (useful for real deployments) May be you also have any ideas which parameters could be added to virtual network node? Why it is not a regexp for the IMSI but actually only the country code and > network code? How you intend to deal with two or three digit network code? Yes, I agree that the current implementation is not enough flexible and it is a good idea to use imsi-prefix instead of mcc and mnc, also it will fix the issue with 3 digit mnc. Do you think it makes sense? But I am not sure that I understand the idea of using regexp for the IMSI, could you please clarify for which cases it could be useful? -- Regards, Ivan Kluchnikov. http://fairwaves.ru -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20160413/e423307e/attachment.htm>