3 Commits

Author	SHA1	Message	Date
Oliver Smith	1968ca922b	sccp_sap_up_ran: ignore RAN until MSC is connected ... Related: SYS#5560 Change-Id: Idf9501412484fa92e8836952609fba7c5443d6c9	2022-03-21 16:36:32 +01:00
Oliver Smith	70cd49dcae	Send RESET to MSC on start up ... Automatically send RESET to the MSC as the BSCNAT starts up. Try it again if it fails, in case the MSC was not started yet or if the SCCP connection was not up yet (right now it does not seem possible to get notified when the SCCP connection is up). Related: SYS#5560 Related: https://osmocom.org/projects/osmo-bscnat/wiki/AoIP_OsmoBSCNAT#RESET Change-Id: Icfec3ec0168c7040e88a536fa48da339349fb6cf	2022-03-21 16:36:32 +01:00
Oliver Smith	49e50de426	Store MSC ... Expect one MSC to be configured in the address book (part of the cs7 section in the config, see doc/examples/osmo-bsc-nat/osmo-bsc-nat.cfg) and store it on start up. Store the MSC in a list, as we may potentially support multiple MSCs in the future. Also that makes it symmetric to the BSC list. Don't use the stored MSCs in the forwarding logic just yet, a future commit will replace the current forwarding code with proper connection mappings. Related: SYS#5560 Change-Id: I711df0c649728f1007857fbfda500ed5ef69287b	2022-03-21 16:36:32 +01:00