<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi Neel,
<div class=""><br class="">
</div>
<div class="">Thanks for the detailed info.</div>
<div class=""><br class="">
</div>
<div class="">But we are using Ubuntu 16.10 as our OS. </div>
<div class=""><br class="">
</div>
<div class="">Can we still used the nightly package for Debian?</div>
<div class=""><br class="">
</div>
<div class="">We tried to install the osmo-bsc but it has an unmet dependencies “libssl1.1”. This seems not available in Ubuntu.</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">Is there an available git version of osmo-bsc, osmo-stp, osmo-msc and osmo-hlr that we can download?<br class="">
<div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="Apple-interchange-newline">
Best Regard,</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="">
</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
Ron Menez</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<a href="mailto:ron.menez@entropysolution.com" class="">ron.menez@entropysolution.com</a></div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="">
</div>
<br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<br class="Apple-interchange-newline">
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Sep 18, 2017, at 7:50 PM, Neels Hofmeyr <<a href="mailto:nhofmeyr@sysmocom.de" class="">nhofmeyr@sysmocom.de</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi Ron,<br class="">
<br class="">
about the libosmo-*mgcp* issues: apologies for your inconvenience, you are<br class="">
hitting a time of active migration, with short periods of things getting out of<br class="">
sync and breaking.<br class="">
<br class="">
The osmo-msc package is currently still failing the builds after renames in<br class="">
libosmo-mgcp* (osmo-mgw.git) caused some fallout in the debian packaging. Most<br class="">
things have been fixed, the hopefully last patch is already in gerrit.<br class="">
<a href="https://gerrit.osmocom.org/3971" class="">https://gerrit.osmocom.org/3971</a><br class="">
Will hopefully fix and merge that today and then kick off another debian<br class="">
packages build.<br class="">
<br class="">
However, looking at<br class="">
https://build.opensuse.org/project/show/network:osmocom:nitb-split:nightly<br class="">
you should be able to install osmo-bsc, only osmo-msc should fail.<br class="">
Wild guess: update the package repositories? (apt-get update)<br class="">
<br class="">
About the osmo-stp connections, I'd first like to make sure that you are aware:<br class="">
the old SCCPlite VTY commands may still be present but have no effect. The<br class="">
connection to osmo-stp is handled by the new SIGTRAN library from libosmo-sccp.<br class="">
<br class="">
If you'd like to change the setting where to reach osmo-stp, it looks like this:<br class="">
https://git.osmocom.org/osmo-bsc/plain/doc/examples/osmo-bsc/osmo-bsc_custom-sccp.cfg<br class="">
particularly:<br class="">
<br class="">
cs7 instance 0<br class="">
point-code 0.42.1<br class="">
asp asp-clnt-OsmoBSC 2905 0 m3ua<br class="">
! where to reach the STP<br class="">
remote-ip 10.23.24.1<br class="">
<br class="">
I am puzzled by this log output:<br class="">
<blockquote type="cite" class=""><000a> bsc_msc.c:171 Attempting to connect MSC() at 192.168.100.11:6666<br class="">
</blockquote>
since it indicates an attempt to connect the old way, but I see that this is<br class="">
code left behind from before the new SIGTRAN, which should instead connect on<br class="">
port 2905. Added to the list of things we need to revisit.<br class="">
<br class="">
<br class="">
Documentation on the new setup is pending. Let me break down how I run things:<br class="">
<br class="">
osmo-stp.cfg:<br class="">
---<br class="">
cs7 instance 0<br class="">
xua rkm routing-key-allocation dynamic-permitted<br class="">
listen m3ua 2905<br class="">
accept-asp-connections dynamic-permitted<br class="">
---<br class="">
<br class="">
osmo-stp -c osmo-stp.cfg<br class="">
<br class="">
Make sure you start osmo-stp first (should be able to handle any startup order<br class="">
in the future, but for now, to make sure).<br class="">
<br class="">
<br class="">
osmo-msc.cfg:<br class="">
---<br class="">
network<br class="">
network country code 901<br class="">
mobile network code 98<br class="">
short name OsmoMSC<br class="">
long name OsmoMSC<br class="">
auth policy closed<br class="">
location updating reject cause 13<br class="">
encryption a5 0<br class="">
rrlp mode none<br class="">
mm info 1<br class="">
msc<br class="">
mgcpgw remote-ip 192.168.0.132<br class="">
---<br class="">
<br class="">
optionally add<br class="">
---<br class="">
cs7 instance 0<br class="">
point-code 0.0.1<br class="">
msc<br class="">
cs7-instance-iu 0<br class="">
cs7-instance-a 0<br class="">
---<br class="">
<br class="">
osmo-msc -c osmo-msc.cfg<br class="">
<br class="">
<br class="">
osmo-bsc.cfg:<br class="">
---<br class="">
network<br class="">
network country code 901<br class="">
mobile network code 70<br class="">
short name osmo-gsm-tester-msc<br class="">
long name osmo-gsm-tester-msc<br class="">
auth policy closed<br class="">
location updating reject cause 13<br class="">
encryption a5 0<br class="">
neci 1<br class="">
rrlp mode none<br class="">
mm info 1<br class="">
handover 0<br class="">
handover window rxlev averaging 10<br class="">
handover window rxqual averaging 1<br class="">
handover window rxlev neighbor averaging 10<br class="">
handover power budget interval 6<br class="">
handover power budget hysteresis 3<br class="">
handover maximum distance 9999<br class="">
timer t3101 10<br class="">
timer t3109 4<br class="">
timer t3113 60<br class="">
bts 0<br class="">
type sysmobts<br class="">
band GSM-1800<br class="">
cell_identity 0<br class="">
location_area_code 23<br class="">
training_sequence_code 7<br class="">
base_station_id_code 63<br class="">
ms max power 33<br class="">
cell reselection hysteresis 4<br class="">
rxlev access min 0<br class="">
channel allocator ascending<br class="">
rach tx integer 9<br class="">
rach max transmission 7<br class="">
ip.access unit_id 1800 0<br class="">
oml ip.access stream_id 255 line 0<br class="">
gprs mode none<br class="">
neighbor-list mode manual<br class="">
si2quater neighbor-list add uarfcn 9800 401 0<br class="">
trx 0<br class="">
rf_locked 0<br class="">
arfcn 868<br class="">
nominal power 23<br class="">
max_power_red 21<br class="">
rsl e1 tei 0<br class="">
timeslot 0<br class="">
phys_chan_config CCCH+SDCCH4<br class="">
timeslot 1<br class="">
phys_chan_config SDCCH8<br class="">
timeslot 2<br class="">
phys_chan_config TCH/H<br class="">
timeslot 3<br class="">
phys_chan_config TCH/H<br class="">
timeslot 4<br class="">
phys_chan_config TCH/H<br class="">
timeslot 5<br class="">
phys_chan_config TCH/H<br class="">
timeslot 6<br class="">
phys_chan_config TCH/H<br class="">
timeslot 7<br class="">
phys_chan_config TCH/H<br class="">
msc<br class="">
token msc_token_23_42<br class="">
core-mobile-country-code 901<br class="">
core-mobile-network-code 70<br class="">
ip.access rtp-base 8000<br class="">
timeout-ping 1800<br class="">
timeout-ping advanced<br class="">
timeout-pong 60<br class="">
codec-list hr3<br class="">
dest 151.80.237.229 5000 184<br class="">
amr-config 12_2k forbidden<br class="">
amr-config 10_2k forbidden<br class="">
amr-config 7_95k forbidden<br class="">
amr-config 7_40k forbidden<br class="">
amr-config 6_70k forbidden<br class="">
amr-config 5_90k allowed<br class="">
amr-config 5_15k forbidden<br class="">
amr-config 4_75k forbidden<br class="">
---<br class="">
<br class="">
osmo-bsc -c osmo-bsc.cfg<br class="">
<br class="">
Above config assumes defaults, a full M3UA/SCCP config would look like<br class="">
<br class="">
---<br class="">
cs7 instance 1<br class="">
point-code 0.42.0<br class="">
asp asp-clnt-msc-0 2905 0 m3ua<br class="">
as as-clnt-msc-0 m3ua<br class="">
asp asp-clnt-msc-0<br class="">
routing-key 2 0.42.0<br class="">
sccp-address bsc_local<br class="">
routing-indicator PC<br class="">
point-code 0.42.0<br class="">
sccp-address msc_remote<br class="">
routing-indicator PC<br class="">
point-code 0.0.1<br class="">
msc 0<br class="">
bsc-addr bsc_local<br class="">
msc-addr msc_remote<br class="">
---<br class="">
<br class="">
<br class="">
Upon startup, I see e.g. osmo-bsc logs like<br class="">
<br class="">
20170918133916790 DLINP <0002> ../../../src/libosmo-netif/src/stream.c:558 accept()ed new link from 127.0.0.1 to port 2905<br class="">
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<br class="">
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<br class="">
<br class="">
<br class="">
Looking through this, I see various bits that still need polishing, but the<br class="">
current osmo-bsc,stp,msc setup should work as it is.<br class="">
<br class="">
I hope you will get a working setup going with this information, and once the<br class="">
osmo-msc debian builds again.<br class="">
<br class="">
Thanks for reporting!<br class="">
<br class="">
~N<br class="">
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>