Has Core 3 been made to behave like Core 1 with
respect to the zaptel drivers?


FC3 is different in that it uses udev. Google, #fedora on freenode.net
and the fedora list are your sources of info should you want to learn
more about udev.

Here's my notes on getting the Zaptel stuff working on Fedora Core 3:

Installation of TDM400P (1-4 port FXS/FXO modules) and X100P on FC3
             with SELinux disabled and all development tools installed

  1.  Make a symlink /usr/src/linux-2.6 -> /lib/modules/`uname -r`/build

  2.  In the shell, do:

      cd /usr/src
      export CVSROOT=:pserver:[EMAIL PROTECTED]:/usr/cvsroot
      cvs login         -- password is "anoncvs"
      cvs checkout zaptel
      cd zaptel

  3.  Copy the designated lines from README.udev into
      /etc/udev/rules.d/<filename>.rules where <filename>
      can be something like "66-zaptel.rules"

  4.  From /usr/src/zaptel, do:

        make clean; make linux26; make install         -- for 2.6 kernels

      This will put the *.ko modules in /lib/modules/<version>/misc/, and
      puts entries in /etc/modprobe.conf for all the modules that will
      run /sbin/ztcfg on each module loaded with modprobe.  The /sbin/ztcfg
      program reads /etc/zaptel.conf for config parameters.

  5.  Create /etc/zaptel.conf config file (see below)

  6.  Power down and unplug the PC

  7.  Plug in the cards and attach a power connector to the TDM400

  8.  Power on

  9.  When the hardware checker finds a new "Tiger Jet" device, just
      ignore it.  (Anyone know how to make it stop bothering me?)

 10.  Do:
         "modprobe wcfxo" for the X100P, and/or
         "modprobe wctdm" (was "wcfxs", which is now an alias) for the TDM400P.

      If they work, you should see messages like:

         Found a Wildcard FXO: Wildcard X101P              -- for the X100P
         Found a Wildcard TDM: Wildcard TDM400P REV E/F    -- for the TDM400P

       On the TDM400P, the light turns green next to the jack
       when the module is loaded,
       regardless of whether a phone is plugged in.

The hardware now is set up.  However, there is a delay in the
creation of the /dev/zap/* devices after running the modprobes
that should be taken into account when running asterisk.

Doug
_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to