osmo-hlr - Osmocom HLR for GSUP protocol towards OsmoSGSN and OsmoCSCN

Age	Commit message (Collapse)	Author	Files	Lines
2019-04-09	USSD: save MO USSD's originating MSC's vlr_number	Oliver Smith	1	-0/+9
	Save the source IPA name in ss_session, so we can send "invalid IMSI" messages to the originating MSC. Remove the fixed size from ss->vlr_number (we don't know the size of the IPA name when it does not come from the database). Add ss->vlr_number_len to give osmo_gsup_addr_send() the format it expects, and to have one less place in the code where the IPA names are not stored as blob. Looking up the IPA name from struct osmo_gsup_conn could either be done like in osmo_gsup_server_ccm_cb() by reading the IPA IEs (which has a FIXME comment), or by finding the route associated with conn. I went with the latter approach, because it seems cleaner to me. Related: OS#3710 Change-Id: If5a65f471672949192061c5fe396603611123bc1
2018-06-24	gsup_router: Use "#pragma once" and add missing #includes	Harald Welte	1	-0/+5
	Change-Id: I2cc43ea5846e5b98281efc897252c8dcc3ef5728
2018-06-24	move osmo_gsup_addr_send() declaration from luop.h to gsup_router.h	Harald Welte	1	-0/+4
	Change-Id: I33165b7b58bd8c863083ed50ce21e3c032c579f5
2016-05-03	Major update; Code now supports SAI, LU and ISD transactions	Harald Welte	1	-0/+8
	We also introduce a 'gsup_router' which enables us to route a transaction to a given VLR. It works based on the SERIAL attribute communicated at time of the IPA multiplex setup as part of the CCM sub-protocol.