OsmoBSC: Newshttps://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092023-12-14T16:56:15ZOpen Source Mobile Communications
Redmine osmo-bsc 1.11.1 releasehttps://projects.osmocom.org/news/2382023-12-14T16:56:15Zosmith
<p>Today we've released osmo-bsc 1.11.1.</p>
<p>This release uses PCUIF 12, which is compatible with osmo-pcu 1.4.0.</p>
<p>The changelog over 1.11.0 is as follows:</p>
<pre>
osmo-bsc (1.11.1) unstable; urgency=medium
[ Philipp Maier ]
* pcuif_proto: rename PCU_IF_FLAG_SYSMO to PCU_IF_FLAG_DIRECT_PHY
* pcuif_proto: clean up last remains of old PCUIF v10
* pcuif_proto: signal BTS model via PCUIF
-- Oliver Smith <osmith@sysmocom.de> Tue, 12 Dec 2023 16:53:00 +0100
</pre> OsmoBSC now *requires* an osmo-mgw to run alongside ithttps://projects.osmocom.org/news/802017-11-09T14:42:15Zneelsnhofmeyr@sysmocom.de
<p><strong>Heads up all <a class="wiki-page" href="https://projects.osmocom.org/projects/osmobsc/wiki">OsmoBSC</a> users:</strong> if you are deploying an osmo-bsc from <code>osmo-bsc.git</code> using the latest master branch (or nightly builds), you may notice voice streams not working anymore.</p>
<p>The reason is that <a class="wiki-page" href="https://projects.osmocom.org/projects/osmobsc/wiki">OsmoBSC</a> now supports intra-BSC handover (handover between separate BTS connected to the same BSC). To be able to redirect RTP streams between separate BTS, OsmoBSC now always requires an <a class="wiki-page" href="https://projects.osmocom.org/projects/osmo-mgw/wiki">OsmoMGW</a> instance to run alongside it.</p>
<p>Documentation on the Wiki and in the Manuals still needs to be updated, please bear with us until we get a chance to adjust those.</p>
<p><div class="flash error">Error executing the <strong>graphviz_link</strong> macro (Missing template wiki_graphviz/macro with {:locale=>[:en], :formats=>[:atom], :variants=>[], :handlers=>[:raw, :erb, :html, :builder, :ruby, :rsb]}. Searched in:
* "/usr/src/redmine/plugins/wiki_mscgen_plugin/app/views"
* "/usr/src/redmine/plugins/wiki_graphviz_plugin/app/views"
* "/usr/src/redmine/plugins/redmine_tags/app/views"
* "/usr/src/redmine/plugins/redmine_openid_provider/app/views"
* "/usr/src/redmine/plugins/redmine_mentions/app/views"
* "/usr/src/redmine/plugins/redmine_lightbox2/app/views"
* "/usr/src/redmine/plugins/redmine_checklists/app/views"
* "/usr/src/redmine/plugins/redmine_banner/app/views"
* "/usr/src/redmine/plugins/clipboard_image_paste/app/views"
* "/usr/src/redmine/app/views"
* "/usr/local/bundle/gems/redmine_crm-0.0.61/app/views"
)</div></p>
<p>An OsmoMGW config example is</p>
<pre>
mgcp
bind ip 127.0.0.1
bind port 2427
rtp net-range 4002 16000
number endpoints 31
rtp-accept-all 1
</pre>
<p>If <a class="wiki-page" href="https://projects.osmocom.org/projects/osmo-mgw/wiki">OsmoMGW</a> is running on the same machine as OsmoBSC with MGCP at 127.0.0.1, OsmoBSC needs no further configuration and will find the <a class="wiki-page" href="https://projects.osmocom.org/projects/osmo-mgw/wiki">OsmoMGW</a> by default at 127.0.0.1 port 2427. More detailed <a class="wiki-page" href="https://projects.osmocom.org/projects/osmobsc/wiki">OsmoBSC</a> side config can be issued like:</p>
<pre>
msc
mgw remote-ip 127.0.0.1
mgw remote-port 2427
mgw endpoint-range 1 31
</pre>
<p>You can find <a class="wiki-page" href="https://projects.osmocom.org/projects/osmo-mgw/wiki">OsmoMGW</a> in the nightly (and "latest") builds as well as opkg feeds, it is installed by the osmo-mgw package and developed in the osmo-mgw.git repository.</p>
<p>The <a class="wiki-page" href="https://projects.osmocom.org/projects/osmobsc/wiki">OsmoBSC</a> change from which on we require an <a class="wiki-page" href="https://projects.osmocom.org/projects/osmo-mgw/wiki">OsmoMGW</a> is <a href="http://git.osmocom.org/osmo-bsc/commit/?id=39c609b7c924524172ad311bdf89f92b7ccf175a" class="external">here</a></p>
<p>Previously, the higher level MGW would directly talk RTP to the BTS, which is now no longer the case. The BSC will always advertise its MGW's RTP ports towards the MSC. This means that the BTS can now be in a network segment that is not reachable by the MSC directly.</p>