https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092017-07-24T14:10:34ZOpen Source Mobile CommunicationsOsmoBSC - Feature #2389: re-add siemens MRPCI message, dropped during MSCSPLIThttps://projects.osmocom.org/issues/2389?journal_id=46762017-07-24T14:10:34Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-2 priority-default closed" href="/issues/2257">Feature #2257</a>: prepare split of the openbsc.git in smaller components</i> added</li></ul> OsmoBSC - Feature #2389: re-add siemens MRPCI message, dropped during MSCSPLIThttps://projects.osmocom.org/issues/2389?journal_id=67122017-12-10T20:16:20Zlaforge
<ul><li><strong>Category</strong> set to <i>Siemens BTS</i></li></ul> OsmoBSC - Feature #2389: re-add siemens MRPCI message, dropped during MSCSPLIThttps://projects.osmocom.org/issues/2389?journal_id=143222019-05-08T17:45:10Zlaforge
<ul><li><strong>Assignee</strong> set to <i>laforge</i></li></ul> OsmoBSC - Feature #2389: re-add siemens MRPCI message, dropped during MSCSPLIThttps://projects.osmocom.org/issues/2389?journal_id=143232019-05-08T17:53:24Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-3 priority-3 priority-high3 closed" href="/issues/2548">Feature #2548</a>: Add support for E1/T1 based BTSs to OsmoBSC</i> added</li></ul> OsmoBSC - Feature #2389: re-add siemens MRPCI message, dropped during MSCSPLIThttps://projects.osmocom.org/issues/2389?journal_id=192512020-08-01T13:39:36Zlaforge
<ul></ul><p>The proper solution was implemented in <a class="changeset" title="BS11: send MRPCI message after HANDOVER COMPLETE and ASSIGNMENT COMPLETE This message is require..." href="https://projects.osmocom.org/projects/osmobsc/repository/osmo-bsc/revisions/8156494f36e2ef8f388aeb698baf964b5e3eb349">8156494f36e2ef8f388aeb698baf964b5e3eb349</a> (not in master), which sends it after ASSIGNMENT COMPLETE and HANDOVER COMPLETE. We could probably also send it immediately after activation of a lchan.</p>
<p>The key aspect is that we need to know CLASSMARK 2 in order to encode the MRPCI message. OsmoBSC currently doesn't keep this information stored anywhere. So we first need to store CM2 as part of the bsc_subsc or the subscr_conn, and then use it whenever we want to encode the MRPCI message.</p> OsmoBSC - Feature #2389: re-add siemens MRPCI message, dropped during MSCSPLIThttps://projects.osmocom.org/issues/2389?journal_id=192522020-08-01T15:24:29Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>first working hack in <a class="external" href="https://gerrit.osmocom.org/c/osmo-bsc/+/19492">https://gerrit.osmocom.org/c/osmo-bsc/+/19492</a></p> OsmoBSC - Feature #2389: re-add siemens MRPCI message, dropped during MSCSPLIThttps://projects.osmocom.org/issues/2389?journal_id=211492021-02-06T12:08:48Zlaforge
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>patch merged.</p>