https://projects.osmocom.org/
https://projects.osmocom.org/favicon.ico?1664741409
2020-10-11T20:05:19Z
Open Source Mobile Communications
OsmoPCU - Bug #4802: TTCN3-centos-pcu-test-sns / ttcn3-pcu-tests-sns failing completely
https://projects.osmocom.org/issues/4802?journal_id=19883
2020-10-11T20:05:19Z
fixeria
<ul></ul><pre>
MTC@DELL: Test case TC_sns_po_size_success finished. Verdict: fail reason: Received unexpected NS: { connId := 1, remName := "127.0.0.1", remPort := 22000, locName := "127.0.0.1", locPort := 23000, msg := { pDU_NS_Reset := { nsPduType := '02'O, causeNS := { iEI := '00'O, ext := '1'B, lengthIndicator := { length1 := 1 }, cause := '01'O }, nS_VCI := { iEI := '01'O, ext := '1'B, lengthIndicator := { length1 := 2 }, nS_VCI := '04D2'O }, nSEI_NS := { iEI := '04'O, ext := '1'B, lengthIndicator := { length1 := 2 }, nSEI := '04D2'O } } } }
</pre>
OsmoPCU - Bug #4802: TTCN3-centos-pcu-test-sns / ttcn3-pcu-tests-sns failing completely
https://projects.osmocom.org/issues/4802?journal_id=19884
2020-10-11T20:15:41Z
fixeria
<ul></ul><p>So we're getting unexpected RESET:</p>
<pre>
unexpected NS: {
connId := 1,
remName := "127.0.0.1",
remPort := 22000,
locName := "127.0.0.1",
locPort := 23000,
msg := {
pDU_NS_Reset := {
nsPduType := '02'O,
causeNS := {
iEI := '00'O,
ext := '1'B,
lengthIndicator := { length1 := 1 },
cause := '01'O
},
nS_VCI := {
iEI := '01'O,
ext := '1'B,
lengthIndicator := { length1 := 2 },
nS_VCI := '04D2'O
},
nSEI_NS := {
iEI := '04'O,
ext := '1'B,
lengthIndicator := { length1 := 2 },
nSEI := '04D2'O
}
}
}
}
vs expected {
connId := ?,
remName := ?,
remPort := ?,
locName := ?,
locPort := ?,
msg := {
pDU_SNS_Size := {
nsPduType := '12'O,
nSEI_NS := {
iEI := '04'O,
ext := '1'B,
lengthIndicator := { length1 := 2 },
nSEI := '04D2'O
},
resetFlag := {
iEI := '0A'O ("\n"),
resetBIT := '1'B,
spare := '0000000'B
},
maxNumberOfNSVCs := {
iEI := '07'O ("\a"),
maxNumberOfNSVCs := '0008'O
},
numberOfIP4_Endpoints := {
iEI := '08'O ("\b"),
numberOfIP_Endpoints := '0004'O
},
numberOfIP6_Endpoints := omit
}
}
}
</pre>
OsmoPCU - Bug #4802: TTCN3-centos-pcu-test-sns / ttcn3-pcu-tests-sns failing completely
https://projects.osmocom.org/issues/4802?journal_id=19891
2020-10-12T10:52:42Z
laforge
<ul></ul><p>The NS-RESET procedure is not applicable to a Gb interface that uses IP-SNS. So either there's a b ug in the configuration, or it's a bug in the NS2 code. <a class="user active" href="https://projects.osmocom.org/users/1741">lynxis</a>, feel free to chime in. Thanks!</p>
OsmoPCU - Bug #4802: TTCN3-centos-pcu-test-sns / ttcn3-pcu-tests-sns failing completely
https://projects.osmocom.org/issues/4802?journal_id=19904
2020-10-12T16:48:31Z
lynxis
<ul></ul><p>strange. I've ran the SNS test cases on debian and they succeed.</p>
OsmoPCU - Bug #4802: TTCN3-centos-pcu-test-sns / ttcn3-pcu-tests-sns failing completely
https://projects.osmocom.org/issues/4802?journal_id=20097
2020-10-24T11:42:43Z
fixeria
<ul></ul><p>Kind reminder: TTCN3-centos-pcu-test-sns [1] is ok, but ttcn3-pcu-test-sns-latest [2] still fails (15 builds in a row, since 581).</p>
<p>[1] <a class="external" href="https://jenkins.osmocom.org/jenkins/view/TTCN3-centos/job/TTCN3-centos-pcu-test-sns/">https://jenkins.osmocom.org/jenkins/view/TTCN3-centos/job/TTCN3-centos-pcu-test-sns/</a><br />[2] <a class="external" href="https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-pcu-test-sns-latest/">https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-pcu-test-sns-latest/</a></p>
OsmoPCU - Bug #4802: TTCN3-centos-pcu-test-sns / ttcn3-pcu-tests-sns failing completely
https://projects.osmocom.org/issues/4802?journal_id=20107
2020-10-25T04:44:48Z
lynxis
<ul></ul><p>The TTCN3 testcase 1c1u is doing SNS Config with<br />pcu 23000 <-> 23001 sgsn<br /> 23000 <-> 23002 sgsn</p>
<p>But now the ttcn is sending a NS Alive for 23000 <> 23000 which isn't configured. The PCU answer with invalid status.</p>
OsmoPCU - Bug #4802: TTCN3-centos-pcu-test-sns / ttcn3-pcu-tests-sns failing completely
https://projects.osmocom.org/issues/4802?journal_id=20108
2020-10-25T04:46:14Z
lynxis
<ul></ul><p><a class="user active" href="https://projects.osmocom.org/users/30187">pespin</a> did you created a release already with the ns2 code?</p>
OsmoPCU - Bug #4802: TTCN3-centos-pcu-test-sns / ttcn3-pcu-tests-sns failing completely
https://projects.osmocom.org/issues/4802?journal_id=20120
2020-10-26T00:05:09Z
lynxis
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> changed from <i>pespin</i> to <i>lynxis</i></li></ul>
OsmoPCU - Bug #4802: TTCN3-centos-pcu-test-sns / ttcn3-pcu-tests-sns failing completely
https://projects.osmocom.org/issues/4802?journal_id=20121
2020-10-26T01:03:07Z
lynxis
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>ttcn3-pcu-tests-sns recoved (still some smaller issues, both debian/centos)</p>
<p>ttcn3-pcu-tests-sns-latest still failing, which is correct!<br />The ttcn test cases got improved. It's now forbidden to attach the cell id on signalling BVC Resets (as the spec says so).</p>
OsmoPCU - Bug #4802: TTCN3-centos-pcu-test-sns / ttcn3-pcu-tests-sns failing completely
https://projects.osmocom.org/issues/4802?journal_id=20122
2020-10-26T01:03:22Z
lynxis
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul>
OsmoPCU - Bug #4802: TTCN3-centos-pcu-test-sns / ttcn3-pcu-tests-sns failing completely
https://projects.osmocom.org/issues/4802?journal_id=20126
2020-10-26T09:29:16Z
pespin
<ul></ul><p>lynxis wrote:</p>
<blockquote>
<p><a class="user active" href="https://projects.osmocom.org/users/30187">pespin</a> did you created a release already with the ns2 code?</p>
</blockquote>
<p>No</p>