Started by an SCM changeBRANCHmasterEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.org laforge@gnumonks.org00002210552210551.00814281425138997eeaff2ff42ec47fcd625ee7dbc3fdbc7ebaecb97eeaff2ff42ec47fcd625ee7dbc3fdbc7ebaecborigin/master97eeaff2ff42ec47fcd625ee7dbc3fdbc7ebaecb97eeaff2ff42ec47fcd625ee7dbc3fdbc7ebaecborigin/master344228284fb053dbfbc70438684cf47b65d12691421878284fb053dbfbc70438684cf47b65d1269142187refs/remotes/origin/master8284fb053dbfbc70438684cf47b65d12691421878284fb053dbfbc70438684cf47b65d1269142187refs/remotes/origin/master97eeaff2ff42ec47fcd625ee7dbc3fdbc7ebaecb97eeaff2ff42ec47fcd625ee7dbc3fdbc7ebaecborigin/masterhttps://gerrit.osmocom.org/osmo-mscfalse#51389221055230504master-osmo-msc #5138951389falsefalse5138990075SUCCESS1776337570108https://jenkins.osmocom.org/jenkins/job/master-osmo-msc/51389/tests/msc_vlr/msc_vlr_tests.ctests/msc_vlr/msc_vlr_test_call.ctests/msc_vlr/msc_vlr_test_gsm_ciph.csrc/libmsc/msc_a.ctests/msc_vlr/msc_vlr_test_authen_reuse.ctests/msc_vlr/msc_vlr_test_umts_authen.csrc/libmsc/gsm_04_08_cc.csrc/libmsc/msc_vgcs.ctests/msc_vlr/msc_vlr_tests.hf202d079d032544aa047e343d6abf87abd066ddf1776088413000https://jenkins.osmocom.org/jenkins/user/aeversbergAndreas Eversbergaeversberg@sysmocom.deCheck for protocol extension bit in message type at a central location Bits 8 and 7 of message type can be used as sequence number or have specific default values. The added check will verify the bits according to the prococol descriptor and Release version. The Rules for these bits are described in GSM TS 124.007, clause 11.2.3.2.1 for Release <= 98 and 11.2.3.2.2 for Release >= 99. There is also no need to clear bit 7 in message type for these protocols, as it is done already in gsm48_hdr_msg_type(). Some unit tests fail without fixes that are included in this patch. Change-Id: Iae41bc6a2e9fd85583509b6c6154dd5a935fb5df 2026-04-13 15:53:33 +0200f202d079d032544aa047e343d6abf87abd066ddfCheck for protocol extension bit in message type at a central locationeditsrc/libmsc/gsm_04_08_cc.ceditsrc/libmsc/msc_vgcs.cedittests/msc_vlr/msc_vlr_tests.cedittests/msc_vlr/msc_vlr_tests.heditsrc/libmsc/msc_a.cedittests/msc_vlr/msc_vlr_test_gsm_ciph.cedittests/msc_vlr/msc_vlr_test_authen_reuse.cedittests/msc_vlr/msc_vlr_test_umts_authen.cedittests/msc_vlr/msc_vlr_test_call.ctests/msc_vlr/msc_vlr_test_call.ctests/msc_vlr/msc_vlr_tests.htests/msc_vlr/msc_vlr_test_gsm_ciph.ctests/msc_vlr/msc_vlr_test_umts_authen.ctests/msc_vlr/msc_vlr_test_authen_reuse.c97eeaff2ff42ec47fcd625ee7dbc3fdbc7ebaecb1776247095000https://jenkins.osmocom.org/jenkins/user/aeversbergAndreas Eversbergaeversberg@sysmocom.deReset 'release_99' flag in test cases at comment_start() Rather than resetting release_99 flag in every test case that did set it, do it in comment_start(). Change-Id: I55a49dd24a5df6ee8e28fa6b410988e82d10c554 2026-04-15 11:58:15 +020097eeaff2ff42ec47fcd625ee7dbc3fdbc7ebaecbReset 'release_99' flag in test cases at comment_start()edittests/msc_vlr/msc_vlr_test_umts_authen.cedittests/msc_vlr/msc_vlr_test_call.cedittests/msc_vlr/msc_vlr_test_gsm_ciph.cedittests/msc_vlr/msc_vlr_tests.hedittests/msc_vlr/msc_vlr_test_authen_reuse.cgithttps://jenkins.osmocom.org/jenkins/user/aeversbergAndreas Eversberg51389https://jenkins.osmocom.org/jenkins/job/master-osmo-msc/IU=--disable-iu,WITH_MANUALS=0,a3=default,a4=default,label=osmocom-master/51389/51389https://jenkins.osmocom.org/jenkins/job/master-osmo-msc/IU=--enable-iu,WITH_MANUALS=1,a3=default,a4=default,label=osmocom-master/51389/