Project

General

Profile

Actions

Bug #5876

open

on HNBAP HNB Register, clear previous UE state if any

Added by neels 11 months ago. Updated 9 months ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
01/25/2023
Due date:
% Done:

0%

Spec Reference:

Description

when a HNB registers with osmo-hnbgw, and the same HNB is already registered, osmo-hnbgw keeps the HNB state and simply logs "(duplicated)" with the HNB Register Request log.

A HNB should only register when it has restarted, and no UE state should stay around when that happens.
So, upon HNB Register Request, if we find that HNB already connected, clear out any previous state on that HNB.

Otherwise we likely keep stale UE state and stale SCCP conns indefinitely, by ignoring a restart of a HNB.

Actions #1

Updated by laforge 9 months ago

  • Assignee set to neels
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)