Project

General

Profile

Bug #2726

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

Added by laforge about 1 month ago. Updated 16 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
12/08/2017
Due date:
% Done:

0%

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 New 12/09/2017
Related to OsmoBSC - Bug #2725: OsmoBSC doesn't release lchan if MSC doesn't answer to CR New 12/08/2017

History

#1 Updated by laforge about 1 month ago

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

#2 Updated by laforge about 1 month ago

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

#3 Updated by laforge 16 days ago

  • Assignee set to dexter

Also available in: Atom PDF