Open Source Mobile Communications: Issues 2020-01-23T21:21:16Z Open Source Mobile Communications Redmine Cellular Network Infrastructure - Feature #4376 (New): Define distinct X timer numbers across all... 2020-01-23T21:21:16Z neels <p>Using osmo_tdef API, we are managing various 3GPP defined T timer numbers (like "T3203")<br />To add our own timers, we're using X timers (like "X1234").<br />We should best choose globally distinct X timer numbers for every program and every use.<br />So far we're seeing a collision of e.g. X1, X2 to mean different things according to context.<br />That would be fine and is manageable, but it also wouldn't be much of a problem to choose distinct number spaces.</p> <p>Create a wiki page like <a class="wiki-page" href="">Port Numbers</a> for X timers (and maybe also for T timers we have implemented, while at it)<br />and possibly fix current duplication in recently added X timer numbers</p> Cellular Network Infrastructure - Bug #4141 (New): No osmux specific code in place during codec n... 2019-08-05T15:57:19Z pespin <p>Current code in OsmoBSC and OsmoMSC doesn't take into account that Osmux is to be used when codec negotiation goes one. That means that supported codec list needs to be correctly configured manually in VTY in order to avoid selecting incorrect codecs (like non-AMR). Moreover if an MS doesn't support AMR, since we don't have transcoding yet, the call cannot take place.</p> <p>Different scenarios need to be listed here and think about what we want to do in each case.</p> Cellular Network Infrastructure - Bug #4139 (New): "make pdf" target exists, but does nothing 2019-08-02T08:33:47Z osmith <p>There is a default "pdf" target, so tab-completion will suggest it and of course people expect it to build the pdf manuals. But currently it just does nothing. We could override it for all projects with this in the topdir<br /><pre> pdf: if BUILD_MANUALS $(MAKE) -C doc/manuals else $(info ---) $(info ERROR: manuals disabled, try './configure --enable-manuals'.) $(info ---) @exit 1 endif </pre></p> Cellular Network Infrastructure - Bug #4131 (Stalled): osmo-gsm-manuals: Use leveloffset attribut... 2019-07-26T13:04:49Z pespin <p>Right now, all documents under osmo-gsm-manuals.git/commons/ start with title level 1 (==). However, if one wishes to add a document with level 2 (===) so it can also be included in other repository document, it will make osmo-gsm-manuals.git "make check" fail due to osmo-gsm-manuals/tests/<br /><pre> echo "include::$${chapter}[]" &gt;&gt; $@; \ </pre></p> <p>Which includes stuff under a test document with level 0 (=). If a document with level different than 1 (==) is added, then it will fail on some versions (like jenkins):<br /><pre> "asciidoc: WARNING: mgcp_extension_osmux.adoc: line 2: section title out of sequence: expected level 1, got level 2" </pre></p> <p>See for instance commit osmo-gsm-manuals.git 061cca4d7345bc4f496324d0b4d30bc51e1f8d23, which had to be fixed up later.</p> <p>The solution here is to use "leveloffset" attribute. To make our life easier in the future, we need to move all documents under common/ to start with level 0 (=), and then use "leveloffset" on all includes in all other repositories using them. This way same document can easily be added on different levels on different documents.</p> <p>Important! It seems this syntax doesn't work for me:<br /><pre> include::chapter2.adoc[leveloffset=+1] </pre></p> <p>However, this does and it's basically the same:<br /><pre> :leveloffset: 1 include::chapter1.adoc[] :leveloffset: 0 </pre></p> <p>Related information:<br /><a class="external" href=""></a><br /><a class="external" href=""></a><br /><a class="external" href=""></a></p> Cellular Network Infrastructure - Feature #4109 (New): debian-repo-install-test: start a virtual ... 2019-07-16T12:36:01Z osmith <p>We could extend <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: no automatic testing of Debian/Ubuntu packages (Resolved)" href="">#3369</a> (which made debian-repo-install-test start up all systemd services of Osmocom programs) to also start a virtual mobile subscriber (phone) and do a location update.</p> Cellular Network Infrastructure - Bug #4108 (New): osmo-ctrl2cgi, osmo-trap2cgi: missing default ... 2019-07-16T12:30:11Z osmith <p>Default configs for osmo-ctrl2cgi and osmo-trap2cgi do not get installed in the debian packages. Therefore the systemd services don't work out of the box.</p> <p>Both programs are part of osmo-python-tests.git.</p> <p>I'm setting this to low priority as I think that the programs are not widely used.</p> Cellular Network Infrastructure - Bug #4069 (New): Implement IPA PING/PONG mechanism everywhere 2019-06-21T14:44:02Z laforge <p>As was seen in <a class="issue tracker-1 status-5 priority-3 priority-high3 closed" title="Bug: Prolonged remaining in state with RSL link gone, OML link open (Closed)" href="">#4061</a>, we're not doing a good job in closing connections if they're dead. Let's improve this situation by implementing an IPA PING sender / PONG receiver which closes+reconnects (client) or simply closes (server) the respective connection.</p> <p>I recently added ipa_keepalive_fsm_start to libosmo-abis. It's used only in osmo-remsim,<br />but should probably be used by virtually any of our programs that implement IPA<br />multiplex, starting from BTS (Abis), BSC (Abis), MSC (SCCPlite, GSUP), HLR (GSUP),<br />all our CTRL interfaces, ... - but anything beyond RSL+OML in BTS+BSC is out of scope for this<br />ticket. I'll add separate tickets about this.</p> <p>Whether or not that specific FSM is used: The IPA PING/PONG logic should exist everywhere.</p> Cellular Network Infrastructure - Feature #4063 (New): Add current version information to the VTY... 2019-06-19T09:51:43Z daniel <p>Currently the only version information in the vty reference manuals is the revision history that needs to be updated manually.</p> <p>This info resides in doc/manuals/*-vty-reference.xml</p> <p>We now have a script to regenerate the actual vty reference (in doc/manuals/vty/*_vty_reference.xml) so updating the revision information should be automated as well.<br />I don't think using the revision history field in docbook makes sense for this task - at least not adding an entry for every change/commit. Maybe we just want to use one revision entry and update that to the date of the commit and use the git describe string of the commit as the revnumber.</p> <p>That way it is at least clear which version this documentation belongs to.</p> Cellular Network Infrastructure - Bug #3753 (New): Update .deb to use dh_missing 2019-01-09T13:36:05Z msuraev <p>While building .deb for libosmocore following warning was observed:<br /><pre> sed -i "/dependency_libs/ s/'.*'/''/" `find . -name '*.la'` dh_install dh_install: Please use dh_missing --list-missing/--fail-missing instead dh_install: This feature will be removed in compat 12. </pre></p> <p>We should follow this recommendation and update our packaging before compat 12 becomes mainstream. We should also check other Osmocom .deb packages because they might have similar issues.</p> Cellular Network Infrastructure - Bug #3725 (Stalled): Jenkins isn't using the credentials store ... 2018-12-12T13:57:52Z osmith <p>The jenkins jobs generated by osmo-ci.git/jobs/master-buils.yml need to be able to upload artifacts to (generated PDF manuals, generated firmware files).<br />Right now, we have the SSH keys of each build slave configured in the authorized_keys of, but that does obviously not scale.</p> <p>laforge wrote in <a class="issue tracker-1 status-3 priority-3 priority-high3 closed" title="Bug: Jenkins can&#39;t upload to (Resolved)" href="">#3720</a>:</p> <blockquote> <p>The proper solution is to use the jenkins server credentials store, which will hold the private key and provision it to the client via ssh-agent. That way the client can upload to the server, and no per-slave configuration is required on the ftp server.</p> </blockquote> <p>Some of the scripts that require the SSH keys are running in docker. Right now we are mounting ~/.ssh in the containers, using the ssh-agent should be possible when mounting the socket and passing the environment variable:</p> <pre> docker run --rm -it --name container_name \ -v $(dirname $SSH_AUTH_SOCK):$(dirname $SSH_AUTH_SOCK) \ -e SSH_AUTH_SOCK=$SSH_AUTH_SOCK my_image </pre> <p>(<a href="" class="external">found here</a>)</p> Cellular Network Infrastructure - Bug #3694 (New): Fix lintian warnings in .deb packages 2018-11-14T14:27:44Z msuraev <p>There's a nice overview page with links to lintian errors/warnings for all the packages currently in Debian:<br /><a class="external" href=""></a><br />This gives a nice overview of what could be improved in our packages. Some of those are rather trivial to fix, others will require more work.</p> Cellular Network Infrastructure - Bug #3660 (Stalled): TTCN3 Jenkins jobs leave Docker containers... 2018-10-17T09:26:36Z osmith <p>The scripts start multiple containers and stops them at the end of the script. When aborting a job with the web interface, the script gets killed and can not do the clean up part. <a href="" class="external">Jenkins kills all child processes</a>, but not the containers as they get spawned by the docker daemon.</p> Ideas to resolve this: <ul> <li>open a bug report at Jenkins to not kill processes with -9 in a bug report, then wait for a stable release with the fix, then implement clean up on receiving SIGABRT in</li> <li>try out the <a href="" class="external">PostBuildScript Plugin</a> (or <a href="" class="external">Post build task</a>, that <a href="" class="external">should work</a> for sure), see if they allow executing code on abort of the job</li> <li>try to attach the environment variable that jenkins is using to decide which processes will be killed (see link above) to the processes in the Docker containers</li> </ul> Cellular Modem Information - Feature #3658 (New): Create a "osmocom-bb-host-latest" docker container 2018-10-16T14:11:32Z osmith <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 #3628 (New): document nanoBTS calibration procedure usi... 2018-10-04T11:13:31Z laforge <p>The nanoBTS has the capability to OCXO calibration against another (macro) BTS. We had implemented this in ipaccess-config, but we apparently never documented how it works.</p> <p>Let's add it somewhere to the nanoBTS related wiki pages.</p> <p>Without trying, I remember that it was part of the "Tests" that can be triggered via OML.</p> <pre> static const struct value_string test_names[] = { »·······{ NM_IPACC_TESTNO_CHAN_USAGE, "Channel Usage" }, »·······{ NM_IPACC_TESTNO_BCCH_CHAN_USAGE, "BCCH Channel Usage" }, »·······{ NM_IPACC_TESTNO_FREQ_SYNC, "Frequency Synchronization" }, »·······{ NM_IPACC_TESTNO_BCCH_INFO, "BCCH Info" }, »·······{ NM_IPACC_TESTNO_TX_BEACON, "Transmit Beacon" }, »·······{ NM_IPACC_TESTNO_SYSINFO_MONITOR, "System Info Monitor" }, »·······{ NM_IPACC_TESTNO_BCCCH_MONITOR, "BCCH Monitor" }, </pre> <p>I think you start with a CHAN_USAGE to see the receive level per ARFCN. You then proceed to a FREQ_SYNC to see which of those have a FCCH (and hence are BCCH/CCCH carrying).</p> Cellular Network Infrastructure - Bug #3567 (New): coverity: move the secret token out of $HOME/o... 2018-09-18T15:34:10Z lynxis <p>When the token has been moved, the jenkins Coverity job is independent from the static path $HOME/osmo-ci.</p> Cellular Network Infrastructure - Feature #3477 (New): add a wiki page explaining interconnection... 2018-08-20T09:21:37Z neels <p>The <a class="wiki-page" href="">Osmocom Network In The Box</a> wiki page explains running components on the same machine.<br />As soon as this is split up between several boxes, numerous config items become necessary to set bind-addresses and remote addresses.<br />Each user manual should explain this, but it would also be nice to have a common wiki page guiding through this process.</p> Cellular Network Infrastructure - Bug #3417 (New): show asciidoc counters does not show all the c... 2018-07-25T07:01:29Z daniel <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 - Bug #3382 (New): Investigate and fix lintian issues listed by D... 2018-07-05T11:37:34Z pespin <p>This web page lists a list of warnings which we may want to fix: <a class="external" href=""></a></p> Cellular Network Infrastructure - Feature #3229 (New): build-system: Improve debian ... 2018-05-03T12:40:28Z pespin <p>The idea is to add extra tests/checks to avoid breaking debian package building during nightly builds in OBS. Instead, let's catch it during gerrit patch submission time and don't allow merging it until it's fixed.</p> <p>We should investigate several tools, like pbuilder, dpkg-build, etc. I recall lynxis also told me something about some kind of lint tool available for this purposes.</p> Cellular Network Infrastructure - Bug #3192 (New): meas_vis: use the lchan identity as primary ke... 2018-04-21T19:21:40Z neels <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="">#2968</a> <a class="issue tracker-2 status-1 priority-1 priority-lowest" title="Feature: obtain and store subscriber identity (New)" href="">#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="">#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... 2018-04-14T12:47:52Z laforge <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 - Bug #3127 (New): update the [[Osmocom Network In The Box]] wiki... 2018-03-30T14:45:12Z neels <p><a class="wiki-page" href="">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' 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 - Bug #2839 (New): statistics split betwteen 2G and 3G 2018-01-18T20:05:59Z laforge <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 - Bug #2728 (Stalled): Align better with 48.103 for AoIP user pla... 2017-12-09T10:34:19Z laforge <p>In most aspects we seem to do what 48.103 States. However, e.g. our payload types for RTP differ from whats specified there. Also not sure aboiut Details oft MARKER behavior and behavior with regard to lost frames on radio interface.</p> Cellular Network Infrastructure - Feature #2451 (New): Add static builds to jenkins jobs 2017-08-18T10:51:23Z msuraev <p>Right now most (all?) Osmocom projects support static builds which is sometimes useful for testing and deployment in particular environments.</p> <p>However, in the absence of per-commit tests it can be easily broken as an unintended side-effect of some patches.</p> <p>We should add "--enable-static" test builds to the corresponding jenkins jobs to avoid breaking it.</p> Cellular Network Infrastructure - Feature #2011 (New): clean-up / merge IPA (and IPA CCM) code of... 2017-04-15T12:54:09Z laforge <p>There are bits and pieces of code supporting different features of the IPA protocol, particularly the CCM part of it distributed over various osmocom projects:</p> <ul> <li>libosmocore (src/gsm/ipa.c)</li> <li>libosmo-abis (src/input/ipa.c, src/input/ipaccess.c)</li> <li>libosmo-netif (src/ipa.c, src/ipa_unit.c)</li> <li>openbsc (in osmo-bsc and osmo-bsc_nat (at the very least, but also ipaccess-proxy and of course abisip-find)</li> <li>osmo-bts (sysmobts_mgr_nl.c)</li> </ul> <p>We should sit down and clean this mess up. There should be one parser and one encoder for IPA and CCM messages, which can be used by all the various code bases.</p> Cellular Network Infrastructure - Feature #1863 (New): check max_power_red vty command 2016-11-29T16:38:51Z neels <p>check that the manual accurately documents max_power_red config command,<br />and verify that it complains about values that are uneven numbers.</p> cellmgr-ng - Bug #1664 (New): m3ua connection should make non-blocking connect 2016-03-17T10:37:51Z zecke <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 programmatically 2016-03-11T09:42:50Z laforge <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 - Bug #1612 (New): more configuration consistency checking 2016-02-23T16:22:14Z laforge <p>Right now it is possible to configure various things that wouldn't work, like an ARFCN that is outside the band of the BTS, or even the TRX.</p> <p>More consistency checks would make sense, together with reasonable error messages.</p>