Project

General

Profile

Actions

Bug #3850

closed

programming of 3 digit MNC does not work

Added by dexter about 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
03/20/2019
Due date:
% Done:

100%

Spec Reference:

Description

While programming 3 digit MCC + 2 digit MNC works flawlessly, problems are experienced when the MNC is extended to 3 digits (which is spec compliant!).

One can use the attached mksim_sjs1_three_digit_mnc.sh script to generate a problematic card. See mksim_sjs1_three_digit_mnc.log for the expected output. The programming works fine and the output also does not show any suspicious behavior. However, when the card is inserted into a phone, the phone seems not to recognize the third digit of the MNC and the digit is chopped off.

The origin of this problem is presumably the way how MCC and MNC are programmed into the sysmo-usim-sjs1. The only way how the sim gets informed about MNC/MCC is the IMSI string. This means for the sim there is no way of knowing if the third digit of the MCC is actually part of the MCC or just the first digit of the consecutive part of the IMSI. Presumbably one needs to write MNC/MCC to some other file as well or set a flag somewhere. This needs to be checked further.


Files

mksim_sjs1_three_digit_mnc.log mksim_sjs1_three_digit_mnc.log 1.15 KB dexter, 03/20/2019 12:01 PM
mksim_sjs1_three_digit_mnc.sh mksim_sjs1_three_digit_mnc.sh 321 Bytes dexter, 03/20/2019 12:01 PM
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)