Daniel Willmann
f96cac5077
When a complete NSE becomes unavailable gbproxy should notify the other side (bss/sgsn). The current code blocks every PtP-BVC (belonging to that BSS) on all SGSNs if a BSS goes down. The BSS-side should not be blocked unless no more SGSN connections are present. We could also remove all BSS nse and wait for those to reconnect. This is not yet implemented. Related: OS#4897 Change-Id: I6354a190ec1090a35c27671c72dab9126d0ad794 |
||
---|---|---|
contrib | ||
debian | ||
doc | ||
include | ||
m4 | ||
src | ||
tests | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
AUTHORS | ||
COPYING | ||
Makefile.am | ||
README.md | ||
README.vty-tests | ||
TODO-RELEASE | ||
configure.ac | ||
git-version-gen | ||
osmoappdesc.py |
README.md
About osmo-gbproxy
osmo-gbproxy is a proxy for the Gb interface within the 3GPP GERAN (GPRS/EDGE RAN) architecture. It is part of the Osmocom Open Source Mobile Communications projects.
It allows you to aggregate many Gb links/connections into one. It also has the ability to convert between different Gb interface protocol stacking, such as from Gb-over-FrameRelay to Gb-over-IP.
Until 2021 it used to be part of the osmo-sgsn git repository, and before that (until 2017) part of openbsc.git
Homepage and Issue Tracker
Find the issue tracker and wiki online at https://osmocom.org/projects/osmo-gbproxy and https://osmocom.org/projects/osmo-gbproxy/wiki, respectively.
Documentation
You can find the user manual at https://ftp.osmocom.org/docs/latest/osmogbproxy-usermanual.pdf and the VTY reference manual at https://ftp.osmocom.org/docs/latest/osmogbproxy-vty-reference.pdf.