Started by upstream project "gerrit-libosmo-sigtran" build number 943943gerrit-libosmo-sigtranjob/gerrit-libosmo-sigtran/COMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42536GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION605100db83691f2efd8fac71d67ec63446b2ab5eGERRIT_PATCHSET_UPLOADER_NAMEpespinGERRIT_PORT29418GERRIT_PROJECTlibosmo-sigtranGERRIT_REFSPECrefs/changes/36/42536/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/libosmo-sigtranPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-libosmo-sigtran/943/PROJECT_NAMElibosmo-sigtranBRANCH_CImaster000071647716471.07101710107874870997099210106387dd31af6c606c7e6e1a2638a3e587614d00106387dd31af6c606c7e6e1a2638a3e587614d0pespin/2.0.00106387dd31af6c606c7e6e1a2638a3e587614d00106387dd31af6c606c7e6e1a2638a3e587614d0pespin/2.0.0607846fcd7a3d8fc68490971c8c67489ee8be84dbf1846fcd7a3d8fc68490971c8c67489ee8be84dbf1osmith/2.1.2846fcd7a3d8fc68490971c8c67489ee8be84dbf1846fcd7a3d8fc68490971c8c67489ee8be84dbf1osmith/2.1.2618fc0a9591a449a0d346eb62003e4e150215f95deffc0a9591a449a0d346eb62003e4e150215f95defosmith/2.1.3fc0a9591a449a0d346eb62003e4e150215f95deffc0a9591a449a0d346eb62003e4e150215f95defosmith/2.1.3434d2b9b7e0a826ce789952ab87758815041a1aa302d2b9b7e0a826ce789952ab87758815041a1aa302pespin/rel-2.1.0d2b9b7e0a826ce789952ab87758815041a1aa302d2b9b7e0a826ce789952ab87758815041a1aa302pespin/rel-2.1.0941605100db83691f2efd8fac71d67ec63446b2ab5e605100db83691f2efd8fac71d67ec63446b2ab5emaster605100db83691f2efd8fac71d67ec63446b2ab5e605100db83691f2efd8fac71d67ec63446b2ab5emaster605100db83691f2efd8fac71d67ec63446b2ab5e605100db83691f2efd8fac71d67ec63446b2ab5emasterssh://jenkins@gerrit.osmocom.org:29418/libosmo-sigtranhttps://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-libosmo-sigtran-build/941/artifacthttps://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-libosmo-sigtran-build/changeshttps://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-libosmo-sigtran-build/941/https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-libosmo-sigtran-build/941/testReportfalse#94171647112755gerrit-libosmo-sigtran-build #941941falsefalse94175417SUCCESS1774872799681https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-libosmo-sigtran-build/941/src/m3ua.c605100db83691f2efd8fac71d67ec63446b2ab5e1774872684000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dem3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalid Routing Context As per RFC4666 3.8.1: """ The "Invalid Routing Context" error is sent if a message is received from a peer with an invalid (unconfigured) Routing Context value. For this error, the invalid Routing Context(s) MUST be included in the Error message." """ Hence add the originating Routing Context IE so the error message can be further originated. For the same reason, also add the Diagnostic Information for the specific cases in the switch statement, and make them more robust about possible null pointer dereference. Change-Id: If821109701e315d17f5334c680670ea6c7bce3bd 2026-03-30 14:11:24 +0200605100db83691f2efd8fac71d67ec63446b2ab5em3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalideditsrc/m3ua.cgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin PedrolpespinCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42536GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION605100db83691f2efd8fac71d67ec63446b2ab5eGERRIT_PATCHSET_UPLOADER_NAMEpespinGERRIT_PORT29418GERRIT_PROJECTlibosmo-sigtranGERRIT_REFSPECrefs/changes/36/42536/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/libosmo-sigtranPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-libosmo-sigtran/943/PROJECT_NAMElibosmo-sigtranBRANCH_CImasterStarted by upstream project "gerrit-libosmo-sigtran-build" build number 941941gerrit-libosmo-sigtran-buildjob/gerrit-libosmo-sigtran-build/000047889478891.0000941605100db83691f2efd8fac71d67ec63446b2ab5e605100db83691f2efd8fac71d67ec63446b2ab5emaster605100db83691f2efd8fac71d67ec63446b2ab5e605100db83691f2efd8fac71d67ec63446b2ab5emaster605100db83691f2efd8fac71d67ec63446b2ab5e605100db83691f2efd8fac71d67ec63446b2ab5emasterssh://jenkins@gerrit.osmocom.org:29418/libosmo-sigtranfalse#9414788953792gerrit-libosmo-sigtran-build » WITH_MANUALS=0,WITH_TCAP=0,a3=default,a4=default,osmocom-gerrit #941941falsefalse94175422SUCCESS1774872799681https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-libosmo-sigtran-build/WITH_MANUALS=0,WITH_TCAP=0,a3=default,a4=default,label=osmocom-gerrit/941/build4-deb12build-ansiblesrc/m3ua.c605100db83691f2efd8fac71d67ec63446b2ab5e1774872684000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dem3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalid Routing Context As per RFC4666 3.8.1: """ The "Invalid Routing Context" error is sent if a message is received from a peer with an invalid (unconfigured) Routing Context value. For this error, the invalid Routing Context(s) MUST be included in the Error message." """ Hence add the originating Routing Context IE so the error message can be further originated. For the same reason, also add the Diagnostic Information for the specific cases in the switch statement, and make them more robust about possible null pointer dereference. Change-Id: If821109701e315d17f5334c680670ea6c7bce3bd 2026-03-30 14:11:24 +0200605100db83691f2efd8fac71d67ec63446b2ab5em3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalideditsrc/m3ua.cgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin PedrolCOMMENT_TYPEDISTROGERRIT_BRANCHmasterGERRIT_CHANGE_NUMBER42536GERRIT_HOSTgerrit.osmocom.orgGERRIT_PATCHSET_NUMBER1GERRIT_PATCHSET_REVISION605100db83691f2efd8fac71d67ec63446b2ab5eGERRIT_PATCHSET_UPLOADER_NAMEpespinGERRIT_PORT29418GERRIT_PROJECTlibosmo-sigtranGERRIT_REFSPECrefs/changes/36/42536/1GERRIT_REPO_URLssh://jenkins@gerrit.osmocom.org:29418/libosmo-sigtranPIPELINE_BUILD_URLhttps://jenkins.osmocom.org/jenkins/job/gerrit-libosmo-sigtran/943/PROJECT_NAMElibosmo-sigtranBRANCH_CImasterStarted by upstream project "gerrit-libosmo-sigtran-build" build number 941941gerrit-libosmo-sigtran-buildjob/gerrit-libosmo-sigtran-build/000069889698891.0000941605100db83691f2efd8fac71d67ec63446b2ab5e605100db83691f2efd8fac71d67ec63446b2ab5emaster605100db83691f2efd8fac71d67ec63446b2ab5e605100db83691f2efd8fac71d67ec63446b2ab5emaster605100db83691f2efd8fac71d67ec63446b2ab5e605100db83691f2efd8fac71d67ec63446b2ab5emasterssh://jenkins@gerrit.osmocom.org:29418/libosmo-sigtranfalse#9416988970473gerrit-libosmo-sigtran-build » WITH_MANUALS=1,WITH_TCAP=1,a3=default,a4=default,osmocom-gerrit #941941falsefalse94175423SUCCESS1774872799681https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/gerrit-libosmo-sigtran-build/WITH_MANUALS=1,WITH_TCAP=1,a3=default,a4=default,label=osmocom-gerrit/941/build5-deb12build-ansiblesrc/m3ua.c605100db83691f2efd8fac71d67ec63446b2ab5e1774872684000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.dem3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalid Routing Context As per RFC4666 3.8.1: """ The "Invalid Routing Context" error is sent if a message is received from a peer with an invalid (unconfigured) Routing Context value. For this error, the invalid Routing Context(s) MUST be included in the Error message." """ Hence add the originating Routing Context IE so the error message can be further originated. For the same reason, also add the Diagnostic Information for the specific cases in the switch statement, and make them more robust about possible null pointer dereference. Change-Id: If821109701e315d17f5334c680670ea6c7bce3bd 2026-03-30 14:11:24 +0200605100db83691f2efd8fac71d67ec63446b2ab5em3ua: m3ua_gen_error_msg(): include Routing Context IE in cause Invalideditsrc/m3ua.cgithttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol