Open Source Mobile Communications: Newshttps://osmocom.org/https://osmocom.org/favicon.ico?16647414092024-03-19T21:30:40ZOpen Source Mobile Communications
Redmine Osmocom Conferences (OsmoDevCon, OsmoCon, OsmoDevCall) - 2024-03-20: No presentation, just chathttps://osmocom.org/news/2522024-03-19T21:30:40Zlaforge
<p>we're happy to announce the next incarnation of <a class="wiki-page" href="https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall">OsmoDevCall</a>.</p>
<p>This time we don't have a formal presentation; looks like everyone has submitted their topics for the <a class="wiki-page" href="https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2024">OsmoDevCon2024</a> coming up in May ;)</p>
<p>When: <strong>Wednesday, March 20, 2024 from 20:00 CET</strong></p>
<table>
<tr>
<th>Time</th>
<th>Topic</th>
<th>Who</th>
</tr>
<tr>
<td>20:00</td>
<td>Meet and Greet</td>
<td>everyone</td>
</tr>
<tr>
<td>20:10</td>
<td>USSE (Unstructured Supplementary Social Event)</td>
<td>everyone</td>
</tr>
</table>
<p>Where: <a class="external" href="https://osmocom.org/OsmoDevCall">https://osmocom.org/OsmoDevCall</a> (Big Blue Button of <a class="external" href="https://franken.de/">https://franken.de/</a>)</p> libosmo-abis - libosmo-abis 1.4.2 and 1.5.2 patch relaseshttps://osmocom.org/news/2512024-03-16T09:06:05Zfixeria
<p>A critical bug has been discovered in <a class="wiki-page" href="https://osmocom.org/projects/libosmo-abis/wiki/Libosmo-abis">libosmo-abis</a>: the calculation of the TCP keepalive user timeout value was incorrect. This issue remained unnoticed for quite some time, ever since the <a href="https://gerrit.osmocom.org/c/libosmo-abis/+/14565" class="external">initial support for <code>TCP_USER_TIMEOUT</code></a> was merged back in Jun 2019 (libosmo-abis >= 0.7.0). However, since it was not yet enabled by default at that time, only users with explicit TCP keepalive configuration in their config files would be affected. The TCP keepalive was later <a href="https://gerrit.osmocom.org/c/libosmo-abis/+/30280" class="external">enabled by default</a> in Nov 2022 (libosmo-abis >= 1.4.0), impacting all users and resulting in a significantly shorter <code>TCP_USER_TIMEOUT</code> value than expected.</p>
<p>The problem has been <a href="https://gerrit.osmocom.org/c/libosmo-abis/+/36079" class="external">fixed in master</a>. Patch releases tagged for two latest minor versions:</p>
<table>
<tr>
<th>Release</th>
<th>Tag</th>
</tr>
<tr>
<td> 1.4.2 </td>
<td> <a class="external" href="https://gitea.osmocom.org/osmocom/libosmo-abis/releases/tag/1.4.2">https://gitea.osmocom.org/osmocom/libosmo-abis/releases/tag/1.4.2</a> </td>
</tr>
<tr>
<td> 1.5.2 </td>
<td> <a class="external" href="https://gitea.osmocom.org/osmocom/libosmo-abis/releases/tag/1.5.2">https://gitea.osmocom.org/osmocom/libosmo-abis/releases/tag/1.5.2</a> </td>
</tr>
</table>
<p>This issue primarily impacted production users operating IPA connections (A-bis/OML, A-bis/RSL, GSUP) over links with delays with RTT approaching one second, such as overloaded/flakey WiFi links or VSAT back-haul. It is unlikely to have affected users with non-overloaded terrestrial/wired back-haul.</p> Cellular Network Infrastructure - Faster I/O with osmo_io and io_uringhttps://osmocom.org/news/2502024-03-14T17:59:45Zlaforge
<p>Last night we enabled <a class="wiki-page" href="https://osmocom.org/projects/libosmocore/wiki/Osmo_io">osmo_io</a> support in the first major sub-system, <a class="wiki-page" href="https://osmocom.org/projects/libosmo-sccp/wiki">libosmo-sigtran</a> in <em>master</em> of our git repositories. This change mainly affects the A and IuCS/IuPS interfaces in osmo-bsc, osmo-msc, osmo-sgsn, osmo-hnbgw, osmo-smlc and osmo-stp.</p>
<p>Sub-systems that have been ported over to osmo_io can easily switch from classic poll/read/write/readmsg/writemsg/recfrom/sendto/recv/send syscall based I/O to <a href="https://unixism.net/loti/what_is_io_uring.html" class="external"><code>io_uring</code></a>, the modern submission/completion-queue based I/O mechanism of the Linux kernel.</p>
<p>Using the io_uring backend of osmo_io will in turn significantly improve the performance of related osmocom programs under high load, where as much as 40% of the process CPU time is spent in I/O related system calls.</p>
<p>All our <a href="https://jenkins.osmocom.org/jenkins/view/TTCN3/" class="external">usual automatic test suites/jenkins jobs</a> continue to use the default (poll) back-end, while we have a set of new <a href="https://jenkins.osmocom.org/jenkins/view/TTCN3-io_uring/" class="external">jenkins jobs running the same test suites against osmocom-programs with the io_uring backend</a> have been introduced.</p>
<p>We will keep the <a class="wiki-page" href="https://osmocom.org/projects/libosmocore/wiki/Osmo_io">osmo_io</a> wiki page updated with the migration/porting status, as more and more sub-systems / applications / interfaces get ported to it.</p> Retronetworking - 2024-03-06: RetroNetCall on decoding Fax G4 protocol traceshttps://osmocom.org/news/2492024-03-04T08:16:23Zlaforge
<p>We're happy to announce the next incarnation of <a class="wiki-page" href="https://osmocom.org/projects/retronetworking/wiki/RetroNetCall">RetroNetCall</a>, the retronetworking oriented spin-off of <a class="wiki-page" href="https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall">OsmoDevCall</a></p>
<p>This time, <a class="user active" href="https://osmocom.org/users/7">laforge</a> will give a brief look <strong>decoding Telefax G4 protocol traces</strong>, as he recently acquired one of the few G4-capable fax machines, a <a class="wiki-page" href="https://osmocom.org/projects/retronetworking/wiki/Canon_FAX-L260i">Canon_FAX-L260i</a>. G4 is the digital-only version of Telefax that works without a modem, directly over the 64k ISDN B-channel.</p>
<p>We'll look into the ITU-specs of Group 4 Facsimile Service as well as at an actual B-channel protocol trace taken a few days ago.</p>
<p>When: <strong>Wednesday, March 6, 2024 from 20:00 CET</strong></p>
<table>
<tr>
<th>Time</th>
<th>Topic</th>
<th>Who</th>
</tr>
<tr>
<td>20:00</td>
<td>Meet and Greet</td>
<td>everyone</td>
</tr>
<tr>
<td>20:10</td>
<td><em>decoding Telefax G4 protocol traces</em></td>
<td><a class="user active" href="https://osmocom.org/users/7">laforge</a></td>
</tr>
<tr>
<td>21:00</td>
<td>USSE (Unstructured Supplementary Social Event)</td>
<td>everyone</td>
</tr>
</table>
<p>Where: <a class="external" href="https://osmocom.org/RetroNetCall">https://osmocom.org/RetroNetCall</a> (Big Blue Button of <a class="external" href="https://franken.de/">https://franken.de/</a>)</p> Osmocom Conferences (OsmoDevCon, OsmoCon, OsmoDevCall) - 2024-02-21: OsmoDevCon2024 Q&A; brief eS...https://osmocom.org/news/2482024-02-20T13:09:33Zlaforge
<p>we're happy to announce the next incarnation of <a class="wiki-page" href="https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall">OsmoDevCall</a>.</p>
<p>This time we don't have a formal presentation; however, <a class="user active" href="https://osmocom.org/users/7">laforge</a> is able to answer any questions regarding the just-announced <a class="wiki-page" href="https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2024">OsmoDevCon2024</a> and give a brief update on the eSIM and eUICC work.</p>
<p>When: <strong>Wednesday, February 21, 2024 from 20:00 CET</strong></p>
<table>
<tr>
<th>Time</th>
<th>Topic</th>
<th>Who</th>
</tr>
<tr>
<td>20:00</td>
<td>Meet and Greet</td>
<td>everyone</td>
</tr>
<tr>
<td>20:10</td>
<td><em>Brief update on eSIM + eUICC work</em></td>
<td><a class="user active" href="https://osmocom.org/users/7">laforge</a></td>
</tr>
<tr>
<td>20:25</td>
<td><em>OsmoDevCon Q&A (as needed)</em></td>
<td><a class="user active" href="https://osmocom.org/users/7">laforge</a></td>
</tr>
<tr>
<td>20:35</td>
<td>USSE (Unstructured Supplementary Social Event)</td>
<td>everyone</td>
</tr>
</table>
<p>Where: <a class="external" href="https://osmocom.org/OsmoDevCall">https://osmocom.org/OsmoDevCall</a> (Big Blue Button of <a class="external" href="https://franken.de/">https://franken.de/</a>)</p> Osmocom Conferences (OsmoDevCon, OsmoCon, OsmoDevCall) - OsmoDevCon 2024 Registration + CfPhttps://osmocom.org/news/2472024-02-19T21:45:39Zlaforge
<p>After several years of break since the COVID-19 pandemic hit, it is my great pleasure to finally announce <a class="wiki-page" href="https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2024">OsmoDevCon2024</a>, our (previously annual) Osmocom Developer Conference <em>for developers, by developers</em>.</p>
<p>The conference is held <strong>May 3rd through May 6th</strong> at the <a href="https://berlin.vandervalk.de" class="external">Van der Valk Hotel Berlin/Brandenburg</a> conference hotel.</p>
<p>Contrary to our past OsmoDevCons (which have all been rather low budget, grass roots events), laforge felt that particularly after the long COVID-related break, it would be nice to do something slightly more fancy: Stay together with the entire group for four days, in a conference hotel.</p>
<p>sysmocom (and hopefully soon other) sponsors will cover the accomodation and conference cost for any volunteers contributing to Osmocom only in their spare time.</p>
<p>If you have contributed to Osmocom projects in the past (writing code, funding, documentation, packaging or related activities) you are eligible to attend. <strong>Please register no later than March 1st on the <a class="wiki-page" href="https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2024">OsmoDevCon2024</a> wiki page!</strong></p>
<p>At the same time, the <a href="https://pretalx.sysmocom.de/osmodevcon2024/cfp" class="external">Call for Proposals</a> is open: I'm sure after several years of a break, everyone must have hacked on (or learned about) many exciting things they would like to share. Any and all proposals are greatly aprreciated. Please don't wait too long so we can put together a draft schedule ASAP.</p> Cellular Network Infrastructure - Binary packages for CentOS 8/AlmaLinux 8 are unmaintainedhttps://osmocom.org/news/2462024-02-14T15:29:02Zosmith
<p>Maintenance of binary packages for CentOS 8 (and compatible distributions, such as AlmaLinux 8) had been funded by <a href="https://www.sysmocom.de/" class="external">sysmocom</a> customers in the past.</p>
This is no longer the case, so we are making the following changes:
<ul>
<li>Patches submitted to gerrit are not building/running regression tests on CentOS 8 anymore.</li>
<li>CentOS 8 binary packages are not tested with our TTCN-3 testsuites anymore on jenkins.osmocom.org.</li>
<li>The daily test that ensures CentOS 8 packages can be installed without conflicts, and Osmocom daemons are running as expected, gets disabled.</li>
</ul>
<p>We will keep the binary packages of CentOS 8 as long as they build fine, but will disable individual packages if they fail to build instead of spending resources on fixing them.</p>
If you are interested in keeping the CentOS 8 packages maintained, contact us as follows:
<ul>
<li>If you would like to fund maintenance of the packages: <a class="email" href="mailto:sales@sysmocom.de">sales@sysmocom.de</a></li>
<li>If you would like to help maintain the packages: <a href="https://osmocom.org/projects/cellular-infrastructure/wiki/IRC_Channel" class="external">IRC</a></li>
</ul> Retronetworking - 2024-02-07: RetroNetCall (no presentation)https://osmocom.org/news/2452024-02-06T18:46:03Zlaforge
<p>We're happy to announce the next incarnation of <a class="wiki-page" href="https://osmocom.org/projects/retronetworking/wiki/RetroNetCall">RetroNetCall</a>, the retronetworking oriented spin-off of <a class="wiki-page" href="https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall">OsmoDevCall</a></p>
<p>This time, there's (again)no formal presentation - just friendly folks hanging out to chat about ancient communications technology.</p>
<p>When: <strong>Wednesday, February 7, 2024 from 20:00 CET</strong></p>
<p>Where: <a class="external" href="https://osmocom.org/RetroNetCall">https://osmocom.org/RetroNetCall</a> (Big Blue Button of <a class="external" href="https://franken.de/">https://franken.de/</a>)</p> OsmocomBB - CSD (Circuit Switched Data) supporthttps://osmocom.org/news/2442024-01-26T22:44:30Zfixeria
<p>We're happy to announce that osmocom-bb now supports <a href="https://en.wikipedia.org/wiki/Circuit_Switched_Data" class="external">Circuit Switched Data</a> calls (see <a class="issue tracker-2 status-3 priority-2 priority-default closed" title="Feature: Circuit Switched Data (CSD) Support in osmocom-bb (Resolved)" href="https://osmocom.org/issues/4396">#4396</a>).<br />It's not 100% complete, there are bugs and missing features (see <a class="issue tracker-2 status-1 priority-2 priority-default" title="Feature: mobile: support data calls @ 14400 bps (TCH/F14.4) (New)" href="https://osmocom.org/issues/6346">#6346</a>, <a class="issue tracker-2 status-1 priority-2 priority-default" title="Feature: mobile: support data calls @ 300 bps and 1200/75 bps (TCH/[FH]2.4) (New)" href="https://osmocom.org/issues/6347">#6347</a>), but it's mature enough to do async transparent data calls.<br />See <a class="wiki-page" href="https://osmocom.org/projects/baseband/wiki/CSD">CSD</a> for more details on the call establishment procedures and the necessary configuration.</p> Osmocom Conferences (OsmoDevCon, OsmoCon, OsmoDevCall) - 2024-01-17: Exploring eUICC and eSIM usi...https://osmocom.org/news/2432024-01-15T09:54:59Zlaforge
<p>we're happy to announce the next incarnation of <a class="wiki-page" href="https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall">OsmoDevCall</a>.</p>
<p>This time, <a class="user active" href="https://osmocom.org/users/7">laforge</a> will be presenting on <strong>Exploring eUICC and eSIM using pySim, lpac and osmo-smdpp</strong></p>
<p>When: <strong>Wednesday, January 17, 2024 from 20:00 CET</strong></p>
<table>
<tr>
<th>Time</th>
<th>Topic</th>
<th>Who</th>
</tr>
<tr>
<td>20:00</td>
<td>Meet and Greet</td>
<td>everyone</td>
</tr>
<tr>
<td>20:10</td>
<td><em>Exploring eUICC and eSIM using pySim, lpac and osmo-smdpp</em></td>
<td><a class="user active" href="https://osmocom.org/users/7">laforge</a></td>
</tr>
<tr>
<td>21:00</td>
<td>USSE (Unstructured Supplementary Social Event)</td>
<td>everyone</td>
</tr>
</table>
<p>Where: <a class="external" href="https://osmocom.org/OsmoDevCall">https://osmocom.org/OsmoDevCall</a> (Big Blue Button of <a class="external" href="https://franken.de/">https://franken.de/</a>)</p>