OpenBSC

openbsc@lists.osmocom.org

3 participants
4155 discussions

by Radiarisainana Sitraka

hello, I would like to ask some question, like , what kind of hardware should I have if i would like to install and doing some demo with osmo-ss7 !? Chears,

7 years, 7 months

OsmoDevCon 2018 schedule planning

by Harald Welte

Dear Osmocom Community, [please respect the Reply-To and post all follow-up discussion to this to openbsc(a)lists.osmocom.org, so we avoid having long threads cross-posted to several mailing lists.] Like every year in early December, it is time to discuss as schedule for OsmoDevCon in the upcoming year. Note: Ths is about OsmoDevCon, the more private meeting of developers, *NOT* about OsmoCon, the public conference. == When, Who, Where == I propose the following date for OsmoDevCon 2018: April 20 - April 23rd, 2018 * Who: Active developers/contributors of Osmocom projects (as usual) * Where: IN-Berlin, Berlin (as usual) Please let me know ASAP if that proposed date works for everyone who'd want to attend. We can still change it now, but I would want to nail down the date pretty soon. == Format == After the experiment of reducing from 4 to 3 days last year (due to OsmoCon), we will again go for *four days* in 2018. However, we should clearly divide the days in a way that e.g. "GSM/3G" topics are on two days, while SDR+Other topics are on the other days, so people not interested in some topics can skip one or two days, as needed. We could even divide it further like: * 1 day 3GPP RAN (osmo-bts, osmo-bsc, osmo-pcu, virt_phy, fake_trx, ...) * 1 day 3GPP CN (osmo-msc, osmo-hlr, osmo-sip-connector, nextepc, etc.) * 2 days misc Regards, and looking forward to meeting you [again] in 2018, 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)

7 years, 7 months

Re: Build failure of network:osmocom:nightly/osmo-mgw in Debian_9.0/x86_64

by Neels Hofmeyr

should be fixed by https://gerrit.osmocom.org/5167 ~N On Mon, Dec 04, 2017 at 08:10:33PM +0000, OBS Notification wrote: > Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… > > Package network:osmocom:nightly/osmo-mgw failed to build in Debian_9.0/x86_64 > > Check out the package for editing: > osc checkout network:osmocom:nightly osmo-mgw > > Last lines of build log: > [ 106s] -M: sendrecv > [ 106s] - > [ 106s] ------ > [ 106s] -composed response: > [ 106s] ------ > [ 106s] -200 1 OK > [ 106s] -I: 1 > [ 106s] - > [ 106s] -v=0 > [ 106s] - > [ 106s] ------ > [ 106s] -Done > [ 106s] ./testsuite.at:21: exit code was 139, expected 0 > [ 106s] 3. testsuite.at:17: 3. mgcp_client (testsuite.at:17): FAILED (testsuite.at:21) > [ 106s] debian/rules:30: recipe for target 'override_dh_auto_test' failed > [ 106s] make[1]: *** [override_dh_auto_test] Error 1 > [ 106s] make[1]: Leaving directory '/usr/src/packages/BUILD' > [ 106s] debian/rules:17: recipe for target 'build' failed > [ 106s] make: *** [build] Error 2 > [ 106s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 > [ 106s] > [ 106s] lamb26 failed "build osmo-mgw_1.2.0.20171204.dsc" at Mon Dec 4 20:10:16 UTC 2017. > [ 106s] > [ 106s] ### VM INTERACTION START ### > [ 110s] [ 101.485505] reboot: Power down > [ 110s] ### VM INTERACTION END ### > [ 110s] > [ 110s] lamb26 failed "build osmo-mgw_1.2.0.20171204.dsc" at Mon Dec 4 20:10:19 UTC 2017. > [ 110s] > > -- > Configure notifications at https://build.opensuse.org/user/notifications > openSUSE Build Service (https://build.opensuse.org/) -- - Neels Hofmeyr <nhofmeyr(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 * Geschäftsführer / Managing Directors: Harald Welte

7 years, 7 months

Re: osmo-mgw[master]: MGCP endpoints: parse as decimal, not hex

by Neels Hofmeyr

I'd like to re-raise this patch I merged for discussion, it's about whether or not OsmoMGW endpoint identifiers are in hex. My patch might have gone in the wrong direction after all. https://gerrit.osmocom.org/4780 ~N On Sat, Dec 02, 2017 at 06:53:39PM +0000, Neels Hofmeyr wrote: > > Patch Set 2: > > elsewhere it seems we are confirming the hex nature of endpoint IDs (or was that a connection identifier?) ... Possibly this needs to be fixed the other way, by libosmo-mgcp-client translating the number-of-endpoints to a hex representation? > > -- > To view, visit https://gerrit.osmocom.org/4780 > To unsubscribe, visit https://gerrit.osmocom.org/settings > > Gerrit-MessageType: comment > Gerrit-Change-Id: Ic18608ff23303c1564548a86d5f6bfa539fe555e > Gerrit-PatchSet: 2 > Gerrit-Project: osmo-mgw > Gerrit-Branch: master > Gerrit-Owner: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> > Gerrit-Reviewer: Harald Welte <laforge(a)gnumonks.org> > Gerrit-Reviewer: Holger Freyther <holger(a)freyther.de> > Gerrit-Reviewer: Jenkins Builder > Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> > Gerrit-HasComments: No

7 years, 7 months

GAPK status update

by Vadim Yanitskiy

Dear Osmocom community, I have been working on GAPK (GSM Audio Packet Knife) for some time, and now I would like to share some achievements. Previously GAPK was represented as a single binary that could be called with some command line arguments in order to perform required operations. This is only handy for humans, but not for other programs, which may also need to perform some format / codec conversations or audio capture / playback. One of such programs is the mobile from OsmocomBB project. Currently, when you're making a voice call, both audio capture and playback are only possible on the L1 side, i.e. on a Calypso based phone. Of course, the audio stream can be redirected via MNCC socket, but this is not what a regular OsmocomBB user would like to do. Moreover, there is a lack of AMR codec support. Also, there is another GNURadio based project named GR-GSM. In short, this is a set of blocks for GSM signal reception, demodulation and further processing. At the moment, one has TCH Full Rate decoding capabilities only. Audio playback is not supported yet. Having these projects in my mind, I have got an idea of creating a shared library from the GAPK source code. And, a few days ago I was managed to get the audio playback working in OsmocomBB. I hope, this library will be also usable for other projects. Brief list of changes were made: - Composed a shared library named libosmogapk - All exposed symbols have got an 'osmo_gapk' prefix - Added a pkg-config manifest and a symbol export map - Integrated the Osmocom logging framework - Benchmarking is now disabled by default - Processing queue now based on the linuxlist - Fixed program exit due to ALSA buffer underrun - Fixed ALSA audio playback from file - Old gapk application was renamed to 'osmo-gapk' and linked against the library - Adjusted verbosity level (normal / debug) - Fixed I/O combinations (ALSA, RTP, file...) check All changes could be found at the fixeria/lib branch of GAPK. I hope to see them merged, and open for discussions ;) With best regards, Vadim Yanitskiy.

7 years, 7 months

Build failed in Jenkins: Coverity-Upload » linux_amd64_debian8 #1687

by jenkins＠lists.osmocom.org

See <http://jenkins.osmocom.org/jenkins/job/Coverity-Upload/label=linux_amd64_de…> ------------------------------------------ [...truncated 2.05 MB...] 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 library containing dlopen... -ldl checking for LIBOSMOCORE... yes checking for LIBOSMOVTY... yes checking for LIBOSMOCTRL... yes checking for LIBOSMOGSM... yes checking for LIBOSMOABIS... yes checking for LIBOSMONETIF... yes checking for LIBOSMOSIGTRAN... yes checking for LIBOSMOSCCP... yes checking for LIBCRYPTO... yes checking for LIBOSMOMGCPCLIENT... yes checking for ANSI C header files... (cached) yes checking dbi/dbd.h usability... yes checking dbi/dbd.h presence... yes checking for dbi/dbd.h... yes checking pcap/pcap.h usability... yes checking pcap/pcap.h presence... yes checking for pcap/pcap.h... yes checking cdk/cdk.h usability... no checking cdk/cdk.h presence... no checking for cdk/cdk.h... no checking for SQLITE3... yes checking if gcc supports -fvisibility=hidden... yes checking whether C compiler accepts -Werror=implicit... yes checking whether C compiler accepts -Werror=maybe-uninitialized... yes checking whether C compiler accepts -Werror=memset-transposed-args... yes checking whether C compiler accepts -Werror=null-dereference... no checking whether C compiler accepts -Werror=sizeof-array-argument... no checking whether C compiler accepts -Werror=sizeof-pointer-memaccess... yes checking whether to enable code coverage support... no checking whether struct tm has tm_gmtoff member... yes checking whether to enable VTY/CTRL tests... no checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating include/Makefile config.status: creating include/osmocom/Makefile config.status: creating include/osmocom/msc/Makefile config.status: creating src/Makefile config.status: creating src/libmsc/Makefile config.status: creating src/libvlr/Makefile config.status: creating src/libcommon/Makefile config.status: creating src/libcommon-cs/Makefile config.status: creating src/osmo-msc/Makefile config.status: creating src/utils/Makefile config.status: creating tests/Makefile config.status: creating tests/atlocal config.status: creating tests/smpp/Makefile config.status: creating tests/sms_queue/Makefile config.status: creating tests/msc_vlr/Makefile config.status: creating doc/Makefile config.status: creating doc/examples/Makefile config.status: creating contrib/Makefile config.status: creating Makefile config.status: creating bscconfig.h config.status: executing tests/atconfig commands config.status: executing depfiles commands config.status: executing libtool commands + make -j 3 echo 1.1.2.37-b8acdc > .version-t && mv .version-t .version make all-recursive make[1]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc' Making all in doc make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/doc' Making all in examples make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/doc/examples' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/doc/examples' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/doc' make[3]: Nothing to be done for 'all-am'. make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/doc' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/doc' Making all in include make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/include' Making all in osmocom make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/include/osmocom' Making all in msc make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/include/osmocom/msc' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/include/osmocom/msc' make[4]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/include/osmocom' make[4]: Nothing to be done for 'all-am'. make[4]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/include/osmocom' make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/include/osmocom' make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/include' make[3]: Nothing to be done for 'all-am'. make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/include' make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/include' Making all in src make[2]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/src' Making all in libcommon make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/src/libcommon' CC bsc_version.o CC common_vty.o CC debug.o CC gsm_data.o CC gsm_data_shared.o CC gsup_client.o CC oap_client.o CC socket.o CC talloc_ctx.o CC gsm_subscriber_base.o CC gsup_test_client.o AR libcommon.a CCLD gsup_test_client make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/src/libcommon' Making all in libvlr make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/src/libvlr' CC vlr.o CC vlr_auth_fsm.o CC vlr_access_req_fsm.o CC vlr_lu_fsm.o AR libvlr.a make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/src/libvlr' Making all in libmsc make[3]: Entering directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/src/libmsc' CC a_iface.o CC a_iface_bssap.o CC auth.o a_iface_bssap.c: In function ‘bssmap_rx_l3_compl’: a_iface_bssap.c:328:11: warning: assignment discards ‘const’ qualifier from pointer target type msg->l3h = TLVP_VAL(&tp, GSM0808_IE_LAYER_3_INFORMATION); ^ a_iface_bssap.c: In function ‘bssmap_rx_ciph_compl’: a_iface_bssap.c:424:12: warning: assignment discards ‘const’ qualifier from pointer target type msg->l3h = TLVP_VAL(&tp, GSM0808_IE_LAYER_3_MESSAGE_CONTENTS); ^ CC msc_vty.o CC db.o CC gsm_04_08.o db.c: In function ‘db_init’: db.c:607:2: warning: ‘dbi_initialize’ is deprecated (declared at /usr/include/dbi/dbi.h:169) [-Wdeprecated-declarations] dbi_initialize(NULL); ^ db.c:609:2: warning: ‘dbi_conn_new’ is deprecated (declared at /usr/include/dbi/dbi.h:199) [-Wdeprecated-declarations] conn = dbi_conn_new("sqlite3"); ^ db.c: In function ‘db_fini’: db.c:673:2: warning: ‘dbi_shutdown’ is deprecated (declared at /usr/include/dbi/dbi.h:171) [-Wdeprecated-declarations] dbi_shutdown(); ^ CC gsm_04_11.o CC gsm_04_14.o CC gsm_04_80.o CC gsm_subscriber.o CC mncc.o CC mncc_builtin.o CC mncc_sock.o CC msc_ifaces.o CC rrlp.o msc_ifaces.c: In function ‘msc_call_assignment’: msc_ifaces.c:255:42: error: ‘struct mgcp_client_conf’ has no member named ‘bts_base’ bts_base = mgcp_client_conf_actual(mgcp)->bts_base; ^ msc_ifaces.c:261:2: warning: ‘mgcp_msg_crcx’ is deprecated (declared at /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/mgcp_client/mgcp_client.h:98): Use mgcp_msg_gen() instead [-Wdeprecated-declarations] msg = mgcp_msg_crcx(mgcp, conn->rtp.mgcp_rtp_endpoint, ^ msc_ifaces.c: In function ‘mgcp_bridge’: msc_ifaces.c:286:2: warning: ‘mgcp_msg_mdcx’ is deprecated (declared at /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/mgcp_client/mgcp_client.h:103): Use mgcp_msg_gen() instead [-Wdeprecated-declarations] msg = mgcp_msg_mdcx(mgcp, ^ msc_ifaces.c: In function ‘msc_call_connect’: msc_ifaces.c:371:2: warning: ‘mgcp_msg_mdcx’ is deprecated (declared at /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/mgcp_client/mgcp_client.h:103): Use mgcp_msg_gen() instead [-Wdeprecated-declarations] msg = mgcp_msg_mdcx(mgcp, ^ msc_ifaces.c: In function ‘msc_call_release’: msc_ifaces.c:417:2: warning: ‘mgcp_msg_dlcx’ is deprecated (declared at /home/osmocom-build/osmo-ci/coverity/install-Osmocom/include/osmocom/mgcp_client/mgcp_client.h:108): Use mgcp_msg_gen() instead [-Wdeprecated-declarations] msg = mgcp_msg_dlcx(mgcp, conn->rtp.mgcp_rtp_endpoint, ^ Makefile:492: recipe for target 'msc_ifaces.o' failed make[3]: *** [msc_ifaces.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[3]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/src/libmsc' Makefile:412: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc/src' Makefile:448: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/osmocom-build/osmo-ci/coverity/source-Osmocom/osmo-msc' Makefile:379: recipe for target 'all' failed make: *** [all] Error 2 [WARNING] Build command ./build_Osmocom.sh exited with code 2. Please verify that the build completed successfully. Emitted 956 C/C++ compilation units (100%) successfully 956 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

7 years, 7 months

Re: osmo-bts-trx init problem

by Vadim Yanitskiy

Hi, > <000b> trx_if.c:409 transceiver (phy0.0) rejected TRX command > with response: 'RSP SETTSC -1' > > What is the problem and how can fix it? The OsmocomBB transceiver is a legacy transceiver, so please add the following line to your 'osmo-bts.cfg': osmotrx legacy-setbsic And please let me know about the results, I'll correct the wiki. With best regards, Vadim Yanitskiy.

7 years, 7 months

Re: Build failure of network:osmocom:nightly/osmo-msc in Debian_9.0/x86_64

by Neels Hofmeyr

These osmo-msc failures are inadvertently caused by https://gerrit.osmocom.org/4701, which is a good change once https://gerrit.osmocom.org/4980 is ready. But until then, I decided to revert it in https://gerrit.osmocom.org/5126. We shall re-apply it as soon as 4980 is merged. I wasn't expecting osmo-msc to use the new client library but needing the old bts_base config -- which I probably applied myself of course, but that detail was lost to me in the meantime. ~N On Fri, Dec 01, 2017 at 08:19:16PM +0000, OBS Notification wrote: > Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… > > Package network:osmocom:nightly/osmo-msc failed to build in Debian_9.0/x86_64 > > Check out the package for editing: > osc checkout network:osmocom:nightly osmo-msc > > Last lines of build log: > [ 136s] from msc_ifaces.c:24: > [ 136s] /usr/include/osmocom/mgcp_client/mgcp_client.h:108:14: note: declared here > [ 136s] struct msgb *mgcp_msg_dlcx(struct mgcp_client *mgcp, uint16_t rtp_endpoint, > [ 136s] ^~~~~~~~~~~~~ > [ 136s] Makefile:508: recipe for target 'msc_ifaces.o' failed > [ 136s] make[4]: *** [msc_ifaces.o] Error 1 > [ 136s] make[4]: Leaving directory '/usr/src/packages/BUILD/src/libmsc' > [ 136s] Makefile:424: recipe for target 'all-recursive' failed > [ 136s] make[3]: *** [all-recursive] Error 1 > [ 136s] make[3]: Leaving directory '/usr/src/packages/BUILD/src' > [ 136s] Makefile:460: recipe for target 'all-recursive' failed > [ 136s] make[2]: *** [all-recursive] Error 1 > [ 136s] make[2]: Leaving directory '/usr/src/packages/BUILD' > [ 136s] Makefile:392: recipe for target 'all' failed > [ 136s] make[1]: *** [all] Error 2 > [ 136s] make[1]: Leaving directory '/usr/src/packages/BUILD' > [ 136s] dh_auto_build: make -j1 returned exit code 2 > [ 136s] debian/rules:45: recipe for target 'build' failed > [ 136s] make: *** [build] Error 2 > [ 136s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 > [ 136s] > [ 136s] cloud120 failed "build osmo-msc_1.1.2.20171201.dsc" at Fri Dec 1 20:19:10 UTC 2017. > [ 136s] > [ 136s] ### VM INTERACTION START ### > [ 140s] [ 111.258730] reboot: Power down > [ 141s] ### VM INTERACTION END ### > [ 141s] > [ 141s] cloud120 failed "build osmo-msc_1.1.2.20171201.dsc" at Fri Dec 1 20:19:14 UTC 2017. > [ 141s] > > -- > Configure notifications at https://build.opensuse.org/user/notifications > openSUSE Build Service (https://build.opensuse.org/) -- - Neels Hofmeyr <nhofmeyr(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 * Geschäftsführer / Managing Directors: Harald Welte

7 years, 7 months

LimeSDR support in osmocom:{nightly,latest} package feeds

by Harald Welte

Dear all, starting from today, we're packaging LimeSuite and (as needed) other dependencies required for using osmo-trx/osmo-bts-trx with LimeSDR in the network:osmocom:nightly and network:osmocom:latest feeds. The package versions are fixed and are not tracking "master" of e.g. limesuite. Only the Osmocom packages are tracking master. Due to the unfortunate fact that the first LimeSuite with osmo-trx support (17.09.0) requiring a cmake later than what Debian 8 ships, LimeSDR support is not working with all of the Distributions/Versions that the rest of the Osmocom stack supports. It appears that LimeSuite also has some build issues on ARM architectures, about which I've submitted an upstream bug report at https://github.com/myriadrf/LimeSuite/issues/151 But at least for x86_64 and i586 architecture, LimeSDR should be supported by the Osmocom package feeds , on Debian 9.0, Ubuntu 16.04, 16.10, 17.04 and 17.10. We will shortly use those packages as part of our osmo-gsm-tester setup at the sysmocom lab, at which point they should receive extensive testing. 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)

7 years, 7 months

Eclipse TITAN public release of SS7/SIGTRAN core protocols

by Harald Welte

Hi all, I've mentioned this many months before, but Ericsson has now (well, a month ago) finally made a public announcement about the public release of their SS7/SIGTRAN core protocols in TTCN-3. You can read more about it at https://www.eclipse.org/forums/index.php/t/1089686/ - where they actually even refer to us as being the trigger to release them. There are still many tests to write beyond those currently existing. Most recently I wrote a set of MGCP tests for our new osmo-mgw, which Philipp is now using to iron out some kinks in the codebase. The past week I've been working on simulating the minimal subset of N numbers of BSCs and N numbers of MSCs from a single test suite in order to test osmo-bsc_nat, and specifically the "IMSI-based routing to different MSCs" feature that Daniel has been working on. It's still work in progress, but definitely the by far most complex TTCN-3 project that I've written so far. After completing that, I would like to spend some more time on OsmoBTS and OsmoBSC related tests. The difficulty here is that the more we get to the RAN / air interface, the less existing prtoocols / codecs exist, so e.g. A-bis RSL would first have to be implemented. The good part is that it's actually super easy using the expressive syntax of the TITAN "raw" codec. Basically you define the structure of the data in files like http://git.osmocom.org/osmo-ttcn3-hacks/tree/library/GSM_RR_Types.ttcn and you don't have to write a single line for encoding/parsing :) 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)

7 years, 7 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC