disable/constrain/hide "multiple msc" concept
There is a lot of complexity in the SCCP and configuration due to OsmoBSC supporting the conenction to multiple MSCs, and then route requests based on IMSI to those MSCs. This feature was once developed for one specific user and use case, which is no longer needed.
I think we should at least hide/disable the feature to avoid any confusion / misconfiguration of the users.
The typical GSM operator will think of MOCN (multi operator core network) or "A flex" when multiple MSCs connected to one BSC are on the table. The old OsmoBSC feature is about neither of those normal use cases.
Updated by neels almost 2 years ago
- Status changed from Feedback to Rejected
This issue is outdated / overhauled.
We have dropped the old imsi filtering feature, and instead have fully featured MSC pooling in place now.
AFAICT there is nothing we should drop about the current implementation.
(Concerning MOCN, implementing that would be a different topic altogether. It should be a different issue.)