OpenBSC January 2026

openbsc@lists.osmocom.org

23 participants
29 discussions

How to Play and Experience Heardle: A Musical Challenge
by subtle.carp.skco＠protectsmail.net 25 Mar '26

25 Mar '26

Are you ready to put your music knowledge to the test? If you love games that challenge your memory and quick thinking, you’ll enjoy Heardle. This addictive game invites players to guess a song based on short audio clips, making it a delightful experience for music lovers and casual gamers alike. Either alone or with friends, Heardle can provide a fun and engaging way to connect through music. https://heardlefree.com/ Gameplay The aim of Heardle is simple: guess the song title using limited audio clues. When you begin, the game plays an initial snippet of a song—typically just a few seconds long. From there, players have six attempts to guess the correct title. Each incorrect guess prompts an additional segment of the song to be revealed, gradually giving you a better chance at making your correct guess. To start playing, visit Heardle, where you’ll find a user-friendly interface. Upon loading, you will be greeted with a "Play" button to kick off the challenge. Once you’ve made your guesses, the game provides immediate feedback, telling you whether your guess was correct and, if not, allowing you to try again until you either guess the song or run out of attempts. Heardle has a different song each day, keeping the experience fresh. There’s no way to repeat a level, which means every day offers a new challenge and a new chance to flex those musical muscles. Tips for Playing Know Your Genres: If you have a favorite genre of music, use that to your advantage! Often, the daily song will belong to a familiar genre, so leverage your own taste to narrow down your guesses. Pay Attention to Context: Sometimes the first snippet might give away an artist or specific musical characteristic—like a distinctive guitar riff or vocal style. Listen closely and let those nuances guide your guesses. Use a Process of Elimination: If you’re unsure but have a few songs in mind, start guessing songs you’re relatively sure of. As you hear more of the song, you can refine your guesses based on the additional snippets. Play with Friends: Heardle can be even more fun when played with friends. Compete to see who can guess the song first or who can guess it in the least attempts. This also adds a social aspect to your gameplay, making it a shared challenge. Practice Regularly: Like any skill, getting better at Heardle takes practice. The more you play, the more familiar you become with popular tracks, artists, and styles, enabling you to make quicker guesses down the road. Conclusion Heardle is not just an entertaining game; it’s also a fantastic way to engage with music on a daily basis. Whether you're a casual listener or a seasoned aficionado, the thrill of uncovering a song you love creates an exciting experience each day. With its engaging format and user-friendly interface, Heardle is a must-try for anyone looking to challenge their musical knowledge. So grab your headphones, gather your friends, and see who can guess the daily hit first! Remember to enjoy the process and celebrate those musical memories, one note at a time. Happy playing!

2 1

OsmoTRX+B205mini crashes when having another USB device on a different port
by JPichel 20 Mar '26

20 Mar '26

Hello everyone, I am experiencing problems when trying to run osmotrx with a b205mini and I connect another USB device to a different port on the machine. When I do this, osmotrx crashes instantly. Also, when I have the other device already plugged in when I start osmotrx, it takes ~20 seconds to crash. Sometimes it just crashes without giving a reason, like here: DLGLOBAL NOTICE Setting SCHED_RR priority 18 (cpu_sched_vty.c:471) DLGLOBAL NOTICE Setting SCHED_RR priority 18 (cpu_sched_vty.c:471) DLGLOBAL NOTICE Available via telnet 127.0.0.1 4237 (telnet_interface.c:88) DLCTRL NOTICE CTRL at 127.0.0.1 4236 (control_if.c:1024) [INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107400; UHD_4.1.0.5-3 DMAIN NOTICE -- Transceiver active with 1 channel(s) (osmo-trx.cpp:621) DLSTATS NOTICE Stats timer expire_count=7: We missed 6 timers (stats.c:169) DLGLOBAL NOTICE Stats timer expire_count=31: We missed 30 timers (rate_ctr.c:350) DTRXCTRL NOTICE Changing TSC from 0 to 7 (Transceiver.cpp:1032) DTRXCTRL NOTICE [chan=0] switching to TRXD version 1 (Transceiver.cpp:1059) DMAIN NOTICE Starting the transceiver (Transceiver.cpp:287) LLDTRXCLK NOTICE Sending CLOCK indications (Transceiver.cpp:1198) UDDEV ERROR No packet received, implementation timed-out (UHDDevice.cpp:782) DDEV FATAL UHD: Receive timed out (UHDDevice.cpp:786) DMAIN FATAL Receive error 0 (radioInterface.cpp:340) DTRXDUL FATAL Something went wrong in thread RxLower, requesting stop (Transceiver.cpp:1359) DMAIN NOTICE Shutting down transceiver... (osmo-trx.cpp:588) DMAIN NOTICE Stopping the transceiver (Transceiver.cpp:345) terminate called without an active exception Aborted And sometimes it reports an USB error and shows the talloc report: DMAIN NOTICE -- Transceiver active with 1 channel(s) (osmo-trx.cpp:621) DLSTATS NOTICE Stats timer expire_count=6: We missed 5 timers (stats.c:169) DLGLOBAL NOTICE Stats timer expire_count=26: We missed 25 timers (rate_ctr.c:350) DTRXCTRL NOTICE Changing TSC from 0 to 7 (Transceiver.cpp:1032) DTRXCTRL NOTICE [chan=0] switching to TRXD version 1 (Transceiver.cpp:1059) DMAIN NOTICE Starting the transceiver (Transceiver.cpp:287) DTRXCLK NOTICE Sending CLOCK indications (Transceiver.cpp:1198) LLUterminate called after throwing an instance of 'uhd::io_error' what(): EnvironmentError: IOError: usb rx6 transfer status: LIBUSB_TRANSFER_OVERFLOW signal 6 received talloc report on 'OsmoTRX' (total 8531 bytes in 29 blocks) rate_ctr.c:233 contains 1160 bytes in 1 blocks (ref 0) 0x559c72388720 trx_rate_ctr.cpp:343 contains 8 bytes in 1 blocks (ref 0) 0x559c723886b0 trx_rate_ctr.cpp:342 contains 40 bytes in 1 blocks (ref 0) 0x559c72389540 trx_rate_ctr.cpp:341 contains 32 bytes in 1 blocks (ref 0) 0x559c723895d0 telnet_connection contains 1 bytes in 1 blocks (ref 0) 0x559c723893d0 struct sched_vty_opts contains 72 bytes in 1 blocks (ref 0) 0x559c723489f0 logging contains 6197 bytes in 13 blocks (ref 0) 0x559c722c5d10 struct trx_ctx contains 1021 bytes in 8 blocks (ref 0) 0x559c722a0e80 msgb contains 0 bytes in 1 blocks (ref 0) 0x559c722c3ac0 full talloc report on 'OsmoTRX' (total 8531 bytes in 29 blocks) rate_ctr.c:233 contains 1160 bytes in 1 blocks (ref 0) 0x559c72388720 trx_rate_ctr.cpp:343 contains 8 bytes in 1 blocks (ref 0) 0x559c723886b0 trx_rate_ctr.cpp:342 contains 40 bytes in 1 blocks (ref 0) 0x559c72389540 trx_rate_ctr.cpp:341 contains 32 bytes in 1 blocks (ref 0) 0x559c723895d0 telnet_connection contains 1 bytes in 1 blocks (ref 0) 0x559c723893d0 struct sched_vty_opts contains 72 bytes in 1 blocks (ref 0) 0x559c723489f0 logging contains 6197 bytes in 13 blocks (ref 0) 0x559c722c5d10 vty_logp_doc_str contains 1377 bytes in 1 blocks (ref 0) 0x559c7231c040 vty_logp_cmd_str contains 260 bytes in 1 blocks (ref 0) 0x559c7231ba00 vty_log_level_doc_str contains 1170 bytes in 1 blocks (ref 0) 0x559c722ff430 vty_log_level_cmd_str contains 236 bytes in 1 blocks (ref 0) 0x559c722ff2d0 vty_log_level_doc_str contains 1305 bytes in 1 blocks (ref 0) 0x559c722fc610 vty_log_level_cmd_str contains 257 bytes in 1 blocks (ref 0) 0x559c722fc4a0 struct log_target contains 330 bytes in 3 blocks (ref 0) 0x559c7220c550 struct osmo_wqueue contains 96 bytes in 1 blocks (ref 0) 0x7ff689ff4090 struct log_category contains 74 bytes in 1 blocks (ref 0) 0x559c722c6290 struct log_info contains 1261 bytes in 3 blocks (ref 0) 0x559c722ac370 uint8_t contains 37 bytes in 1 blocks (ref 0) 0x559c722c6350 struct log_info_cat contains 1184 bytes in 1 blocks (ref 0) 0x559c722c5d80 struct trx_ctx contains 1021 bytes in 8 blocks (ref 0) 0x559c722a0e80 127.0.0.1 contains 10 bytes in 1 blocks (ref 0) 0x559c722c5c20 127.0.0.1 contains 10 bytes in 1 blocks (ref 0) 0x559c722c5ba0 struct cmd_element contains 122 bytes in 2 blocks (ref 0) 0x559c72369030 logging level lms (debug|info|notice|error|fatal) contains 50 bytes in 1 blocks (ref 0) 0x559c7236c1a0 utils.c:386 contains 405 bytes in 1 blocks (ref 0) 0x559c7225e5b0 utils.c:386 contains 65 bytes in 1 blocks (ref 0) 0x559c723524f0 contains 1 bytes in 1 blocks (ref 0) msgb contains 0 bytes in 1 blocks (ref 0) On the BTS side I see several messages of missed timers, but this is something I see also when I don't have the USB plugged in: <0006> scheduler_trx.c:489 GSM clock started, waiting for clock indications <0006> scheduler_trx.c:578 GSM clock skew: old fn=0, new fn=2555007 <0006> scheduler_trx.c:428 FN timer expire_count=4: We missed 3 timers <0006> scheduler_trx.c:606 We were 1 FN slower than TRX, compensated <0006> scheduler_trx.c:606 We were 1 FN slower than TRX, compensated <0006> scheduler_trx.c:428 FN timer expire_count=6: We missed 5 timers <0006> scheduler_trx.c:593 We were 1 FN faster than TRX, compensating <0006> scheduler_trx.c:606 We were 1 FN slower than TRX, compensated <0006> scheduler_trx.c:593 We were 1 FN faster than TRX, compensating <0006> scheduler_trx.c:606 We were 2 FN slower than TRX, compensated <0006> scheduler_trx.c:428 FN timer expire_count=7: We missed 6 timers <0006> scheduler_trx.c:593 We were 1 FN faster than TRX, compensating <0006> scheduler_trx.c:606 We were 1 FN slower than TRX, compensated <0006> scheduler_trx.c:593 We were 1 FN faster than TRX, compensating <0006> scheduler_trx.c:606 We were 1 FN slower than TRX, compensated <0006> scheduler_trx.c:428 FN timer expire_count=7: We missed 6 timers <0006> scheduler_trx.c:593 We were 1 FN faster than TRX, compensating <0006> scheduler_trx.c:606 We were 1 FN slower than TRX, compensated <0006> scheduler_trx.c:428 FN timer expire_count=7: We missed 6 timers <0006> scheduler_trx.c:435 No more clock from transceiver Does anyone know if this is a software or hardware problem? I am thinking maybe it is related to the power supply of the USB port, but I have no idea. I really need to have both devices connected at the same time. Any help or suggestion is appreciated, Jonathan

3 3

Need nano3G (S8 - Model 237A)
by Akib Sayyed 12 Mar '26

12 Mar '26

Dear List I am extremely sorry for off the topic question. I am willing to buy nano3G Nodeb. Is anyone in list have spare which can be sold. Please let me know. -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

7 8

Front and back sides of an MSC
by Mychaela Falconia 17 Feb '26

17 Feb '26

Hello Osmocom community, I have a question about terminology that is not really specific to Osmocom, but is specific to GSM/3G/etc cellular industry, or whatever is left of it. An MSC in a GSM or 3G or any other circuit-switched cellular network has two sides: one side facing the RAN (A interface in GSM, IuCS in 3G), the other side facing PSTN or ISDN or BICC or SIP-I or whatever the fixed telephone network may be. My question: is there a general industry-wide agreement as to which side should be called the front and which should be called the back? To me it seems intuitive to refer to the A/IuCS side of an MSC as the front and the PSTN/ISDN/BICC/SIP-I side of the same MSC as the back. However, I am just one person, and I have no idea whether or not my view is intuitive to others. And it would even worse if the opposite convention happens to be widely used... Hence I am asking this community, in the hope that someone with more industry experience would know how telco network engineers casually refer to RAN-facing and fixed-network-facing sides of an MSC. For a long time I had the idea of building ThemWi MSC as a modular system (multiple processes talking to each other via sockets) with a stripped-down OsmoMSC derivative as the "central" component, and with a radically different placement of MSC-MGW. However, as I started working on more detailed design, I realized a major flaw in my originally envisioned architecture: my original approach to MSC-MGW would break TFO for AMR, specifically the dialogue between TFO-aware BTS and the TRAU equivalent in the MGW. I am now spinning a new architecture in my head, one which tentatively includes two dissimilar MGWs in the MSC. If my front vs back terminology is valid, then the front MGW (talking to AoIP user plane) would perform speech transcoding but become a transparent pass-through for CSD (basically a software-only, IP-based equivalent of a hardware TCSM colocated at the MSC site), while the back MGW would be a transparent pass-through for speech calls, but turn into a complex IWF for CSD. This tentative architecture exactly matches the placement of speech transcoding and CSD IWF functions in traditional hardware MSCs of TDM-based, before-AoIP world. But I need to know if I should keep these front and back terms, or swap them the other way around. M~

4 4

cmd2 update causing pySim-shell to fail
by bryan coxwell 14 Feb '26

14 Feb '26

Hi all, Just wanted to share an issue and a quick workaround I found for it in case anyone else has the same problem. I believe a cmd2 update is causing pySim-shell to fail. After installing it on a fresh install of Ubuntu Server 20.04 and getting the following error when I run "python3 pySim-shell -p0": >Using PC/SC reader interface >Autodetected card type: sysmoUSIM-SJS1 >AIDs on card: > USIM: a0000000871002ffffffff8907090000 >Traceback (most recent call last): > File "pySim-shell.py", line 512, in <module> > app = PysimApp(card, rs, opts.script) > File "pySim-shell.py", line 59, in __init__ > super().__init__(persistent_history_file='~/.pysim_shell_history', allow_cli_args=False, use_ipython=True, auto_load_commands=False, command_sets=basic_commands, >startup_script=script) >TypeError: __init__() got an unexpected keyword argument 'use_ipython' If you run into this you can fix it by uninstalling cmd2 and reinstalling cmd2 with "pip3 install cmd2==1.5". Best, Bryan

13 15

How to Effectively Prepare for the Oracle 1Z0-1127-25 Exam in Minimal Time
by mahmad.iworks＠gmail.com 12 Feb '26

12 Feb '26

Facing a certification exam can feel daunting, especially when time is short. The Oracle 1Z0-1127-25 exam tests a wide range of skills and concepts, requiring both conceptual understanding and practical application. However, with a structured approach, you can study efficiently and make the most of your available time. A good first step is to familiarize yourself with the official exam objectives. Oracle provides a detailed outline of the topics and skills assessed in the 1Z0-1127-25 exam. Breaking the syllabus into smaller, manageable sections allows you to prioritize areas that need the most attention. Start with high-weightage topics and ensure you have a strong understanding of core concepts before moving on to the more advanced material. Next, combine different study resources for a balanced approach. Textbooks, official documentation, and online tutorials are essential for conceptual clarity, but incorporating practice materials is equally important. Many candidates find Oracle <a href="https://www.pass4future.com/oracle/exam/1z0-1127-25">1Z0-1127-25 Exam dumps</a> helpful for familiarizing themselves with question patterns and time management. While these dumps should never replace proper study, they can highlight commonly tested areas and help simulate real exam conditions. Active learning techniques can also save time and improve retention. Creating quick notes, flashcards, or mind maps for complex topics allows for rapid revision. Additionally, scheduling short, focused study sessions, rather than long, unfocused hours, can boost concentration and prevent burnout. Finally, practice consistently. Even in minimal time, attempting mock tests regularly helps track progress, identify weak spots, and build confidence. Review mistakes carefully to ensure you don’t repeat them in the actual exam. By combining clear planning, strategic use of resources like Oracle 1Z0-1127-25 Exam dumps, and consistent practice, it is possible to prepare effectively even with limited time. Remember, the quality of study often outweighs quantity.

2 1

Managing Complicated Laws in BSC Implementations
by Fennellmarian018＠gmail.com 11 Feb '26

11 Feb '26

The complexities of Base Station Controller (BSC) integration in open-source mobile networks have presented me with a number of overlapping areas pertaining to telecommunications legislation and regulatory compliance. In order to better comprehend how international legal standards affect open BSC installations in various jurisdictions, this intersection has unanticipatedly prompted me to seek [url=https://dissertationwritinghelp.uk/law-dissertation-help/]law dissertation help[/url]. I would love to hear from anyone else who has studied legal issues in their OpenBSC-related academic or practical work, as well as suggest some books.

4 3

Video Recordings of OsmoCon 2017
by Harald Welte 09 Feb '26

09 Feb '26

Hi all, the Osmocom Conference 2017 last week was an overwhelming success. We received lots of positive feedback from all sides. Thanks to all the speakers, to the attendees as well as to the anonymous sponsor of the travel grant funds. It is my great pleasure that due to the great support by C3VOC (The CCC Video Operation Center), we have full recordings of all talks given at OsmoCon 2017. You can find the videos on the C3VOC site at https://media.ccc.de/search/?q=osmocon They are also linked individually from the OsmoCon 2017 homepage at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017 I hope the video recordings will be of help for everyone who could not make it to the event in person. We will also be collecting the slides and put them up on the wiki during the next few days. Please don't hesitate to raise any feedback and/or questions. Technical feedback/questions regarding Osmocom software / projects should be addressed to the appropriate mailing lists, such as openbsc(a)lists.osmocom.org. Feedback to the organizers should be sent to osmocon2017(a)sysmocom.de. Looking forward to the next OsmoCon, which we'll expect to be spanning ore than just a single day. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

3 2

Brazilian Knots Salon
by Amelia Emery 05 Feb '26

05 Feb '26

If you’re searching for a natural-looking, protective style that adds length and volume without heavy tension, [url=https://ladybsalon.com/brazilian-knot-extensions-salon/]brazilian knots salon[/url] might be the answer. This salon specializes in the knot method that blends extensions seamlessly with natural hair. From consultations to flawless installs and maintenance tips, this thread explores experiences, results, pricing, and care advice.

2 1

GPRS - local and foreign TLLIs
by Luca Melette 04 Feb '26

04 Feb '26

Hello everybody, after setting up a nanoBTS with OpenBSC/SGSN/GGSN, I had some troubles trying to connect my smartphone to the GPRS cell. Investigating the BTS-to-SGSN traffic, I saw that the frames sent by the SGSN were all marked with the same N(U) value (at LLC layer), the value was 0. With some debug, I found that the there was a mismatch in the TLLI storage, used to keep the status of attached terminals. The mentioned code is contained in gprs_llc.c, involving LL Entity functions and gprs_llc_tx_ui(). /* look-up or create the LL Entity for this (TLLI, SAPI) tuple */ lle = lle_by_tlli_sapi(msgb_tlli(msg), sapi); if (!lle) { struct gprs_llc_llme *llme; LOGP(DLLC, LOGL_ERROR, "LLC TX: unknown TLLI 0x%08x, " "creating LLME on the fly\n", msgb_tlli(msg)); llme = llme_alloc(msgb_tlli(msg)); lle = &llme->lle[sapi]; } The TX function uses the previously received TLLI to lookup for the LLE. The lle_by_tlli_sapi() performs the search, but preliminary it applies a foreign2local TLLI conversion to ensure to have a local one. Since no valid entry for the searched TLLI is found, a new one is created. And the problem is here. The new entry has the foreign TLLI. Next time the lookup fails again, and a new entry is created. This way, the counter N(U) is always reset, and the mobile do not recognize the message sequence and no attach is possible. My question is about foreign and local TLLIs. I patched the lookup, avoiding the conversion, so that the LLE is found and everything works fine... but... What is the sense of the conversion? Should the TLLI be always stored as a local one? Can this problem be solved with another foreign2local while allocating new entries? Actually, my problem has been solved with that workaround. But I'm curious to know what is the right way. Hope somebody can answer :) Thanks. Cheers, LM

5 6

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC January 2026