Project

General

Profile

Actions

Bug #5535

closed

Wrong Cause in BSSMAP CLEAR REQ in emergency call pre-emption situation

Added by laforge almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
A interface
Target version:
-
Start date:
04/19/2022
Due date:
% Done:

100%

Spec Reference:

Description

When a subscriber_conn is released due to pre-emptyion by an emergency call, the BSSMAP Clear Request the BSC sends to the MSC states cause "Equipment Failure", which is of course wrong.

This gives the MSC a wrong impression of why the clear request was sent. We should use the proper cause value (pre-emption).

This would make the MSC understand that some higher priority call is claiming the resource.


Related issues

Related to OsmoBSC - Bug #5534: Wrong RR release cause on pre-emption by emergency call.Resolvedneels04/19/2022

Actions
Actions #1

Updated by laforge almost 2 years ago

  • Related to Bug #5534: Wrong RR release cause on pre-emption by emergency call. added
Actions #2

Updated by neels almost 2 years ago

  • Status changed from New to In Progress
Actions #4

Updated by laforge over 1 year ago

both patches merged, but neither had a "Closes:" tag, so this issue didn't get closed.

Was that an accident, or is there still something to be done here? In any case, "In progress" for 3 months without any updates is not good.

Actions #5

Updated by neels over 1 year ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)