[App_rpt-users] zaptel issues

[AH2S]

Hello group,

I just loaded up a new server with the official ACID distro from the 
AllStarLink Website but I cannot get Asterisk to start.  I copied all my 
configuration files located in /etc/asterisk from my working server to 
the new one so I hoped the transition would be smooth.  When Asterisk 
bombs out, the log file fills up with the following:

[Feb  4 22:48:10] ERROR[14787] asterisk.c: Asterisk has detected a 
problem with your Zaptel configuration and will shutdown for your 
protection.  You have options:
	1. You only have to compile Zaptel support into Asterisk if you need 
it.  One option is to recompile without Zaptel support.
	2. You only have to load Zaptel drivers if you want to take advantage 
of Zaptel services.  One option is to unload zaptel modules if you don't 
need them.
	3. If you need Zaptel services, you must correctly configure Zaptel.


This led me to look into the zaptel driver.  After many changes to its 
config file in /etc/sysconfig/zaptel and trying over and over again, I 
finally reverted back to the original config and began looking at the 
build process itself thinking that maybe I could find some clues.  The 
zaptel driver compiles without issue and loads the kernel module(s) just 
fine.  Everything appears to be functional.  Here's what I get when I 
load the driver after having compiled a fresh zaptel:

[root at allstar zaptel]# /etc/init.d/zaptel start
Loading zaptel framework:                                  [  OK  ]
Waiting for zap to come online...OK
Loading zaptel hardware modules: wct1xxp.
  wcte11xp.
  wctdm24xxp.
  wcfxo.
  wctdm.
No hardware timing source found in /proc/zaptel, loading ztdummy
Running ztcfg:                                             [  OK  ]

Again, everything looks fine.  The device nodes in /dev/zap are there 
(channel, ctl, pseudo, and timer).  So I kept reading and I found a 
thread that said this command:
  od -c /dev/zap/pseudo

should produce this:
  0000000 177 177 177 177 177 177 177 177 177 177 177 177 177 177 177 177
  *

It does produce that output, but only the first time.  After issuing the 
command and getting the strings back the first time, I CTRL-C and get 
back to a prompt.  When I issue the command again, I get nothing back.  
It just sits there waiting for me to interrupt it again with a CTRL-C.  
On a working box when I issue that command, I get those strings back 
immediately, every time.  I believe this difference is what is causing 
my problems.  Unfortunately that is as deep as I've gotten with it.  My 
kernel is:

[root at allstar etc]# uname -r
2.6.18-371.4.1.el5PAE

and it's running on a Intel dual quad-core xeon with 8 GB of RAM.  I'm 
not sure how to proceed from here so any advice would be appreciated.  
Thanks in advance...

-- 
Rob Pectol - AH2S
AllStar Node 2147