OsmoNITB or OpenBSC/OpenBTS, is one better suited for LimeSDR?

Just a few weeks back, I was so excited when I made my first actual call using the LimeSDR and OpenBTS. Now, I’ve moved on to setting up OsmoNITB with my Lime. I know the concept of “better” in software is often very subjective but in the context of the LimeSDR board, which software project do you guys prefer and why?

I prefer the Osmocom stack because the architecture is, or at least can be, closer to what you would see in live networks. OsmoNITB combines numerous functions together, but you can also run with e.g. BSC, MSC and HLR split out as separate components.


I think there are also various performance improvements in the OsmoTRX transceiver over the OpenBTS one (which it was originally forked from).

Plus OpenBTS at least used to be available as community and commercial releases, with the former lagging behind the latter. Whereas Osmocom is fully open and not a mixed licensing model.

Thanks for the reply. Exactly the kind of answer I was looking for. I’m running OsmoNITB in a Ubuntu 16.04 Desktop VM using VMWare Fusion on my Macbook Pro (16 GB ram, SSD, 2.5 Ghz Quad Core). So far, the Osmocom stack is more responsive and I really like the way it presents color coded debug information as events are happening. Thanks again!

1 Like

Hi, hi
you are lucky with smooth running… and looking for more :wink:
I am still fighting with ->
osmo-trx alone is running ok, but with other two some “profanity” comes
from that cooperation soon, one by one alarming and terminating :smiley:

Argh, don’t use that old fork! Support is upstream now in:


Will delete/archive our old/stale fork…

Tnx Andrew,
nice to know (swearing silently) :stuck_out_tongue:

Than, can be useful in case you can provide also some similar example:

For instance my first try was to use that updated source. All good
Than I was looking to try “for real” and without BSC and BTS (or similar)
that is not possible. Googling landed first on above old fork :blush: