<br><br><div class="gmail_quote">On 8 February 2011 17:23, Steve Underwood <span dir="ltr"><<a href="mailto:steveu@coppice.org">steveu@coppice.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 02/09/2011 12:09 AM, Steven Ayre wrote:<br>
> Annex A is just an alternative way of encoding the data, using less<br>
> processing power but at poorer quality. They generate compatible data<br>
> - decoders both with and without annex a support decode both G729 and<br>
> G729A encoded data. The difference is purely in the implementation of<br>
> the encoder/decoder. If your device uses G729A in the SDP, it's broken.<br>
</div>This is correct, but there are still quite a few things around that have<br>
broken SDP that says g729a. The last time I looked, Freeswitch had a<br>
fudge in the source code to tolerate that.<br></blockquote><div><br>Cool, didn't realise that. So no modifications should be needed then.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">><br>
> Annex B uses the same PT & name. It does work in passthrough mode, as<br>
> does plain G729.<br>
</div>There is supplementary info in the SDP to say whether AnnexB is enabled,<br>
like so:<br>
<br>
a=fmtp:18 annexb=yes<br></blockquote><div><br>Which is I believe passed to the other leg. Is that correct?<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
<br>
> -Steve<br>
><br>
><br>
> On 8 February 2011 15:31, curriegrad2004 <<a href="mailto:curriegrad2004@gmail.com">curriegrad2004@gmail.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:curriegrad2004@gmail.com">curriegrad2004@gmail.com</a>>> wrote:<br>
><br>
> G729 only. No A's or AB.<br>
><br>
> If you want to pass through other variants of G.729, you can simply<br>
> modify mod_g729.c to include additional variants of G729<br>
><br>
> Which by the way, I've pasted the area of the code you might want to<br>
> modify. I've done this on mine and it worked fine as pass through.<br>
><br>
> 00217 SWITCH_ADD_CODEC(codec_interface, "G.729A");<br>
> 00218 for (count = 12; count > 0; count--) {<br>
> 00219 switch_core_codec_add_implementation(pool,<br>
> codec_interface,<br>
> 00220<br>
> SWITCH_CODEC_TYPE_AUDIO, 18, "G729A", NULL,<br>
> 8000, 8000, 8000,<br>
> 00221<br>
> mpf * count, spf * count, bpf * count, ebpf *<br>
> count, 1, count * 10,<br>
> 00222<br>
> switch_g729_init, switch_g729_encode,<br>
> switch_g729_decode, switch_g729_destroy);<br>
> 00223 }<br>
><br>
><br>
> On Tue, Feb 8, 2011 at 7:02 AM, Sam <<a href="mailto:u2nsam@gmail.com">u2nsam@gmail.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:u2nsam@gmail.com">u2nsam@gmail.com</a>>> wrote:<br>
> > Hi,<br>
> ><br>
> > Which type of G.729 codec does freeswitch uses in passthrough<br>
> mode ?<br>
> > Is it g729a or g729b or g729ab .<br>
> ><br>
> > Regards<br>
> > Sam<br>
><br>
</div><font color="#888888">Steve<br>
</font><div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br>