https://bugzilla.redhat.com/show_bug.cgi?id=1358293 --- Comment #23 from Peter Lemenkov <lemenkov@xxxxxxxxx> --- (In reply to Tom "spot" Callaway from comment #22) > Does bcg729 implement Annex C+, D, E, F, G, H, or I? No. It implements only a basic A profile (integer codec) also known as G.729a, and B profile, also known as G.729b. B profile is essentially the same as A profile, but with CN (comfort noise), VAD (Voice Auto Detection), and DTX (Discontinuous Transmission) packets handling implemented. "A" profile decoder can handle "B" compliant stream by skipping unknown packets related to CN/VAD/DTX. "B" decoder can handle "A" compliant data w/o any issues. A generic CN/VAD/DTX payload for codecs w/o support (for example - G.711 / G.722) is described in RFC 3389: https://tools.ietf.org/html/rfc3389 Please also read G.729 wikipedia entry carefully. Especially non-technical part below the compatibility matrix and annex descriptions. Just for the record - what people usually call G.729 is a different codec, although compatible, anyone can hardly find in the wild. Other G.729 extensions (C, D, etc) are also not so easy to find. If a codec can encode and decode G.729a stream this means that both parties can hear each other (unknown packets can be skipped, and any bigger "annex" codec can provide compatible output - fixed point, 8 kbit/s, no extensions). G.729.1 is a totally different incompatible codec, and outside of the scope of this library. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx