Osmocom's Base Station Controller for 2G mobile networks https://osmocom.org/projects/osmobsc
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Only meas_json is added so far, since the other related ones are conditionally built. Change-Id: I35ba3c19fcdfb5663691a67c9876537765963c5d
|5 years ago|
|contrib||5 years ago|
|debian||5 years ago|
|doc||5 years ago|
|include||5 years ago|
|m4||6 years ago|
|src||5 years ago|
|tests||5 years ago|
|.gitignore||5 years ago|
|.gitreview||6 years ago|
|.mailmap||7 years ago|
|AUTHORS||6 years ago|
|COPYING||6 years ago|
|Makefile.am||5 years ago|
|README||5 years ago|
|README.vty-tests||5 years ago|
|configure.ac||5 years ago|
|git-version-gen||6 years ago|
|osmoappdesc.py||5 years ago|
OsmoBSC originated from the OpenBSC project, which started as a minimalistic
all-in-one implementation of the GSM Network. In 2017, OpenBSC had reached
maturity and diversity (including M3UA SIGTRAN and 3G support in the form of
IuCS and IuPS interfaces) that naturally lead to a separation of the all-in-one
approach to fully independent separate programs as in typical GSM networks.
OsmoBSC was one of the parts split off from the old openbsc.git. Before, it
worked as a standalone osmo-bsc binary as well as a combination of libbsc and
libmsc, i.e. the old OsmoNITB. Since the standalone OsmoMSC with a true A
interface (and IuCS for 3G support) is available, OsmoBSC exists only as a
separate standalone entity.
- A over IP towards an MSC (e.g. OsmoMSC);
- Abis interfaces towards various kinds of BTS;
- The Osmocom typical telnet VTY and CTRL interfaces.
Find OsmoBSC issue tracker and wiki online at
OsmoBSC-NAT is a specialized solution to navigating RTP streams through a NAT.
(Todo: describe in more detail)