[Asterisk-bsd] fxotune and bsd

[Ian FREISLICH]

"Bob" wrote:
> Why are the /dev files renamed in zaptel BSD?
>
> This fix would be to get rid of the "/" in the sprintf that forms the
> directory name, but should the "/" be put back in when the files are
> created in the first place?
>
> The file is actually called /dev/zap1, /dev/zap2 ...
>
> On Linux it is /dev/zap/1, /dev/zap/2 ...

Atcually, I think it's a little more complicated than that.  My
/dev/zap/ directory has the following contents:

[brane] ~ $ ls -l /dev/zap/
total 0
crw-------  1 root  wheel    0, 117 Dec 14 15:56 channel2
crw-------  1 root  wheel    0, 118 Dec 14 15:56 channel3
crw-------  1 root  wheel    0, 119 Dec 19 18:34 channel4
crw-rw-r--  1 root  wheel    0, 109 Dec 14 15:56 ctl
crw-------  1 root  wheel    0, 116 Dec 14 15:56 timer1

But the channelN devices only show up when Asterisk has connected
to the zaptel driver.  When Asterisk is stopped, only the ctl and
timer devices are present.

I think that FreeBSD uses the ioctl() interface to address the zap
devices.  There was a thread recently in asterisk-dev:

Subject: Re: [asterisk-dev] Zaptel patch advice needed

Where someone wanted more than 255 channels and the major/minor
numbering apparently doesn't allow that, which is probably why the
zaptel-bsd driver didn't even bother with /dev/zap/N.

I'm going to try and see if opening the devices the way the thread
mentioned above does.  Others are welcome to try as well.  I may
have limited success.

Ian

--
Ian Freislich

> -----Original Message-----
> From: asterisk-bsd-bounces at lists.digium.com
> [mailto:asterisk-bsd-bounces at lists.digium.com] On Behalf Of Calvin
> Hendryx-Parker
> Sent: Wednesday, December 19, 2007 8:06 PM
> To: Asterisk on BSD discussion
> Subject: [Asterisk-bsd] fxotune and bsd
> 
> Hi,
> 
> We just setup a new FreeBSD server running asterisk 1.4.13 with a  
> TDM04B card using the zaptel 1.4.6 driver.  Everything compiled and  
> worked from ports including the drivers for the card.  The only issue  
> is that the users are complaining about echo when they call out on the  
> FXO ports.  Seems like fxotune is the magic tool to solve this, but it  
> just gives me these errors when it runs:
> 
> /dev/zap/1 absent: No such file or directory
> /dev/zap/2 absent: No such file or directory
> ...
> /dev/zap/252 absent: No such file or directory
> fxotune: successfully set echo coeffecients on FXO modules
> 
> and it writes out an empty fxotune.conf.
> 
> Anyone else get this to work?
> 
> Thanks,
> Calvin
> 
> -- 
> S i x  F e e t  U p , I n c .  |  "Nowhere to go but open source"
> Silicon Valley: +1 (650) 401-8579 x602
> Midwest: +1 (317) 861-5948 x602
> Toll-Free: 1-866-SIX-FEET
> mailto:calvin at sixfeetup.com
> http://www.sixfeetup.com  |  Zope/Plone Custom Development