Daniel Willmann 37518b3409 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		2021-05-28 17:20:44 +02:00
..
Makefile.am	Move vty node into gbproxy_vty.c	2021-02-12 16:26:22 +01:00
debug.h	Remove unused log categories	2021-02-12 15:47:22 +01:00
gb_proxy.c	Don't route messages to an SGSN if it is down	2021-05-28 17:20:44 +02:00
gb_proxy_ctrl.c	Remove osmo-sgsn relics	2021-03-10 13:52:07 +01:00
gb_proxy_main.c	gbproxy_main: Process options after all initialization is done	2021-04-22 13:40:13 +02:00
gb_proxy_peer.c	Don't route messages to an SGSN if it is down	2021-05-28 17:20:44 +02:00
gb_proxy_vty.c	vty: Print CellId along with RA-ID	2021-04-12 08:18:02 +00:00