Project

General

Profile

Actions

Bug #2870

closed

OsmoMSC is not closing the channel after CM SERV REJ / LU REJ

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

Status:
Resolved
Priority:
High
Assignee:
Category:
A interface (general)
Target version:
-
Start date:
01/24/2018
Due date:
% Done:

100%

Resolution:
Spec Reference:

Description

It seems OsmoMSC is not closing the subscriber connection if it sends a CM SERV REJ / LU REJ. Instead it seems to keep the SCCP connection around indefinitely and wait for the MS/RAN to release? Normally one would expect a rather quick/immediate release after we reject some transaction.

Actions #1

Updated by laforge about 6 years ago

  • Assignee changed from 4368 to daniel
Actions #2

Updated by laforge almost 6 years ago

  • Assignee changed from daniel to neels
Actions #3

Updated by neels almost 6 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

the recent MSC conn fsm release refactoring should have fixed this.
The ttcn3 TC_cmserv_imsi_unknown and other cmserv tests (which expect release in the end) all pass, resolving this issue.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)