On Tue, Sep 20, 2011 at 10:42:52AM -0700, Ryan Crowder wrote: > > Thanks for replying! Here is dahdi_hardware and lspci output. > > dahdi_hardware > pci:0000:02:0c.0 wcte12xp+ d161:8001 Wildcard TE122 > pci:0000:03:0b.0 rxt1+ 0b0b:0305 Rhino R4T1 What happens when you just load the wcte12xp driver? For example: $ /etc/init.d/dahdi stop $ lsmod | grep dahdi (make sure no other drivers are loaded) $ modprobe wcte12xp; dahdi_genconf system (will overwrite your configs) $ dahdi_cfg $ dahdi_test -v -c 5 Opened pseudo dahdi interface, measuring accuracy... 8192 samples in 8191.544 system clock sample intervals (99.994%) 8192 samples in 8188.704 system clock sample intervals (99.960%) 8192 samples in 8190.480 system clock sample intervals (99.981%) 8192 samples in 8190.048 system clock sample intervals (99.976%) 8192 samples in 8189.799 system clock sample intervals (99.973%) --- Results after 5 passes --- Best: 99.994 -- Worst: 99.960 -- Average: 99.976991, Difference: 99.976991 If when just using the wcte12xp driver and dahdi_test still reports poor results I would look in dmesg to see if the driver is reporting anything about increasing the latency. If there are not any messages from the driver and dahdi_test has poor results then I would verify that the system is able to keep accurate wall time. If the problem only occurs when the rxt1 driver is loaded / configured, then I would recommend contacting Rhino technical support. -- 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
|