Actions
Bug #3331
closedOsmoBSC illegaly terminates SCCP connection
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
Updated by laforge almost 6 years ago
attaching pcap file showing the problem.
Updated by laforge almost 6 years 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.
Updated by laforge almost 6 years ago
- Assignee changed from 4368 to laforge
- % Done changed from 0 to 80
Actions
