December 2016 - OpenBSC - lists.osmocom.org

by Max

HI. A little heads up: uhd version in jenkins building osmo-trx should be updated to 3.9.0 - this would allow gerrit #1117 to be properly verified by jenkins. -- Max Suraev <msuraev(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

7 years, 3 months

4
5
0 0

RFC: OsmoDevCon 2017 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.] >From 2012 to 2016 we were running a series of small, invitation-only Osmocom Developer Conferences. Access was intentionally restricted to those community members who have demonstrated an existing track record of contribution to any of the projects under the Osmocom umbrella. This format of a small, tightly knit group of about 20 people has been successful over the years, and I have received a lot of positive feedback from past participants. On the other hand, the Osmocom project has grown in scope and diversity, and some of those projects don't have all that much relationship to each other - except being started by people from within the same group. There's the cellular communications (GSM/GPRS/EDGE/UMTS and hopefully at some point LTE) protocols which is attracting a lot of professional users. And then there's pure community projects like rtl-sdr, OsmocomBB, OsmocomGMR and many other efforts. Particularly the cellular infrastructure projects (OsmoBTS, OsmoPCU, OsmoBTS, OsmoNITB, OsmoSGSN, OpenGGSN, OsmoIuh & co) are somehow "standing out" of the othe projects in the context of having a wider user bsae, and in that user base also primarily commercial users. So I'd like to start a discussion on how to possibly change the event format to accomodate the various interests and parties. I definitely don't want to loose the "annual meeting of old friends" atmosphere, while at the same time also opening up to other interested parties. One idea would be to keep OsmoDevCon as-is and have a separate event where non-contributing/developing users / sysadmins / system integrators could also be attending. Another idea would be to split into a 'user day' and 'developer days' format. This is something the netfilter developer workshops have been using for many years, and from my limited insight quite successfully so. The "user day" is more like a traditional tech conference, with a large auditorium and talks oriented towards users / sysadmins / integrators of the software. The "developer days" are the invitation-only part, for known contributing developers only, similar to what we have at OsmoDevCon. Having both events (or both parts of an event) back-to-back has the advantage that a large number of potential speakers for the 'user day' are already present, and they don't have to travel yet another time. One could even structure it further and say we have one user day, one public 'Osmocom cellular developer day' and then the closed 'OsmoDevCon classic', maybe reduced from 4 days to 3 or even 2 days only? What is the general opinion about this? Are there people lurking on this list who would be interested in attending a public 'user day' or even 'developer day' about the Osmocom cellular projects, with presentations and workshops around topics such as running Osmocom based cellular networks? In terms of when/where, I would suggest to keep the tradition of April in Berlin/Germany. But I'm of course very happy if somebody wants to host it some place else... Regards, and looking forward to meeting you [again] in 2017, 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, 4 months

6
14
0 0

Re: libosmocore[master]: libosmocoding: migrate transcoding routines from OsmoBTS

by Neels Hofmeyr

On Sat, Dec 31, 2016 at 01:10:30PM +0000, Vadim Yanitskiy wrote: > Regarding to the change, there is a problem: despite all tests > pass without any problems on my machine, some tests fail on Jenkins. > I will try to find out, what's wrong. Let me know if I should install some library dependencies or similar on the build slaves... ~N -- - 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, 4 months

1
0
0 0

OsmoNITB timeslots configuration and UmTRX

by Родион Гадыршин

Hello, list. I have umtrx v2.1 and I have already built GSM and GPRS components. Now I want to know which way of configuring timeslots in osmobsc.cfn is the best. I want GPRS, calls and SMS work. My current configuration is: timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config SDCCH8 hopping enabled 0 timeslot 2 phys_chan_config TCH/F hopping enabled 0 timeslot 3 phys_chan_config TCH/F hopping enabled 0 timeslot 4 phys_chan_config PDCH hopping enabled 0 timeslot 5 phys_chan_config PDCH hopping enabled 0 timeslot 6 phys_chan_config PDCH hopping enabled 0 timeslot 7 phys_chan_config PDCH hopping enabled 0 Is there a better way to configure? Maybe better use TCH/F_TCH/H_PDCH, but I have heard, that TCH/F is currently not working in dynamic configurations - only TCH/H does. And there is no only TCH/H_PDCH mode. So, could you please give me an advice?

7 years, 4 months

2
1
0 0

[XTRX] Price?

by Choukou Moun

Hello. Wath is the price of the xtrx board ? Thank you.

7 years, 4 months

2
1
0 0

ki in osmo-nitb's built-in HLR db

by Neels Hofmeyr

Merry x-mas! Just now I found a curious problem with the current osmo-nitb ciphering key. I'm working on the new VLR, which will inherently fix this issue, but in the course of that I recapped the current osmo-nitb's sequence of events for 2G ciphering as it is on the openbsc master branch. It so happens that I'm using a SIM card with a fabricated Ki value of hex: 000102030405060708090a0b0c0d0e0f i.e. starting with a zero byte. I was able to store this in and retrieve from the hlr.sqlite3 db: sqlite> INSERT INTO "AuthKeys" VALUES(57,2,X'000102030405060708090A0B0C0D0E0F'); sqlite> select hex(a3a8_ki) from AuthKeys; 000102030405060708090A0B0C0D0E0F So there were 16 bytes worth of BLOB in the Ki column for sure. But in openbsc's db.c in db_get_authinfo_for_subscr(), I always got DMM <0002> ../../../src/libmsc/auth.c:70 Invalid COMP128v1 key (len=0) Curious, could it be the zero byte? Just to check, I put the zero byte further left: sqlite> select hex(a3a8_ki) from AuthKeys; hex(a3a8_ki) F00102030405060008090A0B0C0D0E ^ nonzero ^^ zero Now the log says: DMM <0002> ../../../src/libmsc/auth.c:70 Invalid COMP128v1 key (len=5) f1 f3 f4 f5 f6 That's even weirder. I was expecting a 7 byte BLOB, of f0 01 02 03 04 05 06 and not f1 f3 f4 f5 f6 ... what on earth ... It appears that we've so far always been unable to use Ki keys that contain a zero byte, or apparently anything that's outside the 7bit ascii space ... ? To be able to recap what the old osmo-nitb is doing (without going to fetch a card reader from the office and reprogram the Ki on the SIM card), I fixed this bug with this funny little hack: https://gerrit.osmocom.org/1504 Todo: are other BLOB values also affected? Is there a better way to fix? Even though the new VLR is on its way, it might be good to get a fix like this out in the meantime ... though it appears that no-one is using ciphering on 2G anyway? ~N -- - 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, 4 months

2
3
0 0

Debugging osmo-trx constellation on XTRX SDR

by Alexander Chemeris

Hi Thomas, We're porting osmo-trx to our XTRX and we see some weird constellation (https://goo.gl/photos/1KycUsv26Z6T6aN97). It looks like a normal GMSK circle is there, but there is also a square like if a signal is clipped. Do you have any idea what could cause this from your previous experience? We're running osmo-trx at 4 SPS. Then we double sample rate in software (XTRX can't handle sample rates below 2 MSPS yet) and then transmit. See first image above. Then we tried to increase sample rate and enabled 4x interpolation in LMS7 - that led to a distorted cicrle + square constellation (https://goo.gl/photos/zMZRecxmZsqiCYMHA). -- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. https://fairwaves.co

7 years, 4 months

2
2
0 0

Error of skipping buffer data

by Mayuri Tendulkar

Hi Team Has anybody seen error like below while running osmo-stack on B210? What could be the reason of this failure? We are seeing this randomly. ERR 140460077602560 20:17:18.4 UHDDevice.cpp:1039:check_rx_md_err: An internal receive buffer has filled at 31.9377 sec. ERR 140460077602560 20:17:18.4 UHDDevice.cpp:1576:write: Skipping buffer data: timestamp=8696668 time_end=8651398 ERR 140460077602560 20:17:18.4 UHDDevice.cpp:1576:write: Skipping buffer data: timestamp=8696668 time_end=8651398 ERR 140460077602560 20:17:18.4 UHDDevice.cpp:1576:write: Skipping buffer data: timestamp=8696668 time_end=8651398 ERR 140460077602560 20:17:18.4 UHDDevice.cpp:1576:write: Skipping buffer data: timestamp=8696668 time_end=8651398 NOTICE 140460079380224 20:17:34.0 Transceiver.cpp:306:stop: Stopping the transceiver ALERT 140460079314688 20:24:03.3 radioInterface.cpp:323:pullBuffer: Receive error 0 ERR 140460079314688 20:24:03.4 UHDDevice.cpp:1039:check_rx_md_err: An internal receive buffer has filled at 437.017 sec. Regards Mayuri

7 years, 4 months

1
0
0 0

sporadic gerrit build job failue: "broken pipe"

by Neels Hofmeyr

We get this more often than not in the openbsc build job, I'm still not sure how to fix it: ====================================================================== ERROR: testBSCreload (__main__.TestVTYNAT) ---------------------------------------------------------------------- Traceback (most recent call last): File "./vty_test_runner.py", line 785, in testBSCreload b0 = nat_bsc_sock_test(0, "lol") File "./vty_test_runner.py", line 1276, in nat_bsc_sock_test ipa_handle_resp(bsc, tk, verbose) File "./vty_test_runner.py", line 1260, in ipa_handle_resp x.send(IPA().id_resp(IPA().identity(name = tk.encode('utf-8')))) error: [Errno 32] Broken pipe ---------------------------------------------------------------------- Ran 43 tests in 51.717s FAILED (errors=1) Reducing the nr of executors hasn't had an effect yet. Could there be another cause? Too fragile timing or something? ~N -- - 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, 4 months

2
4
0 0

indicating a necessary revision

by Neels Hofmeyr

When committing a change that needs a specific change from another project, but that other change is still in the gerrit queue and has no final git commit hash yet, it is handy to use the Change-Id to reference the given decision. Harald recently requested that I always include the Change-Id in the commit log. Now Max says: > It's better to update commit log with git commit hash instead of change-id > before final submission. Can we get consensus? Should we modify the commit log from Change-Id to git hash once the required other commit is through? The Change-Id is always there and can be searched for in the git log; and should we ever decide to rehash the git history or move to another version control software (losing all git hashes), the Change-Id would still be there. But the git hash, once it is finalized, can be used directly on the git commandline. I wouldn't have done the extra effort, but if all agree that the git hash is better, I'll change it (and hopefully remember to do it, too). ~N

7 years, 5 months

1
0
0 0

osmo-iuh-3G_2016_09

by Radiarisainana Sitraka

Hello, I have some question, is it possible to run osmo-iuh with the vodafone signal secure 3 !? or should I root it !? Chears,

7 years, 5 months

2
1
0 0

libosmocore changes / release process

by Neels Hofmeyr

When I now change pretty much anything in libosmocore that I want to use in e.g. openbsc.git, I would like to bump the minor revision and reference that in other projects' configure.ac. The effort is ok if it entails only tagging a revision and using that elsewhere. However, this has come down to a lengthy process: " cleanup TODO-RELEASE file if not empty, bumping API versions accordingly (see comments in TODO-RELEASE) update debian/changelog using "gbp dch" command " https://osmocom.org/projects/cellular-infrastructure/wiki/Make_a_new_releas… So, pretty much every commit in libosmocore will be followed by another commit that is adjusting the changelog...? :/ Should we adjust the changelog along with pretty much any change used outside of libosmocore? :/ (probably not, because reverting anything is made cumbersome) Should we rather, like, make a libosmocore release only once a week and somehow track wich other projects need a bump to the required libosmocore version? I think most projects out there make a release tag only every now and then. We could limit to noting the required libosmocore change-id in other projects' commit logs until the next (minor) release is made...? Can we add a fourth level of version that doesn't require a changelog/debian release? So for every small change I make I would tag 0.9.6.1, 0.9.6.2, etc., and at some point we make 0.9.7 along with a changelog adjustment? Thoughts? ~N -- - 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, 5 months

3
7
0 0

reduce gerrit mails?

by Neels Hofmeyr

Hi Gerrit users, I follow the gerrit mails to get notified of comments and to catch failing builds. The message that a build started or was successful though doesn't help me much, only clutters up space, really. Do you agree? If yes, I would try to silence the "Build started" and "Build successful" messages in our gerrit, if possible without too much effort... ~N

7 years, 5 months

3
5
0 0

[nhofmeyr@sysmocom.de: Re: Help required on : Reproducing the issue]

by Neels Hofmeyr

On Wed, Dec 14, 2016 at 02:24:23PM +0000, Pravin Kumaravel Manoharan wrote: > I tried to reproduce the issue mentioned in http://lists.osmocom.org/pipermail/openbsc/2016-December/009966.html . > While running sanitizer script I got an error gcc: error: unrecognized command line option '-fsanitize=undefined' > So, to avoid this I removed the option from CFLAGS+= and CXXFLAGS+= . That's odd, all compilers I've used so far apparently support -fsanitize=address -fsanitize=undefined anyway: > Then I got the following error : > ERROR: Address Sanitizer: heap-use-after-free on address 0x60380000a00c at pc 0x436acf bp 0x7ffc4456d4e0 sp 0x7ffc4456d4d8 > but I didn't get any SIGSEGV in sgsn_create_pdp_ctx(). Have you reversed the order of those two lines I wrote about earlier to fix the use-after-free yet? This is what I wrote: > I found a use-after-free which isn't the cause for above asan failure: > > gsm0408_gprs_access_cancelled(mm, GMM_CAUSE_GPRS_NOTALLOWED); > LOGMMCTXP(LOGL_NOTICE, mm, "No PDP context to deactivate\n"); > > gsm0408_gprs_access_cancelled() calls mm_ctx_cleanup_free(), and after that the > local mm is non-NULL but freed. Change the order to: > > LOGMMCTXP(LOGL_NOTICE, mm, "No PDP context to deactivate\n"); > gsm0408_gprs_access_cancelled(mm, GMM_CAUSE_GPRS_NOTALLOWED); > > (This second issue is shown when removing test_pdp_deactivation_with_pdp_ctx() > from test_pdp_deactivation()) If you do that, do you still get any asan errors? I hope that you'll be able to reproduce the segfault, since it was seen on both our build server as well as my own laptop... ~N -- - 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 ----- End forwarded message ----- -- - 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, 5 months

1
0
0 0

git tagging

by Max

Hi. With the migration to gerrit the situation around version tagging become even funnier than before. For example right now in libosmocore v0.9.3 does not exist as a git tag, only as entry in debian/changelog. Versions 0.9.5 and 0.9.6 are committed in reversed order - see output of git log --tags --show-notes --decorate | grep 'tag:' | head So the questions are: - how can I add tag '0.9.3' to commit abc46af90fde9e9435dee5f4f472aec3f68d3353 in libosmocore - how can we prevent the inverted commit situation as with 0.9.6 and 0.9.5 in future? - what's the general guidelines for tagging new versions? Do we go through gerrit or ask responsible person (who?) to do it manually? Or even auto-tag commit matching certain criteria? -- Max Suraev <msuraev(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

7 years, 5 months

3
4
0 0

Re: libosmocore[master]: Catch-up with git version tags

by Neels Hofmeyr

On Tue, Dec 13, 2016 at 10:58:12PM +0000, Holger Freyther wrote: > Patch Set 1: Code-Review-1 > > The point of TODO-RELEASE is to remember ABI changes. An ABI change requires increasing the version number of the .so files (see the libtool link in Makefile.am for exact rules but we only bump for incompatible versions). Another point here could be that we can't just create a new minor tag without checking this? Does our non-existent policy dictate that an ABI version change should cause a bump in a "middle" version number? i.e. if a commit has been merged that has ABI changes and I want to tag a commit in order to reference it from another project's configure.ac, am I forced to make a bigger version bump than just 0.9.4 -> 0.9.5? All this would be good topics for the next OsmoDevCon... ~N

7 years, 5 months

1
0
0 0

Re: Osmo-bts/Osmocom-bb virtual layer 1

by Sebastian Stumpf

Hi Harald, > why send a private response and not a mail to the mailing list? Sorry, not intended - misclicked on respond instead of respond to all! :) > If you want, I can give you commit access so you can push your private > branches to git.osmocom.org. I just created an account on osmocom.org and logged in to gerrit via osmocom.org/openid (account: BastusIII). As I have never used git-send-email I prefer the commit access. Thank you! I would call the branches stumpf/virt-phy for both osmo-bts and osmocom-bb. With kind regards, Sebastian Am 12.12.2016 15:15 schrieb "Harald Welte" <laforge(a)gnumonks.org>: Hi Sebastian, why send a private response and not a mail to the mailing list? I think they all are interested to read this. On Mon, Dec 12, 2016 at 01:57:05PM +0100, Sebastian Stumpf wrote: > I have not published the Code yet as the vlayer still lacks some basic > functionality. Would you suggest to do so already? yes, by all means. There's a difference between having code in the public for review / improvements by others and submitting it for inclsion into master as it is considered "fixed" If you want, I can give you commit access so you can push your private branches to git.osmocom.org. For that, you would have to create an account on gerrit.osmocom.org (which requires first creating one on osmocom.org) If you prefer to simply send a patchset by git-send-email or to host you git repos on github or any other git hosting site, that's fine, too. -- - 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, 5 months

3
4
0 0

Re: RBS 2308

by Rajitha peiris

Hi dear.... i am tired with rbs 2308.... i have purchased nano bts....but i will try to improve that also.... if you have any updates pls letme... On Harald Welte <laforge(a)gnumonks.org>, Dec 12, 2016 2:45 AM wrote: Hi Rajitha, On Sun, Dec 11, 2016 at 01:02:19PM +0000, Rajitha peiris wrote: > i was spent more time on it....these days i am reading on oml 2000 ...if there new updates i will tell you.... If you run into a specific issue, please always feel free to contact this list. But make sure to include your full config file, openbsc log output and pcap protocol trace. We need sufficient data for any kind of investigation. -- - 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, 5 months

1
0
0 0

new sanitizer breakage: SIGSEGV in sgsn_create_pdp_ctx()

by Neels Hofmeyr

The sanitizer build used to get through to testing the PCU, now it already fails at openbsc's sgsn test. This happens in the recently added test_pdp_deactivation_with_pdp_ctx: http://jenkins.osmocom.org/jenkins/job/Osmocom_Sanitizer/388/consoleFull commit 1611df5226199da2bf2fba3d22d93cc1a6c6c777 Commit: Pravin Kumarvel <pmanohar(a)radisys.com> CommitDate: Mon Dec 12 17:20:39 2016 +0530 Support Deactivate PDP Context Request from network https://gerrit.osmocom.org/1262 I can reproduce the segmentation fault locally, but only when the sanitizer is enabled. When stepping up to the failure and checking the parameters, all seems to be in order; immediately when trying to step into sgsn_create_pdp_ctx(), the SIGSEGV is fired. So far the actual failure is not clear to me, I haven't found the 0x02 pointer yet that asan complains about: ==21897==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000002 I found a use-after-free which isn't the cause for above asan failure: gsm0408_gprs_access_cancelled(mm, GMM_CAUSE_GPRS_NOTALLOWED); LOGMMCTXP(LOGL_NOTICE, mm, "No PDP context to deactivate\n"); gsm0408_gprs_access_cancelled() calls mm_ctx_cleanup_free(), and after that the local mm is non-NULL but freed. Change the order to: LOGMMCTXP(LOGL_NOTICE, mm, "No PDP context to deactivate\n"); gsm0408_gprs_access_cancelled(mm, GMM_CAUSE_GPRS_NOTALLOWED); (This second issue is shown when removing test_pdp_deactivation_with_pdp_ctx() from test_pdp_deactivation()) The cause for the asan failure shown above and in jenkins still evades me. But I'm afraid we have to revert the patch. Please run the asan build on this patch and re-submit when the cause is clear. How to asan build has been discussed recently: http://lists.osmocom.org/pipermail/openbsc/2016-November/009901.html ~N -- - 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, 5 months

2
2
0 0

TbfTest fails sanitizer build, please take a look @tbf-folks

by Neels Hofmeyr

Dear authors of Tbf, can you make sense of this build failure? https://jenkins.osmocom.org/jenkins/job/Osmocom_Sanitizer/373/console It shows that the expected stderr output of the TbfTest deviates, and the test exits prematurely. interesting output: +tbf_dl.cpp:766:65: runtime error: load of value 32767, which is not a valid value for type 'egprs_puncturing_values' -- got ack for BSN=1258 -- got ack for BSN=1259 -- got ack for BSN=1260 +- got NACK for BSN=1258 +- got NACK for BSN=1259 +- got NACK for BSN=1260 To help reproducing it, find below the jenkins script that runs this sanitizer build. Thanks for any patches that could fix our sanitizer build! ~Neels #!/bin/sh set -ex export BUILDDIR=$PWD/build/ export PKG_CONFIG_PATH=$BUILDDIR/lib/pkgconfig export LD_LIBRARY_PATH=$BUILDDIR/lib/ export PATH="$PATH:$HOME/osmo-ci/scripts" build() { RET=$PWD git clone git://git.osmocom.org/$1 source/$1 cd source/$1 git checkout -b build-branch origin/$2 cd $3 autoreconf --install --force ./configure --prefix=$BUILDDIR $4 make check CFLAGS+="-fsanitize=address -fsanitize=undefined" CXXFLAGS+="-fsanitize=address -fsanitize=undefined" ASAN_OPTIONS="detect_leaks=0" UBSAN_OPTIONS="print_stacktrace=1:halt_on_error=1" \ || cat-testlogs.sh make install CFLAGS+="-fsanitize=address -fsanitize=undefined" CXXFLAGS+="-fsanitize=address -fsanitize=undefined" cd $RET } rm -rf $BUILDDIR rm -rf source mkdir -p source mkdir -p $BUILDDIR/include/sysmocom/femtobts git clone git://git.sysmocom.de/sysmo-bts/layer1-api.git source/layer1-api/ cp source/layer1-api/include/* $BUILDDIR/include/sysmocom/femtobts/ build libosmocore $LIBOSMOCORE_BRANCH ./ build libosmo-abis $LIBOSMOABIS_BRANCH ./ build libosmo-netif $LIBOSMONETIF_BRANCH ./ build libosmo-sccp $LIBOSMOSCCP_BRANCH ./ # gcc ice's #build libsmpp34 $LIBSMPP_BRANCH build openggsn $OPENGGSN_BRANCH ./ build openbsc $OPENBSC_BRANCH ./openbsc "--enable-nat --enable-osmo-bsc --enable-vty-tests --enable-external-tests" build osmo-pcu $OSMOPCU_BRANCH ./ "--enable-sysmocom-dsp --enable-vty-tests" build osmo-bts $OSMOBTS_BRANCH ./ "--enable-sysmocom-bts --enable-trx" -- - 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, 5 months

2
6
0 0

Osmo-bts/Osmocom-bb virtual layer 1

by Sebastian Stumpf

Hi, I further implemented the base of the virtual layer with the purpose of replacing the um-air interface with a multicast-socket solution. This has been started by Harald Welte some time ago in the Osmobts - laforge/virt-bts branch. As I was not really confident enough to create an official new branch before someone had a look on what I did, so I developed in copies of the osmocom-bb and osmo-bts projects on my github-page (https://github.com/BastusIII/osmocom-bb-virt/tree/stumpf/virt-um and https://github.com/BastusIII/osmo-bts-virt/tree/stumpf/virt-bts). If someone finds to time to have a look into them (structure, path, implementation) and give me feedback about it, I would be glad :). Please use the following config files that i have tested: - https://github.com/BastusIII/osmocom-config-files/blob/master/openbsc-virtu… - https://github.com/BastusIII/osmocom-config-files/blob/master/osmobts-virtu… - https://github.com/BastusIII/osmocom-config-files/blob/master/osmocom-bb-mo… What works: BTS: - downlink over gsmtap and a multicast socket - OML and RSL on abis properly established and seems to work - virtual-um connection establishment Osmocom-bb: - virtual-um -- l23 app connection establishment (bridging osmocon, no serial link needed) - BCCH downlink handling and forwarding to l23 app - handling of some l1ctl requests from l23 (e.g. power management had to be mocked, so l23 gets a response and is satisfied) What not: BTS: - missing uplink handling Osmocom-bb - missing uplink routines (RACH, TCH, dedicated channels) - handlers for l23 requests only partially implemented (missing TCH, RACH, ... I a currently a bit overwhelmed by the mass of messages exchanged between l23-app (used mobile, btw.) and the virtual-um and hanging because mobile gets a sync timeout. I am looking forward to hear from you :). Sebastian Stumpf

7 years, 5 months

2
2
0 0

Re: RBS 2308

by Rajitha peiris

hi dear... i was spent more time on it....these days i am reading on oml 2000 ...if there new updates i will tell you.... regards rajitha Sent from my Mi phone On Holger Freyther <holger(a)freyther.de>, Dec 10, 2016 8:42 PM wrote: > On 10 Dec 2016, at 03:10, Rajitha peiris <raji.oshin(a)hotmail.com> wrote: > > > Hi all.. Hi! > Anyone have success with rbs 2308 ??? > If you have any idea pls share ... your contribution will be very welcome! Do you think you can still spend time on improving OpenBSC in 2016? regards holger

7 years, 5 months

2
1
0 0

openbsc build was broken due to change in libosmocore: missing doc for 'log gsmtap [HOSTNAME]'

by Neels Hofmeyr

The libosmocore commit aa00f99be2e4cc64ede20d8c9548b83054696581 adds a VTY item that's missing a doc string, hence breaking the openbsc build (which actually checks the doc strings unlike the libosmocore build job). I pushed the fix I734b22c950242541322e902887bf779c14ba10fd and things should light up "green" (aka blue) again. BTW, in a RL discussion lynxis suggested that it would be good if libosmocore commits were also checked against breaking openbsc. A point against it is that often something in libosmocore is changed and requires a follow-up in openbsc -- if the libosmocore build rejects commits that break openbsc, it would make it impossible to get these changes in. The workaround could be to have a secondary build job that merely comments on gerrit whether the openbsc build still works, without having -V voting powers. Anyway, so far I think it is sufficient to catch these hopefully few cases once the regular master build on jenkins.osmocore.org goes up red, like now. ~N -- - 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, 5 months

2
1
0 0

Re:OpenBSC Digest, Vol 26, Issue 7

by Rajitha peiris

anyone know about rbs 2308 is supported yet or not...or still under experimental stage... thanks regards rajitha peiris sri Lanka Sent from my Mi phone On "openbsc-request(a)lists.osmocom.org" <openbsc-request(a)lists.osmocom.org>, Dec 7, 2016 11:11 PM wrote: Send OpenBSC mailing list submissions to openbsc(a)lists.osmocom.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.osmocom.org/mailman/listinfo/openbsc or, via email, send a message with subject or body 'help' to openbsc-request(a)lists.osmocom.org You can reach the person managing the list at openbsc-owner(a)lists.osmocom.org When replying, please edit your Subject line so it is more specific than "Re: Contents of OpenBSC digest..." Today's Topics: 1. Re: Paging not answered in m2m call (Holger Freyther) 2. Re: Paging not answered in m2m call (Kristian Martens) ---------------------------------------------------------------------- Message: 1 Date: Wed, 7 Dec 2016 18:13:10 +0100 From: Holger Freyther <holger(a)freyther.de> To: Kristian Martens <kristian.martens(a)ng4t.com> Cc: openbsc(a)lists.osmocom.org Subject: Re: Paging not answered in m2m call Message-ID: <D782A7D5-AD0D-4BE0-9898-2AEC6151BAB0(a)freyther.de> Content-Type: text/plain; charset=us-ascii > On 07 Dec 2016, at 17:52, Kristian Martens <kristian.martens(a)ng4t.com> wrote: > > Hello, Hi! > two UEs (A and B) are successfully registered in a network. Now A tries > to call B. B is paged by the core via A interface but the sysmoBSC/BTS > does not seem to page the UE (or UE does not answer paging). What could > be the reason for this behaviour? How could the problem be debugged? > Please find the attached pcap for your reference. nice MNC! The P-TMSI doesn't really look that random but it might be an index into an internal data structure? So on A this looks right. The LAI is 262-79-1 and this is where you are paging. In general it might be: * osmo-bsc doesn't translate this to actual paging. E.g. not linking/ handling the location area identifier. You could trace the RSL protocol and see if a paging command is being sent (periodically) to the BTS? * The MS still has a radio channel open. I notice that clear command is being sent so this is unlikely to be the case. Also IMSI seems to be match.. maybe the MS still calculates the paging group wrongly? That is far fetched though. holger ------------------------------ Message: 2 Date: Wed, 7 Dec 2016 18:41:08 +0100 From: Kristian Martens <kristian.martens(a)ng4t.com> To: Holger Freyther <holger(a)freyther.de> Cc: openbsc(a)lists.osmocom.org Subject: Re: Paging not answered in m2m call Message-ID: <9a4bcc68-e884-0f48-8a26-989b7edf5bca(a)ng4t.com> Content-Type: text/plain; charset="utf-8" Hi, I have captured a trace. Can you find something out? Thanks, Kristian Am 07.12.2016 um 18:13 schrieb Holger Freyther: >> On 07 Dec 2016, at 17:52, Kristian Martens <kristian.martens(a)ng4t.com> wrote: >> >> Hello, > Hi! > >> two UEs (A and B) are successfully registered in a network. Now A tries >> to call B. B is paged by the core via A interface but the sysmoBSC/BTS >> does not seem to page the UE (or UE does not answer paging). What could >> be the reason for this behaviour? How could the problem be debugged? >> Please find the attached pcap for your reference. > > nice MNC! The P-TMSI doesn't really look that random but it might be an > index into an internal data structure? > > So on A this looks right. The LAI is 262-79-1 and this is where you are > paging. In general it might be: > > * osmo-bsc doesn't translate this to actual paging. E.g. not linking/ > handling the location area identifier. You could trace the RSL protocol > and see if a paging command is being sent (periodically) to the BTS? > > * The MS still has a radio channel open. I notice that clear command is > being sent so this is unlikely to be the case. Also IMSI seems to be > match.. maybe the MS still calculates the paging group wrongly? That is > far fetched though. > > > holger -------------- next part -------------- A non-text attachment was scrubbed... Name: 20161207_nopaging.pcap Type: application/octet-stream Size: 26302 bytes Desc: not available URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20161207/dccfca29/at…> ------------------------------ Subject: Digest Footer _______________________________________________ OpenBSC mailing list OpenBSC(a)lists.osmocom.org https://lists.osmocom.org/mailman/listinfo/openbsc ------------------------------ End of OpenBSC Digest, Vol 26, Issue 7 **************************************

7 years, 5 months

2
1
0 0

RBS 2308

by Rajitha peiris

Hi all... Anyone have success with rbs 2308 ??? If you have any idea pls share ... Thanks Regards Rajitha peiris Sri lanka Sent from my Mi phone

7 years, 5 months

2
1
0 0

Re: range1024 encoding question

by Max

In which repo it is? I don't know of other users but I might have overlooked smth. 08.12.2016 21:10, Holger Freyther пишет: > > hard to say. Initially I tried to use less storage but we have other range encoding users and testcases for it? E.g. Jacob created property based testing for it. Did you have a look there? > > holger > > -- Max Suraev <msuraev(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 Directors: Holger Freyther, Harald Welte

7 years, 5 months

1
0
0 0

range1024 encoding question

by Max

Hi. I've stumbled upon situation where range1024 encoding produces weird results - see gerrit #1373 and http://jenkins.osmocom.org/jenkins/job/OpenBSC-gerrit/1515/IU=--disable-iu,… right before "Wrong number of arfcns" Is this because I call it somehow wrong or there's actually a flaw in our implementation? -- Max Suraev <msuraev(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

7 years, 5 months

1
0
0 0

M2M call with no voice

by Kristian Martens

Hello, I got a mobile to mobile call working for signalling only. Two RTP channels are being established successfully. But there are only a few pattern sent over these channels (1 byte 0x23 as UDP payload). Is there a setting I am missing in the configuration files? Please find attached a .zip file with pcap and cfg files. Thanks, Kristian

7 years, 5 months

2
1
0 0

MGCP logging

by Kristian Martens

Dear all, I have switched on logging to file and have set the log level to "debug" for "mgcp" in both osmo-bsc.cfg and osmo-bsc-mgcp.cfg. Still I cannot find any output in the log file related to MGCP if I get an error. Is there a trick to make the MGCP module more verbose? Thanks, Kristian

7 years, 5 months

4
18
0 0

osmo-iuh-3G_2016_09

by Radiarisainana Sitraka

Hello, I would also ask if the osmo-iuh-3G_2016_09 support the new sfr-femto tha sfr sold now (for 90 euro) or it's not available only for le old sfr femto !?Is it possible also for the new femtocell vodafone signal secure 3 !? (and if it's possible I would like to konw how to find Tx-Rx-GND for this femto) Thanks for helping chears,

7 years, 5 months

2
1
0 0

osmo-trx debian nightly builds fail due to uhd requirement

by Harald Welte

Dear all, as osmo-trx has recently introduced a dependency on a super-recent version of UHD (as opposed to what regular stable distributions ship), the nightly debian builds are broken for both Debian 8.0 and Ubuntu 14.04: https://build.opensuse.org/package/show/network:osmocom:nightly/osmo-trx I would like to ask the osmo-trx folks to consider a) adding the uhd version dependencly to the debian rules b) submitting a suitable uhd package version that can be build in the osmoco nightly OBS repository 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, 5 months

4
7
0 0

osmo-trx binary can't be moved between "same" CPUs

by Neels Hofmeyr

Hi osmo-trx folks, I'd like to draw your attention to https://osmocom.org/issues/1869 -- "osmo-trx binary cannot be moved to similar CPU" Has anyone seen this before and/or is up to the task of fixing it? Thanks! ~N -- - 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, 5 months

2
2
0 0

Dynamic TCH/F_PDCH does not work as TCH/F for CS voice call

by Mrinal Mishra

Hello All, As reported earlier "CS call is not working using TCH/F_PDCH dynamic channel configuration" in URRP B210 board(osmo-trx) . We further checked the commit version using git bisect to find out the exact version from where this functionality is broken . Below is the commit version of BSC : c3f72f63afde926dfc46827d6880055597515fb6 dyn TS: fix: ts_subslots() for TCH/F_PDCH in PDCH mode Thanks and Regards, Mrinal

7 years, 5 months

3
2
0 0

libosmocore support for GSMTAP based logging

by Harald Welte

Dear all, when debugging Osmocom programs, one usually looks at either the pcap trace of one of the many interfaces (Um interface via GSMTAP or OsmocomBB, Abis, Gb, Gp or A interface via ethernet, ...) or at the log files of the various osmocom programs. Sometimes it can be hard to match the two different domains, and it is useful to see in sequence when a certain message was received and what kind of actions this triggered inside e.g. OsmoPCU or OSmoSGSN. One could have used the libosmocore 'syslog' log target for this and then configure the local syslog daemon to log to a remote syslog server via the network. However, as there is another local process and context switches involved, the messages were re-ordered. Also, syslog only receives the fully-formatted log string, and not the meta-data like the log level or sub-system. Hence, the idae of having a GSMTAP based log target was floating around the project for many years. I finally implemented this today. The advantage is that in our single-threaded osmocom programs the GSMTAP messages will leave in-sequence with the protocol messages received or transmitted, and there is only the limited chance of re-ordering by the local network stack and/or intermediate routers. Both shouldn't be much of a concern during local debugging. What do you need to use this? 1) The follwoing three libosmcoore commits from gerrit: https://gerrit.osmocom.org/#/c/1355 https://gerrit.osmocom.org/#/c/1356 https://gerrit.osmocom.org/#/c/1357 2) a "log gsmtap" configuration in your config file (or via vty), similar to how syslog logging is configured: === SNIP === log gsmtap localhost logging filter all 1 logging color 1 logging print category 0 logging timestamp 0 logging level all everything logging level rll notice [...] === SNIP === 3) a wireshark with my Change-ID I0de723445e5b5ce0199a4081808111240a9ed047 (can also be found in the laforge/gsmtap-log branch of git://git.osmocom.org/wireshark or http://git.osmocom.org/wireshark/commit/?h=laforge/gsmtap-log&id=3a207894a4… I will leave this in review for a few days and then plan to merge it into libosmocore. The wireshark patch will also be submitted at that time. A screenshot is attached for your reference. There is of course no coloring of the lines in wirshark, but you can set various wireshark filters (e.g. on log level, sub-system) and also use colorization rules to e.g. map sub-systems again to colors. 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, 5 months

1
0
0 0

broken build, reverting CHREQ_T_PDCH_ONE_PHASE and CHREQ_T_PDCH_TWO_PHASE

by Neels Hofmeyr

Heads up, the current openbsc build is broken, as verified by https://jenkins.osmocom.org/jenkins/job/OpenBSC/ This is due to below libosmocore commit, which adds two items to enum chreq_type, thereby implicitly enlarging the ctype_by_chreq struct and breaking the static assert for gsm_network->ctype_by_chreq's size: ../../../src/libbsc/gsm_04_08_utils.c:138:1: error: size of array ‘dummyassert_size’ is negative osmo_static_assert(sizeof(ctype_by_chreq) == ^ What this patch lacks is * adjustment of ctype_by_chreq[] according to the new additions in libbsc/gsm_04_08_utils.c * same for reason_by_chreq[], also in libbsc/gsm_04_08_utils.c * enlarge ctype_by_chreq[] in gsm_network to 18, in openbsc/gsm_data.h. I could try to guess what the ctype_by_chreq[] and reason_by_chreq[] items should be, but to not get distracted from my current task, and since the values don't seem to be used by the current master branches yet, I decided to simply revert the libosmocore commit and leave it up to the original authors to follow up. (No need to mention that those should be merged to libosmocore and openbsc "at the same time" to avoid builds failing.) Thanks and apologies for any inconvenience... ~Neels commit c3c28528de78fd5d50c3a141c2176c0da5dd7075 Refs: 0.9.0-299-gc3c2852 Author: Alexander Couzens <lynxis(a)fe80.eu> AuthorDate: Tue Nov 29 12:42:05 2016 +0100 Commit: Harald Welte <laforge(a)gnumonks.org> CommitDate: Thu Dec 1 15:26:29 2016 +0000 gsm0408: add chreq_type for CHREQ_T_PDCH_ONE_PHASE and CHREQ_T_PDCH_TWO_PHASE For BSC-located pcu the BSC must understand the PDCH chan request. Change-Id: Ice44dcaaf798f93af3652a96c567f8e16a6cf784 --- include/osmocom/gsm/protocol/gsm_04_08.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/osmocom/gsm/protocol/gsm_04_08.h b/include/osmocom/gsm/protocol/gsm_04_08.h index 767aa3d..c05b62e 100644 --- a/include/osmocom/gsm/protocol/gsm_04_08.h +++ b/include/osmocom/gsm/protocol/gsm_04_08.h @@ -1456,6 +1456,8 @@ enum chreq_type { CHREQ_T_PAG_R_TCH_F, CHREQ_T_PAG_R_TCH_FH, CHREQ_T_LMU, + CHREQ_T_PDCH_ONE_PHASE, + CHREQ_T_PDCH_TWO_PHASE, CHREQ_T_RESERVED_SDCCH, CHREQ_T_RESERVED_IGNORE, }; -- - 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, 5 months

2
3
0 0

RBS 2308 Protocol Error

by Caleb Pal

Good Evening, With the recent commits for the OM2000 protocol, I figured it was time to dust off the RBS2308 and see what would happen. I am using the latest version of DAHDI, with a TE122P T1 card. All osmocom software was pulled yesterday and installed successfully on a machine running Debian Stable. When OpenBSC starts, all appears normal with regards to bringing the BTS up until the timeslots for the first TRX are being configured. When the timeslots are configured, a protocol error is given for each. If I change trx0/ts0 from the default of CCCH+SDCCH4 to CCCH, that timeslot is successfully brought up, and the BTS transmits. Other configurations (TCH/F, TCH/F, PDCH, SDCCH8, TCH/F_TCH/H_PDCH) on timeslots 1-7 give the same protocol error. I have attached my openbsc.cfg, the output from the OpenBSC console, a pcap of the failed startup, and my DAHDI configuration. If they do not come through the list server, they are also available at: http://cleb.org/RBS/ Thanks, Caleb

7 years, 5 months

3
4
0 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC December 2016