Jenkins Builder has posted comments on this change by falconia. ( https://gerrit.osmocom.org/c/osmo-bts/+/42165?usp=email )
Change subject: RTP: implement RTP socket abstraction layer
......................................................................
Patch Set 1:
(1 comment)
File src/common/rtp_abstract.c:
Robot Comment from checkpatch (run ID ):
https://gerrit.osmocom.org/c/osmo-bts/+/42165/comment/508a62bb_3f6c64c4?usp… :
PS1, Line 365: twrtp_stats->rx_rtcp_invalid);
code indent should use tabs where possible
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/42165?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: Ic945f6d753ec7f5c0ac5cecc9f71049464de7e8f
Gerrit-Change-Number: 42165
Gerrit-PatchSet: 1
Gerrit-Owner: falconia <falcon(a)freecalypso.org>
Gerrit-CC: Jenkins Builder
Gerrit-Comment-Date: Sun, 22 Feb 2026 03:44:16 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
falconia has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-bts/+/42167?usp=email )
Change subject: RTP: add vty option for ortp vs twrtp selection
......................................................................
RTP: add vty option for ortp vs twrtp selection
With this patch it finally becomes possible for the user to select
which RTP library should be used: ortp or twrtp. ortp is still
the default for now, in order to not alter behavior for existing
installations until twrtp receives more real world testing by users
beyond the original author. Future patches may change the default
or even remove ortp support altogether - but twrtp should receive
more testing as a user opt-in feature first.
Related: OS#6474
Change-Id: Iff4e3a399250c16ba8fe4cb12e4e22f4c6b346ec
---
M include/osmo-bts/bts.h
M src/common/bts.c
M src/common/lchan.c
M src/common/vty.c
4 files changed, 35 insertions(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-bts refs/changes/67/42167/1
diff --git a/include/osmo-bts/bts.h b/include/osmo-bts/bts.h
index ec13d71..8bd3a83 100644
--- a/include/osmo-bts/bts.h
+++ b/include/osmo-bts/bts.h
@@ -319,6 +319,7 @@
struct llist_head bsc_oml_hosts;
unsigned int rtp_jitter_buf_ms;
bool rtp_jitter_adaptive;
+ bool use_twrtp;
struct osmo_twjit_config *twjit_cfg;
uint16_t rtp_port_range_start;
diff --git a/src/common/bts.c b/src/common/bts.c
index 78ea417..11f57a7 100644
--- a/src/common/bts.c
+++ b/src/common/bts.c
@@ -347,6 +347,23 @@
bts->rtp_priority = -1;
bts->emit_hr_rfc5993 = true;
+ /* At the present point in OsmoBTS evolution the user can select
+ * which RTP library should be used: Belledonne ortp (legacy) or
+ * Themyscira twrtp (integrated into libosmo-netif). There is
+ * a desire to eventually deprecate ortp altogether and support
+ * only Osmocom-native twrtp, but because the two implementations
+ * take drastically different approaches to the hard problem of
+ * converting from an incoming RTP stream to fixed timing for
+ * GSM TCH Tx, the transition should involve extensive testing
+ * by users of the software (GSM network operators), as opposed
+ * to being imposed by developers as a flag day change.
+ * The current default is to use ortp, in order to avoid any
+ * surprise changes in behaviour. It is expected that this
+ * default will change at some point in the future, prior to
+ * full discontinuation of support for ortp.
+ */
+ bts->use_twrtp = false;
+
/* Default (fall-back) MS/BS Power control parameters */
power_ctrl_params_def_reset(&bts->bs_dpc_params, true);
power_ctrl_params_def_reset(&bts->ms_dpc_params, false);
diff --git a/src/common/lchan.c b/src/common/lchan.c
index b5623e3..96d3f35 100644
--- a/src/common/lchan.c
+++ b/src/common/lchan.c
@@ -587,7 +587,7 @@
//if (!payload_type)
lchan->tch.last_fn = LCHAN_FN_DUMMY;
lchan->abis_ip.rtp_socket = rtp_abst_socket_create(lchan->ts->trx,
- false, bts->twjit_cfg);
+ bts->use_twrtp, bts->twjit_cfg);
if (!lchan->abis_ip.rtp_socket) {
LOGPLCHAN(lchan, DRTP, LOGL_ERROR, "IPAC Failed to create RTP/RTCP sockets\n");
diff --git a/src/common/vty.c b/src/common/vty.c
index 0411060..4c35cc7 100644
--- a/src/common/vty.c
+++ b/src/common/vty.c
@@ -424,6 +424,8 @@
vty_out(vty, " rtp ip-dscp %d%s", bts->rtp_ip_dscp, VTY_NEWLINE);
if (bts->rtp_priority != -1)
vty_out(vty, " rtp socket-priority %d%s", bts->rtp_priority, VTY_NEWLINE);
+ vty_out(vty, " rtp library %s%s", bts->use_twrtp ? "twrtp" : "ortp",
+ VTY_NEWLINE);
if (bts->rtp_nogaps_mode)
vty_out(vty, " rtp continuous-streaming%s", VTY_NEWLINE);
vty_out(vty, " %srtp internal-uplink-ecu%s",
@@ -797,6 +799,19 @@
return CMD_SUCCESS;
}
+DEFUN_ATTR(cfg_bts_rtp_library,
+ cfg_bts_rtp_library_cmd,
+ "rtp library (ortp|twrtp)",
+ RTP_STR "RTP library selection\n"
+ "Belledonne ortp\n" "Themyscira twrtp\n",
+ BTS_VTY_ATTR_NEW_LCHAN)
+{
+ struct gsm_bts *bts = vty->index;
+
+ bts->use_twrtp = !strcmp(argv[0], "twrtp");
+ return CMD_SUCCESS;
+}
+
DEFUN(cfg_bts_rtp_cont_stream,
cfg_bts_rtp_cont_stream_cmd,
"rtp continuous-streaming",
@@ -2779,6 +2794,7 @@
install_element(BTS_NODE, &cfg_bts_rtp_port_range_cmd);
install_element(BTS_NODE, &cfg_bts_rtp_ip_dscp_cmd);
install_element(BTS_NODE, &cfg_bts_rtp_priority_cmd);
+ install_element(BTS_NODE, &cfg_bts_rtp_library_cmd);
install_element(BTS_NODE, &cfg_bts_rtp_cont_stream_cmd);
install_element(BTS_NODE, &cfg_bts_no_rtp_cont_stream_cmd);
install_element(BTS_NODE, &cfg_bts_rtp_int_ul_ecu_cmd);
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/42167?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newchange
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: Iff4e3a399250c16ba8fe4cb12e4e22f4c6b346ec
Gerrit-Change-Number: 42167
Gerrit-PatchSet: 1
Gerrit-Owner: falconia <falcon(a)freecalypso.org>
Attention is currently required from: Hoernchen, lynxis lazus, pespin.
Hello Jenkins Builder, lynxis lazus, pespin,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Code-Review+1 by pespin, Code-Review-1 by lynxis lazus
Change subject: ccid: fix rdr_to_pc_parameters and rdr_to_pc_hardware_error
......................................................................
ccid: fix rdr_to_pc_parameters and rdr_to_pc_hardware_error
The messages in the spec were different.
Change-Id: I67d5cb876d20b29f4759d5b194606f34b8b966c4
---
M ccid_common/ccid_device.c
M ccid_common/ccid_proto.h
2 files changed, 11 insertions(+), 6 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-ccid-firmware refs/changes/57/42157/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: osmo-ccid-firmware
Gerrit-Branch: master
Gerrit-Change-Id: I67d5cb876d20b29f4759d5b194606f34b8b966c4
Gerrit-Change-Number: 42157
Gerrit-PatchSet: 2
Gerrit-Owner: Hoernchen <ewild(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: Hoernchen <ewild(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu>
Attention is currently required from: Hoernchen.
lynxis lazus has posted comments on this change by Hoernchen. ( https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157?usp=email )
Change subject: ccid: fix rdr_to_pc_parameters and rdr_to_pc_hardware_error
......................................................................
Patch Set 1:
(1 comment)
Commit Message:
https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157/comment/1482dda3_2c… :
PS1, Line 8:
> It is not really important because this was never working and the rdr_to_pc_parameters is pointless […]
Please describe your commit with more than just "fix message a and b".
Please split this into 2 commits because you're fixing 2 messages in different places and fixing the protocol messages are quite important changes.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-ccid-firmware
Gerrit-Branch: master
Gerrit-Change-Id: I67d5cb876d20b29f4759d5b194606f34b8b966c4
Gerrit-Change-Number: 42157
Gerrit-PatchSet: 1
Gerrit-Owner: Hoernchen <ewild(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: Hoernchen <ewild(a)sysmocom.de>
Gerrit-Comment-Date: Sat, 21 Feb 2026 19:33:24 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Hoernchen <ewild(a)sysmocom.de>
Comment-In-Reply-To: lynxis lazus <lynxis(a)fe80.eu>
Attention is currently required from: lynxis lazus.
Hoernchen has posted comments on this change by Hoernchen. ( https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157?usp=email )
Change subject: ccid: fix rdr_to_pc_parameters and rdr_to_pc_hardware_error
......................................................................
Patch Set 1:
(1 comment)
Commit Message:
https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157/comment/4d907793_f7… :
PS1, Line 8:
> What is wrong? "The messages in the spec were different. […]
It is not really important because this was never working and the rdr_to_pc_parameters is pointless because we ignore the set message anyway and never change any parameters, so it was basically "working fine" since the octsim was created despite being wrong, and we do not have any bug reports about weird cards that don't work either. This just aligns it with the spec, that's it.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-ccid-firmware
Gerrit-Branch: master
Gerrit-Change-Id: I67d5cb876d20b29f4759d5b194606f34b8b966c4
Gerrit-Change-Number: 42157
Gerrit-PatchSet: 1
Gerrit-Owner: Hoernchen <ewild(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Comment-Date: Sat, 21 Feb 2026 16:43:25 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Hoernchen <ewild(a)sysmocom.de>
Comment-In-Reply-To: lynxis lazus <lynxis(a)fe80.eu>
Attention is currently required from: Hoernchen.
lynxis lazus has posted comments on this change by Hoernchen. ( https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157?usp=email )
Change subject: ccid: fix rdr_to_pc_parameters and rdr_to_pc_hardware_error
......................................................................
Patch Set 1:
(1 comment)
Commit Message:
https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157/comment/dead1962_d0… :
PS1, Line 8:
> Just to be clear, both messages were just plain wrong, there is no "different" wrong or "different" […]
What is wrong? "The messages in the spec were different." should be also part of the commit messages.
A commit message should explain why you did the change and gives the reader more information than "just read the code" and you know what's wrong.
`fix "stuff"` can mean anything from filling the wrong data, from not sending the data at all
This is such an important change (the part of rdr_to_pc_parameters) in difference to the rdr_to_pc_hardware_error, which is currently not in use.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-ccid-firmware
Gerrit-Branch: master
Gerrit-Change-Id: I67d5cb876d20b29f4759d5b194606f34b8b966c4
Gerrit-Change-Number: 42157
Gerrit-PatchSet: 1
Gerrit-Owner: Hoernchen <ewild(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: Hoernchen <ewild(a)sysmocom.de>
Gerrit-Comment-Date: Sat, 21 Feb 2026 16:13:46 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Hoernchen <ewild(a)sysmocom.de>
Comment-In-Reply-To: lynxis lazus <lynxis(a)fe80.eu>
Attention is currently required from: lynxis lazus.
Hoernchen has posted comments on this change by Hoernchen. ( https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157?usp=email )
Change subject: ccid: fix rdr_to_pc_parameters and rdr_to_pc_hardware_error
......................................................................
Patch Set 1:
(1 comment)
Commit Message:
https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157/comment/8b9dd9ed_8d… :
PS1, Line 8:
> No. This patch stays exactly like this. Both messages were wrong, and now they agree with the spec. […]
Just to be clear, both messages were just plain wrong, there is no "different" wrong or "different" problems, It absolutely does not matter how many bytes or which bytes were wrong, they didn't agree with the spec, there is no "a little bit" wrong when it comes to messages based on a spec, so those messages were just completely wrong, period.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/42157?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: osmo-ccid-firmware
Gerrit-Branch: master
Gerrit-Change-Id: I67d5cb876d20b29f4759d5b194606f34b8b966c4
Gerrit-Change-Number: 42157
Gerrit-PatchSet: 1
Gerrit-Owner: Hoernchen <ewild(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: lynxis lazus <lynxis(a)fe80.eu>
Gerrit-Comment-Date: Sat, 21 Feb 2026 15:28:12 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Hoernchen <ewild(a)sysmocom.de>
Comment-In-Reply-To: lynxis lazus <lynxis(a)fe80.eu>