Attention is currently required from: laforge, neels, pespin.

falconia has posted comments on this change by falconia. ( 
https://gerrit.osmocom.org/c/osmo-bsc/+/41630?usp=email )

Change subject: MGW control: migrate to new API for codecs and payload types
......................................................................


Patch Set 1:

(1 comment)

Patchset:

PS1:
> ACK
In the present patch I change osmo-bsc to use a libosmo-mgcp-client API update 
that happened 3 release cycles ago:

https://gerrit.osmocom.org/c/osmo-mgw/+/34899

The above patch was merged in 2024-01, thus 2024-07 and 2025-02 releases 
already had the new API which I am using here, with the old one marked as 
deprecated. It just so happens that neither osmo-bsc nor osmo-msc was updated 
to use the new API until now! The present patch fixes osmo-bsc, while osmo-msc 
still remains.

The next patch in this series, the one that currently fails to build because 
the needed library patch hasn't been merged yet, does have a TODO-RELEASE entry 
noting use of the new library API - but none should be needed in this patch, as 
I understand it.



--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/41630?usp=email
To unsubscribe, or for help writing mail filters, visit 
https://gerrit.osmocom.org/settings?usp=email

Gerrit-MessageType: comment
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Iafc38a3da64ce7c2f060a32864174dcde9f57b56
Gerrit-Change-Number: 41630
Gerrit-PatchSet: 1
Gerrit-Owner: falconia <[email protected]>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <[email protected]>
Gerrit-Reviewer: laforge <[email protected]>
Gerrit-Reviewer: neels <[email protected]>
Gerrit-CC: pespin <[email protected]>
Gerrit-Attention: neels <[email protected]>
Gerrit-Attention: laforge <[email protected]>
Gerrit-Attention: pespin <[email protected]>
Gerrit-Comment-Date: Tue, 09 Dec 2025 17:12:34 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <[email protected]>
Comment-In-Reply-To: pespin <[email protected]>

Reply via email to