Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/39881?usp=email
to look at the new patch set (#3).
The following approvals got outdated and were removed:
Verified+1 by Jenkins Builder
Change subject: s1gw: ConnHdlr: allow passing {MME,ENB}-UE-S1AP-ID
......................................................................
s1gw: ConnHdlr: allow passing {MME,ENB}-UE-S1AP-ID
This is needed for follow-up UEMux testcases, in which we spawn
multiple virtual UEs with unique {MME,ENB}-UE-S1AP-IDs.
Change-Id: Ife37c77cff348cdfbde191dbad6da816e68ca941
Related: SYS#7288
---
M s1gw/S1GW_ConnHdlr.ttcn
M s1gw/S1GW_Tests.ttcn
2 files changed, 177 insertions(+), 96 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/81/39881/3
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/39881?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: Ife37c77cff348cdfbde191dbad6da816e68ca941
Gerrit-Change-Number: 39881
Gerrit-PatchSet: 3
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/39885?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Verified+1 by Jenkins Builder
Change subject: s1gw: add UEMux TCs for INITIAL CTX SETUP and UE CTX RELEASE
......................................................................
s1gw: add UEMux TCs for INITIAL CTX SETUP and UE CTX RELEASE
Change-Id: I811904e50dd6f0a05b0bb6babebe5b4690e2d3ec
Related: SYS#7288
---
M s1gw/S1GW_Tests.ttcn
M s1gw/S1GW_UEMux.ttcn
M s1gw/expected-results.xml
3 files changed, 127 insertions(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/85/39885/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/39885?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: I811904e50dd6f0a05b0bb6babebe5b4690e2d3ec
Gerrit-Change-Number: 39885
Gerrit-PatchSet: 2
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
fixeria has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/39881?usp=email )
Change subject: s1gw: ConnHdlr: allow passing {MME,ENB}-UE-S1AP-ID
......................................................................
Set Ready For Review
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/39881?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: Ife37c77cff348cdfbde191dbad6da816e68ca941
Gerrit-Change-Number: 39881
Gerrit-PatchSet: 2
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Comment-Date: Mon, 31 Mar 2025 19:56:02 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Attention is currently required from: fixeria, laforge, pespin.
Hello Jenkins Builder, laforge, pespin,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/39882?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Code-Review+1 by laforge, Code-Review+1 by pespin, Verified+1 by Jenkins Builder
Change subject: s1gw: add UEMux TCs for E-RAB SETUP and RELEASE
......................................................................
s1gw: add UEMux TCs for E-RAB SETUP and RELEASE
Change-Id: Ia4583f82a768ca3d185aad596ce8ec9bbd37ad32
Related: SYS#7288
---
M s1gw/S1GW_Tests.ttcn
M s1gw/S1GW_UEMux.ttcn
M s1gw/expected-results.xml
3 files changed, 132 insertions(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/82/39882/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/39882?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: Ia4583f82a768ca3d185aad596ce8ec9bbd37ad32
Gerrit-Change-Number: 39882
Gerrit-PatchSet: 2
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: fixeria, pespin.
Hello Jenkins Builder, pespin,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/erlang/osmo_dia2gsup/+/39884?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Code-Review+1 by pespin
Change subject: gsup_client: disable gen_server event tracing
......................................................................
gsup_client: disable gen_server event tracing
Even with the logging level set to info, we're still seeing this:
*DBG* gsup_client got call ...
*DBG* gsup_client sent ...
Those are messages printed by the gen_server module itself, and
as it turns out we explicitly enable printing them by passing
{debug, [trace]} to gen_server:start_link/3.
This kind of logging is way too verbose and not useful for a
regular user, so let's disable event tracing.
Change-Id: I9d0ca595fd6aab2e0e16944e31dde02f5783c772
Related: SYS#7415
---
M src/gsup_client.erl
M src/osmo_dia2gsup_sup.erl
2 files changed, 2 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/erlang/osmo_dia2gsup refs/changes/84/39884/2
--
To view, visit https://gerrit.osmocom.org/c/erlang/osmo_dia2gsup/+/39884?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: erlang/osmo_dia2gsup
Gerrit-Branch: master
Gerrit-Change-Id: I9d0ca595fd6aab2e0e16944e31dde02f5783c772
Gerrit-Change-Number: 39884
Gerrit-PatchSet: 2
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: laforge, neels, pespin.
falconia has posted comments on this change by falconia. ( https://gerrit.osmocom.org/c/osmo-mgw/+/39869?usp=email )
Change subject: mgw: rtp-patch rfc5993hr: convert to each end's respective format
......................................................................
Patch Set 2:
(6 comments)
Patchset:
PS2:
> and also the BSC has to then be aware of the HR formats in use.
This part would be the biggest difficulty in practice. How would the BSC know which BTS is configured for TS 101 318 vs which is configured for RFC 5993, when it is a vty option in OsmoBTS?
File src/libosmo-mgcp/mgcp_network.c:
https://gerrit.osmocom.org/c/osmo-mgw/+/39869/comment/43c79097_a22c5d4b?usp… :
PS2, Line 691: * consider the full RTP chain of a single call:
> > (my idea so far, can be in a future patch, is to not send any HR payload to a peer until we have r […]
The comment by @laforge@osmocom.org is correct: I also initially thought about sending nothing to all to each peer until that peer sent its own first packet, but then I quickly realized that the result would be no traffic passing at all, ever. Referring to the ASCII art diagram in the detailed comment in my patch, if the policy proposed by @nhofmeyr@sysmocom.de were implemented, each of BSC-MGW-A and BSC-MGW-B would receive packets from BTS-A and BTS-B, but because neither BSC-associated MGW will be the first to send a packet to the CN, neither MSC-MGW-A nor MSC-MGW-B will ever see even one packet.
https://gerrit.osmocom.org/c/osmo-mgw/+/39869/comment/15786ea3_af80d169?usp… :
PS2, Line 698: will always be RFC 5993
> On AoIP, there is no discussion. It is always RFC5993 as that is what (likely, quoting from memory) 3GPP TS 48.103 mandates.
Correct: TS 48.103 is the spec, and it unambiguously specifies RFC 5993 format for HR codec.
https://gerrit.osmocom.org/c/osmo-mgw/+/39869/comment/d7bff7ec_09cde6bb?usp… :
PS2, Line 715: static int rfc5993_hr_convert(struct msgb *msg, struct mgcp_conn_rtp *dst)
> (kind of weird to swap the msgb argument position for no reason)
It is an artifact of how I developed this code in stages. I can flip this argument order in the next patch iteration, no big deal.
https://gerrit.osmocom.org/c/osmo-mgw/+/39869/comment/bc231742_388288f0?usp… :
PS2, Line 1660: strcmp(conn_src->end.cset.codec->subtype_name, "GSM-HR-08") == 0 && conn_src->end.rfc5993_hr_convert) {
> I'd say better split this line into 2.
I originally had it split, but the overzealous linter forced me to join into this longer line! See the diff between patchset 1 and patchset 2, where patchset 1 was rejected (V-1) by the linter.
https://gerrit.osmocom.org/c/osmo-mgw/+/39869/comment/72bff7db_64557059?usp… :
PS2, Line 1661: int rc = examine_rtp_rx_gsmhr(msg, conn_src);
> Is this called always on GSM-HR-08 or only once, until we successfully detected the HR format? ... […]
It is called for every received packet. If we were to perform format detection only on the very first packet, what would happen if a BSC-level handover occurs between two BTS that use (or are configured to use) different HR formats?
--
To view, visit https://gerrit.osmocom.org/c/osmo-mgw/+/39869?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-mgw
Gerrit-Branch: master
Gerrit-Change-Id: I6b446ad83c540fb8b7e1aae24b78c27010212d64
Gerrit-Change-Number: 39869
Gerrit-PatchSet: 2
Gerrit-Owner: falconia <falcon(a)freecalypso.org>
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: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 31 Mar 2025 16:01:55 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de>
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>