Project

General

Profile

Actions

Bug #2732

closed

OsmoBSC sends invalid zero-length BSSAP payload in SCCP RLSD

Added by laforge over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Start date:
12/10/2017
Due date:
% Done:

100%

Spec Reference:

Description

When sending a SCCP RLSD (e.g. in response to a BSSMAP RESET), OsmoBSC includes some invalid BSSAP message as payload.

11:27:30.274418 4 Incoming message was mapped to @SCCP_Types.PDU_SCCP : {
    released := {
        messageType := 4,
        destLocRef := '35AA17'O,
        sourceLocRef := '000004'O,
        releaseCause := 0,
        pointer1 := 1,
        optionalPart := {
            data := {
                paramName := 15,
                paramLength := 8,
                data := '0000000303000000'O
            },
            importance := omit
        },
        eop := {
            paramName := 0
        }
    }
} id 3

11:27:30.277709 mtc BSSAP_CodecPort.ttcn:244: Dynamic test case error: While RAW-decoding type '@BSSAP_Types.PDU_BSSAP': Can not decode type '@BSSAP_Types.PDU_BSSAP', because invalid message was received

Files

Actions #1

Updated by laforge over 6 years ago

  • Project changed from OsmoBSC to libosmo-sccp + libosmo-sigtran
  • Status changed from New to Resolved
  • % Done changed from 0 to 90

Actually turned out to be a libosmo-sigtran bug.

Fix submitted in https://gerrit.osmocom.org/5263

Actions #2

Updated by laforge over 6 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)