Patrick wrote: > > Yes you need USE_RTC for better timing. And you maybe need kernel 2.6.13 > to get the USE_RTC functionality because it depends on the kernel. My > FC4 box has a 2.6.12 kernel which contains the upstream USE_RTC stuff so > I patch the asterisk source to enable it on 2.6.12 too. If you use a > plain vanilla unpatched kernel than yes you will need 2.6.13.
Thank you for the clarification. I use Scientific Linux 4, which probably equal to RHEL4, with its default kernel 2.6.9. I don't know if it has new rtc stuff. I'll try a new kernel later, anyway. > <rant> > The delay issue in meetme has been present for a long time now and it > seems Digium is not interested in fixing it. Afaik a patch was offered > that solved the issue but was rejected by Mark because he felt the extra > thread it used would not work on embedded systems with no memory/cpu > power. Fine if it doesn't but why isn't it then possible to just do: > #ifdef normal_pc_or_server_99.999%_of_people_use > finally_fix_meetme_delay > #endif > </rant> Totally agreed! The increasing delay issue in meetme is a *really problem*. After ten minutes or so conversation, the delay can increase to 3-4 seconds, which is *unaccetable* for most people. All my customers have complains about it. I really hope it can be solved before 1.2 release. So where can I find the patch you mentioned? _______________________________________________ Asterisk-Dev mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
