Attention is currently required from: laforge, pespin, fixeria, keith, dexter.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-msc/+/28509 )
Change subject: Change CC_CAUSE returned on unanswered MT Call
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
regarding proper CC timeout: the old cc implementation apparently only has one overall guard timer, see gsm48_cc_guard_timeout(). Instead of in call_leg.c which is all about RTP, we could set that trans.cc.release_cause value in that gsm48_cc_guard_timeout() function depending on the trans->cc.state?
--
To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/28509
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Change-Id: I4a9cfc388ec9ecb743d154a114a6db638eac4701
Gerrit-Change-Number: 28509
Gerrit-PatchSet: 1
Gerrit-Owner: keith <keith(a)rhizomatica.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: keith <keith(a)rhizomatica.org>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 22 Jul 2022 17:07:26 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: laforge, pespin, fixeria, keith, dexter.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-msc/+/28509 )
Change subject: Change CC_CAUSE returned on unanswered MT Call
......................................................................
Patch Set 1: Code-Review+1
(1 comment)
File src/libmsc/gsm_04_08_cc.c:
https://gerrit.osmocom.org/c/osmo-msc/+/28509/comment/4cd300a7_318ddd36
PS1, Line 281: (trans->cc.state == GSM_CSTATE_CALL_RECEIVED) ?
> In adding this check, I should point out that I do not know what other CC state is possible when we […]
related: the cc state transitioning was written a very long time ago, before we had osmo_fsm. Specially for inter-MSC HO i implemented a new "proper" FSM for CC via MNCC in 2018, in mncc_fsm.[hc], because it was not possible to use the older cc implementation for what inter-msc requires. It is well possible and loosely intended to replace the old cc implementation with this new mncc_fsm (i wrote that intention into the comment on top of mncc_call.c). IMO it would clarify things and have "proper" state transition checking and so forth. Given the relatively low attention to osmo-msc in the past years the cc refactoring hasn't happened, and other things are more pressing, it doesn't seem to be happening any time soon. So until then we're left with figuring out the old cc implementation that osmo-msc still uses in the usual voice call scenarios. So:
It seems to me that you have already figured out at least one case where sending USER_NOTRESPOND makes more sense, and i trust you with that judgement.
I think this patch is fine, but if you would want to limit this cause to mgw X2 expiry:
in call_leg.c, in call_leg_fsm_timer_cb(), you could detect the T that expired:
if (fi->T == -2) ...
the usual pattern we use is to store state about whether a cause value has already been determined, for example add trans.cc.release_cause, and here use that if it is nonzero:
trans->cc.release_cause ? : GSM48_CAUSE_RESOURCE_UNAVAIL
It seems that X2 is also used for a timeout during call release (though actually that seems like dead code), so probably
if (fi->T == -2 && fi->state == CALL_LEG_ST_ESTABLISHING)
trans->cc.release_cause = GSM48_CC_CAUSE_USER_NOTRESPOND;
The missing link is that call_leg doesn't know its cc trans yet, so in call_leg we would need to add a backpointer to the trans, like rtp_stream already has: for_trans.
All of this just if you think it is worthwhile...
--
To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/28509
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Change-Id: I4a9cfc388ec9ecb743d154a114a6db638eac4701
Gerrit-Change-Number: 28509
Gerrit-PatchSet: 1
Gerrit-Owner: keith <keith(a)rhizomatica.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: keith <keith(a)rhizomatica.org>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 22 Jul 2022 17:03:40 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: keith <keith(a)rhizomatica.org>
Gerrit-MessageType: comment
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-cbc/+/28732
to look at the new patch set (#3).
Change subject: Support CBSP/TCP and SBc-AP/SCTP client mode
......................................................................
Support CBSP/TCP and SBc-AP/SCTP client mode
This patch adds support to set up a CBSP link so that osmo-cbc connects
as a TCP client to the BSC, which runs as a TCP server.
Similary, support to set up a SBc-AP link so that osmo-cbc connects
as a SCTP client to the MME, which runs as SCTP server.
A new "mode (client|server|disabled)" VTY command is added to use one
mother or the other, and also to disable the link and hence the peer
until it is set again. This is useful if the peer is under manintenance
for instance.
client sockets are created automatically when the "peer" vty node is
exited if the link is not yet created, hence creating it at startup or
if moved back from "disabled" mode. If client socket dies, it will
keep attempting reconnect every 5 seconds.
Related: OS#4945
Change-Id: I3ec54b615b41b56f7a9c64298e3fcaac37f4b60e
---
M doc/examples/osmo-cbc/osmo-cbc.cfg
M include/osmocom/cbc/cbc_peer.h
M include/osmocom/cbc/cbsp_link.h
M include/osmocom/cbc/sbcap_link.h
M src/cbc_main.c
M src/cbc_peer.c
M src/cbc_vty.c
M src/cbsp_link.c
M src/sbcap_link.c
9 files changed, 476 insertions(+), 32 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-cbc refs/changes/32/28732/3
--
To view, visit https://gerrit.osmocom.org/c/osmo-cbc/+/28732
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-cbc
Gerrit-Branch: master
Gerrit-Change-Id: I3ec54b615b41b56f7a9c64298e3fcaac37f4b60e
Gerrit-Change-Number: 28732
Gerrit-PatchSet: 3
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-MessageType: newpatchset
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-cbc/+/28732 )
Change subject: Support CBSP/TCP and SBc-AP/SCTP client mode
......................................................................
Patch Set 2:
This change is ready for review.
--
To view, visit https://gerrit.osmocom.org/c/osmo-cbc/+/28732
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-cbc
Gerrit-Branch: master
Gerrit-Change-Id: I3ec54b615b41b56f7a9c64298e3fcaac37f4b60e
Gerrit-Change-Number: 28732
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Comment-Date: Fri, 22 Jul 2022 16:13:16 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: neels.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-upf/+/28311 )
Change subject: add contrib/set_cap_net_admin.sh
......................................................................
Patch Set 2:
(1 comment)
Patchset:
PS2:
> two reasons: […]
Doesn't look valid points to me.
- doc/reminder: that's what UserManual is for.
- having to set up cap_net_admin all the time: You also need to run it every time and you don't add a script run_upf.sh for that. This should be set in your own env (osmo-dev?) IMHO, not here, specially since it's basically a oneliner.
I really don't see the point in having this in, let's see what other think.
--
To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/28311
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-upf
Gerrit-Branch: master
Gerrit-Change-Id: If31c304e2602d3c37d5d8a5a2705417b2fc4686c
Gerrit-Change-Number: 28311
Gerrit-PatchSet: 2
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 22 Jul 2022 16:10:21 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: osmith.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ci/+/28638 )
Change subject: scripts/common-obs: use git commit --no-verify
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
i'd like to better understand... --no-verify skips the linter? why do these commits see linter problems at all, and then why does it make sense to skip it?
--
To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/28638
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-ci
Gerrit-Branch: master
Gerrit-Change-Id: Icdb50cdd1217d848e1e640fbffd7a88b9c8bc8c6
Gerrit-Change-Number: 28638
Gerrit-PatchSet: 1
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-CC: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: osmith <osmith(a)sysmocom.de>
Gerrit-Comment-Date: Fri, 22 Jul 2022 16:08:02 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: pespin.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-upf/+/28311 )
Change subject: add contrib/set_cap_net_admin.sh
......................................................................
Patch Set 2:
(1 comment)
Patchset:
PS2:
> As mentioned I'm not sure this is needed here.
two reasons:
it's a doc/reminder of how setting cap_net_admin works.
when developing, after rebuilding osmo-upf i have to set cap_net_admin all the time, it's a convenient script for the dev cycle.
debian packaging: good point, not sure how that is done, would be great if i could delegate that part, i see it as a separate patch; this script is not at all intended to replace whatever the packaging should do.
--
To view, visit https://gerrit.osmocom.org/c/osmo-upf/+/28311
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-upf
Gerrit-Branch: master
Gerrit-Change-Id: If31c304e2602d3c37d5d8a5a2705417b2fc4686c
Gerrit-Change-Number: 28311
Gerrit-PatchSet: 2
Gerrit-Owner: neels <nhofmeyr(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-Comment-Date: Fri, 22 Jul 2022 16:03:13 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment