search for: wctdm

I have an Asterisk box running Fedora Core 4, Asterisk 1.4, Lippri, 1.4, and Zaptel 1.4 The Digium cards installed are TDM2400 and TE110P. Everything was working fine until I upgraded to zaptel 1.2.12 from 1.2.9 Now when I run ztcfg I get the following error message: (CAS signalling on span 2 conflicts with Clear channel on channel 40) --NOTE: signaling was spelled wrong in the error

...commended threshold. I dropped in a TDM400P for testing, and although the timing improved, the symptom remained. The system has an IDE drive, and I verified the hdparm dma/irq settings were enabled. The TDM card was sharing interrupts, so I recompiled the kernel with APIC support. Unfortunately the wctdm module will no longer load after recompile and install into the new kernel directory. I went back to the ztdummy driver with the same problem. Below is the relevant errors and info. Chris # modprobe wctdm FATAL: Error inserting wctdm (/lib/modules/2.6.12-prep/misc/wctdm.ko): Unknown symbol in mod...

...o app_intercom.so app_saycountpl.so cdr_addon_mysql.so format_mp3.so res_config_mysql.so WARNING WARNING WARNING I cannot remember that I have seen that before. asterisk-restart Unable to connect to remote asterisk (does /var/run/asterisk.ctl exist?) FATAL: Error inserting wctdm (/lib/modules/2.6.8-24.11-default/extra/wctdm.ko): Unknown symbol in module, or unknown parameter (see dmesg) FATAL: Error running install command for wctdm vpbx:/usr/local/src/asterisk-sounds # Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk. Free...

Hi, Some weird problem (or I'm too sleepy) happens with a tdm04B revision G (4fxo) Steps: modprobe zaptel modprobe wctdm ztcfg -vv /etc/zaptel.conf fxsls=1-4 # TDM04B defaultzone=us loadzone=us /etc/asterisk/zapata.conf signalling=fxs_ls group=1 context=incoming channel => 1-4 modprobe zaptel and wctdm load fine, however ztcfg -vv shows: 0 channels configured Im using centos 4.4 with Asterisk Version 1.2.13 Za...

Hi List; If I am configuring Diguim Analoge card, then I need to run #modprobe wctdm, but the question why I need to run #modprobe zaptel also? What #modprobe zaptel does a things that #modprobe wctdm does not do? Any help? Regards Bilal ____________________________________________________________________________________ Looking for a deal? Find great prices on fligh...

...x version 2.4 (Linux kernel 2.6.18, Zaptel 1.4.7) zaptel.conf ---------------- # Autogenerated by /usr/sbin/genzaptelconf -- do not hand edit # Zaptel Configuration File # # This file is parsed by the Zaptel Configurator, ztcfg # # It must be in the module loading order # Span 1: WCTDM/0 "Wildcard TDM2400P Board 1" fxsks=1 fxsks=2 fxsks=3 fxsks=4 fxsks=5 fxsks=6 fxsks=7 fxsks=8 fxsks=9 fxsks=10 fxsks=11 fxsks=12 fxsks=13 fxsks=14 fxsks=15 fxsks=16 fxsks=17 fxsks=18 fxsks=19 fxsks=20 # channel 21, WCTDM, no module. # channel 22, WCTDM, no module. # channel 23, WCTDM, no...

Hi All; To overcome the echo problem, what mainly I have to do in the configuration other than the following line in the system.conf under dahdi directory? echocanceller=mg2,1-16 1) How can I know if the digium card supporting echo cancellator? 2) If I am getting a message in the consol that unable to enable the echo cancelator, then what does it means? The hardware is not supporting echo

...shmaker passed register test Module 0: Installed -- AUTO FXS/DPO Module 1: Installed -- AUTO FXO (FCC mode) Module 2: Installed -- AUTO FXO (FCC mode) Module 3: Installed -- AUTO FXO (FCC mode) Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules) Registered tone zone 1 (Australia) lsmod says: wctdm 30912 0 wcfxo 9344 0 zaptel 180388 2 wctdm,wcfxo ztcfg -vv says: Zaptel Version: 1.4.4 Echo Canceller: MG2 Configuration ====================== Channel map: Channel 01: FXO Loopstart (Default) (Slaves: 01) Channel 02: FXS Kewlstart (Default)...

I have linux 2.6.5 running on my machine.I downloaded The latest version of Zaptel from the cvs repoistory.Compiled zaptel with the "make linux26" option. Installed it by modprobe which gave no errors.However when i did "modprobe wctdm" i got the following error. "FATAL: Module wctdm not found." I have no idea why it's happening.Tried Googling but got nothing.ANY Suggestions??

...;m not having any trouble with interrupts, but here's my /proc/interrupts on Fedora Core 2 on a hyper-threading CPU and using the SMP kernel (2.6.5-1.138). I don't think I need to worry about uhci_hcd, nothing is plugged into USB, but libata is the disk driver. How do I get libata and wctdm to use different interrupts? $ cat /proc/interrupts CPU0 CPU1 0: 3995705 3931405 IO-APIC-edge timer 1: 530 489 IO-APIC-edge i8042 2: 0 0 XT-PIC cascade 8: 1 0 IO-APIC-edge rtc 9: 0...

...ov 20 20:51:51 DEBUG[6042]: chan_sip.c:3051 sip_rtp_read: Oooh, format changed to 256 The Call doesn't go through --- Out put of `lspci` . . 00:0a.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface . . . --- Output of `lsmod` Module Size Used by wctdm 37184 4 . . . ----- Output of /proc/zaptel/1 [root at pbx ~]# cat /proc/zaptel/1 Span 1: WCTDM/0 "Wildcard TDM400P REV H Board 1" 1 WCTDM/0/0 FXSKS (In use) 2 WCTDM/0/1 FXOKS (In use) 3 WCTDM/0/2 FXOKS (In use) 4 WCTDM/0/3 FX...

Hi, I'm experiencing an issue with my x86_64 machine containing a Hauppauge PVR-500 (ivtv) and a Digium TDM400p (wctdm, part of zaptel) PCI cards. Independently of each other both cards work fine, but once the wctdm driver is loaded and mythtv tries to record something on the PVR-500 the wctdm driver freaks out. The error message is see is "TDM PCI Master abort" printed over and over again in the syslog....

...in, * ; your manual changes will be LOST. * ; Dahdi Channels Configurations (chan_dahdi.conf) * ; * ; This is not intended to be a complete chan_dahdi.conf. Rather, it is * intended * ; to be #include-d by /etc/chan_dahdi.conf that will include the global * settings * ; * * ; Span 1: WCTDM/0 "Wildcard TDM800P Board 1" (MASTER) * ;;; line="1 WCTDM/0/0 FXSKS (SWEC: MG2)" * signalling=fxs_ks * callerid=asreceived * group=0 * context=from-pstn * channel => 1 * callerid= * group= * context=default * * ;;; line="2 WCTDM/0/1 FXSKS (SWEC: MG2)" *...

...---------------------- Contents of /etc/zaptel.conf ------------------------------------ # Autogenerated by /usr/local/sbin/genzaptelconf -- do not hand edit # Zaptel Configuration File # # This file is parsed by the Zaptel Configurator, ztcfg # # It must be in the module loading order # Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1" # channel 1, WCTDM, inactive. # channel 2, WCTDM, inactive. # channel 3, WCTDM, inactive. fxsks=4 # Global data loadzone = us defaultzone = us ------------------------------------ Contents of /etc/asterisk/zapata.conf --------------------------------...

After getting zaptel from the CVS server, compiling and installing it I type: modprobe zaptel and all is well. Then I type: modprobe wctdm and I get this: modprobe: Can't locate module wctdm Any idea why? I did this yesterday but with the CVS head of Asterisk and I got by this part without a problem. I reinstalled it all today because I wanted the stable release on our server since we use it daily for calls in our office. I a...

Hi, I've installed Asterisk with a TDM400P on a Debian Etch distro. When I reboot the server I get zaptel and wctdm automatically loaded. I'd like to avoid this behaviour. How can I disable this automatic "modprobe wctdm" during boot? Thanks Giorgio

Hello The Ubuntu Asterisk package doesn't install /etc/modprobe.d/dahdi.conf, so I was wondering where to put the following line: ======= options wctdm opermode=FRANCE ======= Should it be in /etc/dahdi/modules? ======= options wctdm opermode=FRANCE ======= Thank you.

I have a TDM400. Just updated Fedora 12 to kernel 2.6.32. Rebuilt and installed dahdi-2.2.1. kernel modules loaded. lsmod | grep wctdm wctdm 37233 0 dahdi 194985 1 wctdm lsmod | grep dahdi dahdi 194985 1 wctdm crc_ccitt 1549 2 dahdi,isdnhdlc dmesg: dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.2.1 ..... dahdi_dummy: Trying to load High R...

...ay I pulled in the latest svn of Dahdi and added the files from a recent kernel in the drivers/staging/echo structure and modified the Kbuild file so it would compile without error. I insmod'ed the module in, and modified my system.conf has echocanceller=oslec. cat /proc/dahdi/1 shows: Span 1: WCTDM/0 "Wildcard TDM410P Board 1" (MASTER) IRQ misses: 1 1 WCTDM/0/0 FXSKS (In use) (EC: OSLEC) 2 WCTDM/0/1 3 WCTDM/0/2 4 WCTDM/0/3 With the reco's from http://www.rowetel.com/ucasterisk/oslec.html#install on configuring the chan_dahdi...

...ypes of channels. Hardware is recognized without problems by operating system and DAHDI: # lspci [...] 00:0a.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface [...] # cat /proc/dahdi/* Span 1: DAHDI_DUMMY/1 "DAHDI_DUMMY/1 (source: HRtimer) 1" (MASTER) Span 2: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" 1 WCTDM/4/0 FXSKS RED 2 WCTDM/4/1 FXOKS 3 WCTDM/4/2 4 WCTDM/4/3 # dahdi_hardware pci:0000:00:0a.0 wctdm+ e159:0001 Wildcard TDM400P REV E/F # dahdi_cfg -vvvvvvv DAHDI Tools Version - 2.1.0.2 D...