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	-7/+17
	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
2019-04-08	Cosmetic: gsup_route_find: comment addr, addrlen	Oliver Smith	1	-1/+7
	Describe the addr, addrlen parameters in gsup_route_find() and (more commonly used) osmo_gsup_addr_send(). Without this description, it is easy to get the parameters wrong and have routes not being found, as shown with debug prints like these: gsup_route_find: addr, addrlen: "MSC-13-37-00-00-00-00", 21 gsup_route_find: comparing with: "MSC-13-37-00-00-00-00\0", 22 Change-Id: Ib79878970bd07caac6eb921af8ae95403b90a4cb
2019-02-14	Log ip:port when adding GSUP routes	Max	1	-1/+1
	Change-Id: I7202fdf59e763dbca261508685555b324ac7e4c0
2018-07-30	GSUP: Log GSUP route add/remove	Harald Welte	1	-0/+5
	Change-Id: I1768d0b8ee7e2821e40a799c9a1c1d900a7ddc48
2016-05-03	Major update; Code now supports SAI, LU and ISD transactions	Harald Welte	1	-0/+85
	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.