Project

General

Profile

Actions

Bug #3841

open

cosmetic: tearing down the old lchan after inter-BSC handover always goes through RELEASE_AFTER_ERROR (instead of normal release)

Added by neels about 5 years ago. Updated almost 5 years ago.

Status:
New
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
03/15/2019
Due date:
% Done:

0%

Spec Reference:

Description

After a successful outgoing inter-BSC Handover, osmo-bsc receives a Clear Command from the MSC and should gracefully release the lchan.
For some intricate ordering of things, though, this Clear Command results in the lchan release being interpreted as an error
and triggers the internal release-in-error code path.

The end result is not harmful at all, just always seeing the lchan transition through WAIT_AFTER_ERROR doesn't accurately reflect that this is what should be happening.

A log transcript follows.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)