<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>Codec negotiation (not the same old stuff)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">I have a H.323 device, let's call it stupid, that supports all variants of G.729. That should be</FONT>
<BR><FONT SIZE=2 FACE="Arial">good, but no. When it negotiates a call between Asterisk and a phone that supports all</FONT>
<BR><FONT SIZE=2 FACE="Arial">varients of G.729, it gets it wrong. Asterisk sends G.729A and the phone sends G.729,</FONT>
<BR><FONT SIZE=2 FACE="Arial">at which point the device transcodes the call, but changes the packetization.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">I'm looking for a way to get Asterisk to offer plain old G.729, so the device (stupid) can</FONT>
<BR><FONT SIZE=2 FACE="Arial">just bridge the RTP. My research shows this should not be required, since G.729 and</FONT>
<BR><FONT SIZE=2 FACE="Arial">G.729A are compatible and don't need transcoding.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">I'm trying to get an answer from the device manufacturer, but I do not have high hopes.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">If it matters, I am using chan_ooh323 with Asterisk 1.2.0.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Thanks,</FONT>
<BR><FONT SIZE=2 FACE="Arial">Dan</FONT>
</P>
<BR>
</BODY>
</HTML>