Hi all,
I'm starting to get used to the new stack with split components, and all
seems to be working fine, SMS and USSD are working, but no voice calls yet.
ps ax:
7611 pts/4 S+ 0:00 osmo-mgw -c osmo-mgw-for-bsc.cfg
7653 pts/6 S+ 0:00 osmo-bsc -c osmo-bsc.cfg
7705 pts/3 S+ 0:00 osmo-msc -c osmo-msc.cfg
7760 pts/8 S+ 0:00 osmo-mgw -c osmo-mgw-for-msc.cfg
7785 pts/0 Sl+ 1:59 osmo-trx
7803 pts/7 S+ 0:08 osmo-bts-trx -c osmo-bts.cfg
17288 pts/1 S+ 0:00 osmo-hlr -l hlr.db -c osmo-hlr.cfg
17299 pts/5 S+ 0:02 osmo-stp -c osmo-stp.cfg
Config files are deeply based in the nitb.tar in the wiki.
I read in an email from December that osmo-bsc_mgcp is still required.
Is that the case?
Thanks,
Rafael Diniz
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
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
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
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
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
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
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