Project

General

Profile

Feature #4272

osmo-hlr proxy routing: don't allow hijacking of routing to existing routes

Added by neels 2 months ago. Updated 2 months ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Target version:
-
Start date:
11/19/2019
Due date:
% Done:

100%


Description

If, in a D-GSM ecosystem, two MSCs are accidentally configured with identical IPA unit names on the GSUP wire,
the first MSC that shows up should continue to work normally, while any later MSC with identical name should be thwarted with OSMO_GSUP_MSGT_E_ROUTING_ERROR responses.
Test that this works as expected, particularly, that there is no way to inadvertently hijack GSUP conversations that are in flight to an MSC with the same name.

History

#1 Updated by neels 2 months ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

tested, and fixed a problem in gsup_server.c so that the ROUTING_ERROR message is indeed sent to the peer that would cause the name collision,
and not the peer that was there first and validly holds the name that the second peer attempts to re-use.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)