https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-02-25T12:15:51ZOpen Source Mobile CommunicationsOsmoBSC - Feature #2968: resurrect meas_feedhttps://osmocom.org/issues/2968?journal_id=78162018-02-25T12:15:51Zlaforge
<ul><li><strong>Assignee</strong> set to <i>neels</i></li></ul> OsmoBSC - Feature #2968: resurrect meas_feedhttps://osmocom.org/issues/2968?journal_id=89772018-04-20T15:06:25Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>50</i></li></ul><p>resurrected meas_feed.c in osmo-bsc.git on branch neels/meas_feed.<br />Only need to test it with an actual BTS to verify that it works.</p> OsmoBSC - Feature #2968: resurrect meas_feedhttps://osmocom.org/issues/2968?journal_id=89792018-04-21T19:22:01Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>I tested my meas_feed patch for osmo-bsc, and it works, but:<br />The meas_vis and meas_web tools though appear to use the lchan's IMSI as primary key to visualizing active lchans.<br />In the old osmo-nitb, we always knew the IMSI of an lchan, and the old meas_feed code even omitted lchans we didn't know the IMSI for.<br />In osmo-bsc, though, we so far hardly ever know the subscriber's IMSI. The measurement feeds mostly have no IMSI.<br />The result is that all lchans' measurement reports are mistaken to belong to the same line, swapping through the data points on a single line.</p>
<p>So meas_vis and meas_web should always have used the lchan's bts,trx,ts,ss number to list the lchans by <a class="issue tracker-1 status-1 priority-1 priority-lowest" title="Bug: meas_vis: use the lchan identity as primary key, not the IMSI (New)" href="https://osmocom.org/issues/3192">#3192</a>.<br />To help current versions of these tools, osmo-bsc can help by trying to identify the IMSI of the subscriber where possible: <a class="issue tracker-2 status-3 priority-1 priority-lowest closed" title="Feature: obtain and store subscriber identity (Resolved)" href="https://osmocom.org/issues/2969">#2969</a>.</p> OsmoBSC - Feature #2968: resurrect meas_feedhttps://osmocom.org/issues/2968?journal_id=89802018-04-21T19:22:26Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-3 priority-1 priority-lowest closed" href="/issues/2969">Feature #2969</a>: obtain and store subscriber identity</i> added</li></ul> OsmoBSC - Feature #2968: resurrect meas_feedhttps://osmocom.org/issues/2968?journal_id=89822018-04-21T19:22:34Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-1 priority-lowest" href="/issues/3192">Bug #3192</a>: meas_vis: use the lchan identity as primary key, not the IMSI</i> added</li></ul> OsmoBSC - Feature #2968: resurrect meas_feedhttps://osmocom.org/issues/2968?journal_id=103282018-07-16T14:33:42Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>50</i> to <i>100</i></li></ul><p>meas_feed.c was added back to osmo-bsc in I186c7a995dd2b81746c32a58b55da64ed195a1ce yet the common tools (meas_vis, meas_web) cannot work with it since they rely on an IMSI being present in each Meas Report. Those need fixing to comprehensively re-enable meas_feed.</p>
<p>Though, the "resurrect meas_feed in osmo-bsc" part is done now. Closing this issue and leaving the remaining meas_feed ecosystem bugs to the other issues linked here already.</p>