Cellular Network Infrastructure

This is not an issue you are reporting. It's neither a bug in the software, nor a feature request.

Please raise general questions about usage either in the discorse forum or on the openbsc mailing list.
Thanks!

fixeria wrote in #note-2:

Hello,

what are the minimal hardware requirements and best operation system to install osmoBTS/MSC/BSC/HLR?

it depends on your performance/coverage expectations, but for a lab setup even an old office laptop from 2015 would be sufficient.
"best operation system" is a subjective criteria. You can use any recent GNU/Linux distribution as long as you know how to install software on it.

Osmocom provides binary packages for Debian and its derivatives (like Ubuntu), see:

https://osmocom.org/projects/cellular-infrastructure/wiki/Latest_Builds
https://osmocom.org/projects/cellular-infrastructure/wiki/Nightly_Builds

So I would recommend picking one of those (unless you want to mess with compiling stuff yourself):

https://downloads.osmocom.org/packages/osmocom:/nightly/

How can they install from this link after the git clone? I did not find a good instruction for installation.

You can find more info on installing binary packages in the wiki.

I have installed osmoBTS on ubuntu 22.04 from this link:
https://downloads.osmocom.org/packages/osmocom%3A/latest/xUbuntu_22.04/Release.key”
But when I try to run it show this eeror:
osmo-bts-virtual -c osmo-bts-virtual.cfg
osmo-bts-virtual: symbol lookup error: osmo-bts-virtual: undefined symbol: osmo_rtp_socket_set_priority

On Wed, Jul 17, 2024 at 12:29:52PM +0000, mtohidi67 wrote:

I have installed osmoBTS on ubuntu 22.04 from this link:
https://downloads.osmocom.org/packages/osmocom%3A/latest/xUbuntu_22.04/Release.key”
But when I try to run it show this eeror:
osmo-bts-virtual -c osmo-bts-virtual.cfg
osmo-bts-virtual: symbol lookup error: osmo-bts-virtual: undefined symbol: osmo_rtp_socket_set_priority

this sounds like you're mixing packages from your distribution with packages from the osmocom:latest feed?

Please make sure all osmocom packages are from osmocom:latest. You can try something like 'dpkg -l | grep
osmo' and look at the version numbers to figure this out.

laforge wrote in #note-4:

On Wed, Jul 17, 2024 at 12:29:52PM +0000, mtohidi67 wrote:

I have installed osmoBTS on ubuntu 22.04 from this link:
https://downloads.osmocom.org/packages/osmocom%3A/latest/xUbuntu_22.04/Release.key”
But when I try to run it show this eeror:
osmo-bts-virtual -c osmo-bts-virtual.cfg
osmo-bts-virtual: symbol lookup error: osmo-bts-virtual: undefined symbol: osmo_rtp_socket_set_priority

this sounds like you're mixing packages from your distribution with packages from the osmocom:latest feed?

Please make sure all osmocom packages are from osmocom:latest. You can try something like 'dpkg -l | grep
osmo' and look at the version numbers to figure this out.

dpkg -l | grep osmo
ii libosmo-abis-dev:amd64 1.0.1-2build3 amd64 Development headers for A-bis interface
ii libosmo-mgcp-client12:amd64 1.12.2 amd64 libosmo-mgcp-client: Osmocom's Media Gateway Control Protocol client utilities
ii libosmo-sccp-dev:amd64 1.3.0+dfsg1-3build2 amd64 Development files for libsccp, libmtp and libxua
ii libosmo-sigtran9:amd64 1.8.2 amd64 Osmocom SIGTRAN library (SCCP, SUA, M3UA and more)
ii libosmoabis13:amd64 1.5.2 amd64 GSM A-bis handling
ii libosmoabis9:amd64 1.0.1-2build3 amd64 GSM A-bis handling
ii libosmocodec0:amd64 1.6.0-3build1 amd64 Osmo codec library
ii libosmocodec4:amd64 1.9.3 amd64 Osmo codec library
ii libosmocoding0:amd64 1.6.0-3build1 amd64 Osmo coding library
ii libosmocore-dev:amd64 1.6.0-3build1 amd64 Development headers for Open Source MObile COMmunications CORE library
ii libosmocore18:amd64 1.6.0-3build1 amd64 Osmo Core library
ii libosmocore21:amd64 1.9.3 amd64 Osmo Core library
ii libosmoctrl0:amd64 1.6.0-3build1 amd64 Osmo control library
ii libosmogb12:amd64 1.6.0-3build1 amd64 Osmo GPRS GB library
ii libosmogsm17:amd64 1.6.0-3build1 amd64 Osmo GSM utility library
ii libosmogsm20:amd64 1.9.3 amd64 Osmo GSM utility library
ii libosmoisdn0:amd64 1.9.3 amd64 Osmo ISDN utility library
ii libosmomtp0:amd64 1.3.0+dfsg1-3build2 amd64 Message Transfer Part for Signaling System 7
ii libosmonetif11:amd64 1.4.0 amd64 Common/shared code regarding network interface for OpenBSC
ii libosmosccp0:amd64 1.3.0+dfsg1-3build2 amd64 Library for Signalling Connection Control Part (SCCP)
ii libosmosdr0:amd64 0.1.8.effcaa7-7 amd64 Software defined radio support for OsmoSDR hardware (library)
ii libosmosim2:amd64 1.6.0-3build1 amd64 Osmo SIM library
ii libosmotrau2:amd64 1.0.1-2build3 amd64 GSM trau handling
ii libosmovty13:amd64 1.9.3 amd64 Osmo VTY library
ii libosmovty9:amd64 1.6.0-3build1 amd64 Osmo VTY library
ii libosmoxua0:amd64 1.3.0+dfsg1-3build2 amd64 Osmocom SCCP support library for generating and parsing messages
ii osmo-bsc 1.11.1 amd64 OsmoBSC: Osmocom's Base Station Controller for 2G circuit-switched mobile networks
ii osmo-bsc-bs11-utils 1.11.1 amd64 Command line utilities for Siemens BS-11 BTS
ii osmo-bsc-dbg:amd64 1.11.1 amd64 OsmoBSC: Osmocom's Base Station Controller for 2G circuit-switched mobile networks
ii osmo-bsc-doc 1.11.1 all PDF documentation
ii osmo-bsc-ipaccess-utils 1.11.1 amd64 Command line utilities for ip.access nanoBTS
ii osmo-bsc-meas-utils 1.11.1 amd64 Command line utilities to manage measurement reports.
ii osmo-bts-virtual 1.7.2 amd64 Virtual Osmocom GSM BTS (no RF hardware; GSMTAP/UDP)
ii osmo-mgw 1.12.2 amd64 OsmoMGW: Osmocom's Media Gateway for 2G and 3G circuit-switched mobile networks
ii osmocom-latest 1.0.0 amd64 Dummy package, which conflicts with: osmocom-nightly osmocom-next
ii soapyosmo-common0.8:amd64 0.2.5-6 amd64 Use gr-osmosdr drivers with SoapySDR (common files)
ii soapysdr0.8-module-osmosdr:amd64 0.2.5-6 amd64 OsmoSDR device support for SoapySDR

mtohidi67 wrote in #note-5:

ii libosmoabis13:amd64 1.5.2 amd64 GSM A-bis handling
ii libosmoabis9:amd64 1.0.1-2build3 amd64 GSM A-bis handling
...
ii libosmocodec0:amd64 1.6.0-3build1 amd64 Osmo codec library
ii libosmocodec4:amd64 1.9.3 amd64 Osmo codec library
...
ii libosmocore18:amd64 1.6.0-3build1 amd64 Osmo Core library
ii libosmocore21:amd64 1.9.3 amd64 Osmo Core library

You're indeed mixing up packages provided by Osmocom with [significantly older] packages provided by Ubuntu itself.

root@5bb7b6fbf554:/# apt show  libosmoabis9
Package: libosmoabis9
Version: 1.0.1-2build3
Priority: optional
Section: universe/libs
Source: libosmo-abis
Origin: Ubuntu
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Debian Mobcom Maintainers <Debian-mobcom-maintainers@lists.alioth.debian.org>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 158 kB
Depends: libc6 (>= 2.14), libosmocore18 (>= 1.4.0), libosmogsm17 (>= 1.4.0), libosmovty9 (>= 1.5.1), libtalloc2 (>= 2.0.4~git20101213)
Homepage: http://openbsc.osmocom.org/trac/wiki/libosmo-abis
Download-Size: 56.6 kB
APT-Sources: http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
Description: GSM A-bis handling

You need to examine the output of dpkg -l | grep osmo and manually remove duplicate entries with older version numbers.
For instance, you should remove libosmoabis9, which is older than libosmoabis13. And so on.

fixeria wrote in #note-6:

mtohidi67 wrote in #note-5:

ii libosmoabis13:amd64 1.5.2 amd64 GSM A-bis handling
ii libosmoabis9:amd64 1.0.1-2build3 amd64 GSM A-bis handling
...
ii libosmocodec0:amd64 1.6.0-3build1 amd64 Osmo codec library
ii libosmocodec4:amd64 1.9.3 amd64 Osmo codec library
...
ii libosmocore18:amd64 1.6.0-3build1 amd64 Osmo Core library
ii libosmocore21:amd64 1.9.3 amd64 Osmo Core library

You're indeed mixing up packages provided by Osmocom with [significantly older] packages provided by Ubuntu itself.

[...]

You need to examine the output of dpkg -l | grep osmo and manually remove duplicate entries with older version numbers.
For instance, you should remove libosmoabis9, which is older than libosmoabis13. And so on.

Thank you for your guidance.
Now this is my log when run BTS . is it ok?
smo-bts-virtual -c osmo-bts-virtual1.cfg
((*))
  |
 / \ OsmoBTS
DLGLOBAL <0011> main.c:132 Unimplemented bts_model_phy_instance_set_defaults
% Ignoring deprecated 'logging level sum (debug|info|notice|error|fatal)'
DLCTRL <0018> control_if.c:1014 CTRL at 127.0.0.1 4238
DL1C <0006> bts_model.c:222 Unimplemented bts_model_ctrl_cmds_install
DLGLOBAL <0011> telnet_interface.c:88 Available via telnet 127.0.0.1 4241
DABIS <000d> fsm.c:456 abis_link(abis_link)[0x55867b83e570]{WAIT_RECONNECT}: Allocated
DABIS <000d> abis.c:535 abis_link(abis_link)[0x55867b83e570]{WAIT_RECONNECT}: state_chg to CONNECTING
DABIS <000d> abis.c:161 A-bis connection establishment to BSC (127.0.0.1) in progress...
DLINP <0013> input/ipaccess.c:1099 enabling ipaccess BTS mode, OML connecting to 127.0.0.1:3002
DABIS <000d> abis.c:479 Input Signal LINE-INIT received for link_type=None
DL1C <0006> phy_link.c:58 phy0: PHY link state change shutdown -> connecting
DOML <0001> phy_link.c:70 NM_RCARRIER_OP(bts0-trx0)[0x55867b8390f0]{DISABLED_NOTINSTALLED}: Received Event PHYLINK_DOWN
DOML <0001> phy_link.c:74 NM_BBTRANSC_OP(bts0-trx0)[0x55867b839340]{DISABLED_NOTINSTALLED}: Received Event PHYLINK_DOWN
DL1C <0006> phy_link.c:58 phy0: PHY link state change connecting -> connected
DOML <0001> phy_link.c:70 NM_RCARRIER_OP(bts0-trx0)[0x55867b8390f0]{DISABLED_NOTINSTALLED}: Received Event PHYLINK_UP
DOML <0001> phy_link.c:74 NM_BBTRANSC_OP(bts0-trx0)[0x55867b839340]{DISABLED_NOTINSTALLED}: Received Event PHYLINK_UP
DLINP <0013> input/ipa.c:141 127.0.0.1:3002 connection done
DLINP <0013> input/ipaccess.c:920 received ID_GET for unit ID 6969/0/0
DABIS <000d> abis.c:381 OML Signalling link up
DABIS <000d> abis.c:390 abis_link(abis_link)[0x55867b83e570]{CONNECTING}: Received Event SIGN_LINK_OML_UP
DABIS <000d> abis.c:200 abis_link(abis_link)[0x55867b83e570]{CONNECTING}: state_chg to CONNECTED
DOML <0001> bts.c:429 Main link established, sending NM Status
DOML <0001> bts.c:435 NM_BTS_SM_OP(bts_sm)[0x55867b756140]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_bts_sm_fsm.c:75 NM_BTS_SM_OP(bts_sm)[0x55867b756140]{DISABLED_NOTINSTALLED}: state_chg to DISABLED_OFFLINE
DOML <0001> oml.c:369 OC=SITE-MANAGER INST=(ff,ff,ff) AVAIL STATE Not installed -> Off line
DOML <0001> oml.c:377 OC=SITE-MANAGER INST=(ff,ff,ff) OPER STATE Disabled -> Disabled
DOML <0001> nm_bts_sm_fsm.c:49 NM_GPRS_NSE_OP(gprs_nse0)[0x55867b752ec0]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_gprs_nse_fsm.c:51 NM_GPRS_CELL_OP(gprs_cell0-0)[0x55867b838e10]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_gprs_cell_fsm.c:77 NM_GPRS_CELL_OP(gprs_cell0-0)[0x55867b838e10]{DISABLED_NOTINSTALLED}: state_chg to DISABLED_DEPENDENCY
DOML <0001> oml.c:369 OC=GPRS-CELL INST=(00,00,ff) AVAIL STATE Not installed -> Dependency
DOML <0001> oml.c:377 OC=GPRS-CELL INST=(00,00,ff) OPER STATE Disabled -> Disabled
DOML <0001> nm_gprs_nse_fsm.c:54 NM_GPRS_NSVC_OP(gprs_nsvc0-0)[0x55867b835330]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_gprs_nsvc_fsm.c:76 NM_GPRS_NSVC_OP(gprs_nsvc0-0)[0x55867b835330]{DISABLED_NOTINSTALLED}: state_chg to DISABLED_DEPENDENCY
DOML <0001> oml.c:369 OC=GPRS-NSVC INST=(00,00,ff) AVAIL STATE Not installed -> Dependency
DOML <0001> oml.c:377 OC=GPRS-NSVC INST=(00,00,ff) OPER STATE Disabled -> Disabled
DOML <0001> nm_gprs_nse_fsm.c:54 NM_GPRS_NSVC_OP(gprs_nsvc0-1)[0x55867b835610]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_gprs_nsvc_fsm.c:76 NM_GPRS_NSVC_OP(gprs_nsvc0-1)[0x55867b835610]{DISABLED_NOTINSTALLED}: state_chg to DISABLED_DEPENDENCY
DOML <0001> oml.c:369 OC=GPRS-NSVC INST=(00,01,ff) AVAIL STATE Not installed -> Dependency
DOML <0001> oml.c:377 OC=GPRS-NSVC INST=(00,01,ff) OPER STATE Disabled -> Disabled
DOML <0001> nm_gprs_nse_fsm.c:92 NM_GPRS_NSE_OP(gprs_nse0)[0x55867b752ec0]{DISABLED_NOTINSTALLED}: state_chg to DISABLED_DEPENDENCY
DOML <0001> oml.c:369 OC=GPRS-NSE INST=(00,ff,ff) AVAIL STATE Not installed -> Dependency
DOML <0001> oml.c:377 OC=GPRS-NSE INST=(00,ff,ff) OPER STATE Disabled -> Disabled
DOML <0001> nm_bts_sm_fsm.c:51 NM_BTS_OP(bts0)[0x55867b838be0]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_bts_fsm.c:100 NM_BTS_OP(bts0)[0x55867b838be0]{DISABLED_NOTINSTALLED}: state_chg to DISABLED_OFFLINE
DOML <0001> oml.c:369 OC=BTS INST=(00,ff,ff) AVAIL STATE Not installed -> Off line
DOML <0001> oml.c:377 OC=BTS INST=(00,ff,ff) OPER STATE Disabled -> Disabled
DOML <0001> nm_bts_fsm.c:50 NM_RCARRIER_OP(bts0-trx0)[0x55867b8390f0]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_bts_fsm.c:51 NM_BBTRANSC_OP(bts0-trx0)[0x55867b839340]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_bb_transc_fsm.c:51 NM_CHAN_OP(bts0-trx0-ts0)[0x55867b839590]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_bb_transc_fsm.c:51 NM_CHAN_OP(bts0-trx0-ts1)[0x55867b839be0]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_bb_transc_fsm.c:51 NM_CHAN_OP(bts0-trx0-ts2)[0x55867b83a230]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_bb_transc_fsm.c:51 NM_CHAN_OP(bts0-trx0-ts3)[0x55867b83a880]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_bb_transc_fsm.c:51 NM_CHAN_OP(bts0-trx0-ts4)[0x55867b83aed0]{DISABLED_NOTINSTALLED}: Received Event OML_UP
DOML <0001> nm_bb_transc_fsm.c:51 NM_CHAN_OP(bts0-trx0-ts5)[0x55867b83b520]{DISABLED_NOTINSTALLED}: Received Event OML_UP

laforge wrote in #note-1:

This is not an issue you are reporting. It's neither a bug in the software, nor a feature request.

Please raise general questions about usage either in the discorse forum or on the openbsc mailing list.
Thanks!