similar to: Not working!

You where SOO right. My idea is to connect the "line" to my pbx and call from internet (h323?) to my linux box, and then dial an extension.. Is there any doc there? Cause Ive read a few and I did not get much really. I should configure asterisk now and the job is done? -----Mensaje original----- De: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com] En

An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20031223/62cf404e/attachment.htm -------------- next part -------------- Hello When I tried loading TDM400P module using insmod command, I get following error messages. Is there some problem with my asterisk installation. Please advise. Thanks Tony $insmod wcfxs Using

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

Hi to everybody, seems that I cannot load the zaptel modules: ztdummy says the following: [root@Hayabusa misc]# modprobe ztdummy /lib/modules/2.4.22/misc/ztdummy.o: unresolved symbol zt_unregister /lib/modules/2.4.22/misc/ztdummy.o: unresolved symbol zt_transmit /lib/modules/2.4.22/misc/ztdummy.o: unresolved symbol zt_receive /lib/modules/2.4.22/misc/ztdummy.o: unresolved symbol zt_register

Hi, I've compiled Asterisk cvs stable (few days ago) unde Suse 9.2 without any problems. We're using te110p and wcte11xp module that is autoloaded by Suse 9.2. Card goes green after reboot, but this meesages appear in logs: Mar 22 11:28:51 linux kernel: Zapata Telephony Interface Registered on major 196 Mar 22 11:28:51 linux modprobe: FATAL: Error inserting torisa

Does anyone keep a known telemarketer caller id database? If not has anyone proposed an Asterisk community project to share this information? Sort of a nation wide blacklist so Asterisk'ers can cut down on the garbage calls... -------------- next part -------------- An HTML attachment was scrubbed... URL:

I'm chasing down a pop/click type of disturbance on a PBX system. Strangely, the disturbance is only heard by the outside caller, the internal recipient hears the caller crystal clear. This seems to have crept up when upgrading the zaptel driver to the 1.2 series while running 1.0.10. I went ahead and upgraded the entire system to 1.2.4. The system is a ~2Ghz AMD 32bit system, with 512MB of

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

I get this warnings while compiling zaptel Any suggestions would be very helpfull. make -C /usr/src/linux-2.6 SUBDIRS=/usr/src/bri-stuff.0.1.0-RC4/zaptel modules make[1]: Entering directory `/usr/src/linux-2.6.8.1' CC [M] /usr/src/bri-stuff.0.1.0-RC4/zaptel/zaptel.o /usr/src/bri-stuff.0.1.0-RC4/zaptel/zaptel.c:163: warning: `fcstab' defined but not used CC [M]

I got a new motherboard and upgraded Asterisk, ... However, I am not lucky enough to get it running again. To compile went ok, besides this remark at the end of asterisk: WARNING WARNING WARNING Your Asterisk modules directory, located at /usr/lib/asterisk/modules contains modules that were not installed by this version of Asterisk. Please ensure that these modules are compatible with

- I'm not a Linux user i'm trying to get in it ... - Fedora core 1 - QuadBRI card bought from junghanns.net - We want to use the card in TE mode to connect to the TELCO - Downloaded BRISTUFF0.0.2(stable) latest from junghanss.net/asterisk - followed the instructions on voip-info.org - compiled everything still got the error when "make load" in qozap : insmod ./qozap.o

Hi list! On a newly installed RHEL 4 box I'm trying to install bristuff-0.2.0-RC8n. Everything did compile but I am running into some problems with the zaphfc driver. First of all when I load zaphfc *before* zaptel (yes I know I shouldn't do that) I get a kernel panic and the box hangs. Not so nice, especially when you are trying to fix stuff from remote locations. But ok. Now for

i have error in install module of tor2. but it compile good. what happen ? ivr2:/usr/src/zaptel # make clean; make install rm -f torisatool makefw tor2fw.h rm -f zttool rm -f *.o ztcfg tzdriver sethdlc rm -f zonedata.lo tonezone.lo libtonezone.so.1.0 *.lo rm -f gendigits tones.h rm -f libtonezone* rm -f tor2ee rm -f core cc -I. -O4 -g -Wall -DBUILDING_TONEZONE -DSTANDALONE_ZAPATA -c -o

Hi, ztdummy says the following: VoiceBOX:/usr/src/zaptel# modprobe ztdummy /lib/modules/2.4.18/misc/ztdummy.o: unresolved symbol zt_unregister /lib/modules/2.4.18/misc/ztdummy.o: unresolved symbol zt_transmit /lib/modules/2.4.18/misc/ztdummy.o: unresolved symbol zt_receive /lib/modules/2.4.18/misc/ztdummy.o: unresolved symbol zt_register /lib/modules/2.4.18/misc/ztdummy.o: insmod

Hi, I had problems described in another thread so went from a start, but now have problems when loading qozap module. I get : # insmod qozap.ko ports=9 insmod: error inserting 'qozap.ko': -1 Unknown symbol in module and in /var/log/messages: module qozap unsupported by SUSE/Novell, tainting kernel. qozap: disagrees about version of symbol zt_receive qozap: Unknown symbol zt_receive

Hi Guys I have been running a test server for a few days now with * 1.0.9 bristuff RC8n. I had a power failure and the test machine was not on the ups. When power was restored I found the following error: FATAL: Error inserting zaphfc (/lib/modules/2.6.11.4-20a-default/misc/zaphfc.ko): Unknown symbol in module, or unknown parameter (see dmesg) My dmesg output: zaphfc: unsupported

Hi Guys, Gals. Ok, so I have latest CVS sources on a debian box, 2.6.10-1-386 kernel kernel headers isntalled in the right plauce and all that stuff .. but whatever I try .. same results, I only need to get ztdummy working for a conference .. but I always end up stuffed :( heres the compile: robin@debian:~/zaptel$ make linux26 cc -I. -O4 -g -Wall -DBUILDING_TONEZONE

I tried implementing my * and it didn't pass the spouse factor at this time. I wanted to hook it up for outbound only at this point to get a better handle on the dial plans and the echo problem. I thought this might have been done before as a natural part of testing - but maybe not. In wcfxo.c I found this: if (!wc->offhook && !wc->ringdebounce) { if

Hello all. Since half december we are trying to implement * as our primary PBX. We had a test machine running with 2 sip phones and a single ISDN card. Since this was working ok, we installed * on our main Debian server. Some specs: P4 2.8 Ghz HyperThreading 512 MB RAM Debian Sid updated every week. Linux 2.6.9 vanilla kernel (not the debian package) 1 Intel Pro 100 nic for internal network 2

Hi! When I try to load the ztdummy driver via "insmod ztdummy", I get the following errors: /lib/modules/2.4.26/misc/ztdummy.o: unresolved symbol zt_unregister /lib/modules/2.4.26/misc/ztdummy.o: unresolved symbol zt_transmit /lib/modules/2.4.26/misc/ztdummy.o: unresolved symbol zt_receive /lib/modules/2.4.26/misc/ztdummy.o: unresolved symbol zt_register I'm using zaptel-1.0.8 and