similar to: zttool user's manual & HDLC Abort errors

Dear All, we have installed a TE410P card on a Dell Poweredge 1750 running a slackware 10 with 2.4.26 Kernel. Then we have made two loops on the card and we have configurated all the 120 channels. Our goals was to perform some stess tests even if in this scenario we used the same box as generator and target. The stress test comprised to generate up to 60 calls at the same time by placing a file

I also experienced this problem and the first thing that really helped out was changing the timing in the span line of the zaptel.conf. Change it to look like this (see below) and see if it helps out. I got the error much less after doing this and eventually got rid of the error completely by removing my raid drives, installing an IDE drive, enabling DMA mode on the Hard Drive, enabling APCI in

Hello, I have searched and searched, and come up with nothing. I am running Asterisk with a wcte110p configured for t1. Our PRI is staying up, and we can make calls however our service provider's logs are flooding with errors and we are getting lots of HDLC Abort (6) on Primary D-Channel Errors. Our provider says it looks like our box is trying to be the master timer on the circuit (which

I receive this error on the asterisk console and it is pretty much ALWAYS coming up. Sometimes there will be a break where it does not display. We had our PRI provider test the lines and they claim that there is no signalling problem. It doesn't matter if there are no calls or if there are 10 calls in progress the error is still displayed. I also get an annoying popping or clicking sound

I'm running Asterisk 1.2.26.1 svn rev 79171 on Trixbox 2.2. libpri 1.2.7 and zaptel 1.2.22.1. The hardware is a HP dl360 single cpu with a TE220B. The system load is below 0.10. I moved the server into production, with one PRI, on Friday. On that day we handled a couple thousand calls and I only saw one HDLC abort message. On Saturday half the calls and two abort messages an hour

I just upgraded my asterisk install from january 2005 CVS HEAD to current CVS HEAD : * zaptel * libpri * asterisk My asterisk have one TE405P with one span (the clock source) pluged into a telco PRI E1, a second span is a PRI E1 to another PBX and the third one is a T1 to a rhino channel bank. Everything went smoothly except that the two PRI span restart every ten seconds after some HDLC

I have 2 servers, configured identically. Each has a TE405P and 2 PRIs. One server was experiencing crackly audio on one circuit, accompanied by HDLC bad FCS messages. The telco recabled and moved me to another port on the DMS-100. The audio is better, but there are still bad FCS problems on the span. I have moved the PRI in question to the other server, and the problem does indeed move with the

Hi all, So, we reverted the LibPRI version and tested it, and then tried with the latest version of everything. Still no changes. The BRI line is in PTMP. If we set the configs to PTMP in the genconf_parameters and try it, we get the following: [Jan 21 17:32:20] ERROR[20341]: chan_dahdi.c:12645 dahdi_pri_error: Unable to receive TEI from network! If we set it to PTP (which it is not) we

I am trying to test out my PRI configuration on a server by conection another asterisk server to it. I have the T-1 cards up and both set to bchan=1-23 and dchan=24 in zaptel.conf I am getting lost on the signalling in zapata.conf. using pri_cpe makes sense for my target box, but I am getting the following errors on my source box if I use pri_net or pri_cpe signalling. May 31 17:15:06

I've read as much as I can on this error and still can't seem to figure out what's causing this error: Jun 23 20:54:58 NOTICE[7483]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 23 20:55:03 NOTICE[7483]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 23 20:55:03 NOTICE[7483]:

Hi fellow asterisk users, I am running Asterisk 1.4.29 with an Digium TE121 card (wcte12xp kernel module) an approx. 100 snom320. The whole installation is running without issues since 5 months. Without having changed anything on the asterisk server for at least 2 months, i noticed "clicking sounds" at external calls over the PRI. Asterisk constantly throws the following messages: ...

Hello Team I have installed the new DL580 and used the new TE420B to add capacity on our ivr. Before I put new E1?s I decided to first move the old e1 from the old system to this new one but it has errors which not only affect the audio quality, but also cause the asterisk to refuse any call after sometime even though the channels seems up and active {seems d-channel fails}.. When processing

UPDATE. The circuit has run clean since the 7th. It seems the telco found a problem after all but they can't tell me what they did... cause they think it was fixed as part of another case. Grrr. Well, I never doubted the T400P too much but I went ahead and bought a different card just in case. Haven't had to use it so far. One of the biggest reasons I did not think the Wildcard was at

hi folks. recently some of our customers complained about bad voice quality on the phone system. i looked at the logs and found a lot of these: [2012-11-03 08:26:38] NOTICE[11305] chan_dahdi.c: PRI got event: HDLC Abort (6) on D-channel of span 1 [2012-11-03 08:26:45] NOTICE[11305] chan_dahdi.c: PRI got event: HDLC Abort (6) on D-channel of span 1 [2012-11-03 08:26:54] NOTICE[11305]

Hi, we have a E1 pri from Citylink, (they are using Ericsson Engine exchange), that are restarting after 5 - 15 minutes, before and after that we can make calls in and out w/o problems. The cards have been tested in two computers (Atholon XP 2200+ and Celeron 2.6Ghz), are on there own IRQ, not showing any IRQ misses in zttool. It's all correctly configuered - zaptel and zapata (attached). We

Hi I am trying to connect asterisk with a Cisco GW 2600 with E1 pri using a Digium, Inc. Wildcard TE210P dual-span T1/E1/J1 card 3.3V (rev 02), Errors: [Jan 28 17:32:33] VERBOSE[6182] logger.c: == Primary D-Channel on span 1 up [Jan 28 17:32:33] WARNING[6182] chan_dahdi.c: PRI Error on span 0: We think we're the CPE, but they think they're the CPE too. [Jan 28 17:32:34] NOTICE[6182]

Hey all, I had a user complaining of calls which were dropping mid-conversation. I looked into the time of one of the calls, and saw the following: Apr 4 12:13:03 WARNING[6670] chan_zap.c: No D-channels available! Using Primary channel 28 as D-channel anyway! Apr 4 12:13:05 WARNING[6660] channel.c: Avoided initial deadlock for '0x82b8430', 10 retries! Apr 4 12:13:05 WARNING[6660]

Hi, We currently have an Asterisk box (P4 2.4 Ghz, 512Mb RAM, 1 T100P, Zhone Channel Bank and 1 E100P) connected to an ISDN running without any problems. That machine is working for about 1 year. Two days ago, we decided to switch that machine for two PowerEdge 600SC (HA) and we got some problems. The running machine (P4 2.4Ghz) has an Intel motherboard with four 32-bit 3.3v PCI slots,

Hi, I am getting this message on the * console on my first pri span. Pri show span show it is down, and I can't make any calls from the span. Apr 27 07:40:23 NOTICE[23988]: chan_zap.c:8202 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 27 07:40:23 NOTICE[23988]: chan_zap.c:8202 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 27

Hi, After upgrading to DAHDI 2.4.0 from Zaptel, I noticed a lot of HDLC errors on my console: [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [Nov 27 01:15:09] NOTICE[2743] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 These errors prevented calls from being made and received on my PRI spans. This seems