Project

General

Profile

Bug #3601

OsmoMSC's GSUP client doesn't send CN domain to the HLR

Added by neels 11 months ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
09/28/2018
Due date:
% Done:

100%

Resolution:

Description

hence all osmo-msc clients are seen as PS clients.
That will lead to client identifications being stored in sgsn_number instead of vlr_number.


Related issues

Related to OsmoHLR - Bug #2796: OsmoHLR doesn't update VLR during UpdateLocationIn Progress12/30/2017

Related to OsmoHLR - Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changesResolved12/28/2017

History

#1 Updated by neels 11 months ago

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

#2 Updated by neels 11 months ago

  • Related to Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changes added

#3 Updated by laforge 11 months ago

It may be the case that in classic GSM the CN domain indicator is optional, as CS
existed before PS. So in absence of the indicator, as HLR I would always assume it's CS.

But sure, we can make it explicit frm the MSC side, I don't really care too much.

#4 Updated by neels 11 months ago

  • Description updated (diff)

#5 Updated by neels 11 months ago

laforge wrote:

It may be the case that in classic GSM the CN domain indicator is optional, as CS
existed before PS. So in absence of the indicator, as HLR I would always assume it's CS.

In GSUP we explicitly specify that a lack of CN domain indicator means PS...
probably from the time it still was the GPRS Subscriber Update Protocol.

#6 Updated by neels 11 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)