Project

General

Profile

News

libosmocore: libosmocore 1.9.3 patch relase

Added by laforge 16 days ago

Today we've released the libosmocore 1.9.3 patch release.

The only changes are to libosmosim, fixing two issues related to the transport of GlobalPlatform APDUs in cardem / osmo-remsim use cases which appeared when using M2M eUICCs with osmo-remsim.

The changelog over 1.9.0 is as follows:

libosmocore (1.9.3) unstable; urgency=medium

  * libosmosim: class_tables: Resolve conflicting CLA=8x INS=F2 definitions
  * libosmosim: class_tables: Fix GlobalPlatform CLA=8x INS=CA/CB GET DATA

 -- Harald Welte <laforge@osmocom.org>  Thu, 06 Jun 2024 19:40:40 +0200

libosmocore (1.9.2) unstable; urgency=medium

  [ Pau Espin Pedrol ]
  * sockaddr_str.h Fix OSMO_SOCKADDR_STR_FMT_ARGS_NOT_NULL syntax error

  [ Daniel Willmann ]
  * logging_gsmtap: Temporarily disable logging when sending the logs
  * Disable uring when building for embedded

 -- Oliver Smith <osmith@sysmocom.de>  Tue, 28 Nov 2023 12:59:15 +0100

libosmocore (1.9.1) unstable; urgency=medium

  [ Manawyrm ]
  * logging: ensure ANSI color escape is sent in same line/before newline

 -- Oliver Smith <osmith@sysmocom.de>  Tue, 28 Nov 2023 11:21:41 +0100

Retronetworking: 2024-06-05: RetroNetCall: Nokia TCSM2 Initial examination

Added by laforge 18 days ago

We're happy to announce the next incarnation of RetroNetCall, the retronetworking oriented spin-off of OsmoDevCall

This time, we have the first part of a series of presentations by falconia on classic circuit-switched GSM TRAU (Transcoder and Rate Adaption Unit): Nokia TCSM2, a bank of TRAUs with E1 interfaces: Part 1, initial examination of the hardware

When: Wednesday, June 5, 2024 from 20:00 CEST (summer time now)

Time Topic Who
20:00 Meet and Greet everyone
20:10 Nokia TCSM2, a bank of TRAUs with E1 interfaces: Part 1, initial examination of the hardware falconia
21:00 USSE (Unstructured Supplementary Social Event) everyone

libsmpp34: libsmpp34 1.14.4 release

Added by osmith 26 days ago

Today we've released libsmpp34 1.14.4.

The changelog over 1.14.0 is as follows:

libsmpp34 (1.14.4) unstable; urgency=medium

  [ Vadim Yanitskiy ]
  * fix warnings about implicit declaration of strtol()
  * build: include git-version-gen into the release tarball

  [ Oliver Smith ]
  * contrib: remove rpm spec file

 -- Oliver Smith <osmith@sysmocom.de>  Mon, 27 May 2024 11:16:01 +0200

libsmpp34 (1.14.3) unstable; urgency=medium

  [ Vadim Yanitskiy ]
  * binaries/Makefile.am: libraries shall not be in AM_LDFLAGS

  [ Oliver Smith ]
  * debian: set compat level to 10

 -- Pau Espin Pedrol <pespin@sysmocom.de>  Tue, 12 Sep 2023 12:40:43 +0200

libsmpp34 (1.14.2) unstable; urgency=medium

  [ Vadim Yanitskiy ]
  * README.md: fix copy-paste: s/libosmocore/libsmpp34/
  * update git URLs (git -> https; gitea)
  * Makefile.am, configure.ac: fix autoreconf related warnings
  * contrib/jenkins.sh: actually build with $PARALLEL_MAKE

  [ Max ]
  * cosmetic: make linter happy
  * Add #define for default SMPP port 2775

  [ Harald Welte ]
  * test_apps: Fix compilation of example smsc code
  * Add -Werror=implicit-int -Werror=int-conversion -Werror=old-style-definition

 -- Pau Espin Pedrol <pespin@sysmocom.de>  Tue, 07 Feb 2023 14:28:28 +0100

libsmpp34 (1.14.1) unstable; urgency=medium

  [ Eric ]
  * configure.ac: fix libtool issue  with clang and sanitizer

  [ Oliver Smith ]
  * contrib: import RPM spec
  * contrib: integrate RPM spec
  * Makefile.am: EXTRA_DIST: debian, contrib/*.spec.in

  [ Vadim Yanitskiy ]
  * debian/control: change maintainer to the Osmocom team / mailing list

  [ Pau Espin Pedrol ]
  * .gitignore: Ignore new autofoo tmp files

 -- Pau Espin Pedrol <pespin@sysmocom.de>  Tue, 23 Feb 2021 18:00:48 +0100

OsmoTRX: osmo-trx 1.6.2 release

Added by osmith about 2 months ago

Today we've released osmo-trx 1.6.2.

The changelog over 1.6.0 is as follows:

osmo-trx (1.6.2) unstable; urgency=medium

  [ Harald Welte ]
  * osmo-trx-uhd: Make sure HOME environment variable is set

  [ Vadim Yanitskiy ]
  * doc/examples: fix missing config files in release tarballs

 -- Oliver Smith <osmith@sysmocom.de>  Wed, 08 May 2024 10:04:43 +0200

osmo-trx (1.6.1) unstable; urgency=medium

  [ Eric Wild ]
  * devices: fix wrong gain to power mapping

 -- Eric Wild <ewild@sysmocom.de>  Thu, 09 Nov 2023 14:16:21 +0200

Cellular Network Infrastructure: Removal of official RPM packages

Added by osmith about 2 months ago

As announced previously, the rpm binary packages for CentOS 8 / AlmaLinux 8 are unmaintained.
There were also binary packages for openSUSE Tumbleweed in the Osmocom OBS, but these had no further testing besides making sure that they build.

sysmocom was still ensuring that the rpm binary packages build from the rpm spec files in our own git repositories. But this
is also significant effort that we would rather spend elsewhere, and so we decided to stop providing rpm builds altogether
and that we will remove the spec files from the git repositories.

A separate set of rpm binary packages and spec files are maintained by Martin Hauke in the openSUSE OBS instance:

Cellular Network Infrastructure: Binary package feeds for Ubuntu 24.04

Added by osmith 2 months ago

The Osmocom project is now offering binary package feeds for the upcoming Ubuntu 24.04 release, for both:

For more information check the related pages linked above.

Binary packages for Ubuntu 20.04 are no longer available. See Linux Distributions for how long we plan to keep binary package repositories active.

Retronetworking: 2024-04-03: RetroNetCall: DIVF dialplan debugging

Added by laforge 3 months ago

We're happy to announce the next incarnation of RetroNetCall, the retronetworking oriented spin-off of OsmoDevCall

This time, we won't have a presentation but intead a joint, collaborative session where we're analyzing and debugging any potentially remaining issues with the dial plan of divf.retronetworking.org, our central soft-switch of the OCTOI community TDMoIP network. Participants are invited to try making certain calls and we will look at logs/traces and see what we can fix or improve.

When: Wednesday, April 3, 2024 from 20:00 CEST (summer time now)

Time Topic Who
20:00 Meet and Greet everyone
20:10 interactive DIVF dialplan debugging laforge
21:00 USSE (Unstructured Supplementary Social Event) everyone

Where: https://osmocom.org/RetroNetCall (Big Blue Button of https://franken.de/)

Osmocom Conferences (OsmoDevCon, OsmoCon, OsmoDevCall): 2024-03-20: No presentation, just chat

Added by laforge 3 months ago

we're happy to announce the next incarnation of OsmoDevCall.

This time we don't have a formal presentation; looks like everyone has submitted their topics for the OsmoDevCon2024 coming up in May ;)

When: Wednesday, March 20, 2024 from 20:00 CET

Time Topic Who
20:00 Meet and Greet everyone
20:10 USSE (Unstructured Supplementary Social Event) everyone

Where: https://osmocom.org/OsmoDevCall (Big Blue Button of https://franken.de/)

libosmo-abis: libosmo-abis 1.4.2 and 1.5.2 patch relases

Added by fixeria 3 months ago

A critical bug has been discovered in libosmo-abis: the calculation of the TCP keepalive user timeout value was incorrect. This issue remained unnoticed for quite some time, ever since the initial support for TCP_USER_TIMEOUT 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 enabled by default in Nov 2022 (libosmo-abis >= 1.4.0), impacting all users and resulting in a significantly shorter TCP_USER_TIMEOUT value than expected.

The problem has been fixed in master. Patch releases tagged for two latest minor versions:

Release Tag
1.4.2 https://gitea.osmocom.org/osmocom/libosmo-abis/releases/tag/1.4.2
1.5.2 https://gitea.osmocom.org/osmocom/libosmo-abis/releases/tag/1.5.2

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.

(1-10/253)

Also available in: Atom

Add picture from clipboard (Maximum size: 48.8 MB)