Bug #4751

config 'msc' / 'core-location-area-code' is a non-feature

Added by neels 7 months ago. Updated 6 months ago.

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


Spec Reference:


OsmoBSC seems to support setting an entire MSC on a forced Location Area Code (LAC).
The only place where this reflects is composing a CGI for an MSC (cgi_for_msc()), when sending a Create Layer 3 and Handover Performed to an MSC.
So an MSC is made to believe that a subscriber comes from a specific LAC.

The reverse direction will not work: when the MSC asks to Page a subscriber on the LAC it thinks the subscriber is camped on,
the BSC will likely not recognise this forced LAC from core-location-area-code, and not Page at all or on the wrong cell.

I also currently don't see how this can work, because overwriting a cell's LAC to the MSC is lossy and cannot be reversed.
The only solution I see is to Page on the entire BSS when an MSC has a forced LAC.

Either properly revive and test this feature, or I guess we can also drop it entirely.

Associated revisions

Revision 60e5ddf6 (diff)
Added by Neels Hofmeyr 6 months ago

drop features 'core-location-area-code' and 'core-cell-identity'

This feature apparently assigned a fixed LAC and CI to a specific MSC, but
looking at the implementation was obviously not useful.

Keep the vty commands for legacy compat, now without effect besides logging an
error via vty_out().

Related: OS#4751
Change-Id: I6bee704e7e5d5b6b86473323bae1fa9fce9241ee


#1 Updated by laforge 7 months ago

in case of doubt, always remove.

#2 Updated by laforge 6 months ago

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

#4 Updated by neels 6 months ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)