similar to: t200_expire: q921_state now is Q921_LINK_CONNECTION_RELEASED

Hello all Asterisk 1.2.10 BRIstuff PRE-1s Debian sarge I have an issue with my ISDN-BRI line. Asterisk tells me my D-Channel is down, no matter is I have an actual line plugged in or not. == Primary D-Channel on span 1 down I somehow got it to work once! The config tools do not indicate any errors whatsoever. Here is a rundown of various listings I can think about. (some things may show

Hi, I'm trying to install a Junghanns quadbri for a few days but i stay with an asterisk error. (Everyone is busy/congested ) Asterisk is working with a Fritz PCbut from one year and now i want to add the quadbri. The quadbri card has been configured in NT mode and with no 100 ohms S/T termoination. (I'm not sure if the S/T parameter is correct) I have installed the bristuff package

Hi, I have the following happen to me after the restart of one of my servers: out of my 3 PRIs (all configured with the same technical settings), the last one isn't coming back. It's underutilized (chances it didn't get a call since my reboot), if it makes a difference . The PRI goes from provisioned to unprovisioned, and I get this regularly: [Jun 22 09:03:48]

Hi, we are trying to install Junghann's quadBRI into Dell PowerEdge 2800 system without success. I don't know if the issue can be that Junghann's card fits 32-bit slot and Dell PE 2800 has only 3 PCI-X 64-bit slots. Can this be an issue? We get "CRC errors for HDLC frame" when the card is initialized. Any idea what can be wrong? 1/ We use latest bristuff packages. 2/

Hi everyone, I'm trying to get a Sangoma A101D-X card talking to a Sasktel PRI (Megalink) circuit and having some trouble getting it to handshake. Thanks for any help or suggestions to diagnose this problem. The problem is that Asterisk has trouble bringing up the link. I see the following lines every couple of minutes: == Primary D-Channel on span 1 up == Primary D-Channel on

Hi, I'm trying to connect quadbri between powered ISDN phone and ISDN line: ISDN <---1---> TE - * - NT <--2--> Phone I use quadbri, suse 9.2 and latest 0.2.0-RC7k bristuff. I've used sample settings provided with package, but do get strange error (I think that I have wrong setting for P2P or P2MP setting and cables 1 and 2). If I connect phone to ISDN with straight cable

Hi All I have a Junghanns BRI 4 port installed where only the first channel of each line is working i.e. channels 1 and 4 work but 2 and 5 don't. Our config is the same on this box as 15 other similar installations where all works well. the only error I see is in /var/log/messages: Jun 28 15:49:31 pbxct kernel: qozap: CRC error for HDLC frame on card 1 (cardID 0) S/T port 2 Jun 28 15:51:27

Hello List, it is a very long time since I wrote here.... It has been still in Zaptel times.... Today I am run into a related problem: I can't get a DAHDI setup to work 100%. I am configuring an Astribank XR00013 (BRI, two ISDN ports). At some degree the installation (latest DAHDI drivers, Asterisk 1.6.0.18 on Centos 5.x) works. I can get incoming calls to the dialplan context that is

Hello everybody, and first of all sorry for my poor English. I'm having trouble with Quadbri installed on Asterisk 1.2.17-BRIstuffed-0.3.0-PRE-1y-e. Everything is working fine, except calling to switched off or "out of coverage" cell phones. In this case I have to wait 40 seconds until Asterisk tell me that "all circuits are busy now" instead of receive cell phone

Ok Guys, I've done a tonne of hunting around on this problem, but can't find much help. I'm running: asterisk 1.4.19.1 libpri 1.4.3 and zaptel 1.4.9.2 which I believe has been modified by RedFone to add the ztd-ethmf module. My interface is a RedFone foneBridge2 4 Span; and I'm connecting to a BT E1 PRI / ISDN30e with 15 lines on span 1, and a legacy Panasonic PBX on span 4. Upon

Hi there, I am attempting to set up a simple BRI and SIP based platform using * with the quadbri card (it's not sharing an IRQ). I enclose my zaptel and zapata.conf files. For the inital test I'm simply trying to connect to the * demo menu. The drivers compile (with a few warning that I believe aren't important - see attachments). chan_zap comiles with the warning: chan_zap.c:

Any ideas? Sangoma support is closed for the evening. I have the latest Sangoma drivers and Asterisk 1.4 everything installed. When I fire up asterisk, I keep getting "Primary D-Channel on span 1 up" repeated over and over. The B channels never come up. There are no errors in any of the logs, zttool, or the wanpipe tools. Intense pri debug output: < Unnumbered frame: < SAPI:

Hi, I'm trying to dial from one Asterisk box to a Patton 4638 BRI gateway. I'm only getting this : [May 8 15:08:24] WARNING[16797]: app_dial.c:1547 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) My setup is : Asterisk 1.6.1.18 libpri 1.4.10.2 1 Junghanns QuadBRI PCI-E express with : - driver

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

caller can't hear anything. Asterisk CLI shows: =3D=3D Primary D-Channel on span 1 down =3D=3D Primary D-Channel on span 1 up =3D=3D Primary D-Channel on span 1 down =3D=3D Primary D-Channel on span 1 up =3D=3D Primary D-Channel on span 1 down =3D=3D Primary D-Channel on span 1 up all the time. Telecom told us that problem is in our box. Fast running zttest give me: --- Results after 279

Hey, I wrote yesterday about PRI dropping, which turned out to just be a regular reset of unused B-channels. This time there's a real issue. As noted earlier I have an ISDN-30 connection, a Digium TE-121 with VPMADT032 echo cancellation. These are my configurations files: == /etc/zaptel.conf loadzone=dk defaultzone=dk span=1,1,0,css,hdb3,crc4 bchan=1-15 dchan=16 bchan=17-31 == ==

"RED: Loss of signal (LOS): The equipment shall assume "loss of signal" when the incoming signal amplitude is, for a time duration of at least 1 ms, more than 20 dB below the nominal amplitude. The equipment shall react within 12 ms by issuing AIS." This sounds like what is happening, and is in order with what one of the technicians said - I was about 20 dB below their

"RED: Loss of signal (LOS): The equipment shall assume "loss of signal" when the incoming signal amplitude is, for a time duration of at least 1 ms, more than 20 dB below the nominal amplitude. The equipment shall react within 12 ms by issuing AIS." This sounds like what is happening, and is in order with what one of the technicians said - I was about 20 dB below their

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> Hi everione,<br> <br> I'm make some test with pri timer T309. I'm using asterisk 1.4.23.1, libpri 1.4.9, dahdi-linux 2.1.0.4 and dahdi-tools 2.1.0.2. But in my tests, the timer fail with a telco

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 .. ....