msc_vlr_test_gsm_ciph.c: fix IMEISV MI: even number of digits, clear odd bit
There is an invalid Mobile Identity in the msc_vlr_test_gsm_ciph test data. This became apparent when applying the new osmo_mobile_identity API (in a following patch). Current Mobile Identity API ignores the error. Change-Id: Ib1d54c59acc8b716de471ca275f54f9d22da3574changes/14/18714/2
parent
5c38c817f2
commit
0ec7b23ee3
|
@ -643,7 +643,7 @@ static void test_ciph_imeisv()
|
|||
|
||||
btw("MS sends Ciphering Mode Complete with IMEISV, VLR accepts and sends GSUP LU Req to HLR");
|
||||
gsup_expect_tx("04010809710000004026f0" CN_DOMAIN VLR_TO_HLR);
|
||||
ms_sends_ciphering_mode_complete("063217094b32244332244372f5");
|
||||
ms_sends_ciphering_mode_complete("063217094332244332244372f5");
|
||||
VERBOSE_ASSERT(lu_result_sent, == RES_NONE, "%d");
|
||||
|
||||
btw("Subscriber has the IMEISV");
|
||||
|
|
|
@ -1790,7 +1790,7 @@ GSUP --> HLR: OSMO_GSUP_MSGT_UPDATE_LOCATION_REQUEST: 04010809710000004026f02801
|
|||
DVLR upd_hlr_vlr_fsm(IMSI-901700000004620:GERAN-A:LU){UPD_HLR_VLR_S_INIT}: state_chg to UPD_HLR_VLR_S_WAIT_FOR_DATA
|
||||
DBSSAP msc_a(IMSI-901700000004620:GERAN-A:LU){MSC_A_ST_AUTH_CIPH}: RAN decode: DTAP
|
||||
DRLL msc_a(IMSI-901700000004620:GERAN-A:LU){MSC_A_ST_AUTH_CIPH}: Dispatching 04.08 message: RR GSM48_MT_RR_CIPH_M_COMPL
|
||||
DBSSAP msc_a(IMSI-901700000004620:GERAN-A:LU){MSC_A_ST_AUTH_CIPH}: RR Ciphering Mode Complete contains Mobile Identity: IMEI-SV-4234234234234275F
|
||||
DBSSAP msc_a(IMSI-901700000004620:GERAN-A:LU){MSC_A_ST_AUTH_CIPH}: RR Ciphering Mode Complete contains Mobile Identity: IMEI-SV-4234234234234275
|
||||
DVLR set IMEISV on subscriber; IMSI=901700000004620 IMEISV=4234234234234275
|
||||
DVLR set IMEI on subscriber; IMSI=901700000004620 IMEI=42342342342342
|
||||
DVLR vlr_lu_fsm(IMSI-901700000004620:GERAN-A:LU){VLR_ULA_S_WAIT_HLR_UPD}: Received Event VLR_ULA_E_ID_IMEISV
|
||||
|
|
Loading…
Reference in New Issue