similar to: JNET's qozap, dahdi and PCI-E Quad

I have a box with 12 T1s (4 Te410P cards). The PSTN provider is reporting slips and ask me to update the clock source. I have my system.conf set as the following but when I run dahdi_scan only the ports on Card 1 are showing up with syncsrc=1 system.conf : span=1,1,0,esf,b8zs bchan=2-24 mtp2=1 span=2,2,0,esf,b8zs bchan=26-48 mtp2=25 span=3,3,0,esf,b8zs bchan=49-72

Hi, When typing dahdi_scan on an OctoBRI-enabled setup, I've got only 8 replies such as : [1] active=yes alarms=RED ... [8] active=yes ... framing=CCS I would expect 16 replies (one per B-channel). Is this correct ? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello! I am trying to configure my digium TE220 dual-span pci express card with Dahdi. I seemed to have managed to set up the card with the Dahdi kernel, as demonstrated by executing dahdi_scan: [1] active=yes alarms=RED description=T2XXP (PCI) Card 0 Span 1 name=TE2/0/1 manufacturer=Digium devicetype=Wildcard TE220 (4th Gen) location=Board ID Switch 0 basechan=1 totchans=31 irq=16

Does anyone know if I could use modprobe command to find out rather than set the jumper on a Digium PRI card? I want to find out the jumper settings on the card without opening the box which will cause down time. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I'm using Sangoma's wanpipe together with dahdi, all software downloaded today at most recent version. Hardware is Sangoma A104, a 4xE1 card. Installation went well. Anyway, wanrouter status shows a different result than dahdi_tool or dahdi_scan. I've just put a hardware loop on port 1. All the other ports are open. wanrouter status shows the expected result: Device name |

I've got an asterisk 1.4.24 box with dahdi complete 2.1.0.3+2.1.0.2 I've got a 2 port T2XXP card attached with on T1 currently plugged in. Inbound calls work fine, but outbound fail with the rather cryptic: [May 19 17:28:07] WARNING[11360]: app_dial.c:1237 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) There are similar threads I've found on the

Hi Marc, Thanks for getting back to me. Marc Muehlfeld wrote on 24-2-2015 21:12: > Hello Bram, > > Am 24.02.2015 um 12:37 schrieb Bram Matthys: >> Is there a way to re-initialize/re-provision DNS? > > No. > That would be a pitty. >> well.. I suppose since I started with 4.0.6 (migrated from Samba 3.x) but >> from a users' point of view everything

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 Bram, Am 31.01.2015 um 10:39 schrieb Bram Matthys: > Hi, > > First of all, apologies in advance to email you off-list. Hope it's ok. > I work at a high school and we use Samba4 for ~250 seats and I'm having the > same issue as you: a DNS .ldb file of 600MB. > I was searching for a way to clean these up and was wondering if you could > share your experience (what

Hi, (cc. asterisk-users, hope that is not a big Faux Pas) I've had trouble with the qozap driver for a LONG time now, where it will not recognise and ignore a missing ISDN2 line on a quad card if one of the 4 ports is unplugged or somehow faulty. The symptom is that is correctly recognises the fault, but then clears the RED ALARM almost immediately, leaving Asterisk thinking that it can call

Good day all Is there a fix for these errors yet for the junghanns cards Jul 26 17:15:05 pbx1 kernel: qozap: dropped audio card 1 cardid 0 bytes 6 z1 1 z2 107 Jul 26 17:15:18 pbx1 kernel: qozap: dropped audio card 1 cardid 0 bytes 6 z1 10 z2 116 Jul 26 17:15:18 pbx1 kernel: qozap: dropped audio card 1 cardid 0 bytes 5 z1 118 z2 97 Jul 26 17:16:33 pbx1 kernel: qozap: dropped audio card 1 cardid

Hi, In my 1.6.1.18 with dahdi 2.2.1.1, I've got : # dahdi_hardware pci:0000:01:0a.0 qozap- 1397:16b8 Junghanns OctoBRI ISDN card Does it mean I should download and use qozap or is it a bug in Dahdi ? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100412/de87e46e/attachment.htm

Hi all, Using Asterisk 1.0.10-BRIstuffed-0.2.0-RC8q with a Junghanns quadBRI (2 spans connected) and a Digium TDM400 for extensions Shouuld I be worried about these lines that keep showing up in my /var/log/messages? qozap: dropped audio card 1 cardid 0 bytes 6 z1 10 z2 116 qozap: dropped audio card 1 cardid 0 bytes 6 z1 50 z2 28 qozap: dropped audio card 1 cardid 0 bytes 6 z1 59 z2 37 .. ....

Hi, Is there a way to re-initialize/re-provision DNS? I have a working domain with 100+ users and computers etc.. I want to preserve all those users, settings and group policies etc, only start the DNS part from scratch. Why? I've been having some (mysterious) issues with Samba 4 DNS since.. well.. I suppose since I started with 4.0.6 (migrated from Samba 3.x) but from a users' point of

Hi all, I'm trying to get a junghanns QuadBRI to coexist in the same machine as a Digium TDM400P card (so I can run the ISDN lines in and bridge with analog phones plugged into the TDM). I'm having a problem loading the modules. If I follow the BRIstuff (0.3.0-pre-1l) install method.... it's to modprobe zaptel, then insmod qozap.o I'm on Debian 2.4.31. That works. But then I

Hello I'd like to configure Asterisk so that... 1. I ring it from my cellphone with CID number displayed, just to notify Asterisk that I wish to make a call 2. Asterisk waits until I hang up, calls me back, and prompts me for the number I wish to call 3. Asterisk puts me on hold through Flash(), which is apparently the equivalent of hitting the R key on European handsets 4. Asterisk calls the

I try to run QuadBRI wih X100P and TDM 4xxP. When I run them separate (ISDN or analog), they work, but together they load with no error messages (when ISDN is loaded first), but phones conected to interfaces are 'dead'. How to solve this? Maciej Kielinski

Hello, ? I have a Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] card which seems to work on 1 machine but not on another. It SHOULD load this driver: ? >dahdi_hardware -v pci:0000:00:00.0 wcb4xxp+ 1397:08b4 Junghanns QuadBRI ISDN card Instead of: >dahdi_hardware -v pci:0000:00:00.0 qozap- 1397:08b4 Generic Cologne ISDN card There is no qozap modul in

Hi All, I have a TE121P card installed and since connected it to the PRI I keep getting the Current Alarm as continually changing from Blue Alarm/Recovering and Recovering. The config I have is: /etc/dahdi/system.conf bchan=1-15,17-31 dchan=16 echocanceller=mg2,1-15,17-31 loadzone = cn defaultzone = cn /etc/asterisk/chan_dahdi.cfg [channels] Context=telco

Hi, For a significant time now (since about 0.2.0-rc8n) the qozap driver has become very verbose if an ISDN line is not connected... I get the messages below every couple of seconds in the asterisk logs. The "flaw" in the messages is the "Alarm cleared" message - The alarm cannot possibly be cleared because there is no physical media connected into that port!!! (BTW - All