Bug #2768
closedOsmoBSC doesn't perform MGCP DLCX in all cases of channel release
100%
Description
Whenever we performed CRCX on one or multiple MGCP connections on osmo-mgw, we must also call DLCX to clean up.
There are situations like at least the one seen in the attached PCAP file in which CRCX+MDCX are called, but the media gateway never sees a DLCX.
I've seen this cause follow-on problems if more connections are allocated on the same endpoint, at which the mgw will refues as only two connections are permitted by endpoint.
We should have a state machine that ensures whever the SCCP connection is closed, and that SCCP connection had MGCP connections, that those MGCP connections are deleted.
Files
Updated by dexter almost 6 years ago
The revised implementation that uses the GSCON FSM (see also https://osmocom.org/issues/2823) should fix this problem. When the GSCON FSM terminates it must make sure that the connection is deleted.
Updated by dexter over 5 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
This is Fixed by GSCON (https://gerrit.osmocom.org/#/c/7142/).