[asterisk-dev] Asterisk tries to transcode vp8 <> g729

Alexander Traud pabstraud at compuserve.com
Sun Dec 6 01:54:04 CST 2020


> codecs [have to be] in "[allow=]audio,video[,text]" order

Did you file an issue report for this? If yes, please, mark my just created report as duplicate: <https://issues.asterisk.org/jira/browse/ASTERISK-29198>

In any case, good catch! Yes, Digium Asterisk still assumes that the *first* codec in the list of "allows" is an audio codec always; although video (and text) are supported for more than a decade, and the codec part got an overhaul for Asterisk 13. If the first codec is video (or text), the source code goes crazy. Perhaps nobody noticed that before. Perhaps dozens noticed that before but did not report.

> Is it worth reporting [in this case]?

In doubt, always report, please. Then, someone else takes the report and feedbacks on that. Even if it stays open, others can passively subscribe to it. And without a report, others might miss the issue (and your great workaround) because not everyone also searches through site:digium.com.

> Is it worth reporting [in general]?

And use the bug tracker at issues.asterisk.org. The Asterisk Team does not transform customer feedback from event, community, and mailing-list channels into the tracker themselves - even if it is a confirmed and reproducible software bug.

Even if you found a workaround for yourself, please, report! The cause of the bug could be much broader, and the workaround incomplete. That makes the difference between a major and a minor severity bug. Until the bug is analyzed, nobody knows if a bug has major or minor severity.

And finally, even minor severity issues often tackle non-functional requirements, things other users stumble upon and waste a lot of time to workaround. "Easy" workaround does not reflect how much time is lost by the customer - time which could have been used differently, for example, to enhance Asterisk.





More information about the asterisk-dev mailing list