https://osmocom.org/https://osmocom.org/favicon.ico?16647414092017-12-23T17:45:51ZOpen Source Mobile CommunicationsOsmoMSC - Bug #2669: osm-msc doesn't clean up BSC statehttps://osmocom.org/issues/2669?journal_id=69402017-12-23T17:45:51Zlaforge
<ul><li><strong>Category</strong> set to <i>A interface (AoIP)</i></li></ul> OsmoMSC - Bug #2669: osm-msc doesn't clean up BSC statehttps://osmocom.org/issues/2669?journal_id=69442017-12-23T17:47:40Zlaforge
<ul><li><strong>Category</strong> changed from <i>A interface (AoIP)</i> to <i>A interface (general)</i></li></ul> OsmoMSC - Bug #2669: osm-msc doesn't clean up BSC statehttps://osmocom.org/issues/2669?journal_id=86332018-04-03T16:41:04Zdexter
<ul></ul><p>See also <a class="issue tracker-2 status-3 priority-2 priority-default closed" title="Feature: let osmo-msc record location area from location update for LAC wide paging (Resolved)" href="https://osmocom.org/issues/2397">#2397</a> As soon as we start collecting LACs we can also collect information about when the BSC appeared first and when the last activity was. This allows us to perform a regular garbage collection.</p> OsmoMSC - Bug #2669: osm-msc doesn't clean up BSC statehttps://osmocom.org/issues/2669?journal_id=87542018-04-09T20:18:59Zdexter
<ul></ul><p>Another idea: Once we can maintain the lists using the VTY, we could also have an VTY option that disables the BSC-Auto-Learning completely if necessary.</p> OsmoMSC - Bug #2669: osm-msc doesn't clean up BSC statehttps://osmocom.org/issues/2669?journal_id=117772018-09-30T11:37:41Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>dexter</i> to <i>osmith</i></li></ul>