On Wed, 09 Jan 2008 08:32:40 -0600, "Darrick Hartman (lists)"
<[EMAIL PROTECTED]> wrote:
>Uncomment that if you expect it to work. The module should be listed in
>ZAPMODS not in rc.modules. [...] Since you have ZAPMODS commented out,
> the zaptel init script doesn't know which modules it should b
Vincent wrote:
> On Wed, 09 Jan 2008 06:01:32 -0600, "Darrick Hartman (lists)"
> <[EMAIL PROTECTED]> wrote:
>> But look in your /etc/rc.conf file for the ZAPMODS variable. You should
>> have that variable set to:
>>
>> ZAPMODS="wctdm"
>
> Yes indeed:
>
> #ZAPMODS="wctdm"
>
> Should I add this
On Wed, 09 Jan 2008 06:01:32 -0600, "Darrick Hartman (lists)"
<[EMAIL PROTECTED]> wrote:
>But look in your /etc/rc.conf file for the ZAPMODS variable. You should
>have that variable set to:
>
>ZAPMODS="wctdm"
Yes indeed:
#ZAPMODS="wctdm"
Should I add this module here, or in rc.modules?
Are we
Vincent wrote:
> On Wed, 9 Jan 2008 12:05:34 +0200, Tzafrir Cohen
> <[EMAIL PROTECTED]> wrote:
>> wcfxo is not needed.
>>
>> Basically all you need is:
>>
>> modprobe
>>
>> This also pulls all of its dependencies (e.g: zaptel)
>>
>> modprobe wctdm
>
> Thanks, but on AstLinux, the modules are no
On Wed, Jan 09, 2008 at 12:26:46PM +0100, Vincent wrote:
> On Wed, 9 Jan 2008 12:05:34 +0200, Tzafrir Cohen
> <[EMAIL PROTECTED]> wrote:
> >wcfxo is not needed.
> >
> >Basically all you need is:
> >
> > modprobe
> >
> >This also pulls all of its dependencies (e.g: zaptel)
> >
> > modprobe wctdm
On Wed, 9 Jan 2008 12:05:34 +0200, Tzafrir Cohen
<[EMAIL PROTECTED]> wrote:
>wcfxo is not needed.
>
>Basically all you need is:
>
> modprobe
>
>This also pulls all of its dependencies (e.g: zaptel)
>
> modprobe wctdm
Thanks, but on AstLinux, the modules are not unloaded:
===
pbx admin # /e
On Wed, Jan 09, 2008 at 10:42:52AM +0100, Vincent wrote:
> BTW, is there an order when loading modules for a TDM card? The
> OpenVox seems to need zaptel, wctdm, and wcfxo, so I just run this:
>
> # modprobe zaptel
> # modprobe wctdm
> # modprobe wcfxo
wcfxo is not needed.
Basically all you nee
On Tue, 08 Jan 2008 13:43:50 -0500, Jared Smith <[EMAIL PROTECTED]>
wrote:
>I always find that looking at the files that are generated
>under /proc/zaptel is very enlightening as far as showing what the
>zaptel drivers are seeing.
Thanks for the tip.
_
On Tue, 8 Jan 2008 20:29:20 +0200, Tzafrir Cohen
<[EMAIL PROTECTED]> wrote:
>This change is simply due to different versions of Zaptel. Zaptel >=
>1.4.6 prints "to configure" because this message is printed (and has
>always been prinetd) before the configuration is actually applied.
Good to know :
On Tue, 2008-01-08 at 19:06 +0100, Vincent wrote:
> Are "dmesg", "lspci -v", "ztcfg -vv" and "zttool" the only tools
> available to investigate this issue?
I always find that looking at the files that are generated
under /proc/zaptel is very enlightening as far as showing what the
zaptel drivers a
On Tue, Jan 08, 2008 at 07:06:17PM +0100, Vincent wrote:
> Hello
>
> Since TDM cards are known for being particular when it comes
> to motherboards (PCI 2.2, etc.), I was wondering if there is a utility
> that can check that the Zaptel driver works OK and can tell if the TDM
> card is compat
Hello
Since TDM cards are known for being particular when it comes
to motherboards (PCI 2.2, etc.), I was wondering if there is a utility
that can check that the Zaptel driver works OK and can tell if the TDM
card is compatible?
That way, if an FXO module is not reporting an incoming call
12 matches
Mail list logo
