OpenBSC September 2018

openbsc@lists.osmocom.org

20 participants
31 discussions

Re: Build failure of network:osmocom:nightly/simtrace2 in xUbuntu_18.04/x86_64
by Neels Hofmeyr 24 Sep '18

24 Sep '18

These build failures are continuously piling up in my inbox. Would it make sense to either fix or disable it? ~N On Sat, Sep 22, 2018 at 08:01:31PM +0000, OBS Notification wrote: > Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/s… > > Package network:osmocom:nightly/simtrace2 failed to build in xUbuntu_18.04/x86_64 > > Check out the package for editing: > osc checkout network:osmocom:nightly simtrace2

2 2

CBSP protocol traces wanted / wireshark dissector
by Harald Welte 19 Sep '18

19 Sep '18

Hi! I recently wrote a wireshark dissector for the CBSP protocol, which is a 3GPP standard for the interface between the Cell Broadcast Centre and the BSC. It's specified in 3GPP TS 48.049 in case you're curious. The dissector can be found at https://code.wireshark.org/review/#/c/29745/ However, I couldn't find any protocol traces to verify the dissector against. So if you happen to have done any work on cell broadcast in 2G network and have a CBSP trace around (or can generate one): Please send it to me, thanks! If I ever find the time, I'd love to add CBSP support to OsmoBSC, and even to go one step further and write a minimal CBC itself. Contributions are of course always welcome, in case there are other interested folks. 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)

1 0

CBCH support for osmo-bts-trx
by Lorenzo Cavallini 19 Sep '18

19 Sep '18

Hello everyone, I was going to add support for CBCH to osmo-bts-trx for a project, then just by chance I looked at this ticket: https://osmocom.org/issues/1617 and I've seen that the issue was reopened 13 days ago. Any chance on getting some pre-pre-pre-alpha patch? I would gladly test and work on it in whatever state the code is now, still better than starting from scratch. Thanks for the awesome work anyway! Best regards, Lorenzo

3 15

Jenkins build is back to normal : Coverity-Upload (jenkins-job-builder) #240
by jenkins＠lists.osmocom.org 19 Sep '18

19 Sep '18

See <https://jenkins.osmocom.org/jenkins/job/osmocom-coverity/240/display/redire…>

1 0

Build failed in Jenkins: Coverity-Upload (jenkins-job-builder) #233
by jenkins＠lists.osmocom.org 18 Sep '18

18 Sep '18

See <https://jenkins.osmocom.org/jenkins/job/osmocom-coverity/233/display/redire…> ------------------------------------------ [...truncated 533.22 KB...] Generating docs for compound osmo_scu_unitdata_param... Generating docs for compound osmo_ss7_as... Generating docs for compound osmo_ss7_asp... Generating docs for compound osmo_ss7_asp_peer... Generating docs for compound osmo_ss7_instance... Generating docs for compound osmo_ss7_link... Generating docs for compound osmo_ss7_linkset... Generating docs for compound osmo_ss7_pc_fmt... Generating docs for compound osmo_ss7_route... Generating docs for compound osmo_ss7_route_table... Generating docs for compound osmo_ss7_routing_key... Generating docs for compound osmo_ss7_user... Generating docs for compound osmo_xlm_prim... Generating docs for compound osmo_xlm_prim_error... Generating docs for compound osmo_xlm_prim_notify... Generating docs for compound osmo_xlm_prim_rk_dereg... Generating docs for compound osmo_xlm_prim_rk_reg... Generating docs for compound osmo_xua_layer_manager... Generating docs for compound osmo_xua_server... Generating docs for compound pcap_hdr... Generating docs for compound pcaprec_hdr... Generating docs for compound sccp_connection... Generating docs for compound sccp_data_callback... Generating docs for compound sccp_system... Generating docs for compound xua_as_fsm_priv... Generating docs for compound xua_asp_fsm_priv... Generating docs for compound xua_common_hdr... Generating docs for compound xua_dialect... Generating docs for compound xua_msg... Generating docs for compound xua_msg_class... Generating docs for compound xua_msg_event_map... Generating docs for compound xua_msg_part... Generating docs for compound xua_parameter_hdr... Generating namespace index... Generating graph info page... Generating directory documentation... Generating index page... Generating page index... Generating module index... Generating namespace index... Generating namespace member index... Generating annotated compound index... Generating alphabetical compound index... Generating hierarchical class index... Generating member index... Generating file index... Generating file member index... Generating example index... finalizing index lists... writing tag file... lookup cache used 2511/65536 hits=19828 misses=2595 finished... cd ./doc && tar cf html.tar */html make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp' make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp' + make install make install-recursive make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp' Making install in include make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include' Making install in sccp make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/sccp' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/sccp' make[4]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/sccp' /usr/bin/install -c -m 644 sccp_types.h sccp.h '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/sccp' make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/sccp' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/sccp' Making install in mtp make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/mtp' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/mtp' make[4]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/mtp' /usr/bin/install -c -m 644 mtp_level3.h mtp_pcap.h '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/mtp' make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/mtp' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/mtp' Making install in osmocom make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/osmocom' Making install in sigtran make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/osmocom/sigtran' make[5]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/osmocom/sigtran' make[5]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/sigtran' /usr/bin/install -c -m 644 xua_types.h xua_msg.h m2ua_types.h sccp_sap.h sigtran_sap.h sccp_helpers.h mtp_sap.h osmo_ss7.h '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/sigtran' /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/sigtran/protocol' /usr/bin/install -c -m 644 protocol/sua.h protocol/m3ua.h protocol/mtp.h '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/sigtran/protocol' make[5]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/osmocom/sigtran' make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/osmocom/sigtran' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/osmocom' make[5]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/osmocom' make[5]: Nothing to be done for 'install-exec-am'. make[5]: Nothing to be done for 'install-data-am'. make[5]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/osmocom' make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/osmocom' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include/osmocom' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include' make[4]: Nothing to be done for 'install-exec-am'. make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/include' Making install in src make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/src' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/src' /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib' /bin/bash ../libtool --mode=install /usr/bin/install -c libosmo-sigtran.la '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib' libtool: install: /usr/bin/install -c .libs/libosmo-sigtran.so.0.2.0 /home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib/libosmo-sigtran.so.0.2.0 libtool: install: (cd /home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib && { ln -s -f libosmo-sigtran.so.0.2.0 libosmo-sigtran.so.0 || { rm -f libosmo-sigtran.so.0 && ln -s libosmo-sigtran.so.0.2.0 libosmo-sigtran.so.0; }; }) libtool: install: (cd /home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib && { ln -s -f libosmo-sigtran.so.0.2.0 libosmo-sigtran.so || { rm -f libosmo-sigtran.so && ln -s libosmo-sigtran.so.0.2.0 libosmo-sigtran.so; }; }) libtool: install: /usr/bin/install -c .libs/libosmo-sigtran.lai /home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib/libosmo-sigtran.la libtool: install: /usr/bin/install -c .libs/libosmo-sigtran.a /home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib/libosmo-sigtran.a libtool: install: chmod 644 /home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib/libosmo-sigtran.a libtool: install: ranlib /home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib/libosmo-sigtran.a libtool: finish: PATH="/home/osmocom-build/osmo-ci/coverity/cov-analysis-linux64-8.5.0/bin/:/usr/local/bin:/usr/bin:/bin:/usr/games:/home/osmocom-build/bin:/opt/coverity/current/bin:/sbin" ldconfig -n /home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib ---------------------------------------------------------------------- Libraries have been installed in: /home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the '-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the 'LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the 'LD_RUN_PATH' environment variable during linking - use the '-Wl,-rpath -Wl,LIBDIR' linker flag - have your system administrator add LIBDIR to '/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib' /usr/bin/install -c -m 644 libsccp.a libmtp.a libxua.a '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib' ( cd '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib' && ranlib libsccp.a ) ( cd '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib' && ranlib libmtp.a ) ( cd '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/lib' && ranlib libxua.a ) make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/src' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/src' Making install in tests make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests' Making install in xua make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/xua' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/xua' make[4]: Nothing to be done for 'install-exec-am'. make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/xua' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/xua' Making install in sccp make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/sccp' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/sccp' make[4]: Nothing to be done for 'install-exec-am'. make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/sccp' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/sccp' Making install in mtp make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/mtp' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/mtp' make[4]: Nothing to be done for 'install-exec-am'. make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/mtp' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/mtp' Making install in m2ua make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/m2ua' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/m2ua' make[4]: Nothing to be done for 'install-exec-am'. make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/m2ua' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/m2ua' Making install in ss7 make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/ss7' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/ss7' make[4]: Nothing to be done for 'install-exec-am'. make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/ss7' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests/ss7' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests' make[4]: Nothing to be done for 'install-exec-am'. make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/tests' Making install in examples make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/examples' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/examples' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/examples' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/examples' Making install in stp make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/stp' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/stp' /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/bin' /bin/bash ../libtool --mode=install /usr/bin/install -c osmo-stp '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/bin' libtool: install: /usr/bin/install -c .libs/osmo-stp /home/osmocom-build/osmo-ci/coverity/install-Osmocom/bin/osmo-stp make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/stp' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/stp' Making install in doc make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/doc' Making install in examples make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/doc/examples' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/doc/examples' make[4]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/share/doc/libosmo-sccp/examples/osmo-stp' /usr/bin/install -c -m 644 osmo-stp.cfg '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/share/doc/libosmo-sccp/examples/osmo-stp' /bin/mkdir -p '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/etc/osmocom' /usr/bin/install -c -m 644 osmo-stp.cfg '/home/osmocom-build/osmo-ci/coverity/install-Osmocom/etc/osmocom' make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/doc/examples' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/doc/examples' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/doc' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/doc' make[4]: Nothing to be done for 'install-exec-am'. make[4]: Nothing to be done for 'install-data-am'. make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/doc' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/doc' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/doc' Making install in contrib make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/contrib' Making install in systemd make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/contrib/systemd' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/contrib/systemd' make[4]: Nothing to be done for 'install-exec-am'. /bin/mkdir -p '/lib/systemd/system' /usr/bin/install -c -m 644 osmo-stp.service '/lib/systemd/system' /usr/bin/install: cannot create regular file '/lib/systemd/system/osmo-stp.service': Permission denied Makefile:328: recipe for target 'install-systemdsystemunitDATA' failed make[4]: *** [install-systemdsystemunitDATA] Error 1 make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/contrib/systemd' Makefile:398: recipe for target 'install-am' failed make[3]: *** [install-am] Error 2 make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/contrib/systemd' Makefile:362: recipe for target 'install-recursive' failed make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp/contrib' Makefile:489: recipe for target 'install-recursive' failed make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/libosmo-sccp' Makefile:788: recipe for target 'install' failed make: *** [install] Error 2 [WARNING] Build command ./build_Osmocom.sh exited with code 2. Please verify that the build completed successfully. Emitted 431 C/C++ compilation units (100%) successfully 431 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 2

re: "codec_pref: fix typo in comment"
by Neels Hofmeyr 17 Sep '18

17 Sep '18

BTW, "iff" is not a typo, it means "If and only if". https://www.merriam-webster.com/dictionary/iff re https://gerrit.osmocom.org/10962 ~N

1 0

shellcheck for our shell scripts?
by Holger Freyther 17 Sep '18

17 Sep '18

Hey, I recently stumbled across shellcheck[1] and think we should make it a goal that our shell scripts don't produce errors/warnings with it. Some of the examples in the GSM tester: In jenkins-build-common.sh line 76: cd "$base" ^-- SC2164: Use 'cd ... || exit' or 'cd ... || return' in case cd fails. In jenkins-build-common.sh line 93: rm -rf * ^-- SC2035: Use ./*glob* or -- *glob* so names with dashes won't become options. What do you think? My approach would be: * Install shellcheck into our build containers * Run them and provide warnings * Fix them over time and on new code * Make CI fail with failures cheers holger [1] https://www.shellcheck.net/

4 3

LimeSDR-USB experience with New Splits Solved!
by Sandi Suhendro 15 Sep '18

15 Sep '18

Osmocom New Splits stacks for voice is SOLVED and stable with LimeSDR! Voice is working actually since back then, my fault is using only C117/118 for test call all the time. Now I just test using newer phone both Caller and Callee and voice is work perfectly! I tested both osmo-trx-lms and osmo-trx legacy. using osmo-trx legacy 0.20 also have better performance using the firmware/gateware version I mention here : firmware/gateware version: LimeSDR-USB_HW_1.3_r3.0.img and LimeSDR-USB_HW_1.4_r2.9.rbf from LimeSuite . There is trace in wireshark when using old phone as C117/118, the BTS always freeze and send Measurement Indication all the time when calling is made and answered, but with newer phone, the Indication is normal. -- Best Regards, DUO

3 4

Re: Osmo-pcu error: PCU interface version number of BTS (7) is different (9).
by Pau Espin Pedrol 14 Sep '18

14 Sep '18

Sorry forgot to reply-all and didn't send original mail to ML, re-sending now. On 9/14/18 3:25 PM, Pau Espin Pedrol wrote: > Hi Rafael, > > You may want to check at PCU_IF_VERSION in both osmo-pcu.git and > osmo-pcu.git > > It seems that you are running a recent osmo-pcu together with a quite > old osmo-bts (from at least Feb 28 2018, see osmo-bts.git > 4046e3b3dd0cffd53d8d0d1f3e1bf9d0dec83ede), and they are not protocol > compatible. > > So you need to either use a newer osmo-bts (preferred I guess) or switch > to an older osmo-pcu which uses PCU_IF_VERSION 7. > > If you are using NuRan original firmware, you either ask them to update > their stuff or your are pretty much on your own to build new images > (with non-upstream osmocom versions afaik). > > At sysmocom we maintain meta-sysmocom-bsp [1] which together with > system-images [2] and osmocom's meta-telephny [3] allows to build > firmware for both sysmobts and litecell 1.5 machines, together with SDKs > to compile software for them. > > I think generated images are not available publicly, but I guess you can > either attempt building them yourself or perhaps ask sysmocom customer > support to have access to it. > > [1] https://git.sysmocom.de/poky/meta-sysmocom-bsp/ > [2] https://git.sysmocom.de/poky/system-images/ > [3] https://git.osmocom.org/meta-telephony/ > > Regards, > Pau > -- - 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

3 3

Re: Osmo-pcu error: PCU interface version number of BTS (7) is different (9).
by Pau Espin Pedrol 14 Sep '18

14 Sep '18

And again, forgot to include the list, sorry ;) On 9/14/18 3:59 PM, Pau Espin Pedrol wrote: > Hi Rafael, > > I'm not sure right now about the details of the binary firmware > installation and the exact rights you have as customer/user regarding > it, but I guess you can ask NuRan to provide them, or take them from > your current LC 1.5 image you are using if they are available there. I > think the headers are at least provided publicly in gitlab: > https://gitlab.com/nrw_noa > > Regards, > Pau -- - 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC September 2018