Project

General

Profile

Bug #2846

MSC doesn't close SCCP/BSSAP connection on CM SERV REQ tht cannot be parsed

Added by laforge 4 months ago. Updated 2 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
01/20/2018
Due date:
% Done:

0%

Resolution:

Description

If sending a CM SERV REQ that's invalid, I get

<000a> a_iface_bssap.c:699 Rx BSC DT: 00 15 57 05 01 03 17 0f 05 24 01 01 50 09 21 26 24 10 32 54 76 98 0f 
<000a> a_iface_bssap.c:629 Rx MSC DT1 BSSMAP COMPLETE LAYER 3
<000a> a_iface_bssap.c:291 BSC has completed layer 3 connection (conn_id=1)
<000a> a_iface_bssap.c:311 Unable to parse element CELL IDENTIFIER (wrong field length) -- discarding message!

but the MSC doesn't close the SCCP connection. It also doesn't send AUTH REQ or any other L3 message, basically keeping the radio channel open for no reason at all.

History

#1 Updated by laforge 7 days ago

  • Assignee changed from sysmocom to stsp

#2 Updated by neels 2 days ago

It is likely that this got fixed by http://git.osmocom.org/osmo-msc/commit?id=e3d3dc6ea218a07161eeb80ae864a96bef2d8e61 but worth testing before closing this.

Also available in: Atom PDF