similar to: Problem with wct4xxp - cannot make calls

Hi, I am about to pull my hair out after trying to get our PRI up and working. We are switching from a Cisco gateway to an Asterisk box which provides the 23 phone lines for our office. So, because the Cisco gateway is working I can assume I have all the settings right (b8zs, esf, dms100, etc) and the PRI is live (because we are switching over). When dialing from PSTN, I get busy signal. When

I have the following software installed in a Centos Box with a TE420 (5th Gen) card. . Centos 6.5 64-bit . Asterisk 1.4.22 . dahdi-linux-complete-2.9.1.1+2.9.1 . libpri-1.4.14. Even without plugging in the ISDN into span 1, all 4 spans are flashing red. Plugging an E1 into span 1 makes no difference. My system.conf is just simply: loadzone=au defaultzone=au span=1,1,0,ccs,hdb3,crc4 bchan=1-15

TE410P card down. I have three (3) TE410P in one machine running asterisk with SS7. My problems started last week when one of my cards started switching to E1 every time after reboot. I set the following in dahdi.conf and that solve the problem. /etc/modprobe.d/ options wct4xxp t1e1override=0x00 Now all 4 ports on that card is down with Red Alarm. I tried rebooting the machine and

I'm trying to install a TE410P this is what happens with compiled zaptel 1.0.9, 1.2-beta and 1.0.9 from http://updates.xorcom.com/iso/ this is my zaptel.conf (checked with the provider the values): span=1,1,0,ccs,hdb3,crc4 bchan=1-15,17-31 dchan=16 loadzone=it defaultzone=it then I modprobe wct4xxp debug=1 t1e1override=15 and the kernel says : Sep 30 16:12:40 localhost kernel: Zapata

Hello all- I have a Digium TE410P in an HP DL145 G2 dual processor server that generates well over 100,000 interrupts per second (sometimes I?ve counted 160,000+ per second) generally resulting in either the system becoming swamped and unusable or the kernel disabling the IRQ the TE410P is on resulting in the spans on that card being unusable. I have confirmed that the card is good by placing it

I've seen this consistently on three systems, with three different cards, and multiple versions of DAHDI. At first I thought the issue only occurred on newer, Nehalem-based, systems, but I reproduced it on a Core 2 Duo box as well. I've tested with dahdi-linux 2.2.0.2, dadhi- linux-complete 2.0.0+2.0.0, 2.1.0.2+2.1.0.2, and 2.2.0.2+2.2.0. The card is a Digium TE220B which uses the

Hi anyone have a idea for debug my digium TE405P card ? My zaptel.conf: span=1,1,0,ccs,hdb3 bchan=1-15,17-31 dchan=16 loadzone = fr defaultzone = fr My Zapata.conf: [channels] language=fr context=from-E1 switchtype = euroisdn pridialplan = unknown signalling = pri_cpe usecallerid=yes hidecallerid=no callwaiting=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes

So, I've compiled and installed libpri-1.4.11.5, dahdi-linux-complete-2.4.1+2.4.1 and asterisk-1.6.2.17.1, but chan_dahdi is not getting built. If I do a "make menuselect" in asterisk I see it listed with XXX, meaning that dependencies are not met. XXX chan_dahdi Depends on: res_smdi(M), dahdi(E), tonezone(E), pri(E), ss7(E), openr2(E) res_smdi gets built fine, dahdi is

Hello I just updated the kernel, dahdi-linux and dahdi-tools Im also using now asterisk 1.4.26.1 And im still with a red light (not RED/YELLOW anymore): [root at catumbela ~]# /etc/rc.d/init.d/dahdi status ### Span 1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" (MASTER) HDB3/ RED 1 PRI CAS RED 2 PRI CAS RED 3 PRI CAS RED 4 PRI

Hi I got the 2nd Gen firmware upgraded on the TE405P. I recompiled after putting in the upgraded board but did not change any conf, but the spans become active but will not come up. I guess I am missing something or are the any changes to the zaptel/libpri software that is required. I cannot find any info about this or does this new firmware only work with latest CVS. I am using 1.0.9 with

I attempted an upgrade of our production system from Asterisk/Zaptel 1.2 to 1.4 this weekend. Intially everything looked like it was working properly, but some time in the day following the upgrade, the system died to a kernel panic. I wasn't able to catch the entire kernel dump on the console unfortunately. I attempted to isolate the panic, and found that when 'service zaptel stop'

Greetings, According to the FAQ "When you load the module and have no circuit/channel bank the LED's should flash red" I get the "knight rider" lights before the module loads, but after the modules are loaded I don't get any lights, other equipment plugged in or not. The card has been on my shelf a while so I wonder if it needs a firmware upgrade ? Can the cards

The Asterisk Development Team is pleased to announce the first release of DAHDI-Linux 2.6.0 and DAHDI-Tools 2.6.0. 2.6.0 is a feature release which: - Adds support for the TE820 8-span card to the wct4xxp driver. - Decrease load time of analog cards supported by the wctdm24xxp driver. - Adds sysfs object model to facilitate persistent span numbering and early loading of modules

The Asterisk Development Team is pleased to announce the first release of DAHDI-Linux 2.6.0 and DAHDI-Tools 2.6.0. 2.6.0 is a feature release which: - Adds support for the TE820 8-span card to the wct4xxp driver. - Decrease load time of analog cards supported by the wctdm24xxp driver. - Adds sysfs object model to facilitate persistent span numbering and early loading of modules

Hi list, I'm having trouble with DTFM tones detection. Usually, some tones are being received duplicated in Asterisk, some not. As you can imagine, that's a very big problem involving IVR menu options, Meetme conferences protected with passwords, and so on. We are currently using DAHDi 2.2.0.2, module wct4xxp, which is managing a Digium TE220B card, with a hardware echo canceller

Hi list, I'm having trouble with DTFM tones detection. Usually, some tones are being received duplicated in Asterisk, some not. As you can imagine, that's a very big problem involving IVR menu options, Meetme conferences protected with passwords, and so on. We are currently using DAHDi 2.2.0.2, module wct4xxp, which is managing a Digium TE220B card, with a hardware echo canceller

Hi, I'm trying to get a TE212 working on a Dell PowerEdge 1850 running Debian etch using the latest release of libpri (1.4.0), zaptel (1.4.2.1) and asterisk (1.4.4). The initilization of the Octasic echo canceller seems to fail when the wct4xxp module is loaded. [...] VPM450: echo cancellation for 64 channels Failed to open chip, code 00103017! VPM450: Failed to initialize [...] By looking

Hi list, After a lot of testing + troubleshooting, I guess I'm observing what I am now calling a regression with zaptel 1.4.10 (is it?) As such I call for peer feedback, before either asking Digium install support or filing a bug. Thanks in advance! System: HP Proliant DL380 G5 with 2x PCI-X + 1x PCIe riser card OS: Centos 5 Kernel: 2.6.18-53.1.14.el5 (also tested under

I'm using two Rhino channel banks (first 12FXO/12FXS, second 24FXS). These connect to a Digium TE210P card. I'm running kernel 2.6.10 and I've tried Asterisk (w/zaptel) 1.0.9, 1.2 beta, and CVS from today. The results are the same for all versions: Right after I reboot, and modprobe wct4xxp, my analog phone connected to port 13 of the first channel bank (first FXS port) gets a dial

The Asterisk Development Team has announced the releases of: DAHDI-Linux-v2.9.2 DAHDI-Tools-v2.9.2 dahdi-linux-complete-2.9.2+2.9.2 This release is available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete * Mostly stability patches affecting