https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092018-01-04T10:37:52ZOpen Source Mobile CommunicationsOsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=70002018-01-04T10:37:52Zlaforge
<ul><li><strong>Assignee</strong> set to <i>neels</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=77022018-02-20T12:08:03Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>neels</i> to <i>stsp</i></li></ul> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=79442018-03-01T21:44:46Zlaforge
<ul></ul><p>There's now a test case: HLR_Tests.TC_vty_msisdn_isd</p>
<p><a class="external" href="https://gerrit.osmocom.org/7039">https://gerrit.osmocom.org/7039</a></p> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=86142018-03-29T16:44:46Zstsp
<ul></ul>Looking at the HLR TC_vty_msisdn_isd test, it looks like this test:
<ol>
<li>Sends a location update sending the subscriber's initial msisdn.</li>
<li>Changes the subscriber's msisdn in the HLR's database via VTY.</li>
<li>Now waits and expects a communication of this new msisdn, initiated by the HLR.</li>
</ol>
I am unsure how the HLR could initiate this communication in its current implementation.<br />The HLR runs as a gsup server loop which only responds to incoming requests from clients.<br />The way I understand it, to fix the problem we would need to either:
<ol>
<li>Make the test send another location update or initiate some other GSUP communication with the HLR, and then expect to receive updated subscriber information.</li>
<li>Make it possible for the HLR to initiate a new (client) connection to the VLR (server) and then send the insert subscriber data message.</li>
</ol>
<p>Am I missing something?</p> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=86152018-03-29T16:56:06Zstsp
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=86262018-04-03T10:41:47Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>for the record, as discussed today: the GSUP connection between {MSC,SGSN} and HLR persists, you can send messages anytime. If an {MSC,SGSN} isn't connected then per definition it is not ready to receive subscriber updates (probably down or broken).</p> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=87442018-04-09T10:00:09Zstsp
<ul></ul><p>This patch fixes the external behaviour: <a class="external" href="https://gerrit.osmocom.org/7685">https://gerrit.osmocom.org/7685</a><br />It may not be the perfect solution in terms of code maintainability but<br />already gets us one step further.</p> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=88332018-04-12T08:59:41Zstsp
<ul></ul><p>Now waiting for a review of <a class="external" href="https://gerrit.osmocom.org/#/c/7743/">https://gerrit.osmocom.org/#/c/7743/</a></p> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=90802018-04-30T12:04:07Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-4 priority-high2 closed" href="/issues/3154">Bug #3154</a>: osmo-hlr should send updated subscriber data to relevant VLR/SGSN only</i> added</li></ul> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=91922018-05-07T11:11:16Zstsp
<ul></ul><p>Now waiting for review of this change: <a class="external" href="https://gerrit.osmocom.org/#/c/7992/">https://gerrit.osmocom.org/#/c/7992/</a></p> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=94262018-05-18T12:52:32Zstsp
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>Above change has been merged. Closing this issue.</p> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=99272018-06-15T16:05:52Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>New</i></li></ul><p>I'll be reverting to the old behavior in <a class="external" href="https://gerrit.osmocom.org/#/c/osmo-hlr/+/9647">https://gerrit.osmocom.org/#/c/osmo-hlr/+/9647</a>, so this bug must be reopened. The new behavior was just as broken as the previuos...</p> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=116602018-09-28T00:38:57Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/3601">Bug #3601</a>: OsmoMSC's GSUP client doesn't send CN domain to the HLR</i> added</li></ul> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=116622018-09-28T01:19:31Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Assignee</strong> changed from <i>stsp</i> to <i>neels</i></li></ul><p>I have working patches ready on branches neels/upd_subscr (both in osmo-hlr and osmo-msc).<br />The remaining question is still what identification to use for GSUP clients like MSC and SGSN.<br />So far using the IPA_IDTAG_SERNR ('MSC-00-00-00-00-00-00') which is technically too long for the HLR db<br />(enlarged the storage but that is questionable).</p> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=120012018-10-04T12:44:04Zneelsnhofmeyr@sysmocom.de
<ul></ul><p><a class="external" href="https://gerrit.osmocom.org/11233">https://gerrit.osmocom.org/11233</a></p> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=120022018-10-04T12:44:13Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>90</i></li></ul> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=121312018-10-10T11:29:03Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>above patch waiting for <a class="external" href="https://gerrit.osmocom.org/11232">https://gerrit.osmocom.org/11232</a> which needs further code review, after first remarks were addressed.</p> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=121552018-10-11T11:56:32Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>first preparatory patch merged, now <a class="external" href="https://gerrit.osmocom.org/c/osmo-hlr/+/11233">https://gerrit.osmocom.org/c/osmo-hlr/+/11233</a> waiting for code review.</p> OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changeshttps://projects.osmocom.org/issues/2785?journal_id=143662019-05-09T00:27:24Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>90</i> to <i>100</i></li></ul>