similar to: X100P echo problems - seem to be fixed now

After speaking with several people, and even participating in a forum of several other people with echo issues, I thought I'd share what we've done (well actually what our chief R&D engineer, Brett Bourn has done...) First let me say that normal cheapy PC hardware couldn't be made to function with out echo. We tried on both the single port Digium T1 card and the 4 port Digium T1

I notice the zaptel Makefile option the mark2 option & KFLAGS+=-DAGGRESSIVE_SUPPRESSOR is now gone. Does simply adding these options still compile in a certain echo can - or is there an other method of activating a particular can. I have not had to update my machine that is connected to pstn for a while & I don't want to jump into echotraining without a way to quickly enable what has

We have been pretty much able to solve our echo problems, except for the primary mode in which we desire to operate our system. See system diagram at bottom. Prior to making adjustments to cancel echos (all echocancel=no): Call Type Result (Before) --------- --------------- CP <- LEC PRI * TDMoE * FXO -> AP

The echo canceller algorithms aren't doing anything. We get extreme echo during the conversation, it appears even before the call connects, the echo is there... This only happens with SIP to/from WCFXO (analog POTS). Looking at the Zaptel configuration: /etc/asterisk/zapata.conf: echocancel=yes echocancelwhenbridged=yes rxgain=0.8 txgain=0.8 (although none of the above options

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

I have a pIII system with a x100p card. I've installed everything, got it working, no problems. I had a few problems with echo in calls through the X100p card so I read about enabling KFLAGS+=-DAGGRESSIVE_SUPPRESSOR in the zaptel makefile. After I did this I ran *. All I got was two flashing leds on the keyboard (scroll lock and caps lock). Everything else was frozen. So I thought,

I used to get bad echo and also voice breaking up during a conversation, so I upgraded the machine (from a PII 300 to a Athlon 1.8GHz) and have resolved the voice breaking up issues but still seem to have a fairly bad echo on *both* sides of the conversation. Currently I am only using the system for outbound calls, so I am always calling from the digium USB port phone and out to the telco using a

Hi! I currently have the X100P and TDM400P Asterisk cards. For obtaining Asterisk PBX: I have no direct connection to internet, so I use ftp and download the neweast packages: zaptel-0.7.0, libpri-0.4.0, asterisk-0.5.0. The environment I compiled the tool: PC (HP): Intel PIII 500 MHz OS: Red Hat Linux 8.0 (Upgrade from Red Hat Linux 7.1). When I compile the first package (zaptel-0.7.0), I

I'm testing out my SNOM 200 phone by trying to call out through NuFone. When I do so, I don't hear an echo at all (in fact I can't hear myself through the phone) but the callee can hear an echo when she speaks. NuFone tells me their network is totally digital and so can't be involved in an echo. This is all well and good, but the echo is still there. Any suggestions? As a

Thank you for the suggestions Andrew. I have not come across some of them before and will give them a shot. Based on my reading, changing the motherboard should have minimal impact unless that motherboard and the TDM400P don't get along (aka. IRQ sharing). I have disabled everything that is not needed and I do not believe I have any IRQ problems and I am NEVER wrong ;). Calls are crisp and

I'm sure this is a simple problem to fix. Does anyone know what might cause these errors? [eric@vulcan zaptel]$ make gcc -I/usr/src/linux-2.4/include -O6 -DMODULE -D__KERNEL__ -DEXPORT_SYMTAB -I/usr/src/linux/drivers/net -Wall -I. -Wstrict-prototypes -fomit-frame-pointer -I/usr/src/linux/drivers/net/wan -I /usr/src/linux/include -I/usr/src/linux/include/net -DMODVERSIONS -include

Just wondering if there is a reason PPP support is compiled into zapata by *default*: # Uncomment for Generic PPP support (i.e. ZapRAS) # KFLAGS+=-DCONFIG_ZAPATA_PPP Especially since the comments imply that it should be commented out by default... The main reason I ask is because I usually try to re-compile the kernel to only include the bits that I need, and so I don't include PPP...

I have compiled the zaptel library and zaprtc on a system that gives the following from "uname -a": Linux fxxxxxx76.mydomain.de 2.4.18-64GB-SMP #1 SMP Wed Mar 27 13:58:12 UTC 2002 i686 unknown Makefile for zaptel had the following line uncommented: # KFLAGS+=-D__SMP__ When doing the "make load" for zaprtc I get the following error: modprobe zaptel

Hello all, My set up is a fractionated t1, with 1-6 voice channels, 21-24 data channels. I have a t100P installed in a amd 1500 with 512meg. Question: In order to set up the data channels, is the following correct? 1) compile new kernel with generic hdlc support 2) compile hdlc from hq.pm.waw.pl/hdlc 3) uncomment KFLAGS+=DConfig_ZAPATA_NET in zaptel makefile 4) compile zaptel, 5 compile rest

Hello, I'm new to Asterisk and would like to know SIP support status. Are there any testing been done with some widely deployed client (Cisco SIP IP phone, ...)? I was using Vocal but I'm now interested in Asterisk as it seems to offer more features...if it supports SIP. Thanks for your help. Francois.

With one IVR payment system, I noticed quite a difference in DTMF transmission between these two cards. The IVR missed nearly all digits from X100P, while receiving digits from TDM fine. Since neither card process or synthesize audio, what can the difference be? (This particular IVR has problem with some regular phone devices, too.) Yuan Liu

Hello I was wondering whether anyone has managed to get an X100P card to receive Caller ID information in the UK (connected to a BT line)? I guess that it probably won't work at present because BT sends the CID information before the first ring - hence there is no event to wake up the channel. I can hear it using ztmonitor, but it is far too soon for anything to receive it. According to the

I came into this with my eyes wide open. I have read ABSOLUTELY EVERYTHING there is to be found on the net about avoiding echo problems BEFORE I even attempted to create a production system. Since lots of people are apparently using this in production environments now I just assumed that echo IS avoidable. As others have recommended, I created a test system with the proposed production

Hi, Thanks for giving me a detailed reply on hardware needs steven. I have been looking at the archives in detail and found a few people have had problems with zaptel compilation on suse(kernel-source-2.4.19.SuSE-342 // gcc 3.2.2 ) ... is shifting to red hat the only viable scenario...would be a pain cuz suse comes with sun java desktop system( just bought it !! ) ... any fixes would be a

Has anyone has issues with echo using a Wildcard with a PRI from a major Canadian Telco? (Bell, Telus, AllStream, Sprint, Group Telecom). We are using a T1 from GT that is giving use annoying echos whenever a SIP/IAX2 client calls a local analog line. Calling cells phones is no issue since its digital. Regardless, there should be no issue with echo on a PRI at all. NOC at GT is telling us