Project

General

Profile

Actions

Bug #2869

closed

OsmoMSC is not rejecting CM re-establishment

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

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

100%

Resolution:
Spec Reference:

Description

If a MS looses a call, it may trigger the call re-establishment procedure as per TS 24.008 Section 4.5.1.6.

OsmoMSC is neither handling nor rejecting such a request, see:

<000a> a_iface_bssap.c:699 Rx BSC DT: 00 1b 57 05 08 00 62 22 40 00 17 00 2a 17 0e 05 28 00 01 50 08 29 26 24 00 00 00 00 22 
<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=27)
<000a> a_iface_bssap.c:53 Allocating A-Interface subscriber conn: lac 23, conn_id 27
<000a> a_iface_bssap.c:71 A-Interface subscriber connection successfully allocated!
<0000> gsm_04_08.c:3316 subscr unknown: Message not permitted for initial conn: GSM48_MT_MM_CM_REEST_REQ
<000a> a_iface_bssap.c:339 User has been accepted by MSC.
Actions #1

Updated by laforge over 6 years ago

  • % Done changed from 0 to 80
Actions #2

Updated by laforge over 6 years ago

  • Status changed from New to In Progress
Actions #3

Updated by laforge about 6 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 80 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)