On Tue, Sep 20, 2011 at 11:38:35AM -0700, Ryan Crowder wrote: > Do you think this error has anything to do with it? > > dahdi_genconf > /usr/sbin/dahdi_genconf: missing default group (termtype=UNKNOWN) > It doesn't populate dahdi-channels.conf so I have to configure > chan_dahdi.conf manually. You can safely ignore this. There is an open issue [1] for this is the DAHDI-Tools project on the issue tracker. [1] https://issues.asterisk.org/jira/browse/DAHTOOL-55 > Here are the results... not really better. > :/etc/dahdi# dahdi_test > Opened pseudo dahdi interface, measuring accuracy... > 99.608% 99.419% 99.608% 99.608% 99.415% 99.608% 99.415% 99.608% > 99.608% 99.416% 99.608% 99.415% 99.608% 99.608% 99.415% 99.608% > 99.415% 99.608% 99.608% 99.416% 99.608% 99.415% 99.608% 99.608% > 99.415% 99.608% 99.415% 99.608% 99.608% 99.415% 99.608% 99.415% ^C > --- Results after 32 passes --- > Best: 99.608 -- Worst: 99.415 -- Average: 99.529880, Difference: > 100.004770 > :/etc/dahdi# dahdi_test -v -c 5 > Opened pseudo dahdi interface, measuring accuracy... > > 8192 samples in 8159.801 system clock sample intervals (99.607%) > 8192 samples in 8159.528 system clock sample intervals (99.604%) > 8192 samples in 8239.840 system clock sample intervals (100.584%) > 8192 samples in 8159.856 system clock sample intervals (99.608%) > 8192 samples in 8239.840 system clock sample intervals (100.584%) > --- Results after 5 passes --- > Best: 99.608 -- Worst: 99.416 -- Average: 99.530042, Difference: > 99.997230 Interesting. This looks fine then and it's most likely a result of the dahdi_test process not being scheduled on your system in a timely fashion. Your cummulative timing results were 99.997% which is good. What do you get when you run: $ chrt -f 99 dahdi_test -v -c 5 That will run the dahdi_test process at the highest possible priority. -- Shaun Ruffell Digium, Inc. | Linux Kernel Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: www.digium.com & www.asterisk.org
|