Project

General

Profile

Actions

Bug #2980

closed

in bssmap_rx_l3_compl(), we decode the L3-complete MCC-MNC but never verify their actual value

Added by neels about 6 years ago. Updated almost 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
02/22/2018
Due date:
% Done:

0%

Resolution:
Spec Reference:

Description

It seems that messages coming in over the A interface are allowed to completely mismatch the MCC-MNC setting in the MSC's config.
It might be a valid feature to serve more than one MCC-MNC with our MSC, but if we do, we shouldn't have an MCC-MNC configured in the osmo-msc.cfg that gets ignored silently.

See in bssmap_rx_l3_compl(), that we decode the LAI, but the resulting mcc and mnc never get compared to or passed on to anything.
http://git.osmocom.org/osmo-msc/tree/src/libmsc/a_iface_bssap.c?id=2568f0177995ca0e8314bace1940b8c9d8117209#n304

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)