Feature #3454

disable/constrain/hide "multiple msc" concept

Added by laforge over 2 years ago. Updated 25 days ago.

A interface
Target version:
Start date:
Due date:
% Done:


Spec Reference:


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.

Related issues

Related to OsmoBSC - Feature #3682: Intra-domain connection of OsmoBSC to multiple MSCsResolved11/06/2018


#1 Updated by laforge 11 months ago

  • Related to Feature #3682: Intra-domain connection of OsmoBSC to multiple MSCs added

#2 Updated by laforge 26 days ago

  • Status changed from New to Feedback
  • Assignee changed from sysmocom to neels

not sure how much of this still applies, now that we have MSC pooling support (see #3682)

#3 Updated by neels 25 days 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.)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)