Open Source Mobile Communications: Issueshttps://osmocom.org/https://osmocom.org/favicon.ico?15286125692019-02-08T14:25:46ZOpen Source Mobile Communications
Redmine Cellular Network Infrastructure - Bug #3794 (New): 'make install' overwrites $prefix/etc/osmocom/...https://osmocom.org/issues/37942019-02-08T14:25:46Zneelsnhofmeyr@sysmocom.de
<p>Installation of default config files overwrites etc/osmocom/*.cfg!<br />We must definitely stop doing that.</p> Cellular Network Infrastructure - Bug #3768 (New): user manuals don't describe statsd exporterhttps://osmocom.org/issues/37682019-01-26T11:05:24Zlaforge
<p>In fact, not only is documentation for the statsd exporter missing, but also documentation for the entire "statistics item reporting" sub-system.</p>
<p>See <a class="external" href="http://ftp.osmocom.org/api/latest/libosmocore/core/html/group__stats.html#details">http://ftp.osmocom.org/api/latest/libosmocore/core/html/group__stats.html#details</a> for the related API documentation.</p> Cellular Modem Information - Feature #3658 (New): Create a "osmocom-bb-host-latest" docker containerhttps://osmocom.org/issues/36582018-10-16T14:11:32Zosmith
<p>The ttcn3-bts-test-latest jenkins job should use the "latest" version of everything that is used for the test.<br />But since there is no "latest" tag in the osmocom-bb.git repository, we can't build a osmocom-bb-host-latest docker image.</p>
<p>The current workaround is using osmocom-bb-host-master for ttcn3-bts-test-latest.</p> Cellular Network Infrastructure - Feature #3587 (Feedback): Possibility to route SMS messages ove...https://osmocom.org/issues/35872018-09-24T21:21:35Zfixeria
<p>At the moment there is only one way to route short messages between an Osmocom-based<br />network and some external entity (e.g. SMSC) - SMPP interface. It's implemented in<br />both <a class="wiki-page" href="https://osmocom.org/projects/openbsc/wiki">OpenBSC</a> and <a class="wiki-page" href="https://osmocom.org/projects/osmomsc/wiki">OsmoMSC</a>, and can be optionally enabled during<br />the build configuration (using --enable-smpp).</p>
<p>The fundamental problem of SMPP is the need of transcoding between its primitives and<br />pretty complex SMS protocol. Moreover, in some cases this transcoding is not desired.</p>
<p>In commercial networks MAP (Mobile Application Part, see 3GPP TS 29.002) protocol is<br />used for forwarding MO/MT short messages between different network entities. There is<br />a special group of short message management services defined in MAP, see section 12.</p>
<p>The problem of MAP comes from the protocol stack it belongs to - SS7, its complexity.<br />Instead of SS7/MAP, Generic Subscriber Update Protocol (GSUP) is used in Osmocom CNI.<br />Basically GSUP is an Osmocom-specific non-standard protocol designed around the same<br />architecture as the MAP messages/operations, but without the complexity of SS7, and<br />without the need for ASN.1 encoding.</p>
<p>Implementing a possibility to route SMS messages over GSUP would facilitate the<br />integration of Osmocom CNI with third-party networks and components. In general,<br />this task would require us to replicate the SM-related messages and IEs in GSUP,<br />and to implement proper message forwarding in <a class="wiki-page" href="https://osmocom.org/projects/osmomsc/wiki">OsmoMSC</a>.</p>
<p>Draft message sequence charts can be found here: <a class="external" href="https://gerrit.osmocom.org/10604/">https://gerrit.osmocom.org/10604/</a></p> Cellular Network Infrastructure - Bug #3417 (New): show asciidoc counters does not show all the c...https://osmocom.org/issues/34172018-07-25T07:01:29Zdaniel
<p>Since show asciidoc counters only iterates through the allocated rate_ctr/stat_item groups it does not necessarily show all the counters that can be available.</p>
<p>For example the sgsn only creates (and reports) bssgp:bss_ctx counters if there is actually a bssgp configured in the sgsn. While you could argue that this is just a misconfiguration the issue remains with counters allocated for each mm or pdp context. As long as no phones are GMM attached the command show asciidoc counters does not know about any statistics for mm or pdp context.</p>
<p>We could add commands to add the rate_ctr_group_desc ans osmo_stat_item_group_desc to another list which keeps track of available counters and traverse that for show asciidoc stats as we don't need the actual allocations for counter values that the *_group_alloc() functions do. Group and counter description needed for documentation are all available from the *_group_desc structs.</p>
<p>This would mean that we need to register every counter group independently from the *_group_alloc() calls happening right now, so the documentation knows about them - but as a side effect we could also have a function to allocate a rate_ctr/stat_item group by name (instead of struct pointer). Not sure how useful that would be.</p> Cellular Network Infrastructure - Feature #3386 (New): Generate man pages at build time from adoc...https://osmocom.org/issues/33862018-07-06T10:24:03Zpespin
<p>Once we have documentation being build in each project repository separately (see <a class="issue tracker-2 status-3 priority-2 priority-default closed" title="Feature: Move project specific manuals from osmo-gsm-manuals to each respective git repository (Resolved)" href="https://osmocom.org/issues/3385">#3385</a>), we want to generate man pages for each repository.</p>
<p>The idea here is to have an .adoc file with all the required content to be used in the man pag, and which is already included in the user manual. Then we need to scripts/makefile to transform this .adoc file into man source format and make it be build and installed when --enable-man is passed. Then, install it in the debian packages (which means we in turn need to modify dh_configure or similar to pass the --enable-man flag, and somehow include the common osmo-gsm-manuals.git in there when sending to OBS).</p> Cellular Network Infrastructure - Bug #3382 (New): Investigate and fix lintian issues listed by D...https://osmocom.org/issues/33822018-07-05T11:37:34Zpespin
<p>This web page lists a list of warnings which we may want to fix: <a class="external" href="https://lintian.debian.org/maintainer/Debian-mobcom-maintainers@lists.alioth.debian.org.html">https://lintian.debian.org/maintainer/Debian-mobcom-maintainers@lists.alioth.debian.org.html</a></p> Cellular Network Infrastructure - Bug #3370 (New): osmo-bts "substituting all-zero burst" and osm...https://osmocom.org/issues/33702018-06-29T19:28:23Zrlehm
<p>Running newest versions of LimeSuite, osmo-nitb, osmo-bts-trx, osmo-trx-lms, osmo-pcu, osmo-sgsn, and osmo-ggsn on a LimeSDR-USB. GSM capabilities work as normal, but once osmo-bts-trx connects to osmo-pcu the bts outputs:<br /><pre><code class="text syntaxhl"><span class="CodeRay">20/16 Substituting all-zero burst (current_fn=1527981, elapsed=2
&lt;0007&gt; scheduler.c:917 1528136/1152/12/23/20 Substituting all-zero burst (current_fn=1528137, elapsed=2
&lt;0007&gt; scheduler.c:917 1528162/1152/12/49/46 Substituting all-zero burst (current_fn=1528163, elapsed=2
&lt;0007&gt; scheduler.c:917 1528188/1152/12/24/20 Substituting all-zero burst (current_fn=1528189, elapsed=2
...
</span></code></pre><br />and pcu outputs:<br /><pre><code class="text syntaxhl"><span class="CodeRay">&lt;0001&gt; pcu_l1_if.cpp:390 RACH request received: sapi=1 qta=0, ra=123, fn=1528801, cur_fn=1528804, is_11bit=0
&lt;0008&gt; tbf.cpp:977 Allocating UL TBF: MS_CLASS=0/0
&lt;0008&gt; tbf.cpp:538 TBF(TFI=0 TLLI=0x00000000 DIR=UL STATE=NULL) Setting Control TS 5
&lt;0008&gt; tbf.cpp:923 TBF(TFI=0 TLLI=0x00000000 DIR=UL STATE=NULL) Allocated: trx = 0, ul_slots = 20, dl_slots = 00
&lt;0008&gt; bts.cpp:746 TBF(TFI=0 TLLI=0x00000000 DIR=UL STATE=FLOW) set ass. type CCCH [prev CCCH:0, PACCH:0]
&lt;0008&gt; bts.cpp:754 TBF(TFI=0 TLLI=0x00000000 DIR=UL STATE=FLOW) TX: START Immediate Assignment Uplink (AGCH)
&lt;0008&gt; tbf.cpp:647 TBF(TFI=0 TLLI=0xe70c9306 DIR=DL STATE=WAIT RELEASE) T3193 timeout expired, freeing TBF
&lt;0008&gt; tbf.cpp:482 TBF(TFI=0 TLLI=0xe70c9306 DIR=DL STATE=RELEASING) free
&lt;0007&gt; gprs_ms.cpp:672 MS (IMSI ): Link quality 0dB (0dB) left window [5, 8], modifying uplink CS level: CS-2 -&gt; CS-1
&lt;000a&gt; tbf_ul.cpp:295 TBF(TFI=0 TLLI=0x00000000 DIR=UL STATE=FLOW) Decoded premier TLLI=0x00000000 of UL DATA TFI=0.
&lt;000c&gt; tbf_ul.cpp:392 LLC [PCU -&gt; SGSN] TBF(TFI=0 TLLI=0xd274c680 DIR=UL STATE=FLOW) len=78
PayloadType = 1 | spare = 0 | R = 0 | MESSAGE_TYPE = 1 | TLLI = 0xd274c680 | CTRL_ACK = 3 | Exist_AdditionsR5 = 0 | Padding = 43|43|43|43|43|43|43|43|43|43|43|43|43|43|43|43|43|
&lt;0007&gt; gprs_rlcmac_meas.cpp:106 UL RSSI of TLLI=0xd274c680: -40 dBm
</span></code></pre><br />over and over again (with some payload data in between). The SGSN and GGSN server don't appear to be receiving any packets and the phone does not have data.</p>
<p>I'm using the default .cfg files provided by myriadrf and have set all the necessary iptables rules for forwarding traffic through the GGSN tunnel.</p> Cellular Network Infrastructure - Bug #3369 (New): no automatic testing of Debian/Ubuntu packageshttps://osmocom.org/issues/33692018-06-28T22:12:23Zlaforge
We should have some automatic test job for the Debian/Ubuntu packages to ensure that the packaging is consistent. Tests should at the very minimum ensure:
<ul>
<li>that the included example config files can actually be parsed and the respective <code>osmo-*</code> programs can be started with them</li>
<li>that the included example configs are compatible, i.e. if all example configs are used, the resulting network is functional</li>
</ul>
<p>If we include systemd service files, one could also check if the processes are properly started by them.</p> Cellular Network Infrastructure - Bug #3192 (New): meas_vis: use the lchan identity as primary ke...https://osmocom.org/issues/31922018-04-21T19:21:40Zneelsnhofmeyr@sysmocom.de
<p>While re-adding meas_feed to osmo-bsc.git, I noticed that the meas_vis and meas_web tools appear to use the lchan's IMSI as primary key to visualizing active lchans. They should use the bts,trx,ts,ss number instead.</p>
<p>See also: <a class="issue tracker-2 status-3 priority-2 priority-default closed" title="Feature: resurrect meas_feed (Resolved)" href="https://osmocom.org/issues/2968">#2968</a> <a class="issue tracker-2 status-1 priority-1 priority-lowest" title="Feature: obtain and store subscriber identity (New)" href="https://osmocom.org/issues/2969">#2969</a></p>
<p>meas_vis is currently still in openbsc.git, it should probably move over to osmo-bsc <a class="issue tracker-2 status-6 priority-2 priority-default closed" title="Feature: move meas_vis and meas_json over to osmo-bsc.git (Rejected)" href="https://osmocom.org/issues/3191">#3191</a>.<br />meas_web is external, but it could make sense to send a pull request.</p> Cellular Network Infrastructure - Bug #3167 (New): Build osmo-*-master docker containers with add...https://osmocom.org/issues/31672018-04-14T12:47:52Zlaforge
<p>In order to catch use-after-free and similar bugs during TTCN-3 test execution, it would be great if we'd modify the <code>docker-playground/osmo-*-master</code> containers to build with asan enabled. We'd of course have to capture the stderr output of the related processes somehow into jenkins (e.g. as artefacts) to reap the benefits from this.</p> Cellular Network Infrastructure - Feature #3128 (New): mention invalidated vty options in [[OsmoN...https://osmocom.org/issues/31282018-03-30T14:47:28Zneelsnhofmeyr@sysmocom.de
<p><a class="wiki-page" href="https://osmocom.org/projects/cellular-infrastructure/wiki/OsmoNITB_Migration_Guide">OsmoNITB Migration Guide</a></p>
<p>Some vty options are being removed in osmo-bsc <a class="external" href="https://gerrit.osmocom.org/7428">https://gerrit.osmocom.org/7428</a> .<br />Did the same exist in osmo-nitb? If yes we should mention that they shall be removed in the migration to osmo-msc.</p> Cellular Network Infrastructure - Bug #3127 (New): update the [[Osmocom Network In The Box]] wiki...https://osmocom.org/issues/31272018-03-30T14:45:12Zneelsnhofmeyr@sysmocom.de
<p><a class="wiki-page" href="https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In_The_Box">Osmocom Network In The Box</a></p>
<ul>
<li>MGW endpoint management has changed, there is no need to provide the endpoint range with the MGCP clients anymore. Clarify with dexter and edit away the parts concerned with that.</li>
<li>GGSN routing: at the time of writing and until now I'm not a routing/iptables guru. I've since added a '-s 192.168.42.0/24' to my iptables rules to only nat for phones' IP addresses; so that whole topic might be good to review in this wiki page / the GGSN manual. It's not compulsory that we say much about that topic in our docs, but at least make sure we don't actively mislead with my half-knowledge. (BTW, I'm still seeing my nat thwarted when the docker service is running on my machine)</li>
<li>replay the howto 1:1 and see if everything still works, update the attached tar of config files</li>
</ul> Cellular Network Infrastructure - Feature #3047 (New): Test make distcheck and make maintainer-cl...https://osmocom.org/issues/30472018-03-09T13:10:08Zpespin
<p>Recently it was reported that osmo-trx make maintainer-clean was broken (already fixed). We should ideally test these during jenkins build, by adding the following bits to all contrib/jenkin.sh:<br /><pre>
$MAKE distcheck
$MAKE maintainer-clean
</pre></p> Cellular Network Infrastructure - Feature #2909 (New): Document user plane handling with BSC+MSC ...https://osmocom.org/issues/29092018-02-06T01:06:56Zlaforge
<p>We need some kind of documentation on how the new, OsmoMGW-enabled user plane domain looks like. This includes the BSC-colocated OsmoMGW as well as the MSC-colocated OsmoMGW, as well as details on the use of MGCP between the respective call agents and MGW instances.</p>
Non-exhaustive list of topics to include:
<ul>
<li>message sequence charts</li>
<li>diagrams showing netwokr elemetns and control + user plane relationships</li>
<li>dynamic endpoint allocation</li>
<li>outlook on re-integrated support for E1 BTS</li>
<li>name MGCP/MGW related config parameters in BSC and MSC config</li>
<li>outlook on Osmux re-integration</li>
<li>interaction between MNCC signaling and user plane at MSC</li>
<li>outlook on IuUP</li>
</ul>
<p>This is not really a user manual of a given single network element, but a document that describes the relation between the respective elements. Individual sections/chapters could possibly be reused/included into the BSC/MGW/MSC user manuals, but let's have a look at this after having a draft of that document.</p>
<p>Let's also make sure we use any existing bits and pieces from the osmo-mgw manuals (and the ladder diagrams I created there), as well as the wiki and possibly any not-yet-public ladder diagrams dexter might have created in recent months.</p> Cellular Network Infrastructure - Bug #2839 (New): statistics split betwteen 2G and 3Ghttps://osmocom.org/issues/28392018-01-18T20:05:59Zlaforge
<p>many of our statistics/countrs currnetly don't distinguish between 2G and 3G bearer. This means we cannot know how many 2G vs 3G LU we have received in a given period of time, for example.</p> Cellular Network Infrastructure - Feature #2819 (New): migrate to python3https://osmocom.org/issues/28192018-01-07T11:37:27Zmsuraev
<p>Python 2 is scheduked for complete deprecation by upstream in 2 years - <a class="external" href="https://pythonclock.org/">https://pythonclock.org/</a><br />We should migrate all remaining python 2 code to python 3.</p>
<p>The code in osmo-python-tests iscompatible with both python 2 and 3 as of 2f266e0cec10e32db8781a8fb788b0432c33d6d9.</p>
<p>This allows to migrate code which uses it (ctrl and vty tests) to python 3. Once there're no more python 2 code depending on osmo-python-tests, we can drop support for python 2 from osmo-python-tests.</p> Cellular Network Infrastructure - Bug #2791 (New): osmo-python-tests: osmo_ctrl.py: there is no a...https://osmocom.org/issues/27912017-12-28T22:37:24ZlynxisCellular Network Infrastructure - Bug #2640 (New): Debian nightly packages should conflict with d...https://osmocom.org/issues/26402017-11-15T05:49:53Zlaforge
<p>If a user first uses packages from the network:osmocom:nightly feed, and then switches to the network:osmocom:latest feed, we would ideally want a situation where the "nightly" packages conflict with the "latest" ones, as the version numbers and dependencies of "nightly" will not properly work out. This is due to the fact that the source code version numbers are not incremented/tagged on a daily/nightly basis, but only once we tag a new version (which will then create new "latest" packages).</p>
<p>Yes, we know, a skilled user will understand there's a problem and will make sure to properly uninstall any "nightly" packages before installing "latest".</p>
<p>The same should be true for "nightly" vs. the official packages in upstream Debian/Ubuntu.</p>
<p>It's not yet clear how we can achieve this, but it would be great to have it in place. When "latest" or "official" packages are install, all "nightly" packages should be removed due to a conflict in dpkg packaging information.</p> Cellular Network Infrastructure - Feature #2623 (New): SCCP/M3UA: detect restart of osmo-msc and ...https://osmocom.org/issues/26232017-11-07T23:25:36Zneelsnhofmeyr@sysmocom.de
<p>Connecting osmo-bsc and osmo-hnbgw to the MSC and SGSN via an OsmoSTP instance, it is currently not possible to detect that the MSC or SGSN has restarted.</p>
<p>Scenario: using a sysmoBTS as a NITB, change MSC config, restart MSC -- now osmo-bsc happily continues to run and does not even notice that it is an entirely new MSC instance running in the core net now.</p>
<p>In the old days, the SCCPlite link would go down, but since now OsmoSTP is in-between and has no concept of who depends on who, no-one is notifying BSC or HNBGW that MSC or SGSN have gone down. Find out how this is intended to be solved if at all, and devise a way how osmo-bsc will restart and/or reconnect to a new MSC instance, and so forth.</p> Cellular Network Infrastructure - Bug #2620 (New): Testing NITB Migration Guidehttps://osmocom.org/issues/26202017-11-07T16:24:05Zlynxis
<p>Follow the migration guide and try it.</p> Cellular Network Infrastructure - Feature #2558 (In Progress): Scripts to manage thousands of "mo...https://osmocom.org/issues/25582017-10-06T14:53:38Zlaforge
<p>The goal here is to be able to run a network with hundreds of BTSs, several hundreds of TRXs and thousands of MSs from a single command, in order to perform load testing against OsmoBSC.</p>
<p>The scripts should make sure all related processes are started reliably, their termination is recorded, and somehow their result / error / logging is aggregated and reported.</p> Cellular Network Infrastructure - Feature #2554 (New): Reference/Demo setup + documentation for u...https://osmocom.org/issues/25542017-10-06T14:39:27ZlaforgeCellular Network Infrastructure - Feature #2299 (Stalled): osmo-gsm-manuals: reflect split of sep...https://osmocom.org/issues/22992017-05-27T18:24:28Zneelsnhofmeyr@sysmocom.de
<p>After the split of OsmoNITB and separation of openbsc.git to several repositories, we need to adjust the documentation accordingly.</p> Cellular Network Infrastructure - Bug #1921 (New): osmo-gsm-manuals: Purge-MS operation doc error?https://osmocom.org/issues/19212017-01-17T22:46:58Zneelsnhofmeyr@sysmocom.de
<p>In the GSUP docs, currently OsmoSGSN manual 13.4.5 Purge MS,<br />it looks like this is a GSUP message between two SGSNs,<br />but the ladder diagram shows SGSN <-> Network Peer (HLR).</p>
<p>Verify that this should be another SGSN and fix the diagram.</p> Cellular Network Infrastructure - Support #1719 (Stalled): review different 'getting started' gui...https://osmocom.org/issues/17192016-05-17T15:39:32Zlaforge
<p>There are plenty of different guides on how to compile + configure + run an OpenBSC based network. Some related to OsmoTRX based BTSs, some to nanoBTS, some ot E1 based BTSs.</p>
Let's clean this up and divided it into
<ul>
<li>sections that are common among all configurations</li>
<li>sections that are related to a specific BTS hardware (or hardware class)</li>
</ul>
<p>Also clearly indicate that building the software from source is only an optional step and refer to the OBS dpkg nightly builds as preferred method for regular users.</p> Cellular Network Infrastructure - Feature #1700 (Feedback): Document existing statistics/counters...https://osmocom.org/issues/17002016-05-04T14:17:53Zlaforge
<p>there are some statistics/counters available in OsmoNITB, OsmoSGSN, OsmoBTS, OsmoPCU</p>
<p>Please identify all of them and add documentation in the respective user manual.</p> cellmgr-ng - Bug #1664 (New): m3ua connection should make non-blocking connecthttps://osmocom.org/issues/16642016-03-17T10:37:51Zzecke
<p>The M3UA connection is made but the connect may block. This is nothing we want</p>
<pre>
connect(15, {sa_family=AF_INET, sin_port=htons(2905), sin_addr=inet_addr("A.B.C.D")}, 16
</pre>
<p>There should already be examples for non-blocking connect.</p> Cellular Network Infrastructure - Bug #1652 (New): Expose statistics / KPIs programmaticallyhttps://osmocom.org/issues/16522016-03-11T09:42:50Zlaforge
<p>We'd like to expose a number of statistics from the Osmocom network elements in a way how they can be processed programmatically by another program.</p>
<p>The actual interface is TBD. It could maybe re-use the control interface?</p>
<p>The same interface should then be available from all the relevant network elements - with of course the values being dependent on the functionality of the element.</p> Cellular Network Infrastructure - Feature #1590 (New): Extension of Control Interface / external ...https://osmocom.org/issues/15902016-02-23T15:47:47Zlaforge
<p>The request to configure most (or all?) NITB parameters not only by VTY but also via an external SNMP agent via the control interface has come up several times.</p>
<p>The control interface would have to be extended with all relevant (which are those?) parameters.</p>
<p>An external SNMP agent would have to be developed, attaching to the control interface. python snmp might be a good candidate as basis for that.</p>