Attention is currently required from: osmith, fixeria.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/32343 )
Change subject: bsc: improve TC_assignment_csd
......................................................................
Patch Set 1: Code-Review+1
(1 comment)
File bsc/MSC_ConnectionHandler.ttcn:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/32343/comment/cbeb5521_1056…
PS1, Line 212: if (ie.ipa
the more ttcn3-native way would probably to match against a template and simply leave it to the automatic "template mismatch" logging to allow the user to see what doesn't match. But of course one can also do it like here. It's just that the philosophy of TTCN3 is exactly that you don't have to have 200 if-clauses testing for individual fielsds of every packet. Doesn't make too much difference in this specific case.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/32343
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: Id0e0c5631d7a36635e1ef49cf5bf554f0336556b
Gerrit-Change-Number: 32343
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 20 Apr 2023 00:18:39 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: osmith.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/32369 )
Change subject: CSD: support non-transparent data rates
......................................................................
Patch Set 1: Code-Review-1
(1 comment)
File src/osmo-bsc/abis_rsl.c:
https://gerrit.osmocom.org/c/osmo-bsc/+/32369/comment/786930bc_bc66cab7
PS1, Line 459: GSM48_CMODE_DATA_43k5
same as last commit: you cannot do more than 14k4 (NT) or 14k5 (T) in a single TCH/F.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/32369
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Ib5f4bdf17a9833f65a0b623a033da838a2594d68
Gerrit-Change-Number: 32369
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 20 Apr 2023 00:14:50 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: osmith.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/32367 )
Change subject: CSD: support 29k0, 32k0 transp data
......................................................................
Patch Set 1: Code-Review-1
(1 comment)
Patchset:
PS1:
I think the comment is very mis-leading. This change doesn't make us magically support bit-rates that are beyond the capability of a single timeslot. Supporting anything above 14k5 transparent means having to implement multi-channel assignments (HSCSD), whihc would have large impact on the channel allocator and many other parts of osmo-bsc. There is no plan or requirement to implement HSCSD, so it really would be best not to imply (in code or commit log) that we do support it in any way.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/32367
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: I03fd3ca19b08d5cff8748ba9cf2f21d4befaf338
Gerrit-Change-Number: 32367
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 20 Apr 2023 00:14:05 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: pespin, dexter.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-abis/+/32371 )
Change subject: e1d: set fd number back to 0 on failure
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
> That's true, I was also wondering about this. […]
stdin might be closed by an application, leading to the re-use of fd==0 for some other file (the next file/socket opened after closing stdin). It's still unlikely, but the risk is real.
--
To view, visit https://gerrit.osmocom.org/c/libosmo-abis/+/32371
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-abis
Gerrit-Branch: master
Gerrit-Change-Id: Ic49e93550f0cff1a30644408ef7dc0648be768df
Gerrit-Change-Number: 32371
Gerrit-PatchSet: 1
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 20 Apr 2023 00:10:35 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Comment-In-Reply-To: dexter <pmaier(a)sysmocom.de>
Gerrit-MessageType: comment