similar to: PRI D-channel errors

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

Hi all, as good? I am trying to go up a board TE110P with link E1 ISDN PRI to establish connection with a central office Siemens HiPath 4000. But I am having the following errors: Server1:~ # asterisk -r Asterisk 1.2.10, Copyright (C) 1999 - 2006 Digium, Inc. and others. Created by Mark Spencer <markster@digium.com> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'show warranty'

Hi!, this issue makes me crazy. I read a lot of docs, also * mailling list and I try a lot of things without success. Any help will be appreciated. Here is the info: Hardware: -------------------------------------------- Supermicro Server with motherboard X7DB8, chipset Intel 5000P, Xeon 5050 Digium TE110P Software --------------------------------------------- Asterisk version 1.2.12.1

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

Hi all, After running fine for a few months now asterisk seems to hang frequently , still functioning but the DAHDI channels seem busy (users report a busy signal when calling or being called) A reboot will allow it to run for another day or maybe 2 or 3 till the problem occurs again. running stock Asterisk 1.6.2.9-2+squeeze2 on Debian with stock kernel 2.6.32-5-686 i get the following

Hi All, I am facing problem with E1 line. I have installed Asterisk (1.4.20.1) on a system with Digium TE420 card (Zaptel- 1.4.10) But every now and then I face problem of down E1's. The log show lot of entries like "pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2" This happens on a regular basis and the E1 becomes up after some time. My

Hi all, Last night I went to replace an Asterisk 1.4 + mISDN + b410p box with Asterisk 1.6.2 and DAHDI BRI - to no avail. I had two servers so copied network setting etc from the working one, moved the card across, ran dahdi_genconf etc and it didn't work. Here's the console output with notices disabled: lucas*CLI> pri intense debug span 1 Enabled debugging on span 1 [Dec 16

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

I am trying to connect two machines to each other with an T1 crossover cable. The first machine has two TE120P cards - one connecting to the telco on an ISDN PRI. The second to a crossover T1 cable to a second machine which has one TE120P card. Telco <-cA-> Machine1 <-cB-> Machine2 Machine1: Two TE120P cards Machine2: One TE120P card cA: Standard T1 Cable cB: Crossover T1

---------- Forwarded message ---------- From: Jan Prunk <janprunk at gmail.com> Date: Sep 13, 2007 3:35 PM Subject: Bad FCS error To: asterisk-users at lists.digium.com Hello ! I am getting the following error in asterisk logs: Sep 11 17:33:30 NOTICE[2187] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Sep 11 21:45:08 NOTICE[2187] chan_zap.c: PRI got event:

Hello list, We're currently facing some issues concerning T.38 gateway faxing. This is a device used almost exclusively for receiving faxes. Calls are incoming to asterisk on a SIP trunk (sangoma netborder) using G711A. Gateway mode is activated in the asterisk dialplan towards a Cisco SPA 112 running firmware 1.3.5. We are using asterisk 1.8.13.0 with the T.38 gateway patch applied (I know I

Skipped content of type multipart/alternative-------------- next part -------------- Console logs from Asterisk A: Executing Dial("SIP/test0-5821", "Zap/6/327557670||Tt") in new stack -- Requested transfer capability: 0x00 - SPEECH -- Called 6/327557670 -- Zap/6-1 is proceeding passing it to SIP/test0-5821 -- Accepting UNAUTHENTICATED call from 195.66.73.122:

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]:

I have been getting quite a bit of PRI Resets using my Quad PRI Digium card. Prior to the resets I am getting similar notices to the following chan_zap.c:7482 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 3 Telco claims the PRI's are fine on their end and that it is my unit. Is this timing? (google somewhat leads to this) I am running 1.08 asterisk zaptel

Hello, I have following problem with Sangoma A104 card: CLI> pri show span 1 Primary D-channel: 16 Status: Provisioned, Down, Active Switchtype: EuroISDN Type: CPE Window Length: 0/7 Sentrej: 0 SolicitFbit: 0 Retrans: 0 Busy: 0 Overlap Dial: 0 T200 Timer: 1000 T203 Timer: 10000 T305 Timer: 30000 T308 Timer: 4000 T313 Timer: 4000 N200 Counter: 3 NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI

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 everyone, I have been having some problems lately with our PRI and Asterisk, or maybe it is just me. It happens once maybe twice a day, but when some of our customers are calling in, the phone just drops on them. I pulled the information below from the log from one that happened. I notice why it is happening, but I can't seem to figure out a way to stop it from happening. I also

Hello, I've got a running system in which logs are full of messages such as: [Jun 10 07:24:14] NOTICE[2414] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2 The strange thing is those messages are coming from a single span. My setup is : Asterisk 1.6.1.18 Junghanns OctoBRI with wcb4xxp driver libpri 1.4.10.2 dahdi 2.3.0 3 BRI lines in PtMP mode What does this

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