hnbgw: initial_ue_empty_cr: use larger payload to trigger empty SCCP CR
osmo-hnbgw will deprecate the 'sccp cr max-payload-len' config option.
To still trigger the 130 byte limit that is now enforced in
libosmo-sigtran, enlarge the NAS PDU.
So far the limit set via VTY was 0 bytes, which will no longer happen in
osmo-hnbgw after I18dece84b33bbefce8617fbb0b2d79a7e5adb263.
Related: OS#5906 SYS#5968
Change-Id: I174b2ce06a31daa5a129c8a39099fe8962092df8
diff --git a/hnbgw/HNBGW_Tests.ttcn b/hnbgw/HNBGW_Tests.ttcn
index eb7fad0..2aa6407 100644
--- a/hnbgw/HNBGW_Tests.ttcn
+++ b/hnbgw/HNBGW_Tests.ttcn
@@ -612,7 +612,15 @@
sAC := int2oct(pars.hnb.sac, 2),
iE_Extensions := omit
}
- var octetstring nas := f_rnd_octstring(10);
+ var octetstring nas;
+ if (pars.separate_sccp_cr) {
+ /* SCCP CR has a payload length limit of 130 bytes. To trigger this limit, the RANAP + NAS PDU has to be
+ * > 130 bytes. It doesn't need to be 131 bytes in the NAS PDU alone, but let's just make it definitely
+ * large enough. */
+ nas := f_rnd_octstring(131);
+ } else {
+ nas := f_rnd_octstring(10);
+ }
var IuSignallingConnectionIdentifier sigc_id := int2bit(f_rnd_int(1000), 24);
var GlobalRNC_ID grnc_id := {
pLMNidentity := lai.pLMNidentity,