Attention is currently required from: neels, pespin. laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hnbgw/+/31431 )
Change subject: context map: introduce RUA and SCCP FSMs to fix leaks ...................................................................... Patch Set 5: Code-Review+1 (2 comments) File include/osmocom/hnbgw/context_map.h: https://gerrit.osmocom.org/c/osmo-hnbgw/+/31431/comment/ce2ee4d9_2f263045 PS5, Line 22: enum map_rua_fsm_event { not critical, but this is where the ISO/OSI style request/indication naming could be useful to clearly see the direction of such an "event". the _RX_ are indications telling the FSM that something happens. Just like SCCP_DISC, HNB_LINK_LOST. Where TX_RANAP_MSG and _EV_PLEASE_DISCONNECT are requests to the FSM. File src/osmo-hnbgw/hnbgw_rua.c: https://gerrit.osmocom.org/c/osmo-hnbgw/+/31431/comment/3a993d43_7a99de14 PS5, Line 183: { RUA_ProcedureCode_id_Connect, "id-Connect" }, > AFAIK the messages are called "id-Connect" in RUA, including the "id-", > whatever the meaning may be No, the procdures are not called "id-Connect", but "CONNECT". See the section headlines of 25.468 9.1.x. That "id-" some artefact of the asn.1 syntax, so they have differnt names for the identifier from the type name. -- To view, visit https://gerrit.osmocom.org/c/osmo-hnbgw/+/31431 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-hnbgw Gerrit-Branch: master Gerrit-Change-Id: I6ff7e36532ff57c6f2d3e7e419dd22ef27dafd19 Gerrit-Change-Number: 31431 Gerrit-PatchSet: 5 Gerrit-Owner: neels <[email protected]> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <[email protected]> Gerrit-CC: pespin <[email protected]> Gerrit-Attention: neels <[email protected]> Gerrit-Attention: pespin <[email protected]> Gerrit-Comment-Date: Tue, 21 Feb 2023 14:13:59 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: Yes Comment-In-Reply-To: neels <[email protected]> Comment-In-Reply-To: pespin <[email protected]> Gerrit-MessageType: comment
