Project

General

Profile

Bug #2796

OsmoHLR doesn't update VLR during UpdateLocation

Added by laforge 4 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
12/30/2017
Due date:
% Done:

0%


Description

For some reason, the VLR column in the HLR table is not updated when a subscriber performs an Update Location procedure.

History

#1 Updated by neels about 2 months ago

What should go in the VLR column? We have the IPAC_IDTAG_SERNR producing something like "SGSN-00-00-00-00-00-00" and "MSC-00-00-00-00-00-00". The HLR also has sgsn_number and sgsn_address columns, could be set to the same / to the remote GSUP client address, by switching on osmo_gsup_message.cn_domain...

#2 Updated by neels about 2 months ago

the IDTAG_SERNR is handled in osmo_gsup_server_ccm_cb() in osmo-hlr/src/gsup_server.c

#3 Updated by laforge about 2 months ago

In a real 3GPP HLR with MAP, it's the global title of the respective VLR which is stored.

For us, it is "any other unique identifier of the VLR", and I think it hasn't been specified yet so far.

I'm against using the IP address, as this will break all kinds of dynamic address or NAT scenarios (which currently work as GSUP is a strict client->server protocol).

IDTAG_SERNR might be an idea, maybe also some other IDTAG? We should make it user-configurable then to ensure multiple MSCs have differnet identifiers.

Also available in: Atom PDF