OsmoBSC illegaly terminates SCCP connection
I've been very puzzled while looking at A interface protocol traces generated by our test suite:
- The BSC is at least in some situations disconnecting SCCP!
This is a blatant spec violation, as (of course) the BSC doesn't take such decisions. Following the usual master/slave logic at the hierarchical interfaces, it's obviously the MSC.
3GPP TS 48.006 Section 9.2 "Connection release" also clearly states:
This procedure is always initiated at the MSC side.