Project

General

Profile

Actions

Bug #4595

closed

MSC tries to find BSSMAP TLV for OSMUX in IuCS/RANAP traffic

Added by laforge almost 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
IuCS support
Target version:
-
Start date:
06/08/2020
Due date:
% Done:

100%

Resolution:
Spec Reference:

Description

This obviously doesn't make sense:

<000f> ran_peer.c:138 ran_peer(UTRAN-Iu:RI-SSN_PC:PC-0-150-3:SSN-RANAP)[0x56063f4ac550]{READY}: Failed parsing TLV looking for Osmux support

Actions #1

Updated by pespin almost 4 years ago

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

neels Why do you say it doesn't make sense? AFAIU osmux is used in the core network starting from osmo-mgw, so it's unrelated to the RAN technology in use?

Actions #2

Updated by neels almost 4 years ago

I didn't say that :P

But it does make sense because it is on IuCS, and the hNodeBs we support definitely don't support osmux

Actions #3

Updated by neels almost 4 years ago

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

neels wrote:

I didn't say that :P

But it does make sense because it is on IuCS, and the hNodeBs we support definitely don't support osmux

pespin and especially because using the GSM 08.08 TLV definitions on a RANAP encoded message is plain wrong.

Decoding a message in ran_peer.c is completely the wrong place.
I'm moving it in https://gerrit.osmocom.org/c/osmo-msc/+/19024

Actions #4

Updated by neels over 3 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)