osmo-hlr[master]: notify GSUP clients when HLR subscriber information changes

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.org
Mon Apr 9 17:35:55 UTC 2018


Patch Set 1:

(1 comment)

https://gerrit.osmocom.org/#/c/7685/1/src/hlr.c
File src/hlr.c:

Line 49: /* Trigger 'Insert Subscriber Data' messages to all connected GSUP clients.
to all GSUP clients is ok for now, as we only expect a single MSC+SGSN to be connected.  However, in larger scale networks we should check to update only those MSC/SGSN which are listed in the subscriber data as the "current serving VLR/SGSN" for that subscriber.  I believe we already have those fields in our database model, not sure if they're already populated though.   In any case, we should at least have a a FIXME here to keep remembering something must be done in the future to avoid ISD into VLRs/SGSNs that are not even serving the subscriber.  At that point, the respective "vlr_subscriber" would be allocated/created in them, despite the subscriber not existing.


-- 
To view, visit https://gerrit.osmocom.org/7685
To unsubscribe, visit https://gerrit.osmocom.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Iffe1d7afb9fc7dbae542f70bbf5391ddc08a14b4
Gerrit-PatchSet: 1
Gerrit-Project: osmo-hlr
Gerrit-Branch: master
Gerrit-Owner: Stefan Sperling <ssperling at sysmocom.de>
Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-HasComments: Yes



More information about the gerrit-log mailing list