OpenBSC September 2018

openbsc@lists.osmocom.org

20 participants
36 discussions

Re: Help with sccp library
by mosbah abdelkader 07 Jul '25

07 Jul '25

> I don't understand. This callback will be called with data you need to write > to the network. In case of MTP Level3 you will need to wrap that around the > msgb you got. I means: is the interaction with mtp3 layer implemented (is sending sccp data by mtp3 implemented by the library?)? Also, what about the reception of data from mtp3 layer. is that implemented in the sccp lib. I am asking these questions because I see the code of mtp3 in the lib but no significant call is present in the sccp part of the lib. Thank you for your help.

4 3

dynamic traffic channels
by Neels Hofmeyr 20 May '25

20 May '25

On Tue, Jun 28, 2016 at 10:05:28AM +0200, Harald Welte wrote: > [translated from german] > is it certain that we switch a channel to PDCH only when > gprs mode != none? A TS can be GSM_PCHAN_TCH_F_PDCH; those are the only ones for which we send a PDCH ACT message. We send a PDCH ACT message - during init (CHANNEL OML's state changed to enabled -> send PDCH ACT), - and upon channel release ack when pchan == GSM_PCHAN_TCH_F_PDCH. So the question is, when we receive a channel release ack, could that be the PDCH release and we switch PDCH right back on by accident? No, because we only receive a chan rel ack when the *TCH/F* is being released. That is because the PDCH release is initiated "internally" from the PDCH DEACT, and thus this condition in common/rsl.c rsl_tx_rf_rel_ack() catches on, which existed before dyn PDCH: if (lchan->rel_act_kind != LCHAN_REL_ACT_RSL) { LOGP(DRSL, LOGL_NOTICE, "%s not sending REL ACK\n", gsm_lchan_name(lchan)); return 0; } In rsl_rx_rf_chan_rel() the rel_act_kind is set to LCHAN_REL_ACT_RSL, but not in the rsl_rx_dyn_pdch(). This is analogous to the ip.access way -- the ip.access nanobts replies to a PDCH DEACT with a PDCH DEACT ACK and doesn't send a separate channel release ack. Maybe we could set rel_act_kind to some new LCHAN_REL_ACT_IPAC_DYN_PDCH for clarity? (But we shouldn't actually send a release ack, to stay compatible.) Even though it works as-is, we should indeed add another flag check: - We do check the flags that no ACT/DEACT is already pending; - And we do send a PDCH DEACT only if ts->flags & TS_F_PDCH_ACTIVE; - But we would send a PDCH ACT despite ts->flags & TS_F_PDCH_ACTIVE. This should never happen, but it would make sense to ensure that. ~Neels

3 5

Save the Date: OsmoCon 2018 on October 18-19, 2018
by Harald Welte 19 Oct '18

19 Oct '18

== OsmoCon 2018 == OsmoCon (Osmocom Conference) 2018 is the technical conference for Osmocom users, operators and developers! We are happy to announce the date of OsmoCon 2018. It has been scheduled on October 18 + 19, 2018 and will happen in Berlin, Germany. For the second time, the Osmocom Conference brings together users, operators and developers of the Osmocom Open Source cellular infrastructure projects, such as OsmoBTS, OsmoBSC, OsmoSGSN, OpenGGSN and others. Join us for two days of presentations and discussions with the main developers behind Open Source Mobile Communications, as well as commercial and non-profit users of the Osmocom cellular infrastructure software. You can find some initial information in our wiki at http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2018 which will be updated as more information becomes available. == Call for Participation == We're also at the same time announcing the Call for Participation and call on everyone with experiences to share around the Osmocom member projects to submit talks, workshops, discussions or other proposals. You can find the CfP at https://pretalx.sysmocom.de/osmocon2018/cfp We are particularly looking for contributions about: * updates on features/functionality/status of individual Osmocom projects * success stories on how Osmocom projects are deployed in practice * migration from OsmoNITB to the post-NITB architecture * tutorials / workshops on how to setup / analyze Osmocom projects * statistics, reporting, operations aspects of Osmocom projects * third-party open source utilities to be used with Osmocom projects Looking forward to meeting many existing and new Osmocom users at OsmCon this October! Regards, Harald Welte -- - 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 4

Re: LimeSDR-USB experience with New Splits Solved!
by Vadim Yanitskiy 06 Oct '18

06 Oct '18

> Are you referring to the ones from 2015 or so with > Russian titles? Those are the only ones I am aware of Yes. There are few. Check out this one: https://youtu.be/jw-63aOOPk0 > how do you know that phone was running against an > Osmocom network [...] I know the author. Also, you can see the logs of OpenBSC on the background of the mentioned video. > The relation is simple: if phones like Mot C1xx running > Motorola's original factory fw don't work with Osmocom > networks, [...] In order to confirm, I just tested a Motorola C118 running the original firmware with Osmocom-based network. LimeSDR-Mini was used as PHY for OsmoTRX. Everything works fine, including: SDCCH: SMS, USSD, other signaling TCH/H: both HR and AMR codecs TCH/F: FR, AMR and EFR codecs Probably, the author of this topic has some problems with codec / network configuration. With best regards, Vadim Yanitskiy.

2 1

Trace needed: AMR voice call signalling on SCCP in AoIP network
by Philipp Maier 25 Sep '18

25 Sep '18

Hello Folks, I am trying to resolve some open questions about the encoding of the AMR codec configuration bits S0-S15. (see also 3GPP TS 48.008, 3.2.2.103, "The coding of Speech Codec Element for FR_AMR, HR_AMR and OHR_AMR:" and 3GPP TS 28.062, Table 7.11.3.1.3-2) Since I do not have any AoIP network that I could trace against to verify that all my assumptions about the coding of those bits are correct I would love to see a trace from some other network. It would be kind if anyone of you could help me out with that. All I need is a trace from a call. It is important that AMR is negotiated in the Assignment request. best regards, Philipp Maier -- Philipp Maier <pmaier(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

1 0

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC September 2018