https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-02-21T16:03:17ZOpen Source Mobile CommunicationsOsmoBTS - Bug #2965: No measurement reports sent for channels other than TCHhttps://osmocom.org/issues/2965?journal_id=77272018-02-21T16:03:17Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/2975">Bug #2975</a>: OsmoBTS doesn't generate measurement indications in absence of uplink bursts</i> added</li></ul> OsmoBTS - Bug #2965: No measurement reports sent for channels other than TCHhttps://osmocom.org/issues/2965?journal_id=77952018-02-23T23:28:34Zlaforge
<ul><li><strong>Assignee</strong> set to <i>laforge</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul><p>what kind of SDCCH have you tried? SDCCH/4 or SDCCH/8?</p>
<p>My testing has shown that they are present for SDCCH/8 but missing for SDCCH/4.</p>
<p>I have pushed a fix for the bug I have observed to <a class="external" href="https://gerrit.osmocom.org/6871">https://gerrit.osmocom.org/6871</a></p>
<p>Please comment on whether this fixes your issues, too, or if you experience missing measurement reports beyond SDCCH/4.</p> OsmoBTS - Bug #2965: No measurement reports sent for channels other than TCHhttps://osmocom.org/issues/2965?journal_id=77962018-02-23T23:50:48Zlaforge
<ul></ul><p>Actually, I was wrong. The problem affected both SDCCH/4 and SDCCH/8.</p>
<p>I don't understand how those old/existing fn102 were computed and how they have been verified. At least with osmo-bts-trx, my patches are required to make measurement reports work. This must be double-checked with other BTS types.</p>
<p><a class="user active" href="https://osmocom.org/users/15">dexter</a>: Do you have any idea how you verified measurement reports for SDCCH/4 and SDCCH/8 at the time?</p> OsmoBTS - Bug #2965: No measurement reports sent for channels other than TCHhttps://osmocom.org/issues/2965?journal_id=78722018-02-26T14:12:31Zlaforge
<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>80</i></li></ul><p>related patch has been merged to master.</p> OsmoBTS - Bug #2965: No measurement reports sent for channels other than TCHhttps://osmocom.org/issues/2965?journal_id=78942018-02-27T07:27:04Zlaforge
<ul><li><strong>Assignee</strong> changed from <i>laforge</i> to <i>dexter</i></li></ul><p>Please verify measurement reports now are present formall channel types on sysmo/octphy</p> OsmoBTS - Bug #2965: No measurement reports sent for channels other than TCHhttps://osmocom.org/issues/2965?journal_id=78992018-02-27T08:29:45Zkeith
<ul></ul><p>Looks good on sysmoBTS 1002 (with nightly build)<br />I am seeing meas for SDCCH and TCH<br />:)</p> OsmoBTS - Bug #2965: No measurement reports sent for channels other than TCHhttps://osmocom.org/issues/2965?journal_id=79292018-03-01T09:37:53Zdexter
<ul></ul><p>The patch in question dates back to code that had had been contributed by Octasic inc. I have checked the code against the specification. Since I managed to find the numeric values 11 and 36 in 3GPP TS 45.008 the implementation looked plausible to me. However, I had difficulties to understand the offsets in the code and I still have them (even with the corrected version).</p>
<p>I did tests for the traffic channels only (see OS#2329). The signaling channels slipped through.</p> OsmoBTS - Bug #2965: No measurement reports sent for channels other than TCHhttps://osmocom.org/issues/2965?journal_id=79472018-03-01T23:10:31Zlaforge
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li></ul>