This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Ron ron.menez at entropysolution.comHi 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 at entropysolution.com<mailto:ron.menez at entropysolution.com> On Sep 18, 2017, at 7:50 PM, Neels Hofmeyr <nhofmeyr at sysmocom.de<mailto:nhofmeyr at 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-sccp.cfg 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170919/31bfcee6/attachment.htm>