Project

General

Profile

Bug #3331

OsmoBSC illegaly terminates SCCP connection

Added by laforge 2 months ago. Updated about 2 months ago.

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

100%

Estimated time:
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.
20180611-bsc-closes-sccp.pcap 20180611-bsc-closes-sccp.pcap 5.58 KB laforge, 06/11/2018 11:08 AM

History

#1 Updated by laforge 2 months ago

attaching pcap file showing the problem.

#2 Updated by laforge 2 months ago

this is the likely cause of what makes TC_bssmap_clear_does_not_cause_bssmap_reset and TC_ms_rel_ind_does_not_cause_bssmap_reset fail, as they (rightfully) don't expect a N-DISCONNECT.ind from the BSC.

#3 Updated by laforge 2 months ago

  • Assignee changed from sysmocom to laforge
  • % Done changed from 0 to 80

#4 Updated by laforge 2 months ago

  • Status changed from New to In Progress

#5 Updated by laforge 2 months ago

  • % Done changed from 80 to 100

patch merged

#6 Updated by laforge about 2 months ago

  • Status changed from In Progress to Resolved

patch long merged

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)