Project

General

Profile

Bug #2726

OsmoBSC doesn't release lchan if MSC refuses connection (CR -> CREF)

Added by laforge 5 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
High
Assignee:
laforge
Category:
-
Target version:
-
Start date:
12/08/2017
Due date:
% Done:

100%

Spec Reference:

Description

If the MSC responds with CREF, it appears that the lchan is not released. At least not in a way that's visible to RSL, i.e. no RF CHAN REL or the like.

I'm implementing a test case in TTCN-3 for this: TC_chan_act_ack_est_ind_refused

Related issues

Related to OsmoBSC - Bug #2731: OpenBSC doesn't release lchan if MSC does a hard SCCP disconnect Resolved 12/09/2017
Related to OsmoBSC - Bug #2725: OsmoBSC doesn't release lchan if MSC doesn't answer to CR Resolved 12/08/2017

History

#1 Updated by laforge 5 months ago

  • Related to Bug #2731: OpenBSC doesn't release lchan if MSC does a hard SCCP disconnect added

#2 Updated by laforge 5 months ago

  • Related to Bug #2725: OsmoBSC doesn't release lchan if MSC doesn't answer to CR added

#3 Updated by laforge 4 months ago

  • Assignee set to dexter

#4 Updated by laforge 3 months ago

  • Status changed from New to In Progress
  • Assignee changed from dexter to laforge
  • % Done changed from 0 to 70

I have a patch for this in Change-Id I64a46b5bcd4272e3fa2ff4ee824c2f3fdff6854b of the lafogre/fsm branch

#5 Updated by laforge 3 months ago

  • Priority changed from Normal to High

#6 Updated by laforge 3 months ago

  • Status changed from In Progress to Stalled

waiting for dexter to complete the work on the FSM branch

#7 Updated by laforge about 1 month ago

  • Status changed from Stalled to Resolved
  • % Done changed from 70 to 100

patch has been merged, testcase passed.

Also available in: Atom PDF