Project

General

Profile

OsmoBSC now *requires* an osmo-mgw to run alongside it

Added by neels 10 days ago

Heads up all OsmoBSC users: if you are deploying an osmo-bsc from osmo-bsc.git using the latest master branch (or nightly builds), you may notice voice streams not working anymore.

The reason is that OsmoBSC 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 OsmoMGW instance to run alongside it.

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.

An OsmoMGW config example is

mgcp
 bind ip 127.0.0.1
 bind port 2427
 rtp net-range 4002 16000
 number endpoints 31
 rtp-accept-all 1

If OsmoMGW is running on the same machine as OsmoBSC with MGCP at 127.0.0.1, OsmoBSC needs no further configuration and will find the OsmoMGW by default at 127.0.0.1 port 2427. More detailed OsmoBSC side config can be issued like:

msc
 mgw remote-ip 127.0.0.1
 mgw remote-port 2427
 mgw endpoint-range 1 31

You can find OsmoMGW 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.

The OsmoBSC change from which on we require an OsmoMGW is here

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.


Comments