Bug #3391
Updated by neels over 5 years ago
Testing the new osmo-bsc against an SCCPlite MSC, I notice that the initial no IPA Identity ACK received from PING is emitted as with the legacy osmo-bsc. Hence the SCCPlite MSC is disallowed by never accepts the FSM, new osmo-bsc as valid IPA peer, ignoring all BSSMAP messages. Looking at the code, I see that libosmo-sccp only receives IPA_MSGT_PING and hence the connection _PONG, but apparently never emits these messages. I also notice that ipa_asp_fsm_priv contains a pong_timer that should presumably wait after an emitted PING, but is not accepted. never started. (Various issues have crept into this ticket, I'm editing this to reduce to * IIUC the xua_asp_fsm should emit an IPA Identity ACK reception.) PING as soon as it notices an established IPA link. * It seems odd that in an FSM, we have an osmo_timer as well. Why is it not a distinct state with a state timeout?
