<br><br><div><span class="gmail_quote">On 4/5/06, <b class="gmail_sendername">Goldenear</b> <<a href="mailto:goldenear@free.fr">goldenear@free.fr</a>> wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
>>Why could not asterisk use by default timing from (software)<br>>>rtc ?<br>>><br>>><br>><br>>It does, in 2.6 .<br>><br>><br>><br>Really ? I run Asterisk with kernel 2.6 and I have warning messages
<br>because no zaptel module is present :(</blockquote><div><br><br>in the case of no zaptel hardware available, modprobe ztdummy first<br></div><br>Secondly, reliable (clocked) rtp timing just moved from asterisk's svn test-this-branch to svn trunk
<br><br>You have to enable it by setting internal_timing=yes in /etc/asterisk/asterisk.conf in the [options] area.<br><br>In my testing thus far (not from trunk, but test-this-branch), it works beautifully.<br><br>I have seen VAD work well for the first time between asterisk and a spa-3000, and in high packet loss situations (think wireless) where losing the rtp packet on one side used to lead to packets not being sent from the other side, which could get kind of pathological pre internal_timing - it's marvelous.
<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">_______________________________________________<br>--Bandwidth and Colocation provided by
<a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-dev mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev
</a><br></blockquote></div><br><br clear="all"><br>-- <br>Mike Taht<br>PostCards From the Bleeding Edge<br><a href="http://the-edge.blogspot.com">http://the-edge.blogspot.com</a>