Attention is currently required from: fixeria.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/33581 )
Change subject: scheduler: fix wrong union field in _sched_compose_tch_ind()
......................................................................
Patch Set 1: Code-Review+2
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/33581
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: I2f6794d229ad8219e3835a6eb74513672e497d5d
Gerrit-Change-Number: 33581
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 06 Jul 2023 09:39:05 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: fixeria.
pespin has removed a vote from this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/33583 )
Change subject: scheduler: unify argument names/order for _sched_compose_*_ind()
......................................................................
Removed Code-Review+2 by pespin <pespin(a)sysmocom.de>
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/33583
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: I3d8c90b82f2a55b0c5c2d6b4efb8fd962508534d
Gerrit-Change-Number: 33583
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-MessageType: deleteVote
jolly has abandoned this change. ( https://gerrit.osmocom.org/c/osmo-msc/+/33507 )
Change subject: ASCI: Add VGCS/VBS call control specific data to gsm_trans
......................................................................
Abandoned
Merged with Change-ID: I9947403fde8212b66758104443c60aaacc8b1e7b
--
To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/33507
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Change-Id: I37d68a89a101fa579680fd3cf170cd3dc5a148e4
Gerrit-Change-Number: 33507
Gerrit-PatchSet: 9
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: abandon
Attention is currently required from: neels, pespin.
jolly has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-msc/+/33498 )
Change subject: ASCI: Use a unique call-id for RTP streams
......................................................................
Patch Set 6:
(1 comment)
File include/osmocom/msc/msc_t.h:
https://gerrit.osmocom.org/c/osmo-msc/+/33498/comment/6e87af82_e25cb29a
PS6, Line 33: uint32_t call_id;
> mgcp_call_id? Or is/will it used for other purposes?
The call ID is used to identify the call between MSC and BSS. It can be used by the MGW to identify the call for logging and accounting purpose. It can also be used to directly interconnect user data inside BSS. Because our implementation uses MGCP does not mean that call_id can be used for MGW only. I would leave it "call_id".
--
To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/33498
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Change-Id: I36c5f159fa0b54fb576ff8bd279928b895554793
Gerrit-Change-Number: 33498
Gerrit-PatchSet: 6
Gerrit-Owner: jolly <andreas(a)eversberg.eu>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Thu, 06 Jul 2023 06:39:21 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment