Project

General

Profile

Feature #3641

Make "logging filter imsi " work for (currently) unknown subscribers

Added by daniel 2 months ago. Updated 3 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
10/09/2018
Due date:
% Done:

100%

Spec Reference:

Description

osmo-bsc only allows filtered logging base on IMSI it already knows. We should change this so a log filter can also be created for a subscriber that is currently unknown to osmo-bsc.

The attached untested patch should work as intended. It will create the subscriber in the logging filter imsi statement if it doesn't exist. Once we get an CompleteL3 message with the IMSI the code should reuse this subscriber and the logging filter should work.

History

#1 Updated by pespin 5 days ago

  • Status changed from New to In Progress
  • Assignee set to pespin

#2 Updated by pespin 5 days ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 80

Submitted together with other patches to fix related code:
https://gerrit.osmocom.org/#/c/osmo-bsc/+/12250/

So now most stuff is logged correctly under imsi filter, but I was unable were to find information related to Location Update in order to add the log context there. Is LU and MIdentity just forwarded and not parsed by BSC?

#3 Updated by pespin 4 days ago

  • Assignee changed from pespin to daniel
  • % Done changed from 80 to 90

Patches Merged.

As far as I understood, according to Neels l3 info is forwarded by bsc directly to MSC without being parsed, that's why we don't see the IMSI during location update.

daniel If that's fine for you, go ahead and close the issue.

#4 Updated by daniel 3 days ago

  • Status changed from Feedback to Resolved
  • % Done changed from 90 to 100

Yeah, until we have messages where osmo-msc can tell osmo-bsc about the subscriber this is as good as it gets.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)