Patch Set 1: > how did you test it exactly? AFAICT you cannot provoke this > behavior with real OsmoBTS as it will always send the RSL CCCH > LOAD INDICATION or an EVENT CHANGE REPORT or anything immediately > after the connection is up. So in order to trigger this situation, > you'd have to establish RSL without sending any messages on it?
I have only verified that a sysmobts connects fine (receives SACH filling, channel assignment, etc) and that an osmo-bts-virtual can now connect without the regression which was documented in issue #2719. Should I try to construct a test case where the RSL link is not marked UP because a BTS does not send anything? It seems reasonable to assume that the link would not be marked UP in this case, because we'd never call ipaccess_sign_link(). -- To view, visit https://gerrit.osmocom.org/7503 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I78a152671a00b95c997830f7161fca92bb898fa3 Gerrit-PatchSet: 1 Gerrit-Project: osmo-bsc Gerrit-Branch: master Gerrit-Owner: Stefan Sperling <[email protected]> Gerrit-Reviewer: Harald Welte <[email protected]> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: Stefan Sperling <[email protected]> Gerrit-HasComments: No
