Commit
5ec2d97eafb31c7f52f2d670749935e37f98bf75
by Vadim Yanitskiys1ap_proxy: fix E-RAB FSM lookup for RELEASE related IEs
We use a tuple of {MmeUeId, EnbUeId, RABId} to register and lookup
E-RAB FSMs in the registry. Using RABId alone is wrong (because
it's not a globally unique ID) and will never yield anything.
Because of this bug the E-RAB FSMs were never terminated properly.
This was found thanks to the ttcn3-s1gw-test and remained unnoticed
so far because in test_e_rab_release() we still have this TODO:
%% TODO: make sure that the E-RAB FSM has been terminated
We'll need to add some E-RAB introspection API to implement this.
Change-Id: Ic737e7b0c08562ecfd641ce4e3c2f27c26f8560e
Fixes: 935a0f02 "{sctp,s1ap}_proxy: employ E-RAB FSMs"