Started by an SCM changeBRANCHmasterEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.org laforge@gnumonks.org0000106414610641461.00917091702045e5f56dd35f1b2347a59f88b401b59997798fff67e5f56dd35f1b2347a59f88b401b59997798fff67refs/remotes/origin/pmaier/fixgre5f56dd35f1b2347a59f88b401b59997798fff67e5f56dd35f1b2347a59f88b401b59997798fff67refs/remotes/origin/pmaier/fixgr2067969f9c0e4bcb3cbf46be3a592315aa8a9a39e807969f9c0e4bcb3cbf46be3a592315aa8a9a39e807origin/master969f9c0e4bcb3cbf46be3a592315aa8a9a39e807969f9c0e4bcb3cbf46be3a592315aa8a9a39e807origin/master13208f289234f74045496c3752bf1bb9397302f3e9128f289234f74045496c3752bf1bb9397302f3e912refs/remotes/origin/pmaier/ara-m8f289234f74045496c3752bf1bb9397302f3e9128f289234f74045496c3752bf1bb9397302f3e912refs/remotes/origin/pmaier/ara-m13533d815859830197b9c55e0a49a1bd2532f71285e13d815859830197b9c55e0a49a1bd2532f71285e1refs/remotes/origin/pmaier/keepfiles3d815859830197b9c55e0a49a1bd2532f71285e13d815859830197b9c55e0a49a1bd2532f71285e1refs/remotes/origin/pmaier/keepfiles1421568e8ae9b817ec2473907bfdd30870410890ffb0568e8ae9b817ec2473907bfdd30870410890ffb0refs/remotes/origin/pmaier/fixapdu568e8ae9b817ec2473907bfdd30870410890ffb0568e8ae9b817ec2473907bfdd30870410890ffb0refs/remotes/origin/pmaier/fixapdu14676a555ac5ccad9ee2cae5e0ba247990f824f8e9b66a555ac5ccad9ee2cae5e0ba247990f824f8e9b6refs/remotes/origin/pmaier/aramtest6a555ac5ccad9ee2cae5e0ba247990f824f8e9b66a555ac5ccad9ee2cae5e0ba247990f824f8e9b6refs/remotes/origin/pmaier/aramtest1816e4ea1c997348370ba1d7415bfd926ac873b58c87e4ea1c997348370ba1d7415bfd926ac873b58c87refs/remotes/origin/osmith/wipe4ea1c997348370ba1d7415bfd926ac873b58c87e4ea1c997348370ba1d7415bfd926ac873b58c87refs/remotes/origin/osmith/wip2022f57f047c627392c40fbe349b1a73ccebe05dc005f57f047c627392c40fbe349b1a73ccebe05dc005refs/remotes/origin/pmaier/otatestf57f047c627392c40fbe349b1a73ccebe05dc005f57f047c627392c40fbe349b1a73ccebe05dc005refs/remotes/origin/pmaier/otatest4024f888a0414101dee4f20aa12579491fcc71707b34f888a0414101dee4f20aa12579491fcc71707b3refs/remotes/origin/master4f888a0414101dee4f20aa12579491fcc71707b34f888a0414101dee4f20aa12579491fcc71707b3refs/remotes/origin/master969f9c0e4bcb3cbf46be3a592315aa8a9a39e807969f9c0e4bcb3cbf46be3a592315aa8a9a39e807origin/masterhttps://gerrit.osmocom.org/pysimfalse#206710641461054637master-pysim #20672067falsefalse206771040SUCCESS1774461909950https://jenkins.osmocom.org/jenkins/view/registry/job/master-pysim/2067/pySim/ts_51_011.py969f9c0e4bcb3cbf46be3a592315aa8a9a39e8071774449296000https://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.depmaier@sysmocom.depySim/EF.SMSP: fix encoding of TP-Destination Address The TP-Destination Address in EF.SMSP uses the same encoding as the TS-Service Centre Address field. However, even though the encoding of both fields looks almost identical, it actually isn't. The TS-Service Centre Address field encodes the length field as octets required for the call_number + one octet for ton_npi. (see also: 3GPP TS 24.011, section 8.2.5.2) The TP-Destination Address uses the number of digits of the call_number directly in the length field. (see also: 3GPP TS 23.040, section 9.1.2.5) Related: SYS#7765 Change-Id: I55c123c9e244e5a6e71a0348f5d476ef03e618e8 2026-03-25 15:34:56 +0100969f9c0e4bcb3cbf46be3a592315aa8a9a39e807pySim/EF.SMSP: fix encoding of TP-Destination AddresseditpySim/ts_51_011.pygithttps://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.de2067https://jenkins.osmocom.org/jenkins/view/registry/job/master-pysim/JOB_TYPE=docs,a1=default,a3=default,a4=default,label=osmocom-master/2067/2067https://jenkins.osmocom.org/jenkins/view/registry/job/master-pysim/JOB_TYPE=pylint,a1=default,a3=default,a4=default,label=osmocom-master/2067/2067https://jenkins.osmocom.org/jenkins/view/registry/job/master-pysim/JOB_TYPE=test,a1=default,a3=default,a4=default,label=simtester/2067/