>Information on timing sources can be found here: >https://wiki.asterisk.org/wiki/display/AST/Timing+Interfaces
>As noted on that page, ConfBridge can use any timing interface Asterisk >provides, and is not limited to the DAHDI timing interface. Generally, >timerfd is a good timing interface. >That aside, I would try to rule out external issues with the garbled audio >before changing the timing source. Things like: > - Analysis of the RTP traffic (along with potential jitter) > - CPU utilization with an active conference (95% idle doesn't mean that >some core isn't pegged) > - Any potential transcoding issues or codec issues >Matt Hi Matt - thanks. Looks like I am ONLY loading: res_timing_pthread res_timing_dahdi But I dont think the res_timing(x) is working on CentOS 5. res_timing_timerfd does not even seem to be compiled on this box. How do I tell for sure what its using and if its good. All I saw in the asterisk log was the two res_timing_pthread and res_timing_dadhi being loaded. Everything else is fine actually. It worked with the card, and withthout the card just sending audio to one endpoint has audio issues in a conference. The machine is doing nothign else at that time. Thanks, Jerry
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Check out the new Asterisk community forum at: https://community.asterisk.org/ New to Asterisk? Start here: https://wiki.asterisk.org/wiki/display/AST/Getting+Started asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
