Hi All,
Is there a link on how to integration osmo-bsc to osmo-msc? or osmo-bsc_nat is required to integrate osmo-bsc to osmo-msc?
A config file for both osmo-bsc and osmo-msc that can be shared will be greatly appreciated.
TIA.
Best Regard,
Ron Menez ron.menez@entropysolution.commailto:ron.menez@entropysolution.com
On Sun, Sep 17, 2017 at 12:16:39PM +0000, Ron wrote:
Is there a link on how to integration osmo-bsc to osmo-msc?
You need osmo-stp, as both osmo-bsc and osmo-msc implement only an M3UA ASP role.
or osmo-bsc_nat is required to integrate osmo-bsc to osmo-msc?
no.
A config file for both osmo-bsc and osmo-msc that can be shared will be greatly appreciated.
Working config files are in the 'doc/examples' folders of the osmo-bsc and osmo-msc repositories.
Thank you very much for the immediate reply Harald.
We’ll be trying to install osmo-stp too to integrate both osmo-bsc and osmo-msc.
Best Regard,
Ron Menez ron.menez@entropysolution.commailto:ron.menez@entropysolution.com
On Sep 17, 2017, at 9:21 PM, Harald Welte <laforge@gnumonks.orgmailto:laforge@gnumonks.org> wrote:
On Sun, Sep 17, 2017 at 12:16:39PM +0000, Ron wrote:
Is there a link on how to integration osmo-bsc to osmo-msc?
You need osmo-stp, as both osmo-bsc and osmo-msc implement only an M3UA ASP role.
or osmo-bsc_nat is required to integrate osmo-bsc to osmo-msc?
no.
A config file for both osmo-bsc and osmo-msc that can be shared will be greatly appreciated.
Working config files are in the 'doc/examples' folders of the osmo-bsc and osmo-msc repositories.
-- - Harald Welte <laforge@gnumonks.orgmailto:laforge@gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
On Sun, Sep 17, 2017 at 01:45:26PM +0000, Ron wrote:
We’ll be trying to install osmo-stp too to integrate both osmo-bsc and osmo-msc.
FYI: It's part of the libosmo-sccp.git repository. It also contains an example config file. If you start all three programs on the same machine with the included example program files, they should find each other.
Documentation is still not produced yet. This new "post NITB" architecture is too recent. It's basically the "osmocom bleeding edge" and it will take another couple of weeks (expected) until there's the corresponding user manuals.
After manuals have been created and all related wiki pages updated/created, we will officially "deprecate" OsmoNITB development, which means that new patches will have to be first merged to OsmoBSC/OsmoMSC, before they can be back-ported to OsmoNITB. We'll also likely only accept bug fixes for legacy OsmoNITB at that point, while new features must go to OsmoBSC+OsmoMSC.
Regards, Harald
Hi Harald,
Installed the osmo-stp in the same machine with osmo-msc and osmo-bsc but unfortunately, osmo-bsc logs still shows connection timeout and tries to reconnect again.
<000a> bsc_msc.c:278 Attempting to reconnect to the MSC() <000a> bsc_msc.c:271 Attempting to reconnect to the MSC(). <000a> bsc_msc.c:171 Attempting to connect MSC() at 192.168.100.11:6666 <000a> bsc_msc.c:211 MSC() Connection in progress <000a> bsc_msc.c:67 MSC() Connection timeout. <000a> osmo_bsc_msc.c:391 Lost MSC connection. Freing stuff.
We used the config files from the "doc/examples” folder.
We also tried to change the IP address from the local IP and 127.0.0.1 but still the same issue.
I’m not sure if my osmo-msc and osmo-bsc is out-dated but we also tried to get an updated version of both osmo-msc and osmo-bsc. Still we were unable to install it correctly. We have the following error:
Errors: osmo-msc: configure: error: Package requirements (libosmo-mgcp-client >= 1.0.0) were not met:
No package 'libosmo-mgcp-client’ found
osmo-bsc: configure: error: Package requirements (libosmo-legacy-mgcp >= 0.0.1) were not met:
No package 'libosmo-legacy-mgcp' found
I’m checking what package to install but unfortunately, those package requirements is unavailable from the nightly-build and from the git repo.
Best Regard,
Ron Menez ron.menez@entropysolution.commailto:ron.menez@entropysolution.com
On Sep 17, 2017, at 10:06 PM, Harald Welte <laforge@gnumonks.orgmailto:laforge@gnumonks.org> wrote:
On Sun, Sep 17, 2017 at 01:45:26PM +0000, Ron wrote: We’ll be trying to install osmo-stp too to integrate both osmo-bsc and osmo-msc.
FYI: It's part of the libosmo-sccp.git repository. It also contains an example config file. If you start all three programs on the same machine with the included example program files, they should find each other.
Documentation is still not produced yet. This new "post NITB" architecture is too recent. It's basically the "osmocom bleeding edge" and it will take another couple of weeks (expected) until there's the corresponding user manuals.
After manuals have been created and all related wiki pages updated/created, we will officially "deprecate" OsmoNITB development, which means that new patches will have to be first merged to OsmoBSC/OsmoMSC, before they can be back-ported to OsmoNITB. We'll also likely only accept bug fixes for legacy OsmoNITB at that point, while new features must go to OsmoBSC+OsmoMSC.
Regards, Harald
-- - Harald Welte <laforge@gnumonks.orgmailto:laforge@gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
Hi Ron,
about the libosmo-*mgcp* issues: apologies for your inconvenience, you are hitting a time of active migration, with short periods of things getting out of sync and breaking.
The osmo-msc package is currently still failing the builds after renames in libosmo-mgcp* (osmo-mgw.git) caused some fallout in the debian packaging. Most things have been fixed, the hopefully last patch is already in gerrit. https://gerrit.osmocom.org/3971 Will hopefully fix and merge that today and then kick off another debian packages build.
However, looking at https://build.opensuse.org/project/show/network:osmocom:nitb-split:nightly you should be able to install osmo-bsc, only osmo-msc should fail. Wild guess: update the package repositories? (apt-get update)
About the osmo-stp connections, I'd first like to make sure that you are aware: the old SCCPlite VTY commands may still be present but have no effect. The connection to osmo-stp is handled by the new SIGTRAN library from libosmo-sccp.
If you'd like to change the setting where to reach osmo-stp, it looks like this: https://git.osmocom.org/osmo-bsc/plain/doc/examples/osmo-bsc/osmo-bsc_custom... particularly:
cs7 instance 0 point-code 0.42.1 asp asp-clnt-OsmoBSC 2905 0 m3ua ! where to reach the STP remote-ip 10.23.24.1
I am puzzled by this log output:
<000a> bsc_msc.c:171 Attempting to connect MSC() at 192.168.100.11:6666
since it indicates an attempt to connect the old way, but I see that this is code left behind from before the new SIGTRAN, which should instead connect on port 2905. Added to the list of things we need to revisit.
Documentation on the new setup is pending. Let me break down how I run things:
osmo-stp.cfg: --- cs7 instance 0 xua rkm routing-key-allocation dynamic-permitted listen m3ua 2905 accept-asp-connections dynamic-permitted ---
osmo-stp -c osmo-stp.cfg
Make sure you start osmo-stp first (should be able to handle any startup order in the future, but for now, to make sure).
osmo-msc.cfg: --- network network country code 901 mobile network code 98 short name OsmoMSC long name OsmoMSC auth policy closed location updating reject cause 13 encryption a5 0 rrlp mode none mm info 1 msc mgcpgw remote-ip 192.168.0.132 ---
optionally add --- cs7 instance 0 point-code 0.0.1 msc cs7-instance-iu 0 cs7-instance-a 0 ---
osmo-msc -c osmo-msc.cfg
osmo-bsc.cfg: --- network network country code 901 mobile network code 70 short name osmo-gsm-tester-msc long name osmo-gsm-tester-msc auth policy closed location updating reject cause 13 encryption a5 0 neci 1 rrlp mode none mm info 1 handover 0 handover window rxlev averaging 10 handover window rxqual averaging 1 handover window rxlev neighbor averaging 10 handover power budget interval 6 handover power budget hysteresis 3 handover maximum distance 9999 timer t3101 10 timer t3109 4 timer t3113 60 bts 0 type sysmobts band GSM-1800 cell_identity 0 location_area_code 23 training_sequence_code 7 base_station_id_code 63 ms max power 33 cell reselection hysteresis 4 rxlev access min 0 channel allocator ascending rach tx integer 9 rach max transmission 7 ip.access unit_id 1800 0 oml ip.access stream_id 255 line 0 gprs mode none neighbor-list mode manual si2quater neighbor-list add uarfcn 9800 401 0 trx 0 rf_locked 0 arfcn 868 nominal power 23 max_power_red 21 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 timeslot 1 phys_chan_config SDCCH8 timeslot 2 phys_chan_config TCH/H timeslot 3 phys_chan_config TCH/H timeslot 4 phys_chan_config TCH/H timeslot 5 phys_chan_config TCH/H timeslot 6 phys_chan_config TCH/H timeslot 7 phys_chan_config TCH/H msc token msc_token_23_42 core-mobile-country-code 901 core-mobile-network-code 70 ip.access rtp-base 8000 timeout-ping 1800 timeout-ping advanced timeout-pong 60 codec-list hr3 dest 151.80.237.229 5000 184 amr-config 12_2k forbidden amr-config 10_2k forbidden amr-config 7_95k forbidden amr-config 7_40k forbidden amr-config 6_70k forbidden amr-config 5_90k allowed amr-config 5_15k forbidden amr-config 4_75k forbidden ---
osmo-bsc -c osmo-bsc.cfg
Above config assumes defaults, a full M3UA/SCCP config would look like
--- cs7 instance 1 point-code 0.42.0 asp asp-clnt-msc-0 2905 0 m3ua as as-clnt-msc-0 m3ua asp asp-clnt-msc-0 routing-key 2 0.42.0 sccp-address bsc_local routing-indicator PC point-code 0.42.0 sccp-address msc_remote routing-indicator PC point-code 0.0.1 msc 0 bsc-addr bsc_local msc-addr msc_remote ---
Upon startup, I see e.g. osmo-bsc logs like
20170918133916790 DLINP <0002> ../../../src/libosmo-netif/src/stream.c:558 accept()ed new link from 127.0.0.1 to port 2905 20170918133916790 DLSS7 <000c> ../../../src/libosmo-sccp/src/osmo_ss7.c:1606 (r=127.0.0.1:50020<->l=127.0.0.1:2905): New m3ua connection accepted 20170918133916790 DLSS7 <000c> ../../../src/libosmo-sccp/src/osmo_ss7.c:1642 (r=127.0.0.1:50020<->l=127.0.0.1:2905): created dynamicASP asp-dyn-1
Looking through this, I see various bits that still need polishing, but the current osmo-bsc,stp,msc setup should work as it is.
I hope you will get a working setup going with this information, and once the osmo-msc debian builds again.
Thanks for reporting!
~N
Hi Neel,
Thanks for the detailed info.
But we are using Ubuntu 16.10 as our OS.
Can we still used the nightly package for Debian?
We tried to install the osmo-bsc but it has an unmet dependencies “libssl1.1”. This seems not available in Ubuntu.
BTW, we are hoping to have the git version instead of the nightly package. We are also exploring in doing some development on our side.
Is there an available git version of osmo-bsc, osmo-stp, osmo-msc and osmo-hlr that we can download?
Best Regard,
Ron Menez ron.menez@entropysolution.commailto:ron.menez@entropysolution.com
On Sep 18, 2017, at 7:50 PM, Neels Hofmeyr <nhofmeyr@sysmocom.demailto:nhofmeyr@sysmocom.de> wrote:
Hi Ron,
about the libosmo-*mgcp* issues: apologies for your inconvenience, you are hitting a time of active migration, with short periods of things getting out of sync and breaking.
The osmo-msc package is currently still failing the builds after renames in libosmo-mgcp* (osmo-mgw.git) caused some fallout in the debian packaging. Most things have been fixed, the hopefully last patch is already in gerrit. https://gerrit.osmocom.org/3971 Will hopefully fix and merge that today and then kick off another debian packages build.
However, looking at https://build.opensuse.org/project/show/network:osmocom:nitb-split:nightly you should be able to install osmo-bsc, only osmo-msc should fail. Wild guess: update the package repositories? (apt-get update)
About the osmo-stp connections, I'd first like to make sure that you are aware: the old SCCPlite VTY commands may still be present but have no effect. The connection to osmo-stp is handled by the new SIGTRAN library from libosmo-sccp.
If you'd like to change the setting where to reach osmo-stp, it looks like this: https://git.osmocom.org/osmo-bsc/plain/doc/examples/osmo-bsc/osmo-bsc_custom... particularly:
cs7 instance 0 point-code 0.42.1 asp asp-clnt-OsmoBSC 2905 0 m3ua ! where to reach the STP remote-ip 10.23.24.1
I am puzzled by this log output: <000a> bsc_msc.c:171 Attempting to connect MSC() at 192.168.100.11:6666 since it indicates an attempt to connect the old way, but I see that this is code left behind from before the new SIGTRAN, which should instead connect on port 2905. Added to the list of things we need to revisit.
Documentation on the new setup is pending. Let me break down how I run things:
osmo-stp.cfg: --- cs7 instance 0 xua rkm routing-key-allocation dynamic-permitted listen m3ua 2905 accept-asp-connections dynamic-permitted ---
osmo-stp -c osmo-stp.cfg
Make sure you start osmo-stp first (should be able to handle any startup order in the future, but for now, to make sure).
osmo-msc.cfg: --- network network country code 901 mobile network code 98 short name OsmoMSC long name OsmoMSC auth policy closed location updating reject cause 13 encryption a5 0 rrlp mode none mm info 1 msc mgcpgw remote-ip 192.168.0.132 ---
optionally add --- cs7 instance 0 point-code 0.0.1 msc cs7-instance-iu 0 cs7-instance-a 0 ---
osmo-msc -c osmo-msc.cfg
osmo-bsc.cfg: --- network network country code 901 mobile network code 70 short name osmo-gsm-tester-msc long name osmo-gsm-tester-msc auth policy closed location updating reject cause 13 encryption a5 0 neci 1 rrlp mode none mm info 1 handover 0 handover window rxlev averaging 10 handover window rxqual averaging 1 handover window rxlev neighbor averaging 10 handover power budget interval 6 handover power budget hysteresis 3 handover maximum distance 9999 timer t3101 10 timer t3109 4 timer t3113 60 bts 0 type sysmobts band GSM-1800 cell_identity 0 location_area_code 23 training_sequence_code 7 base_station_id_code 63 ms max power 33 cell reselection hysteresis 4 rxlev access min 0 channel allocator ascending rach tx integer 9 rach max transmission 7 ip.access unit_id 1800 0 oml ip.access stream_id 255 line 0 gprs mode none neighbor-list mode manual si2quater neighbor-list add uarfcn 9800 401 0 trx 0 rf_locked 0 arfcn 868 nominal power 23 max_power_red 21 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 timeslot 1 phys_chan_config SDCCH8 timeslot 2 phys_chan_config TCH/H timeslot 3 phys_chan_config TCH/H timeslot 4 phys_chan_config TCH/H timeslot 5 phys_chan_config TCH/H timeslot 6 phys_chan_config TCH/H timeslot 7 phys_chan_config TCH/H msc token msc_token_23_42 core-mobile-country-code 901 core-mobile-network-code 70 ip.access rtp-base 8000 timeout-ping 1800 timeout-ping advanced timeout-pong 60 codec-list hr3 dest 151.80.237.229 5000 184 amr-config 12_2k forbidden amr-config 10_2k forbidden amr-config 7_95k forbidden amr-config 7_40k forbidden amr-config 6_70k forbidden amr-config 5_90k allowed amr-config 5_15k forbidden amr-config 4_75k forbidden ---
osmo-bsc -c osmo-bsc.cfg
Above config assumes defaults, a full M3UA/SCCP config would look like
--- cs7 instance 1 point-code 0.42.0 asp asp-clnt-msc-0 2905 0 m3ua as as-clnt-msc-0 m3ua asp asp-clnt-msc-0 routing-key 2 0.42.0 sccp-address bsc_local routing-indicator PC point-code 0.42.0 sccp-address msc_remote routing-indicator PC point-code 0.0.1 msc 0 bsc-addr bsc_local msc-addr msc_remote ---
Upon startup, I see e.g. osmo-bsc logs like
20170918133916790 DLINP <0002> ../../../src/libosmo-netif/src/stream.c:558 accept()ed new link from 127.0.0.1 to port 2905 20170918133916790 DLSS7 <000c> ../../../src/libosmo-sccp/src/osmo_ss7.c:1606 (r=127.0.0.1:50020<->l=127.0.0.1:2905): New m3ua connection accepted 20170918133916790 DLSS7 <000c> ../../../src/libosmo-sccp/src/osmo_ss7.c:1642 (r=127.0.0.1:50020<->l=127.0.0.1:2905): created dynamicASP asp-dyn-1
Looking through this, I see various bits that still need polishing, but the current osmo-bsc,stp,msc setup should work as it is.
I hope you will get a working setup going with this information, and once the osmo-msc debian builds again.
Thanks for reporting!
~N
On Tue, Sep 19, 2017 at 08:34:16AM +0000, Ron wrote:
But we are using Ubuntu 16.10 as our OS.
We do build packages for Ubuntu 16.10. https://build.opensuse.org/project/show/network:osmocom:nightly (old osmo-nitb) https://build.opensuse.org/project/show/network:osmocom:nitb-split:nightly (new M3UA)
The failures still need resolving, but otherwise it's there.
BTW, we are hoping to have the git version instead of the nightly package. We are also exploring in doing some development on our side. Is there an available git version of osmo-bsc, osmo-stp, osmo-msc and osmo-hlr that we can download?
See http://git.osmocom.org To contribute, see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit
I have recently published a "top-level makefile" project to build osmocom 2G and 3G, which might be helpful to build everything with just a few commands:
git clone git://git.osmocom.org/osmo-dev less osmo-dev/README
~N
Hi Neels,
Thank you for the info shared.
If we able to develop something that can be good for the community, we’ll share it as well.
As of now, the osmo-bsc for Ubuntu is not yet ready from the nightly package. We’ll wait till everything is ok.
And if the git repo is already ready for download, we’ll then start immediately.
We’ll also check the "top-level makefile” project and see what we can do from there.
Thank you.
Best Regard,
Ron Menez ron.menez@entropysolution.commailto:ron.menez@entropysolution.com
On Sep 21, 2017, at 1:45 AM, Neels Hofmeyr <nhofmeyr@sysmocom.demailto:nhofmeyr@sysmocom.de> wrote:
On Tue, Sep 19, 2017 at 08:34:16AM +0000, Ron wrote: But we are using Ubuntu 16.10 as our OS.
We do build packages for Ubuntu 16.10. https://build.opensuse.org/project/show/network:osmocom:nightly (old osmo-nitb) https://build.opensuse.org/project/show/network:osmocom:nitb-split:nightly (new M3UA)
The failures still need resolving, but otherwise it's there.
BTW, we are hoping to have the git version instead of the nightly package. We are also exploring in doing some development on our side. Is there an available git version of osmo-bsc, osmo-stp, osmo-msc and osmo-hlr that we can download?
See http://git.osmocom.org To contribute, see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit
I have recently published a "top-level makefile" project to build osmocom 2G and 3G, which might be helpful to build everything with just a few commands:
git clone git://git.osmocom.org/osmo-dev less osmo-dev/README
~N
-- - Neels Hofmeyr <nhofmeyr@sysmocom.demailto:nhofmeyr@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
Hi Neels,
We tried to compile the osmo-bsc from git.osmocom.orghttp://git.osmocom.org. But we still have the same error until now:
checking for LIBOSMOLEGACYMGCP... no configure: error: Package requirements (libosmo-legacy-mgcp >= 0.0.1) were not met:
No package 'libosmo-legacy-mgcp' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.
Alternatively, you may set the environment variables LIBOSMOLEGACYMGCP_CFLAGS and LIBOSMOLEGACYMGCP_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details.
We are using Ubuntu 10.04 and the directory where we compiled the osmo-bsc is in “/usr/local/osmo-bsc”.
We also did the following:
export LD_LIBRARY_PATH="/usr/local/lib"
export PKG_CONFIG_PATH="/usr/local/lib/pkgconfig"
But we still have the same error.
We also run the “git log” to confirm the committed version:
commit 918cfeb7870b118842c710dd88226ac70529fb5e Author: Max <msuraev@sysmocom.demailto:msuraev@sysmocom.de> Date: Fri Sep 29 14:33:35 2017 +0200
Fix repo split aftermath
* remove checks for non-existent tests * always enable bsc and nat-trie tests because both are built unconditionally * enable gsm0408 test which was removed by mistake * adjust gsm0408 test output to remove SMS-related results
Change-Id: I73ad079a6333ba56e73b7c4d1d0e9c8255c2a03b Related: OS#2257
commit 14f9772f146dd8890bfbe15eb030d7fedbeb6ab8 Author: Harald Welte <laforge@gnumonks.orgmailto:laforge@gnumonks.org> Date: Sun Oct 1 11:09:47 2017 +0800
gsm0408_test: Verify that BA-IND is 0 in SI2xxx and 1 in SI5xxx
This adds a test case to explicitly verify the BA-IND is as expected by the behaviour introduced in Change-Id I1cd0dc51026dcd0e508e63eea4e333e6b184787a
Related: OS#2525 Change-Id: I3e5b260af97ce96a221e4d51f6c1b41d58817a59
commit aa70d9d828a8163b8cf40c86de11694afeb05f65 Author: Harald Welte <laforge@gnumonks.orgmailto:laforge@gnumonks.org> Date: Sat Sep 30 09:22:30 2017 +0800
Make sure BA-IND in all SI2xxx is '0' and in all SI5xxx is '1'
In masurement reports sent by the MS, this can then be used to correlate if a given measurement report was in response to a BCCH/neighbor list received on BCCH (SI2xxx) or on dowlink SACCH (SI5xxx).
Closes: OS#2525 Change-Id: I1cd0dc51026dcd0e508e63eea4e333e6b184787a
commit d6a52e993d428b47cf6e8d3280b787e07dc9b855 Author: Harald Welte <laforge@gnumonks.orgmailto:laforge@gnumonks.org> Date: Sat Sep 30 09:22:14 2017 +0800
libbsc: document arguments of generate_bcch_chan_list()
Change-Id: I5afc6e6a5a1d6b6a8ee73fdb60cc28074cf8585b
Is the failures for the git version still existing, or we only have an issue in our OS installation?
TIA.
Best Regard,
Ron Menez ron.menez@entropysolution.commailto:ron.menez@entropysolution.com
On Sep 21, 2017, at 2:00 PM, Ron <ron.menez@entropysolution.commailto:ron.menez@entropysolution.com> wrote:
Hi Neels,
Thank you for the info shared.
If we able to develop something that can be good for the community, we’ll share it as well.
As of now, the osmo-bsc for Ubuntu is not yet ready from the nightly package. We’ll wait till everything is ok.
And if the git repo is already ready for download, we’ll then start immediately.
We’ll also check the "top-level makefile” project and see what we can do from there.
Thank you.
Best Regard,
Ron Menez ron.menez@entropysolution.commailto:ron.menez@entropysolution.com
On Sep 21, 2017, at 1:45 AM, Neels Hofmeyr <nhofmeyr@sysmocom.demailto:nhofmeyr@sysmocom.de> wrote:
On Tue, Sep 19, 2017 at 08:34:16AM +0000, Ron wrote: But we are using Ubuntu 16.10 as our OS.
We do build packages for Ubuntu 16.10. https://build.opensuse.org/project/show/network:osmocom:nightly (old osmo-nitb) https://build.opensuse.org/project/show/network:osmocom:nitb-split:nightly (new M3UA)
The failures still need resolving, but otherwise it's there.
BTW, we are hoping to have the git version instead of the nightly package. We are also exploring in doing some development on our side. Is there an available git version of osmo-bsc, osmo-stp, osmo-msc and osmo-hlr that we can download?
See http://git.osmocom.orghttp://git.osmocom.org/ To contribute, see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit
I have recently published a "top-level makefile" project to build osmocom 2G and 3G, which might be helpful to build everything with just a few commands:
git clone git://git.osmocom.org/osmo-dev less osmo-dev/README
~N
-- - Neels Hofmeyr <nhofmeyr@sysmocom.demailto:nhofmeyr@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
Hi again,
checking for LIBOSMOLEGACYMGCP... no configure: error: Package requirements (libosmo-legacy-mgcp >= 0.0.1) were not met:
Maybe you have not installed osmo-mgw.git, where libosmo-legacy-mgcp comes from?
We are aware that the current state of wiki and manuals does not reflect the new repositories at all yet, working on it. Noting that a list of what is found where and depends on what would be good.
~N
Hi Neels,
Thank you for the immediate response.
What we did is we started from scratch again by reinstalling all the libraries and osmo elements using git.
We successfully installed all the elements without errors.
Thank you for your support.
Best Regard,
Ron Menez ron.menez@entropysolution.commailto:ron.menez@entropysolution.com
On Oct 4, 2017, at 7:16 AM, Neels Hofmeyr <nhofmeyr@sysmocom.demailto:nhofmeyr@sysmocom.de> wrote:
Hi again,
checking for LIBOSMOLEGACYMGCP... no configure: error: Package requirements (libosmo-legacy-mgcp >= 0.0.1) were not met:
Maybe you have not installed osmo-mgw.git, where libosmo-legacy-mgcp comes from?
We are aware that the current state of wiki and manuals does not reflect the new repositories at all yet, working on it. Noting that a list of what is found where and depends on what would be good.
~N
-
Harald Welte -
Neels Hofmeyr -
Ron