Project

General

Profile

Actions

Bug #3331

closed

OsmoBSC illegaly terminates SCCP connection

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

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
06/11/2018
Due date:
% Done:

100%

Spec Reference:

Description

I've been very puzzled while looking at A interface protocol traces generated by our test suite:

  • The BSC is at least in some situations disconnecting SCCP!

This is a blatant spec violation, as (of course) the BSC doesn't take such decisions. Following the usual master/slave logic at the hierarchical interfaces, it's obviously the MSC.

3GPP TS 48.006 Section 9.2 "Connection release" also clearly states:

This procedure is always initiated at the MSC side.

Files

20180611-bsc-closes-sccp.pcap 20180611-bsc-closes-sccp.pcap 5.58 KB laforge, 06/11/2018 11:08 AM
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)