search for: zt_qevent_lock

...inserting wctdm (/lib/modules/2.6.12-prep/misc/wctdm.ko): Unknown symbol in module, or unknown parameter (see dmesg) FATAL: Error running install command for wctdm # dmesg wctdm: disagrees about version of symbol zt_receive wctdm: Unknown symbol zt_receive wctdm: disagrees about version of symbol zt_qevent_lock wctdm: Unknown symbol zt_qevent_lock wctdm: disagrees about version of symbol zt_ec_chunk wctdm: Unknown symbol zt_ec_chunk wctdm: disagrees about version of symbol zt_transmit wctdm: Unknown symbol zt_transmit wctdm: disagrees about version of symbol zt_unregister wctdm: Unknown symbol zt_unregist...

...Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk. Freed a Wildcard module wctdm unsupported by SUSE/Novell, tainting kernel. wctdm: disagrees about version of symbol zt_receive wctdm: Unknown symbol zt_receive wctdm: disagrees about version of symbol zt_qevent_lock wctdm: Unknown symbol zt_qevent_lock wctdm: disagrees about version of symbol zt_ec_chunk wctdm: Unknown symbol zt_ec_chunk wctdm: disagrees about version of symbol zt_transmit wctdm: Unknown symbol zt_transmit wctdm: disagrees about version of symbol zt_unregister wctdm: Unknown symbol zt_unregist...

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

Good Day list, My head is pounding from google overload. Does anyone know if there is any way to park a call and specify the ("context", "Extension", and Priority) of where to call back to if the call times out and is parked too long? ParkAndAnnounce does this feature, however I do not like that it has to call you back to announce the location. I want my cake and eat it

Hello, Talking with Soren Sratje about Caller ID in Brazil, we compare ours DTMF tones captured by ztmonitor. wcfxo correctly recognize the "DTMF CLIP" and asterisk shot the AST_STATE_PRERING correctly. But the DTMF tones are not reconized. In the chan_zap.c, the code: if (f->frametype == AST_FRAME_DTMF) { (...) Does not occurs because the frametype is always reconized as voice

Hi all, I am seeing on my logs this message: Jun 13 09:14:51 DEBUG[4944] chan_zap.c: Monitor doohicky got event Event 160 on channel 3 Jun 13 09:14:51 DEBUG[4944] chan_zap.c: Monitor doohicky got event Event 160 on channel 3 (repeated much more then what I will show here). I see that it comes from static void* do_monitor(void *data) in chan_zap.c, but I do not understand what does it

...class zaptel.c:132: error: parse error before "config_must_be_included_before_module" zaptel.c:132: warning: type defaults to `int' in declaration of `config_must_be_included_before_module' zaptel.c:132: warning: data definition has no type or storage class zaptel.c: In function `zt_qevent_lock': zaptel.c:648: error: parse error before "unsigned" zaptel.c: In function `zt_reallocbufs': zaptel.c:744: error: parse error before "unsigned" zaptel.c: In function `close_channel': zaptel.c:934: error: parse error before "unsigned" zaptel.c: In function `...

...507: error: parse error before '*' token /usr/include/asm/uaccess.h:525: error: parse error before '*' token /usr/include/asm/uaccess.h:526: error: parse error before '*' token /usr/include/asm/uaccess.h:527: error: parse error before '*' token zaptel.c: In function `zt_qevent_lock': zaptel.c:657: error: parse error before "unsigned" zaptel.c: In function `zt_reallocbufs': zaptel.c:753: error: parse error before "unsigned" zaptel.c: In function `close_channel': zaptel.c:943: error: parse error before "unsigned" zaptel.c: In function `...