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/gerrit-log@lists.osmocom.org/.
Harald Welte gerrit-no-reply at lists.osmocom.orgHarald Welte has submitted this change and it was merged. ( https://gerrit.osmocom.org/13715 ) Change subject: Document subscribers create on demand feature ...................................................................... Document subscribers create on demand feature Add a new section in the subscribers chapter, with detailed explanation of the use cases and related OsmoHLR and OsmoMSC configuration. Related: OS#2542 Change-Id: I2dd4a56f7b8be8b5d0e6fc32e04459e5e278d0a9 --- M doc/manuals/chapters/subscribers.adoc 1 file changed, 21 insertions(+), 0 deletions(-) Approvals: Jenkins Builder: Verified Vadim Yanitskiy: Looks good to me, approved Harald Welte: Looks good to me, approved diff --git a/doc/manuals/chapters/subscribers.adoc b/doc/manuals/chapters/subscribers.adoc index bb57d24..9f87131 100644 --- a/doc/manuals/chapters/subscribers.adoc +++ b/doc/manuals/chapters/subscribers.adoc @@ -67,3 +67,24 @@ |ms_purged_ps|1|3GPP TS 23.008 chapter 2.7.6 |=== +=== Configuring the Subscribers Create on Demand Feature + +Usually a HLR will only allow mobile equipment (ME) on the network, if the HLR +has a subscriber entry with the ME's IMSI. But OsmoHLR can also be configured to +automatically create new entries for new IMSIs, with the +subscriber-create-on-demand VTY option. The obvious use case is creating the +new subscriber entry and then allowing the ME to use both the CS +(Circuit Switched) and PS (Packet Switched) NAM (Network Access Mode). + +On the other hand, operators might only want to give network access to IMSIs, of +which they know the owner. In order to do that, one can set the default NAM to +"none" and manually approve new subscribers by enabling their nam_cs and nam_ps +parameters (e.g. over the VTY). + +Oftentimes it is hard to know, which IMSI belongs to which ME, but the IMEI is +readily available. If you configure your MSC to send IMEI checking requests to +the HLR, before sending location update requests, the subscribers created on +demand can also have the IMEI stored in the HLR database. With OsmoMSC, this +is done by writing "check-imei-rqd early" in the "msc" section of osmo-msc.cfg. +Then enable storing the IMEI when receiving check IMEI requests with +"store-imei" in the OsmoHLR configuration. -- To view, visit https://gerrit.osmocom.org/13715 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-hlr Gerrit-Branch: master Gerrit-MessageType: merged Gerrit-Change-Id: I2dd4a56f7b8be8b5d0e6fc32e04459e5e278d0a9 Gerrit-Change-Number: 13715 Gerrit-PatchSet: 9 Gerrit-Owner: Vadim Yanitskiy <axilirator at gmail.com> Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org> Gerrit-Reviewer: Jenkins Builder (1000002) Gerrit-Reviewer: Vadim Yanitskiy <axilirator at gmail.com> Gerrit-Reviewer: osmith <osmith at sysmocom.de> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20190521/954ebcc0/attachment.htm>