pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/28168 )
Change subject: ggsn: TC_act_deact_retrans_duplicate: Fix case where initial seq_nr is 65535
......................................................................
ggsn: TC_act_deact_retrans_duplicate: Fix case where initial seq_nr is 65535
Change-Id: I2a7a399cf962311aaf7270260cb2e4e00e5a676a
---
M ggsn_tests/GGSN_Tests.ttcn
1 file changed, 5 insertions(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/68/28168/1
diff --git a/ggsn_tests/GGSN_Tests.ttcn b/ggsn_tests/GGSN_Tests.ttcn
index 3993ad6..358d756 100644
--- a/ggsn_tests/GGSN_Tests.ttcn
+++ b/ggsn_tests/GGSN_Tests.ttcn
@@ -2096,7 +2096,11 @@
/* g_c_seq_nr was increased during f_pdp_ctx_del(), we want a
duplicate. If it was not a duplicate, osmo-ggsn would answer
with a failure since that PDP ctx was already deleted. */
- g_c_seq_nr := g_c_seq_nr - 1;
+ if (g_c_seq_nr == 0) {
+ g_c_seq_nr := 65535;
+ } else {
+ g_c_seq_nr := g_c_seq_nr - 1;
+ }
f_pdp_ctx_del(ctx, '1'B, expect_diameter := false);
/* Now send a new pdp ctx del (increased seqnum). It should fail with cause "non-existent": */
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/28168
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: I2a7a399cf962311aaf7270260cb2e4e00e5a676a
Gerrit-Change-Number: 28168
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: newchange
Attention is currently required from: iedemam, neels.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/28165 )
Change subject: stats: new trackers for lchan life duration (v2)
......................................................................
Patch Set 1:
(1 comment)
File src/osmo-bsc/bts.c:
https://gerrit.osmocom.org/c/osmo-bsc/+/28165/comment/85bb77b3_81b5d41e
PS1, Line 768: if (!lchan->activate.concluded)
> I wonder: you are probably then not counting last interval since .concluded was set to true.
Nevermind this one, I was confused. I think the comment is actually confusing. It's not "inactive lchans" but "lchans not yet active" or "lchans in process of being activated" right?
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/28165
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Ie3771233ecbd4bc24a24fb22c1064a18e7b8b2b0
Gerrit-Change-Number: 28165
Gerrit-PatchSet: 1
Gerrit-Owner: iedemam <michael(a)kapsulate.com>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: iedemam <michael(a)kapsulate.com>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 19 May 2022 20:08:58 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: iedemam, neels.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/28165 )
Change subject: stats: new trackers for lchan life duration (v2)
......................................................................
Patch Set 1:
(4 comments)
Patchset:
PS1:
It may make sense to do some profiling how much time it takes to run the whole callback function for all the BTSs, to see if it makes more sense to split the timer per BTS. If it takes a lot of time it may block the osmo-bsc from forwarding stuff.
File src/osmo-bsc/bts.c:
https://gerrit.osmocom.org/c/osmo-bsc/+/28165/comment/f0986220_0eed4f43
PS1, Line 768: if (!lchan->activate.concluded)
I wonder: you are probably then not counting last interval since .concluded was set to true.
https://gerrit.osmocom.org/c/osmo-bsc/+/28165/comment/3884051f_f6fb8022
PS1, Line 772: timespecsub(&now, &lchan->active_stored, &elapsed);
what if it's first time? active_stored is {0,0} ?
EDIT: I see it's stored in lchan_on_fully_established(). Maybe write a comment about that here.
File src/osmo-bsc/bts_trx_vty.c:
https://gerrit.osmocom.org/c/osmo-bsc/+/28165/comment/b914c556_f60124f4
PS1, Line 574: vty_out(vty, " Activated %s seconds ago%s",
"Active for: %d seconds%s" would probably fit more in existing print format.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/28165
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Ie3771233ecbd4bc24a24fb22c1064a18e7b8b2b0
Gerrit-Change-Number: 28165
Gerrit-PatchSet: 1
Gerrit-Owner: iedemam <michael(a)kapsulate.com>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: iedemam <michael(a)kapsulate.com>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 19 May 2022 20:07:35 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: pespin.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/libosmocore/+/28166
to look at the new patch set (#2).
Change subject: coding: fix decoding of AHS_SID_UPDATE frames (BER ~50%)
......................................................................
coding: fix decoding of AHS_SID_UPDATE frames (BER ~50%)
As was demonstrated in [1], there is a TCH/AHS specific problem in
libosmocoding causing unexpected BER ~50% in decoded AHS_SID_UPDATE
frames. The reason is that A[H]S_SID_UPDATE employs quite tricky
interleaving algorithm, which is different from the algorithm used
by normal TCH/AHS speech frames or A[F]S_SID_UPDATE frames.
+---------+--------------------+---------+--------------------+
| in-band | SID marker | in-band | coded data |
+---------+--------------------+---------+--------------------+
| 16 bits | 212 bits | 16 bits | 212 bits |
* AHS_SID_UPDATE is interleaved over 456 bits (4 Normal Bursts):
** both halves (228 bits each) contain coded in-band data (16 bits),
** the first half contains the identification marker (212 bits),
** the second half contains the encoded SID_UPDATE (212 bits).
The first half (containing the SID marker) is carried by even bits
of the first two bursts and odd bits of the last two bursts. The
marker allows us to detect that it's an AHS_SID_UPDATE.
The other half is carried by even bits of the last two bursts and
odd bits of the first two bursts. However, the current code does
not use odd bits of the first two bursts at all, so buffer cB[]
in gsm0503_tch_ahs_decode_dtx() contains only 114 out of 228 bits.
This patch changes the logic, so that gsm0503_tch_ahs_decode_dtx()
would not split AHS_SID_UPDATE onto two frames anymore like its
TCH/AFS equivalent does, but attempt to deinterleave the second
half and attempt to decode the payload immediately.
Change-Id: I8686d895e96fa0e606c1898b6574cc80a8f46983
Related: [1] I434157e2091a306c039123cea08d84bd8533c937
Related: SYS#5853
---
M src/coding/gsm0503_coding.c
M tests/dtx/dtx_gsm0503_test.ok
2 files changed, 25 insertions(+), 15 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/libosmocore refs/changes/66/28166/2
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/28166
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I8686d895e96fa0e606c1898b6574cc80a8f46983
Gerrit-Change-Number: 28166
Gerrit-PatchSet: 2
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: newpatchset
Attention is currently required from: pespin.
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/28166 )
Change subject: coding: fix decoding of AHS_SID_UPDATE frames (BER ~50%)
......................................................................
Patch Set 1:
(2 comments)
File src/coding/gsm0503_coding.c:
https://gerrit.osmocom.org/c/libosmocore/+/28166/comment/b037748f_a040de77
PS1, Line 2685: case AMR_OTHER:
> so no more "AMR_OTHER" case now? It goes into default?
Yes, it goes to default. As stated in the commit message, we don't split up detection and decoding of SID_UPDATE onto two frames anymore. This is also why I remove 'dtx_prev' above.
File tests/dtx/dtx_gsm0503_test.ok:
https://gerrit.osmocom.org/c/libosmocore/+/28166/comment/a7c952c2_41323e5f
PS1, Line 23: ==> gsm0503_tch_ahs_decode_dtx() yields 'AMR_OTHER (audio)' (rc=-1, BER 111/212)
> Shouldn't this be BER 212/212?
Not really. gsm0503_tch_ahs_decode_dtx() internally matches deinterleaved bits against several bit-sequences (markers), so in this case some bits matched one of the markers, but only part of it.
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/28166
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I8686d895e96fa0e606c1898b6574cc80a8f46983
Gerrit-Change-Number: 28166
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 19 May 2022 19:56:52 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: dexter.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/pysim/+/28163 )
Change subject: pySim-shell: make APDU command available on the lowest level
......................................................................
Patch Set 1:
(2 comments)
File pySim-shell.py:
https://gerrit.osmocom.org/c/pysim/+/28163/comment/4f6444e7_c5dc7b71
PS1, Line 227: if (self.card):
I think in python you don't usually put parenthesis around a single condition in an if statement, see "if new == True:" above.
https://gerrit.osmocom.org/c/pysim/+/28163/comment/684a6018_275b38cd
PS1, Line 257: if (data):
same here. "if data:" should do the trick.
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/28163
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: I601b8f17bd6af41dcbf7bbb53c75903dd46beee7
Gerrit-Change-Number: 28163
Gerrit-PatchSet: 1
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 19 May 2022 19:54:05 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment