Project

General

Profile

Actions

Feature #3644

open

allow arbitrary bytes in Global Title (GT), a.k.a. the VLR,SGSN's identification towards the HLR

Added by neels about 4 years ago. Updated about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
10/11/2018
Due date:
% Done:

0%

Spec Reference:

Description

osmo-msc and osmo-sgsn send IPA_IDTAG_SERNR identifications to osmo-hlr of the form "MSC-00-00-00-00-00-00".
We've already enlarged the vlr_number and sgsn_number fields in osmo-hlr's subscriber struct to make room for this.
However, the real Global Title to identify an entity like the MSC should be allowed to contain arbitrary bytes and lengths.

Particularly, in osmo-hlr's luop, the luop->peer is just a pointer and needs a length.
Furthermore we should not expect nul termination, as we currently do, for proper GT support.
We should also adjust osmo-hlr's database scheme for arbitrary GT blobs.


Related issues

Related to OsmoMSC - Bug #3355: OsmoMSC doesn't provide unique IDTAG_SERNR in IPA CCMResolvedstsp06/23/2018

Actions
Related to OsmoSGSN - Bug #3356: OsmoSGSN doesn't provide unique IDTAG_SERNR in IPA CCMIn Progressosmith06/23/2018

Actions
Actions #1

Updated by neels about 4 years ago

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

Updated by neels about 4 years ago

  • Related to Bug #3356: OsmoSGSN doesn't provide unique IDTAG_SERNR in IPA CCM added
Actions #3

Updated by laforge about 3 years ago

  • Assignee set to neels
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)