[Asterisk-Users] zaptel fxotune.c tool

Rich Adamson radamson at routers.com
Sat Jan 8 08:06:37 MST 2005


I noticed the following came into cvs head yesterday:

> Update of /usr/cvsroot/zaptel
> In directory mongoose.digium.com:/tmp/cvs-serv2118
> 
> Modified Files:
> 	fxotune.c wctdm.c wctdm.h 
> Log Message:
> More TDM card echo API modifications.  Making the fxotune program automatically
> find the correct coefficients for the module.  Lots of neat stuff.

I did a complete cvs head checkout, compile, etc. Then compiled the
zaptel/fxotune on RHv9 with one TDM04b installed and working. After
stopping asterisk and running fxotune, I see:

 [root at phoenix zaptel]# ./fxotune -i   
 open(/dev/zap/0): No such file or directory

There is no zap0 on this system.

If I modify the fxotune.c statement:
  for (i = 0; i < 255; i++) {   
to start with i=1, then I get:

 [root at phoenix zaptel]# ./fxotune -i        
 Could not read request 1600 bytes from /dev/random.  Using only 340
 Error in read: Bad address
 Could not read request 1600 bytes from /dev/random.  Using only 340
 Error in read: Bad address
 Could not read request 1600 bytes from /dev/random.  Using only 340
 Unable to write: Bad address
 Could not read request 1600 bytes from /dev/random.  Using only 340
 Error in read: Bad address
 open(/dev/zap/5): No such device or address
 [root at phoenix zaptel]# 

Am I missing something, not running the app correctly, or is the app
not ready for prime time?

Rich





More information about the asterisk-users mailing list