Bug #3601
OsmoMSC's GSUP client doesn't send CN domain to the HLR
100%
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
History
#1 Updated by neels over 1 year ago
- Related to Bug #2796: OsmoHLR doesn't update VLR during UpdateLocation added
#2 Updated by neels over 1 year ago
- Related to Bug #2785: OsmoHLR forgets to send InsertSubscriberData to VLR/SGSN when data changes added
#3 Updated by laforge over 1 year 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 over 1 year ago
- Description updated (diff)
#5 Updated by neels over 1 year 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 over 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
