osmo-bsc - OsmoBSC: Osmocom's Base Station Controller for 2G circuit-switched mobile networks

Age	Commit message (Collapse)	Author	Files	Lines
2022-03-04	support "empty" SCCP N-Connect from MSC	Neels Hofmeyr	1	-0/+2
	Teach osmo-bsc to handle empty N-Connect. So far we were always expecting user data in an SCCP N-Connect from an MSC. However, it is perfectly valid for an initial BSSMAP request to follow later. This is relevant for: - Handover Request (incoming inter-BSC handover) - Perform Location Request (query physical location of the MS) Add state WAIT_INITIAL_USER_DATA with new timeout net X25. Always enter this state so that we don't have two separate code paths for handling initial user data. Related: SYS#5864 Change-Id: I535c791fa01e99a2226392eb05f676ba6c3cc16e
2022-02-08	bssmap_reset: make T4 user configurable	Philipp Maier	1	-0/+2
	The timer (T4) that controls the re-sending of the BSSMAP RESET can not be changed via the VTY, althrough it is defined via a tdef struct. Lets add a description along with default values to make it configurable via the VTY. Change-Id: I1fb5699220ab8a643a168567a89c6f381fe433a7 Related: SYS#5796
2021-11-10	implement all_allocated:{sdcch,tch} rate counters	Neels Hofmeyr	1	-0/+6
	Based on allAvailable{SDCCH,TCH}Allocated performance indicators, see 3GPP TS 52.402. Related: SYS#4878 Related: Ib3997a827c9cc43d1361bb0cf3bfab9f6d91bf82 (osmo-ttcn3-hacks) Change-Id: I8b06e435a224c8708cd6c67e97ee5413718fc1ed
2021-04-28	lchan_fsm: mode modify: fix missing timeouts and error transitions	Neels Hofmeyr	1	-0/+4
	Change-Id: I6364cfb78f661f5f7473dcec488e361e6a1dc9e4
2021-04-28	Lb: add missing X12 timer configurability	Neels Hofmeyr	1	-0/+2
	While adding timers for Channel Mode Modify, I notice that X12 is used in lcs_ta_req.c, but missing in net_init.c. Add it so that it is exposed on the VTY configuration. Change-Id: I19540f64de4937b39963bb66bebb1b5d433c2be2
2020-10-09	LCS: implement the bulk of Location Services	Neels Hofmeyr	1	-0/+2
	Depends: I4d7302a4853518916b6b425e710c10568eb2ffe5 (libosmocore) Change-Id: I28314ba97df86a118497e9b2770e2e6e2484e872
2020-09-18	lchan_fsm, lchan_rtp_fsm: make all timers configurable	Oliver Smith	1	-0/+12
	Choose saner timer numbers before exposing to the user config. Related: SYS#4897 Change-Id: I637fcdde93c11158de46157d494c060bb36bdcfb
2020-09-18	clean up timer definitions: introduce groups, move some T to X	Neels Hofmeyr	1	-52/+93
	Backwards compatibly, introduce timer groups in OsmoBSC, and move some non-specified T timers to new X timers: T993111 -> X3111 T993210 -> X3210 T999 -> X4 Why X4? because there already is an X3 used elsewhere in Osmocom, and I find it less confusing if X-numbers don't repeat across programs. See https://osmocom.org/projects/cellular-infrastructure/wiki/List_of_Timer_numbers Drop unused timers from g_mgw_tdefs. Only X2427 has an actual effect. (libosmo-mgcp-client recently moved T2427001 to X2427.) Put libosmo-mgcp-client related timers to the 'mgw' group, like in osmo-msc. This makes the MGCP timeout configurable for the first time. Keep previous timer commands as DEFUN_HIDDEN, and also translate the moved T timers to X timers on-the-fly. All previous VTY commands still work, and new 'timer [(net\|mgw)] ...' commands are added. timer.vty shows this. Remove the "_OPTIONAL" from the legacy "timer" and "show timer" commands, so that they don't ambiguously overload the new "timer [(net\|mgw)] ..." commands. Related: OS#4539 Related: If097f52701fd81f29bcca1d252f4fb4fca8a04f7 (osmo-mgw) Change-Id: I4beec47502afa193dee343869c4be55dc6a4b536
2020-09-16	add timer.vty	Neels Hofmeyr	1	-0/+95
	Before transitioning some unspecified T timers to X timers, and to introduce timer groups, first add this timer VTY test. Changes here will illustrate that the legacy commands will still work and redirect to new timer definitions. Related: OS#4539 Change-Id: Ie1bc635e16dc9a4040d063e1d9a51cdc76d9d1f2