OsmoMSC never releases MO call if MNCC doesn't respond to SETUP
It seems like the call is never released in case the MNCC interface never responds to a MO SETUP.
See attached trace.
Terminating the MNCC handler doesn't seem to change this either, at leaset not on the CC signalling side. The log prints:
<0004> mncc_sock.c:85 MNCC Socket has LOST connection <0001> gsm_04_08.c:191 Clearing all currently active transactions!!! <0007> msc_mgcp.c:1049 (subscriber:IMSI:262420000000026) invalid mgcp context, call release failed. <0001> gsm_04_08.c:1307 (ti 08 sub IMSI:262420000000026) new state INITIATED -> NULL
however, no attempt is made to send a CC release to the MS, nor is the SCCP connection cleared.
#2 Updated by neels over 2 years ago
There is a patch series coming to refactor the MSC's conn FSM to discard connections as soon as the use count reaches zero.
It is worth checking this error separately, i.e. make sure that an MNCC SETUP timeout indeed results in a use count decrement.
The FSM does not handle CC timeouts, that is still done the "old" way within our CC implementation.
Might be worth a thought to implement an actual CC FSM as well, as a child of the subscr_conn FSM, with timeouts for each state except the active call.