but that fails to compile on Ubuntu 16.04 - some bizarre #warning Please apply the sofia-sip-gcc-4.8.patch. So go back a few years to an older head
$ git checkout jolly/handover
Branch jolly/handover set up to track remote branch jolly/handover from origin.
Switched to a new branch ‘jolly/handover’
That’ll build and install, but for one small mismatch:
000000 ERROR (in gsm.cpp/mncc_fd_read() line 1366): MNCC version different. BSC version is 5
so just edit lcr/mncc.h and change the version from 3 to 5
#define MNCC_SOCK_VERSION 5
rebuild and install and now handsets can call each other.
Well i tried to get this to work in lubuntu osmotrx fails after this
ERR 139798566057728 13:58:15.6 UHDDevice.cpp:350:uhd_msg_handler: MCU error code(5): Loopback signal weak, not connected?
WARNING 139798179600128 13:58:16.7 UHDDevice.cpp:347:uhd_msg_handler: popping from TX, samples popped 0/1020
WARNING 139798358517504 13:58:16.7 UHDDevice.cpp:347:uhd_msg_handler: L
ALERT 139798566024960 13:59:42.7 UHDDevice.cpp:1067:writeSamples: UHD: Device send timed out
I burned lots of hours trying to make this work including IgnasJ configs and dozen of variations as well as countless number of code forks. Best I could accomplish was clean Tx of GSM signal, phones can see the network as “PLMN Test 1” but at no point have I had any success registering any phone to it. The whole thing is experimental, I get it, it was fun trying to make it work but it never did on my side. Perhaps there exists some “unique” combination of OS environment, osmo-nitb/osmo-bts/osmo-trx code versions/forks, and config settings that make it work but I have not discovered it yet.
Just got gprs working with an old phone, enough to (slowly) upload a photo of the LimeSDR to Facebook
I’m running all on one box with USB3 to the radio and ethernet to a nat gateway, Ubuntu 16.04 - so here are all my config files that work. There are tricks, like the example cfg in the source have different unit-id’s for the bts and the nitb bsc, plus the aforementioned rx-gain is 1 and needs cranked up to 43 or so.
My last challenge was disable the ufw (uncomplicated firewall), flush all rules out of iptables and load the one nat rule, then it started working - you can watch the traffic with tcpdump -i tun4 - it’s amazing what a cheap watch is accessing.
Watching the 2 videos in the Readme below helped explain a lot.
Also, fwiw, I just tried switching FROM: osmo-nitb (the old openbsc) & openbsc.cfg
TO: osmo-hlr & osmo-hlr.cfg - home location register (users)
osmo-mgw & osmo-mgw.cfg - media gateway (hopefully route to asterisk someday?)
osmo-msc & osmo-msc.cfg - mobile switching center
osmo-bsc & osmo-bsc.cfg - base station controller
still use the same osmo-pcu,sgsn,ggsn,trx and osmo-bts-trx is started up last.
Was not too painful and GPRS is working
Thanks for the cfg files . but if you explained what to install and where that would be great !!
I changed the install.sh script a bit to add the missing dependencies , Now he install all without problems
echo “Install UHD”
git clone https://github.com/EttusResearch/uhd
cd uhd
cd host
mkdir build
cd build
cmake …/
make
sudo make install
sudo ldconfig
export LD_LIBRARY_PATH=/usr/local/lib
echo “Install libosmocore”
git clone git://git.osmocom.org/libosmocore.git
cd libosmocore/
autoreconf -i
./configure
make
sudo make install
sudo ldconfig -i
cd …
echo "Install LimeSuite"os
rm -rf LimeSuite
git clone https://github.com/myriadrf/LimeSuite
cd LimeSuite/build/
cmake …
make -j8
sudo make install
sudo ldconfig
cd …/…/
echo “Install osmo-trx”
git clone https://github.com/osmocom/osmo-trx.git
cd osmo-trx
autoreconf -fi
./configure
make -j5
make check
sudo make install
sudo ldconfig
cd …/
osmocom has been doing a lot of work recently, they just had a developers conference ( https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2018 ) and are changing (and naturally breaking) a bunch of things, I’m not sure the reasoning behind some of the requirements. For one thing osmo-trx now requires libusrp-dev.
I just rolled back osmo-trx to commit 53bdb7f82abbbcd7ecbb31c12ba877661bc6852f which builds osmo-trx, not osmo-trx-uhd and had to set LimeSuite back to v17.12 commit fe53178a3c74ce983ca8314c582c0547f723ec20 to get it all to work.
You’re welcome to try out my docker image Has LimeSuite, Soapy, uhd, osmoGSM stack, config files and startup scripts already sorted out. Much easier than trying to explain how it was done, which I’ve mostly forgotten :\
Wow Thanks !! I did not know that docker can be installed on Raspberry PI “https://blog.hypriot.com/getting-started-with-docker-and-windows-on-the-raspberry-pi/” today I’ll definitely try it . My Limesdr mini will work with your docker ?
Just read that (docker for 64/86) on the ARM processor can not start
I will think further (which single board computer to buy)
Thanks
sudo osmo-trx-uhd -c osmo-trx.cfg gives an error message
linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.1-36-ge7d011ee
Tue May 8 21:54:30 2018 DMAIN <0000> UHDDevice.cpp:662 [tid=140248111228864] No UHD devices found with address ‘’
Tue May 8 21:54:30 2018 DMAIN <0000> osmo-trx.cpp:446 [tid=140248111228864] Failed to create radio device
Shutting down transceiver…
Maybe it’s because I’m trying in Virtualbox ?. After sudo osmo-trx-uhd -c osmo-trx.cfg Virtualbox disables and enables USB back .
Today I’ll try on a physical hardware
