Project

General

Profile

Actions

Bug #2990

closed

OsmoBTS doesn't seem to ever send a DELETE INDICATION

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

Status:
Resolved
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
02/24/2018
Due date:
% Done:

100%

Spec Reference:

Description

As per TS 48.058, when there are too many IMMEDIATE ASSIGN for the BTS to handle, it shall send DELETE INDICATIONs back to the BSC. There's little point in trying to grow the queue indefinitely. Rather, we should detect if the rate of new IMM.ASS is larger than those that we can actually send over Um, and then start to issue DELETE INDICATIONs

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)