| commit | 37518b3409ca24f4c2e0699de49ebafae14bd4af | [log] [tgz] |
|---|---|---|
| author | Daniel Willmann <dwillmann@sysmocom.de> | Thu May 27 18:13:36 2021 +0200 |
| committer | Daniel Willmann <dwillmann@sysmocom.de> | Fri May 28 17:20:44 2021 +0200 |
| tree | 688a691ef891ec8fe7aff2e035aa499908a79e32 | |
| parent | a42963421f0e0a1ad97ae57b4ce19e1bfd30e16c [diff] |
Don't route messages to an SGSN if it is down If an SGSN in a pool is down we expect the messages to instead be sent to a different SGSN in the pool. That SGSN will not necessarily know what to do with those messages, but it should (implicitly) detach that UE so that it can reattach at the new SGSN. Otherwise UEs on a failed SGSN would simply stop working as the messages would never be forwarded anywhere. Fixes: OS#4952 Change-Id: I3f794659866e1f31496a39ca631b3b042a60aa27
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
Find the issue tracker and wiki online at https://osmocom.org/projects/osmo-gbproxy and https://osmocom.org/projects/osmo-gbproxy/wiki, respectively.
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.