search for: ztclock

Digging further into the FXO cpu spike vs clock issue, I removed the 18.432 MHZ crystal from an FXO card and replaced it with a 20.000 MHZ crystal. This of course forced the zaptel timing way off ~ 93% accurate using ztclock. I then proceeded to modify the wcfxo.c driver source code to set the proper PLL divider values to return the DAA clock back to 8 Khz. I came up with the values of N1=25, M1=72 and CGM=1. I wrote the corresponding values out to registers 7, 8 & 10. This seemed to bring the clock back closer...

I've made some modifications to zttest in order to use it as a frame clock accuracy tester / slip detector. I'm not certain if that was it's original purpose, but it seems that a lot of folks try to use it that way. The result is something that I'm calling ztclock for now to help avoid confusion. I'm including the source at the end of this post. You can compile it by placing the source in your zaptel source directory as ztclock.c and building with: cc -I. -O3 -g -Wall ztclock.c -o ztclock Here is a sample run of the test: -- snip -- ./ztclock ztclo...

...etc versions asterisk 1.2.4, zaptel 1.2.4, libpri 1.2.2, spandsp 0.0.2pre25). I have tried later versions of asterisk, zaptel, and libpri, but not a 0.0.3version of spandsp. I have sent faxes from many different fax machines, all show the problem. I have attempted to run a utility I found called ztclock... suprisingly of the 4 pri's the "best" as far as spandsp results are concerned is Xspedius (of the 4 it is the only one that ever receives 10+page faxes without error, still only about 50% of the time, but the other 3 never receive more than 10 pages without failing a page). Howeve...