On Tue, 2007-04-17 at 23:25 +0300, Tzafrir Cohen wrote:
> My guess: timing.
>
> Remove all the calls to ztcfg from modprobe.conf, use a proper init.d
> script, and you won't need to modprobe anything except wctdm .
On my system at least, there is nothing in modprobe.conf at all
regarding zaptel
On Tue, Apr 17, 2007 at 09:51:02AM -0600, Greg Woods wrote:
> On Tue, 2007-04-17 at 13:47 +1200, Aaron Martin wrote:
>
> > If I manually run the following commands:
> >
> > modprobe zaptel
> > modprobe wctdm
> > ztcfg -vvv
> > asterisk -vvvc
> >
> > Then SOMETIMES asterisk will work perfectly wi
On Tue, 2007-04-17 at 13:47 +1200, Aaron Martin wrote:
> If I manually run the following commands:
>
> modprobe zaptel
> modprobe wctdm
> ztcfg -vvv
> asterisk -vvvc
>
> Then SOMETIMES asterisk will work perfectly with the zap channels, allowing
> both
> incoming and outgoing calls as per my di
I am having problems with my zaptel channels on my fresh install of Asterisk
1.4.2 on Fedora core 6.
I have a new Digium TDM400P with 2 FXO modules.
Both dmesg and ztcfg -vvv show the FXO modules loading correctly:
-
Zaptel Version: 1.4.1
Echo Canceller: MG2
Configuration
