Hello,
I battled with osmo-bts-trx this afternoon; it didn't want to build with old (at least not any I tried) nor recent libosmocore, so I ended up using a chainsaw and cutting pieces out of it. The outcome is here: https://github.com/shimaore/osmo-bts You can see what I had to remove here: https://github.com/shimaore/osmo-bts/commit/b5ac1c000e6d7bea57f7c1d8d47f43f9...
This version builds with libosmocore etc `master` revisions.(*) Once compiled this gives me a piece of software that starts and prints out messages on the console, and apparently connects to the transceiver on one side, and to osmo-bsc on the other side.
Anyhow, sending this out in hope this might save someone else a few hours. :} S.
(*) The `abis` and `rsl` code are completely different in recent libosmocore, I suspect this build uses the old `abis` code embedded inside osmo-bts. The sysmo-bts code was updated, but not the trx-bts code.
Hello,
Martin O'Shield encouraged me to post the documentation I had started on OsmoCom integration with UmTRX, so here you go:
* https://github.com/shimaore/umtrx-osmo-bts which describes how to get started with the BTS side
* https://github.com/shimaore/umtrx-osmo-bsc which deals with the BSC side
Basically each of these contain a "how.txt" file on how to build the software, and a "start.sh" template script on how to start it.
Feel free to use github's Issues and Pull Requests to ask questions or suggest changes. S.
Hi Stephane,
On 25 December 2013 22:10, stephane@shimaore.net wrote:
Hello,
I battled with osmo-bts-trx this afternoon; it didn't want to build with old (at least not any I tried) nor recent libosmocore, so I ended up using a chainsaw and cutting pieces out of it.
I recently followed the instructions on the wiki and it worked fine for me and without having to make any changes.
http://openbsc.osmocom.org/trac/wiki/network_from_scratch
Cheers,
Andrew
On Sat, Dec 28, 2013 at 2:04 PM, Andrew Back andrew@carrierdetect.com wrote:
Hi Stephane,
On 25 December 2013 22:10, stephane@shimaore.net wrote:
Hello,
I battled with osmo-bts-trx this afternoon; it didn't want to build with old (at least not any I tried) nor recent libosmocore, so I ended up using a chainsaw and cutting pieces out of it.
I recently followed the instructions on the wiki and it worked fine for me and without having to make any changes.
Btw, since recent updates in osmo-trx, you should use the master branch from the official Osmocom repo: http://cgit.osmocom.org/osmo-trx/ (preferred way) or the master branch from fairwaves osmo-trx repo: https://github.com/fairwaves/osmo-trx The latter may lag compared to the official Osmocom osmo-trx and thus is less preferred,
Hi Andrew,
I recently followed the instructions on the wiki and it worked fine for me and without having to make any changes. http://openbsc.osmocom.org/trac/wiki/network_from_scratch
I guess I must have tried that at first but skipped it because openbsc didn't want to build in the `jolly/testing` branch. However for the little bits open-bts-trx depends on in the openbsc code, this works fine (oops!).
So really the current path to compile the osmo-bts-trx jolly/trx branch remains to use the openbsc jolly/testing branch (as indicated on the wiki). I'll update my notes.
As I said, the jolly/testing branch of openbsc doesn't build fully. (Although I guess this still leaves you with an osmo-nitb binary!) The `master` branch of openbsc builds properly, that's why I got stuck with that in my mind ("it builds so it's the one to use!").
I'm not sure what the feature differences and stability are, though. osmo-nitb (master branch) crashes when I try to place mobile-to-mobile calls, I need to experiment with the different versions. S.
Hi all,
I think this discussion is better suited for the openbsc mailing list, as it is not specific to UmTRX. I would recommend you to move it there.
That said, we're using network_from_scratch procedure here, may be with minor changes, and it works very well.
Crashes you've seen may be related to some incompatibility between osmo-bts, osmo-nitb and libosmocore.
On Sat, Dec 28, 2013 at 6:42 PM, stephane@shimaore.net wrote:
I recently followed the instructions on the wiki and it worked fine for me and without having to make any changes. http://openbsc.osmocom.org/trac/wiki/network_from_scratch
I guess I must have tried that at first but skipped it because openbsc didn't want to build in the `jolly/testing` branch. However for the little bits open-bts-trx depends on in the openbsc code, this works fine (oops!).
So really the current path to compile the osmo-bts-trx jolly/trx branch remains to use the openbsc jolly/testing branch (as indicated on the wiki). I'll update my notes.
As I said, the jolly/testing branch of openbsc doesn't build fully. (Although I guess this still leaves you with an osmo-nitb binary!) The `master` branch of openbsc builds properly, that's why I got stuck with that in my mind ("it builds so it's the one to use!").
I'm not sure what the feature differences and stability are, though. osmo-nitb (master branch) crashes when I try to place mobile-to-mobile calls, I need to experiment with the different versions. S.
-- Stéphane Alnet -- Telecom Artisan. OpenSource Advocate. Development and integration for FreeSwitch, OpenSIPS, CouchDB, Node.js. Mobile: +33643482771 - http://shimaore.net/ - https://github.com/shimaore/
-
Alexander Chemeris -
Andrew Back -
stephane＠shimaore.net