https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092018-01-22T01:03:21ZOpen Source Mobile CommunicationsOsmoMSC - Bug #2854: OsmoMSC never updates bearer capability from MNCChttps://projects.osmocom.org/issues/2854?journal_id=71992018-01-22T01:03:21Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-1 priority-lowest" href="/issues/2832">Feature #2832</a>: MNCC doesn't include field for "supported codecs"</i> added</li></ul> OsmoMSC - Bug #2854: OsmoMSC never updates bearer capability from MNCChttps://projects.osmocom.org/issues/2854?journal_id=72012018-01-22T01:03:51Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-7 priority-1 priority-lowest" href="/issues/1683">Bug #1683</a>: osmo-sip-connector: Implement codec selection / move codec selection to osmo-msc</i> added</li></ul> OsmoMSC - Bug #2854: OsmoMSC never updates bearer capability from MNCChttps://projects.osmocom.org/issues/2854?journal_id=72032018-01-22T01:03:57Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-3 priority-high3 closed" href="/issues/1663">Bug #1663</a>: don't connect channels of incompatible voice codec</i> added</li></ul> OsmoMSC - Bug #2854: OsmoMSC never updates bearer capability from MNCChttps://projects.osmocom.org/issues/2854?journal_id=75402018-02-07T09:00:25Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>4368</i> to <i>daniel</i></li></ul> OsmoMSC - Bug #2854: OsmoMSC never updates bearer capability from MNCChttps://projects.osmocom.org/issues/2854?journal_id=75862018-02-12T11:26:25Zlaforge
<ul></ul><p>TS 24.008 states "bearer capabilities" can be present in the following L3 CC messsages:</p>
<ul>
<li>CALL CONFIRMED
<ul>
<li>we parse them in osmo-msc</li>
</ul>
</li>
<li>CALL PROCEEDING
<ul>
<li>we encode them in osmo-msc</li>
</ul>
</li>
<li>EMERGENCY SETUP
<ul>
<li>we parse them in osmo-msc</li>
</ul>
</li>
<li>MODIFY
<ul>
<li>we parse and encode them in osmo-msc</li>
</ul>
</li>
<li>MODIFY COMPLETE
<ul>
<li>we parse and encode them in osmo-msc</li>
</ul>
</li>
<li>MODIFY REJECT
<ul>
<li>we parse and encode them in osmo-msc</li>
</ul>
</li>
<li>ESTABLISHMENT CONFIRMED</li>
<li>SETUP
<ul>
<li>we parse and encode them in osmo-msc</li>
</ul></li>
</ul>
<p>In terms of MNCC primitives, any primitive received on MNCC triggering any of the above CC messages should be able to contain bearer capabilities.</p> OsmoMSC - Bug #2854: OsmoMSC never updates bearer capability from MNCChttps://projects.osmocom.org/issues/2854?journal_id=75882018-02-12T11:37:01Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-1 priority-lowest" href="/issues/2933">Bug #2933</a>: change of trans->bearer_cap (e.g. via MNCC) will not trigger BSSMAP ASSIGNMENT</i> added</li></ul> OsmoMSC - Bug #2854: OsmoMSC never updates bearer capability from MNCChttps://projects.osmocom.org/issues/2854?journal_id=75892018-02-12T11:38:07Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> changed from <i>daniel</i> to <i>laforge</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>90</i></li></ul><p>Patch in <a class="external" href="https://gerrit.osmocom.org/6381">https://gerrit.osmocom.org/6381</a></p> OsmoMSC - Bug #2854: OsmoMSC never updates bearer capability from MNCChttps://projects.osmocom.org/issues/2854?journal_id=76242018-02-14T11:17:50Zlaforge
<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><p>merged</p>