OpenBSC January 2018

openbsc@lists.osmocom.org

29 participants
56 discussions

testing osmo-bsc osmo-hlr osmo-msc
by Sandi Suhendro 22 Jan '18

22 Jan '18

Hello guys. Im testing the osmo-bsc osmo-hlr osmo-msc. I can make call but sometimes cannot, also same with text message. now the auto create subscriber not working which is Im looking and its very good and nice improovement. I ussually using osmo-sip-connector with openbsc and asterisk, but since I read that osmo-msc handling the features and also for future osmocom GSM stacks, so Im trying to migrate and test it. does my setting for the osmocom stacks is right with this? : osmo-bsc -c ~/osmo/osmo-bsc.cfg osmo-hlr -l hlr.db -c ~/osmo/osmo-hlr.cfg osmo-stp -c ~/osmo/osmo-stp.cfg osmo-mgw -c ~/osmo/osmo-mgw-for-msc.cfg osmo-mgw -c ~/osmo/osmo-mgw-for-bsc.cfg osmo-msc -c ~/osmo/osmo-msc.cfg DId I miss something? Im sure I miss something. :-) and how to connect osmo-msc with asterisk? Thanks. -- Best Regards, DUO

2 2

Build failed in Jenkins: Coverity-Upload » linux_amd64_debian8 #1736
by jenkins＠lists.osmocom.org 22 Jan '18

22 Jan '18

See <http://jenkins.osmocom.org/jenkins/job/Coverity-Upload/label=linux_amd64_de…> ------------------------------------------ [...truncated 2.16 MB...] CC osmo-bts-sysmo/sysmo_l1_fwd.o CXXLD libgprs.la CXXLD osmo-pcu CXXLD osmo-pcu-remote make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/src' Making all in examples make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/examples' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/examples' Making all in tests make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/tests' CXX pcu_emu.o CXX test_replay_gprs_attach.o CC openbsc_clone.o CXX test_pdp_activation.o CXXLD emu/pcu_emu make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/tests' make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu' + make install Making install in include make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/include' make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/include' make[2]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include' /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/pcu' /usr/bin/install -c -m 644 osmocom/pcu/pcuif_proto.h '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/pcu' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/include' make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/include' Making install in src make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/src' make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/src' /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/bin' /bin/sh ../libtool --mode=install /usr/bin/install -c osmo-pcu '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/bin' libtool: install: /usr/bin/install -c osmo-pcu /home/osmocom-build/osmo-ci/coverity/install-Osmocom/bin/osmo-pcu make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/src' make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/src' Making install in examples make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/examples' make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/examples' make[2]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/etc/osmocom' /usr/bin/install -c -m 644 osmo-pcu.cfg '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/etc/osmocom' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/examples' make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/examples' Making install in tests make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/tests' make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/tests' make[2]: Nothing to be done for 'install-exec-am'. make[2]: Nothing to be done for 'install-data-am'. make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/tests' make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu/tests' make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu' make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu' make[2]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib/pkgconfig' /usr/bin/install -c -m 644 osmo-pcu.pc '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib/pkgconfig' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu' make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-pcu' + popd ~/osmo-ci/coverity/source-Osmocom + build_osmobts + pushd osmo-bts ~/osmo-ci/coverity/source-Osmocom/osmo-bts ~/osmo-ci/coverity/source-Osmocom + do_build --enable-sysmocom-bts --enable-trx + autoreconf --install --force libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying file `./ltmain.sh' libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. configure.ac:21: installing './compile' configure.ac:23: installing './config.guess' configure.ac:23: installing './config.sub' configure.ac:9: installing './install-sh' configure.ac:9: installing './missing' src/common/Makefile.am: installing './depcomp' src/osmo-bts-sysmo/Makefile.am:25: warning: bin_PROGRAMS was already defined in condition TRUE, which includes condition ENABLE_SYSMOBTS_CALIB ... src/osmo-bts-sysmo/Makefile.am:10: ... 'bin_PROGRAMS' previously defined here src/osmo-bts-sysmo/Makefile.am:12: warning: source file 'misc/sysmobts_par.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:12: but option 'subdir-objects' is disabled automake: warning: possible forward-incompatibility. automake: At least a source file is in a subdirectory, but the 'subdir-objects' automake: automake option hasn't been enabled. For now, the corresponding output automake: object file(s) will be placed in the top-level directory. However, automake: this behaviour will change in future Automake versions: they will automake: unconditionally cause object files to be placed in the same subdirectory automake: of the corresponding sources. automake: You are advised to start using 'subdir-objects' option throughout your automake: project, to avoid future incompatibilities. src/osmo-bts-sysmo/Makefile.am:27: warning: source file 'misc/sysmobts-calib.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:27: but option 'subdir-objects' is disabled src/osmo-bts-sysmo/Makefile.am:27: warning: source file 'misc/sysmobts-layer1.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:27: but option 'subdir-objects' is disabled src/osmo-bts-sysmo/Makefile.am:31: warning: source file 'misc/sysmobts_mgr.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:31: but option 'subdir-objects' is disabled src/osmo-bts-sysmo/Makefile.am:31: warning: source file 'misc/sysmobts_misc.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:31: but option 'subdir-objects' is disabled src/osmo-bts-sysmo/Makefile.am:31: warning: source file 'misc/sysmobts_par.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:31: but option 'subdir-objects' is disabled src/osmo-bts-sysmo/Makefile.am:31: warning: source file 'misc/sysmobts_nl.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:31: but option 'subdir-objects' is disabled src/osmo-bts-sysmo/Makefile.am:31: warning: source file 'misc/sysmobts_mgr_2050.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:31: but option 'subdir-objects' is disabled src/osmo-bts-sysmo/Makefile.am:31: warning: source file 'misc/sysmobts_mgr_vty.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:31: but option 'subdir-objects' is disabled src/osmo-bts-sysmo/Makefile.am:31: warning: source file 'misc/sysmobts_mgr_nl.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:31: but option 'subdir-objects' is disabled src/osmo-bts-sysmo/Makefile.am:31: warning: source file 'misc/sysmobts_mgr_temp.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:31: but option 'subdir-objects' is disabled src/osmo-bts-sysmo/Makefile.am:31: warning: source file 'misc/sysmobts_mgr_calib.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:31: but option 'subdir-objects' is disabled src/osmo-bts-sysmo/Makefile.am:42: warning: source file 'misc/sysmobts_util.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:42: but option 'subdir-objects' is disabled src/osmo-bts-sysmo/Makefile.am:42: warning: source file 'misc/sysmobts_par.c' is in a subdirectory, src/osmo-bts-sysmo/Makefile.am:42: but option 'subdir-objects' is disabled tests/agch/Makefile.am:7: warning: source file '$(srcdir)/../stubs.c' is in a subdirectory, tests/agch/Makefile.am:7: but option 'subdir-objects' is disabled tests/cipher/Makefile.am:7: warning: source file '$(srcdir)/../stubs.c' is in a subdirectory, tests/cipher/Makefile.am:7: but option 'subdir-objects' is disabled tests/misc/Makefile.am:9: warning: source file '$(srcdir)/../stubs.c' is in a subdirectory, tests/misc/Makefile.am:9: but option 'subdir-objects' is disabled tests/paging/Makefile.am:7: warning: source file '$(srcdir)/../stubs.c' is in a subdirectory, tests/paging/Makefile.am:7: but option 'subdir-objects' is disabled tests/power/Makefile.am:8: warning: source file '$(srcdir)/../stubs.c' is in a subdirectory, tests/power/Makefile.am:8: but option 'subdir-objects' is disabled tests/sysmobts/Makefile.am:8: warning: source file '$(top_srcdir)/src/osmo-bts-sysmo/utils.c' is in a subdirectory, tests/sysmobts/Makefile.am:8: but option 'subdir-objects' is disabled tests/sysmobts/Makefile.am:8: warning: source file '$(top_srcdir)/src/osmo-bts-sysmo/l1_if.c' is in a subdirectory, tests/sysmobts/Makefile.am:8: but option 'subdir-objects' is disabled tests/sysmobts/Makefile.am:8: warning: source file '$(top_srcdir)/src/osmo-bts-sysmo/oml.c' is in a subdirectory, tests/sysmobts/Makefile.am:8: but option 'subdir-objects' is disabled tests/sysmobts/Makefile.am:8: warning: source file '$(top_srcdir)/src/osmo-bts-sysmo/l1_transp_hw.c' is in a subdirectory, tests/sysmobts/Makefile.am:8: but option 'subdir-objects' is disabled tests/sysmobts/Makefile.am:8: warning: source file '$(top_srcdir)/src/osmo-bts-sysmo/tch.c' is in a subdirectory, tests/sysmobts/Makefile.am:8: but option 'subdir-objects' is disabled tests/sysmobts/Makefile.am:8: warning: source file '$(top_srcdir)/src/osmo-bts-sysmo/calib_file.c' is in a subdirectory, tests/sysmobts/Makefile.am:8: but option 'subdir-objects' is disabled tests/sysmobts/Makefile.am:8: warning: source file '$(top_srcdir)/src/osmo-bts-sysmo/calib_fixup.c' is in a subdirectory, tests/sysmobts/Makefile.am:8: but option 'subdir-objects' is disabled tests/sysmobts/Makefile.am:8: warning: source file '$(top_srcdir)/src/osmo-bts-sysmo/misc/sysmobts_par.c' is in a subdirectory, tests/sysmobts/Makefile.am:8: but option 'subdir-objects' is disabled tests/sysmobts/Makefile.am:8: warning: source file '$(top_srcdir)/src/osmo-bts-sysmo/eeprom.c' is in a subdirectory, tests/sysmobts/Makefile.am:8: but option 'subdir-objects' is disabled tests/tx_power/Makefile.am:7: warning: source file '$(srcdir)/../stubs.c' is in a subdirectory, tests/tx_power/Makefile.am:7: but option 'subdir-objects' is disabled + ./configure --prefix=/home/osmocom-build/osmo-ci/coverity/install-Osmocom --enable-sysmocom-bts --enable-trx checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether make supports nested variables... (cached) yes checking whether make sets $(MAKE)... (cached) yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking how to print strings... printf checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for mt... mt checking if mt is a manifest tool... no checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for pkg-config... /usr/bin/pkg-config checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.20... yes checking for ANSI C header files... (cached) yes checking for LIBOSMOCORE... yes checking for LIBOSMOVTY... yes checking for LIBOSMOTRAU... yes checking for LIBOSMOGSM... yes checking for LIBOSMOCTRL... yes checking for LIBOSMOABIS... yes checking for LIBOSMOCODEC... yes checking for LIBOSMOCODING... yes checking for ORTP... yes checking whether to enable support for sysmobts calibration tool... no checking whether to enable support for sysmoBTS L1/PHY support... yes checking for sysmocom/femtobts/superfemto.h... no configure: error: sysmocom/femtobts/superfemto.h can not be found in . [WARNING] Build command ./build_Osmocom.sh exited with code 1. Please verify that the build completed successfully. Emitted 1913 C/C++ compilation units (100%) successfully 1913 C/C++ compilation units (100%) are ready for analysis For more details, please look at: /home/osmocom-build/osmo-ci/coverity/source-Osmocom/cov-int/build-log.txt Build step 'Execute shell' marked build as failure

1 4

OSMO-TRX with OSMO-NITB and OSMO-BTS error
by Ronan Empig 22 Jan '18

22 Jan '18

Hi, I am using LimeSDR and I would like to setup a mini GSM base station. I am following this instructions: https://discourse.myriadrf.org/t/limesdr-osmo-trx-no-work/1938/27 However, I am getting trouble starting tranceiver: *TERMINAL 1:* ronan@ronan-MS-N014:~/Downloads$ osmo-nitb -c openbsc.cfg -l hlr.sqlite3 -P -C <0005> abis_nm.c:2800 (bts=0,trx=0) Changing adm. state Unlocked -> Unlocked [vty] <001e> telnet_interface.c:104 telnet at 127.0.0.1 4242 <0005> bsc_init.c:465 WARNING: You are running an 'accept-all' network on a BTS that is not barred. This configuration is likely to interfere with production GSM networks and should only be used in a RF shielded environment such as a faraday cage! <0020> input/ipaccess.c:848 enabling ipaccess BSC mode on 0.0.0.0 with OML 3002 and RSL 3003 TCP ports <0017> smpp_smsc.c:1001 SMPP at 0.0.0.0 2775 <0025> control_if.c:854 CTRL at 127.0.0.1 4249 DB: Database initialized. DB: Database prepared. <0020> input/ipa.c:263 accept()ed new link from 127.0.0.1 to port 3002 <0005> abis_nm.c:507 BTS0 feature 'EGPRS' reported via OML does not match statically set feature: 0 != 1. Please fix. <0005> abis_nm.c:507 BTS0 feature 'OML Alerts' reported via OML does not match statically set feature: 1 != 0. Please fix. <0005> abis_nm.c:573 BTS0: ARI reported sw[0/2]: sysmobts is 0.7.0.20180115 <0005> abis_nm.c:446 BTS0 reported variant: omso-bts-trx <0005> abis_nm.c:468 BTS0 Attribute Manufacturer Dependent State is unreported <0005> abis_nm.c:573 BTS0: ARI reported sw[0/1]: TRX_PHY_VERSION is Unknown <0020> input/ipa.c:263 accept()ed new link from 127.0.0.1 to port 3003 <0004> bsc_init.c:311 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 514 using MCC=1 MNC=1 LAC=1 CID=0 BSIC=63 <0020> input/ipaccess.c:243 Sign link vanished, dead socket <0020> input/ipaccess.c:71 Forcing socket shutdown with no signal link set *TERMINAL 2:* ronan@ronan-MS-N014:~/Downloads$ osmo-bts-trx -c osmo-bts.cfg ((*)) | / \ OsmoBTS <0017> control_if.c:854 CTRL at 127.0.0.1 4238 <0010> telnet_interface.c:104 telnet at 127.0.0.1 4241 <0012> input/ipaccess.c:886 enabling ipaccess BTS mode, OML connecting to 127.0.0.1:3002 <000b> trx_if.c:599 Open transceiver for phy0.0 <0012> input/ipa.c:129 connection done. <0012> input/ipaccess.c:707 received ID get <0001> oml.c:229 O&M Get Attributes [0], Manufacturer Dependent State is unsupported by TRX. <0001> oml.c:680 Ignoring T200[0] (150 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:680 Ignoring T200[1] (180 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:680 Ignoring T200[2] (180 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:680 Ignoring T200[3] (1680 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:680 Ignoring T200[4] (520 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:680 Ignoring T200[5] (165 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:680 Ignoring T200[6] (1680 ms) as sent by BSC due to suspected LAPDm bug! <0001> oml.c:1049 ADM state already was Unlocked <0012> input/ipa.c:129 connection done. <0012> input/ipaccess.c:707 received ID get <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <000b> trx_if.c:172 No response from transceiver for phy0.0 <0007> l1sap.c:462 Invalid condition detected: Frame difference is 1108205-0=1108205 > 1! <0007> l1sap.c:462 Invalid condition detected: Frame difference is 1108421-1108300=121 > 1! <0007> l1sap.c:462 Invalid condition detected: Frame difference is 1108638-1108435=203 > 1! <0007> l1sap.c:462 Invalid condition detected: Frame difference is 1108855-1108652=203 > 1! <0007> l1sap.c:462 Invalid condition detected: Frame difference is 1109072-1108870=202 > 1! <0007> l1sap.c:462 Invalid condition detected: Frame difference is 1109289-1109086=203 > 1! <0001> bts.c:210 Shutting down BTS 0, Reason No clock from osmo-trx <0007> l1sap.c:462 Invalid condition detected: Frame difference is 1112227-1109693=2534 > 1! <0001> oml.c:1049 ADM state already was Unlocked <0001> oml.c:1049 ADM state already was Unlocked <0001> oml.c:1049 ADM state already was Unlocked <0001> oml.c:1049 ADM state already was Unlocked <0001> oml.c:1049 ADM state already was Unlocked <0001> oml.c:1049 ADM state already was Unlocked <0001> oml.c:1049 ADM state already was Unlocked <0001> oml.c:1049 ADM state already was Unlocked <0001> bts.c:205 BTS is already being shutdown. <000b> trx_if.c:172 No response from transceiver for phy0.0 Shutdown timer expired ronan@ronan-MS-N014:~/Downloads$ *TERMINAL 3:* ronan@ronan-MS-N014:~/Downloads$ sudo osmo-trx -e [sudo] password for ronan: linux; GNU C++ version 5.4.0 20160609 <%2802%29%20016%200609>; Boost_105800; UHD_003.010.002.000-release Info: SSE3 support compiled in and supported by CPU Info: SSE4.1 support compiled in, but not supported by CPU Config Settings Log Level............... NOTICE Device args............. TRX Base Port........... 5700 TRX Address............. 127.0.0.1 GSM Core Address.........127.0.0.1 Channels................ 1 Tx Samples-per-Symbol... 4 Rx Samples-per-Symbol... 4 EDGE support............ Enabled Reference............... Internal C0 Filler Table......... Disabled Multi-Carrier........... Disabled Tuning offset........... 0 RSSI to dBm offset...... 0 Swap channels........... 0 -- Make connection: 'LimeSDR-USB [USB 2.0] 9060B00470E28' -- Reference clock 30.720 MHz -- Device name: LimeSDR-USB -- Reference: 30.72 MHz -- Init LMS7002M(0) -- Ver=7, Rev=1, Mask=1 -- LMS7002M calibration values caching Disable -- Transceiver active with 1 channel(s) NOTICE 139639362156288 07:03:23.5 Transceiver.cpp:791:driveControl: Changing TSC from 0 to 7 NOTICE 139639362156288 07:03:23.5 Transceiver.cpp:244:start: Starting the transceiver ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=174420 time_end=171360 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=174420 time_end=171360 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=179520 time_end=176460 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=179520 time_end=176460 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=184620 time_end=181560 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=184620 time_end=181560 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=190740 time_end=186660 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=190740 time_end=186660 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=196860 time_end=192780 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=196860 time_end=192780 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=201960 time_end=198900 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=201960 time_end=198900 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=207060 time_end=204000 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=207060 time_end=204000 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=213180 time_end=209100 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=213180 time_end=209100 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=217260 time_end=215220 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=217260 time_end=215220 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=224400 time_end=219300 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=224400 time_end=219300 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=229500 time_end=226440 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=229500 time_end=226440 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=234600 time_end=231540 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=234600 time_end=231540 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=239700 time_end=236640 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=239700 time_end=236640 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=245820 time_end=241740 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=245820 time_end=241740 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=251940 time_end=247860 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=251940 time_end=247860 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=258060 time_end=253980 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=258060 time_end=253980 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=263160 time_end=260100 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=263160 time_end=260100 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=268260 time_end=265200 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=268260 time_end=265200 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=273360 time_end=270300 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=273360 time_end=270300 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=279480 time_end=275400 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=279480 time_end=275400 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=285600 time_end=281520 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=285600 time_end=281520 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=290700 time_end=287640 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=290700 time_end=287640 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=322320 time_end=292740 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=322320 time_end=292740 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=328440 time_end=324360 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=328440 time_end=324360 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=333540 time_end=330480 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=333540 time_end=330480 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=338640 time_end=335580 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=338640 time_end=335580 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=343740 time_end=340680 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=343740 time_end=340680 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=349860 time_end=345780 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=349860 time_end=345780 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=355980 time_end=351900 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=355980 time_end=351900 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=360060 time_end=358020 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=360060 time_end=358020 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=367200 time_end=362100 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=367200 time_end=362100 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=372300 time_end=369240 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=372300 time_end=369240 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=378420 time_end=374340 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=378420 time_end=374340 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=383520 time_end=380460 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=383520 time_end=380460 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=389640 time_end=385560 ERR 139639362090752 07:03:24.4 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=389640 time_end=385560 ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 0.359668 ALERT 139639362090752 07:03:24.5 UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 0.359668 ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err: Current time: 0.120517, Previous time: 0.359668 ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err: Current time: 0.120517, Previous time: 0.359668 ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=399840 time_end=391680 ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=399840 time_end=391680 ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=410040 time_end=408000 ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=410040 time_end=408000 ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=415140 time_end=412080 ERR 139639362090752 07:03:24.7 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=415140 time_end=412080 ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 0.383206 ALERT 139639362090752 07:03:24.7 UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 0.383206 ERR 139639362090752 07:03:24.8 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=440640 time_end=417180 ERR 139639362090752 07:03:24.8 UHDDevice.cpp:1383:write: Skipping

5 11

osmo-trx with USRP1 - libusrp vs. UHD
by Alexander Huemer 21 Jan '18

21 Jan '18

Hi! I played with osmo-trx today and tried to run it with a USRP1 that I have laying around, though to no avail. osmo-trx supports two kinds of devices, USRP1 via libusrp and UHD. libusrp was last included in gnuradio 3.4.2[1] from Dec 2013, it unsurprisingly does not build on a recent Linux distribution, due to API incompatibilities with boost. The USRP1 would theoretically be supported by UHD, though the device initialization code in osmo-trx explicitly treats it differently, see [2,3]. I found an old ML post[4] from 2015 that pretty much asks the same question but did not get an answer. Supposedly there is a simple reason why USRP1 is not driven via UHD in osmo-trx, but I don't know. Can somebody please enlighten me? Tom, maybe you? I would like to understand whether it is feasible to use an USRP1 with UHD for osmo-trx or one would have to go down the rabbit hole to build libusrp on a modern system. Kind regards, -Alex [1] https://gnuradio.org/releases/gnuradio/ [2] https://git.osmocom.org/osmo-trx/tree/Transceiver52M/UHDDevice.cpp#n512 [3] https://git.osmocom.org/osmo-trx/tree/Transceiver52M/USRPDevice.cpp [4] https://lists.osmocom.org/pipermail/openbsc/2015-January/000058.html

5 14

libosmocore wiki page and doxygen online documentation
by Pau Espin Pedrol 18 Jan '18

18 Jan '18

Hi, I was trying to find if the doxygen documentation is uploaded and publicly available somewhere in some web server. Google pointed me to this libosmocore wiki page: ftp://ftp.osmocom.org/api/latest/libosmonetif/ In there, there are several links to stuff like http://www.osmocom.org/doc/libosmocore/latest/html/, but I get access forbidden when trying to use that one. On the other hand, I found somewhere else a link to http://ftp.osmocom.org/api/latest/libosmonetif/html/ which seems to be working. Now the question is: which is the expected way to access the documentation? should "www.osmocom.org" work instead of having to use "ftp.osmocom.org"? -- - Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

2 1

OSmux ideas implementation
by Rafael Diniz 17 Jan '18

17 Jan '18

Hi people, Is there anything implemented from the OSmux[1] ideas? [1] http://ftp.osmocom.org/docs/latest/osmux-reference.pdf Thanks, Rafael Diniz

2 2

Help required for non-sync Handover
by Muhammad Awais Aslam 16 Jan '18

16 Jan '18

Hi, We have manged to decode the BSIC in dedicated mode which were not implemented before. Now we are working on the synchronize and non-synchronize Handover. Once we send the fake measurement report to the BTS we get a handover command from the network. That could be synchronized or non-synchronized. In case of synchronized hand over, without making any changes in the TPU clock offset and the frame number and frequency correction, we are able to complete the handover process most of the time. In case of non-synchronized handover, a physical info is required from the network when mobile station would send Handover access burst to the network before the timer expires but we never get physical info during this period. Here we are stuck. Changes: for non-synchronized handover we need to change the TPU offset and frequency correction offset and frame number parameters which we stored during the BSIC decoding. We set these values before we send handover access burst to the network but no success. Anybody who is working on the handover currently or in the past can discuss these things with me so we can figure out why we are not getting the physical info during the non-sync handover. I have also attached the main changed files with this email. I hope someone would give advice how to debug the issue. Regards M. Awais

3 6

binary packages problem
by Rafael Diniz 16 Jan '18

16 Jan '18

Hi all, Anyone experiencing this error in Latest packages (Debian 9): "The following packages have unmet dependencies: osmo-mgw : Depends: libosmo-mgcp0 but it is not installable" Nightly works great thou. Cheers, Rafael Diniz

2 1

stow fallout, problem in osmo-bts-sysmo build
by Neels Hofmeyr 16 Jan '18

16 Jan '18

In osmo-bts, we just have the configure flag --enable-sysmocom-bts, and don't pass a header include location. i.e. we expect the header files to exist locally. I'm a bit stumped on why introducing stow would cause this to break. IIUC stow should only affect the installed dependencies, while the sysmocom headers are just placed in a local dir? If we can't fix the osmo-bts build quickly, we'll have to revert the stow patch until that works. https://jenkins.osmocom.org/jenkins/view/master/job/master-osmo-bts/36/BTS_… The build scripts are (obviously) in osmo-bts/contrib/ and osmo-ci/scripts. Any help is appreciated. ~N

2 2

External USSD interface development
by Vadim Yanitskiy 16 Jan '18

16 Jan '18

Dear Harald, In this mail I would like to express my thoughts and ideas regarding to the 'external interface for USSD'. To provide some background for other mailing list members, who are not aware of this topic, I'll explain it in a few sentences. We already have an external interface for SMS - SMPP. But unfortunately, the same cannot be said about USSD. There is no built-in support of any interface, which could be used to handle USSD requests in a separate application. So, at the moment we only handle *#100# (own number request), which is implemented as a part of both OsmoMSC and legacy OsmoNiTB. And if one would like to implement additional USSD commands, it's required to modify and recompile the whole project :/ Fairwaves team already have some draft implementation for legacy OsmoNiTB, which relays on the libosmocore's GSM 04.80 API. And having the external interface in the mainline would be great not only for Fairwaves, but for the whole Osmocom project and its users. The problem is that the current libosmocore's GSM 04.80 API is not complete and requires some critical modifications, which of course cannot be integrated immediately. Moreover, this implementation doesn't follow Osmocom coding style, for example, unlike other functions, where return code rc = 0 means success, there it means error... So, first of all, we need to know, how many projects are using the current API, especially non-Osmocom projects. After that (taking it into account), it shall be decided: - Should we keep the old API / ABI and maintain all new features among with it. This way would force us to duplicate the existing code and use different symbols. Then the old API would continuously became deprecated... - Should we make all the critical changes in the current API (increasing the libosmocore version?). This way would break builds of dependent projects and would suppose fixing compatibility with the new API. But, at the same time, the implementation would be cleaner and closer to the specification, without any deprecated duplication... Personally, I prefer the second way. At the same time, I want to make the modification as much transparent as possible. Speaking about Osmocom projects, the only users of the GSM 04.80 API are OsmoMSC and legacy OsmoNiTB. Both projects utilize it for '*#100#' handling only :/ To be more convincing, let's look at the following code: #define MAX_LEN_USSD_STRING 31 struct ss_request { uint8_t opcode; uint8_t ss_code; uint8_t ussd_text[MAX_LEN_USSD_STRING + 1]; uint8_t transaction_id; uint8_t invoke_id; }; This is what the current API allows you to obtain from a SS-request (e.g. '*#100#') coming from user. And what's wrong here? - The 'ss_request' doesn't indicate a part of the library it comes from. Would be better to use 'gsm0480_ss_request'. - The 'ussd_text' length doesn't follow the specification, where USSD OCTET STRING length is 160 bytes. So, the amount of characters depends on used coding scheme. - The information about SS-message type, component type, text length and used DCS (Data Coding Scheme), etc. is missing. Despite it could be important for the external application. So, let's discuss together all the 'pros and cons', and decide together, how should we facilitate the external USSD interface development. With best regards, Vadim Yanitskiy.

5 5

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC January 2018