Project

General

Profile

Bug #67

gb_proxy keeps stale PTP-BVCI <-> NSVCI mappings

Added by laforge over 2 years ago. Updated 11 months ago.

Status:
New
Priority:
Low
Assignee:
Category:
osmo-gbproxy
Target version:
-
Start date:
Due date:
% Done:

0%

Spec Reference:

Description

When BVCI A first establishes a connection through NSVCI/NSEI B, then later establishes a connection through NSVCI/NSEI A, gb_proxy permanently keeps a stale proxy mapping associating BVCI A with NSVCI B.

This causes all downlink messages from the SGSN to be routed still through NSVCI B, despite now NSVCI A being the correct one.

History

#1 Updated by laforge about 6 years ago

  • Status changed from New to In Progress

#2 Updated by laforge over 2 years ago

  • Priority changed from High to Normal

#3 Updated by laforge over 2 years ago

  • Status changed from In Progress to New

#4 Updated by laforge over 2 years ago

  • Priority changed from Normal to Low

#5 Updated by laforge 11 months ago

  • Project changed from OpenBSC to OsmoSGSN
  • Category deleted (osmo-gb_proxy)

#6 Updated by laforge 11 months ago

  • Category set to osmo-gbproxy

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)