Hello everyone,
we are struggling to set up an 2G network using single bsc and msc components rather than osmo-nitb. We successfully managed to run an 2G-Network with osmo-nitb using an usrp-n210 as trx.
Now how is the BSC supposed to connect to the MSC? In an older build of the osmo-bsc and like described in the osmo-msc user manual I was able to setup an cs7 instance using the m3ua via osmo-stp to the msc. But as I'm using the nighlty-packages now there is no longer a way to configure cs7 instances in the BSC and since we are completely new to this project we aren't up to date with all the recent changes. Apologizes for that.
We're also struggling to build the osmo-bsc sources. It quits with "bsc_vty.c:313:5: error: implicit declaration of function ‘OSMO_SEC2DAY’". So I guess there is a package missing but I couldn't find out which one it is.
TIA
Best regards,
Ralf
On 19.10.2017 14:15, gsm sim wrote:
We're also struggling to build the osmo-bsc sources. It quits with "bsc_vty.c:313:5: error: implicit declaration of function ‘OSMO_SEC2DAY’". So I guess there is a package missing but I couldn't find out which one it is.
That means the version of libosmocore you're using is too old. In general, rule of thumb is: if you build latest master of osmo* than you also have to install the latest master of all of its libosmo* dependencies.
On Thu, Oct 19, 2017 at 02:15:16PM +0200, gsm sim wrote:
Now how is the BSC supposed to connect to the MSC?
osmo-bsc --> osmo-stp <-- osmo-msc
The cs7 instance setup you mention should work.
BTW, I have the task of writing a migration guide from OsmoNITB to separate OsmoBSC+OsmoMSC that should cover these topics, which I'm planning to start today. It should be in the osmocom.org wiki soon.
I'm using the nighlty-packages
Note that so far there are separate repositories, one containing the old osmo-bsc binary that only speaks SCCPlite, and a separate one with the new packages that speak SCCP/M3UA.
The subtle difference at the moment is that the new SCCP/M3UA version of osmo-bsc is called 'osmo-bsc_*.deb' and is in https://build.opensuse.org/project/show/network:osmocom:nitb-split:nightly
While the old osmo-bsc version that can only do SCCPlite and has no M3UA support is called 'osmocom-bsc_*.deb' ('osmocom' vs. 'osmo') and is in https://build.opensuse.org/project/show/network:osmocom:nightly
(We are working on it to join the "split" ones with the standard "nightly" feed)
See also https://osmocom.org/projects/cellular-infrastructure/wiki/Nightly_Builds
In our OpenEmbedded builds, we have already renamed the old osmo-bsc to 'osmo-bsc-sccplite', it might be a good idea to do the same for debian packaging.
~N
Hello guys,
thanks a lot for your answers. So it looks like our failure was to use a mix of the wrong nightly builds and builds from source. I'm in the process of implementing the right repos now. Good to see that we were on the right way with our bsc -> stp <- msc setup and can narrow down our confusion.
On Thu, Oct 19, 2017 at 5:11 PM, Neels Hofmeyr nhofmeyr@sysmocom.de wrote:
BTW, I have the task of writing a migration guide from OsmoNITB to separate OsmoBSC+OsmoMSC that should cover these topics, which I'm planning to start today. It should be in the osmocom.org wiki soon
Looking forward to your guide helping with some open questions.
Best regards and have a nice weekend,
Ralf
On Fri, Oct 20, 2017 at 09:46:56AM +0200, gsm sim wrote:
Hello guys,
thanks a lot for your answers. So it looks like our failure was to use a mix of the wrong nightly builds and builds from source.
I wonder why you were building something from source at all. Everything is packaged as nightly builds, and unless you are making some changes to the code (which we are very happy to receive as contribution to the project!) there shouldn't be a need to build from source.
Regards, Harald
On Fri, Oct 20, 2017 at 10:02 AM, Harald Welte laforge@gnumonks.org wrote:
I wonder why you were building something from source at all.
Yeah now with the recent experience I got from the mailing list I'm wondering too. So we weren't aware of the nitb-split nightly builds at all and due to that we had an inconsistent mix of builds...
In terms of communication between bts - bsc - stp - msc - mgw everything is fine now. There are other problems now but I think this is related to false configuration.
Regards,
Ralf
-
gsm sim -
Harald Welte -
Max -
Neels Hofmeyr