Attention is currently required from: laforge, pespin.

dexter has posted comments on this change. ( 
https://gerrit.osmocom.org/c/osmo-mgw/+/27392 )

Change subject: mgcp_codec: fix oa/bwe comparison in mgcp_codec_pt_translate()
......................................................................


Patch Set 5:

(2 comments)

File src/libosmo-mgcp/mgcp_codec.c:

https://gerrit.osmocom.org/c/osmo-mgw/+/27392/comment/6ea38604_0ed6485e
PS1, Line 369: static bool codecs_same(struct mgcp_rtp_codec *codec_a, struct 
mgcp_rtp_codec *codec_b, bool match_pload_fmt)
> Yes, format conversion is transcoding in a "scientific" definition of the 
> word. […]
Ack


https://gerrit.osmocom.org/c/osmo-mgw/+/27392/comment/7dc8f996_39b061d9
PS1, Line 431:  /* In case we weren't able to find an exact match, we will try 
to find a match that is the same codec, but the
> agreeing with pespin
Than it is probably better to refactor the existing code a bit. The function 
that finds the payload type on the opposite connection could also find a 
convertible codec that could be the exactly the same or something that OsmoMGW 
can convert. That would be more flexible as we get access to the resulting 
codec struct instead of only the payload type. I have put that part in a follow 
up patch.



--
To view, visit https://gerrit.osmocom.org/c/osmo-mgw/+/27392
To unsubscribe, or for help writing mail filters, visit 
https://gerrit.osmocom.org/settings

Gerrit-Project: osmo-mgw
Gerrit-Branch: master
Gerrit-Change-Id: Ifbd201a2749009a4644a29bd77e1d0fc0c124a9d
Gerrit-Change-Number: 27392
Gerrit-PatchSet: 5
Gerrit-Owner: dexter <pma...@sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: msuraev <msur...@sysmocom.de>
Gerrit-CC: laforge <lafo...@osmocom.org>
Gerrit-CC: pespin <pes...@sysmocom.de>
Gerrit-Attention: laforge <lafo...@osmocom.org>
Gerrit-Attention: pespin <pes...@sysmocom.de>
Gerrit-Comment-Date: Mon, 27 Mar 2023 13:56:46 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <lafo...@osmocom.org>
Comment-In-Reply-To: pespin <pes...@sysmocom.de>
Comment-In-Reply-To: dexter <pma...@sysmocom.de>
Gerrit-MessageType: comment

Reply via email to