diff options
authorNeels Hofmeyr <neels@hofmeyr.de>2019-12-12 01:31:04 +0100
committerNeels Hofmeyr <neels@hofmeyr.de>2019-12-23 19:02:34 +0100
commit862761191300e086c67e1647d897886378f51e8f (patch)
parent36244d2d1804b544b976c5f01b05600644a325cd (diff)
gsup: indicate CN-Domain in SendAuthInfo Requestsneels/sms_over_gsup
In order for osmo-hlr to be able to 100% guarantee distinct INDs for CS and PS, set CN-Domain = CS in all SendAuthInfo Requests. In Milenage auth, it is highly desirable that osmo-hlr guarantees use of distinct INDs for CS and PS domains. If an MSC and SGSN attached at the same time use the same IND bucket to generate Milenage SQN, that collision would rapidly waste SQNs and load osmo-hlr with requesting new auth tuples on each CS/PS Complete-Layer3. So far, osmo-msc did not indicate the CN domain in the GSUP SendAuthInfo Request, which was neither required nor evaluated. The CN-Domain is only sent for the UpdateLocation Request that usually follows later. Related: OS#4318 Change-Id: I22f44068268e62801cadbf6542efaf153423cd65
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/msc_vlr/msc_vlr_test_call.c b/tests/msc_vlr/msc_vlr_test_call.c
index eca0ca1d0..6df5d9c6b 100644
--- a/tests/msc_vlr/msc_vlr_test_call.c
+++ b/tests/msc_vlr/msc_vlr_test_call.c
@@ -172,7 +172,7 @@ static void lu_geran_noauth()
btw("Location Update request causes a GSUP LU request to HLR");
lu_result_sent = RES_NONE;
- gsup_expect_tx("04010809710000000156f0280102" VLR_TO_HLR);
+ gsup_expect_tx("04010809710000000156f0" CN_DOMAIN VLR_TO_HLR);
ms_sends_msg("0508" /* MM LU */
"7" /* ciph key seq: no key available */
"0" /* LU type: normal */