fixeria has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-e1-recorder/+/33759 )
Change subject: configure.ac: migrate from python2 to python3
......................................................................
configure.ac: migrate from python2 to python3
Fortunatelly we don't have any python2 specific code, so just bump.
Change-Id: Ib293c60cf66000b3e2520f7a02f39c4baa1c5ce9
---
M configure.ac
M osmoappdesc.py
2 files changed, 15 insertions(+), 4 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-e1-recorder refs/changes/59/33759/1
diff --git a/configure.ac b/configure.ac
index 568584d..3effcde 100644
--- a/configure.ac
+++ b/configure.ac
@@ -110,9 +110,9 @@
[Include the VTY/CTRL tests in make check [default=no]]),
[enable_ext_tests="$enableval"],[enable_ext_tests="no"])
if test "x$enable_ext_tests" = "xyes" ; then
- AC_CHECK_PROG(PYTHON2_AVAIL,python2,yes)
- if test "x$PYTHON2_AVAIL" != "xyes" ; then
- AC_MSG_ERROR([Please install python2 to run the VTY/CTRL tests.])
+ AC_CHECK_PROG(PYTHON3_AVAIL,python3,yes)
+ if test "x$PYTHON3_AVAIL" != "xyes" ; then
+ AC_MSG_ERROR([Please install python3 to run the VTY/CTRL tests.])
fi
AC_CHECK_PROG(OSMOTESTEXT_CHECK,osmotestvty.py,yes)
if test "x$OSMOTESTEXT_CHECK" != "xyes" ; then
diff --git a/osmoappdesc.py b/osmoappdesc.py
index 485a83b..56df5bc 100644
--- a/osmoappdesc.py
+++ b/osmoappdesc.py
@@ -1,4 +1,4 @@
-#!/usr/bin/env python
+#!/usr/bin/env python3
app_configs = {
"osmo-e1-recorder": ["doc/examples/osmo-e1-recorder.cfg"]
--
To view, visit https://gerrit.osmocom.org/c/osmo-e1-recorder/+/33759
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-e1-recorder
Gerrit-Branch: master
Gerrit-Change-Id: Ib293c60cf66000b3e2520f7a02f39c4baa1c5ce9
Gerrit-Change-Number: 33759
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-MessageType: newchange
fixeria has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-smlc/+/33758 )
Change subject: configure.ac: migrate from python2 to python3
......................................................................
configure.ac: migrate from python2 to python3
Fortunatelly we don't have any python2 specific code, so just bump.
Change-Id: Iaab94a1e896b78dc8699256e326edc165b0ed922
Related: OS#5950
---
M configure.ac
1 file changed, 15 insertions(+), 3 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-smlc refs/changes/58/33758/1
diff --git a/configure.ac b/configure.ac
index 65ebd59..484d689 100644
--- a/configure.ac
+++ b/configure.ac
@@ -117,9 +117,9 @@
[Include the VTY/CTRL tests in make check [default=no]]),
[enable_ext_tests="$enableval"],[enable_ext_tests="no"])
if test "x$enable_ext_tests" = "xyes" ; then
- AC_CHECK_PROG(PYTHON2_AVAIL,python2,yes)
- if test "x$PYTHON2_AVAIL" != "xyes" ; then
- AC_MSG_ERROR([Please install python2 to run the VTY/CTRL tests.])
+ AC_CHECK_PROG(PYTHON3_AVAIL,python3,yes)
+ if test "x$PYTHON3_AVAIL" != "xyes" ; then
+ AC_MSG_ERROR([Please install python3 to run the VTY/CTRL tests.])
fi
AC_CHECK_PROG(OSMOTESTEXT_CHECK,osmotestvty.py,yes)
if test "x$OSMOTESTEXT_CHECK" != "xyes" ; then
--
To view, visit https://gerrit.osmocom.org/c/osmo-smlc/+/33758
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-smlc
Gerrit-Branch: master
Gerrit-Change-Id: Iaab94a1e896b78dc8699256e326edc165b0ed922
Gerrit-Change-Number: 33758
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-MessageType: newchange
pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-pcu/+/33756 )
Change subject: pcu_l1_if: Document tx_pch empty IMSI scenario
......................................................................
pcu_l1_if: Document tx_pch empty IMSI scenario
Related: OS#6097
Change-Id: I327ca0e0f53be2d9b2a0705fe4de600229bdc5f9
---
M src/pcu_l1_if.cpp
1 file changed, 24 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-pcu refs/changes/56/33756/1
diff --git a/src/pcu_l1_if.cpp b/src/pcu_l1_if.cpp
index a256962..f42a3d4 100644
--- a/src/pcu_l1_if.cpp
+++ b/src/pcu_l1_if.cpp
@@ -275,6 +275,16 @@
else
memset(data, '0', IMSI_DIGITS_FOR_PAGING);
+ /* OS#6097: if strlen(imsi) == 0: We assume the MS is in non-DRX
+ * mode (TS 44.060 5.5.1.5) and hence it is listening on all CCCH blocks
+ * (TS 45.002 6.5.3, 6.5.6).
+ * Hence, pgroup 000 is taken "randomly" to send it over it. This of
+ * course not optimal since it can actually be sent on any CCCH blocks,
+ * so we are delaying the ImmAss for no good reason. But anyway,
+ * pcu_l1if_tx_pch() is deprecated and pcu_l1if_tx_pch_dt() should be
+ * used instead, which doesn't suffer from this problem.
+ */
+
/* block provided by upper layer comes without first byte (plen), prepend it manually: */
OSMO_ASSERT(sizeof(data) >= IMSI_DIGITS_FOR_PAGING + 1 + block->data_len);
data[IMSI_DIGITS_FOR_PAGING] = (plen << 2) | 0x01;
@@ -297,6 +307,10 @@
pch_dt.tlli = tlli;
if (imsi)
OSMO_STRLCPY_ARRAY(pch_dt.imsi, imsi);
+ /* OS#6097: if strlen(pch_dt.imsi) == 0: We assume the MS is in non-DRX
+ * mode (TS 44.060 5.5.1.5) and hence it is listening on all CCCH blocks
+ * (TS 45.002 6.5.3, 6.5.6).
+ */
pch_dt.data[0] = (plen << 2) | 0x01;
bitvec_pack(block, pch_dt.data + 1);
--
To view, visit https://gerrit.osmocom.org/c/osmo-pcu/+/33756
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit-Change-Id: I327ca0e0f53be2d9b2a0705fe4de600229bdc5f9
Gerrit-Change-Number: 33756
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: newchange
Attention is currently required from: fixeria.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/33755 )
Change subject: cosmetic: Document DRX_TIMER_MAX upper limit on BCCH smaller than possible range
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
I'm not actually sure whether that NOTE means the value should be >=4 or actually <=4 ....
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/33755
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: I5c8699bb5357a74805c25e8d02e982b25b47555d
Gerrit-Change-Number: 33755
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-CC: Jenkins Builder
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 14 Jul 2023 17:03:30 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-bsc/+/33754
to look at the new patch set (#3).
Change subject: SI13: Set DRX_TIMER_MAX value actually transmitted
......................................................................
SI13: Set DRX_TIMER_MAX value actually transmitted
The set of values in seconds which can be expressed in the 3-bit field
DRX_TIMER_MAX (0s, 1s, 2s, 4s,...64s) don't include the "3s" that where
being specified. Instead, libosmocore's encode_drx_timer() was
taking both upper boundary "4s" and encoding it "0b011".
Hence, better write the value actually being transmitted to MS, to avoid
users/readers confusion.
More related info can be found on TS 44.060 Table 12.24.2 and TS 45.002
6.5.6.
Related: OS#6097
Change-Id: Ibf01a50b258e197ba5e3173492513349ddffdb38
---
M src/osmo-bsc/system_information.c
1 file changed, 21 insertions(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-bsc refs/changes/54/33754/3
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/33754
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Ibf01a50b258e197ba5e3173492513349ddffdb38
Gerrit-Change-Number: 33754
Gerrit-PatchSet: 3
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-MessageType: newpatchset