Project

General

Profile

Bug #3356

OsmoSGSN doesn't provide unique IDTAG_SERNR in IPA CCM

Added by laforge 23 days ago. Updated 23 days ago.

Status:
New
Priority:
High
Assignee:
Category:
GSUP interface
Target version:
-
Start date:
06/23/2018
Due date:
% Done:

0%

Estimated time:
Spec Reference:

Description

OsmoSGSN currently identifies itself simply as "SGSN" over the IPA/GSUP link to OsmoHLR.

This is wrong as it results in all OsmoSGSNs (in a multi-SGSN network) to register using the same identity, which in turn will render the HLR unable to store which SGSN is actually serving the subscriber, and/or to route messages accordingly.

It appears the change to "SGSN" was made in Change-Id: I0a60681ab4a4d73e26fe8f0637447db4b6fe6eb2 from "SGSN-00-00-00-00-00-00" before. Both the old and the new name are wrong though, as they're not unique.

The correct behavior AFAICT is "SGSN-" prefix with whatever unique identifier behind. We could make that suffix configurable in the VTY, if there's no other way to derive any other locally unique identifier. MAC addresses work fine for BTSs, but not for SGSNs: There might be any number of OsmoSGSNs running on the same physical / virtual machine with only one MAC address...


Related issues

Related to OsmoMSC - Bug #3355: OsmoMSC doesn't provide unique IDTAG_SERNR in IPA CCMNew2018-06-23

Related to OsmoHLR - Bug #2796: OsmoHLR doesn't update VLR during UpdateLocationNew2017-12-30

History

#1 Updated by laforge 23 days ago

  • Related to Bug #3355: OsmoMSC doesn't provide unique IDTAG_SERNR in IPA CCM added

#2 Updated by laforge 23 days ago

  • Related to Bug #2796: OsmoHLR doesn't update VLR during UpdateLocation added

#3 Updated by laforge 23 days ago

Note: The identifier must stay unique even across re-starts of the SGSN.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)