similar to: PRI Errors

Out of the blue i started receiving the following error on my PRI line which connects my asterisk server to a Norstar 0x32 key system. The asterisk zaptel.conf file was configure as follows and this config worked for 6 months until friday. Nothing was changed on either system prior to friday. here is teh zaptel.conf span=1,0,0,esf,b8zs bchan=1-23 dchan=24 span=2,0,0,esf,b8zs bchan=25-47 dchan=48

My PRI is being reset at least once a day with the following errors in the logs. zaptel, zapata, libpri, and asterisk are from CVS this morning.. This has been happening for weeks on all versions (including -stable). the T100P card appears to NOT be sharing an IRQ. xenon# cat /proc/interupts CPU0 0: 1203977 XT-PIC timer 1: 3 XT-PIC keyboard 2:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Good day eveyone, I'm hoping that someone can help me. Perhapps i'm overlooking the obvious, in truth, I hope that I am. I've scoured the mailing list and google, and haven't come up with much. I have a Digium T400P thats been connected to a channel bank for testing for some time now. all has been well. I've now just had

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

In my * server I have a T100P, connected with a T1 crossover cable to an Adtran TA750 with 2 FXO cards. After I do 'modprobe wct1xxp;ztcfg' the alarm on the card starts blinking red. Running zttool confirmed that yes, it is a red alarm. I've read a few previous posts on this type of setup and I'm not too much closer. What should I be checking next? A different cable? The

List, I have a TE410P (T1 mode, all PRI) and a T100P (fxoks, for fxs channel bank). I cannot seem to get the T100P to send any clock to the channel bank. I prefer that it use the same clock source as the TE410P, but it doesn't matter if it's not in sync just as long as it's there. The TE410P is configured 3x pri_cpe, 1x pri_net. The three cpe go to XO Sonus switch, the net to

Hello everybody, Just was wondering if somebody can help for G711 fax passthrough w/ asterisk. The issue I have is regarding codec upspeed when the call is already connected using G729 for example. The setup is fax---ATA---asterisk---Cisco---fax When codec upspeed should happen, ATA or Cisco will send a G711 reINVITE causing the codec to be switched over, but asterisk does NOT

Folks, I'm experimenting with bringing multiple (8) analog lines from our local telco into a Carrier Access ADIT 600 channel bank with an FXO module, then having this talk to Asterisk via the T1 TDM controller on the ADIT and a TE405P card. I don't know if this will work well (ie: give me decent echo cancellation, call disconnect supervision, caller ID etc) but I haven't had much

I need to know how to setup the data side of the T1 on my Linux Box. I have found information about configuring a PRI and HDLC but nothing about the Frame-Relay type setup for data. The following is information from our T1 provider. Network T1: Framing = ESF Line code = B8ZS Build out = 0-133ft(DSX)/0dB(CSU) Clock = network Pulse-density-enforce = off alarm-option = on alarm-delay = 15

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

Does anyone have any experience getting a Mitel SX-200 EL/ML PBX system to work with *? I'm not getting inbound or outbound calls to work. (Inbound caller gets line busy tone.) SETTINGS FROM MITEL: I built a Crossover cable and connected it like this: PSTN--T1--ASTRISK--T1--OLD MITEL -Crossover Cable Pin-out: 1 - 4 2 - 5

Hi, Maybe someone has seen this before... I've installed a new T100P, but it doesn't seem to work. I've attached the T100P to an Adtran 750 using a crossover cable. The Adtran shows a red alarm on the T1 interface. The Adtran has been set to factory defaults with FXS cards in 1-3 and an FXO card in 5. The T100P shows no signs of life--the leds are not lit. Should I be seeing

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

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

We are running Asterisk version 1.4.23-1, libpri-1.4.9 and zaptel-1.4.12.1 and two Digium TE220Ps. Debugs are set to 10. We have a T1 PRI connected to the telco. Over the last 4-5 days, we have getting Yellow/Red alarms coming from the T1 PRI. The other two ports in use are connected to internal test switches (Avaya Legend/Avaya Definity), and are not showing any errors.

Hi, We have got a new PRI card at one of our Office locations and now I need to install the the device on a remote server. Is there any way to know if the device is loaded already. When I give " cat /proc/zaptel/* " it returns the following. # cat /proc/zaptel/* Span 1: WCT1/0 "Wildcard TE122 Card 0" (MASTER) B8ZS/ESF RED IRQ misses: 2 1 WCT1/0/1

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

I am having a problem with a new PRI turn-up on dahdi 2.5.0 and asterisk 1.8.5 that I have not seen before. The PRI is setup as B8ZS, ESF and the span shows up and ok. This PRI is merely a crossover T1 going into an old DC0 class 5 switch. I am getting the following errors over and over again [Aug 16 10:26:10] NOTICE[8002]: chan_dahdi.c:3043 my_handle_dchan_exception: PRI got event: HDLC Bad FCS

Asterisk is getting red alarms on my T1, sometimes once or twice a day, but today it happened 5 times. Even once is too many. Every call in progress is dropped. Please help! What do I need to do? What can I try? I've googled and searched this list and can't find anything. Here's an example from the logs: Feb 7 13:37:54 WARNING[32451] chan_zap.c: Detected alarm on channel 6: Red

I'm installing TE405P card. This is my zaptel.conf. -------------------------------------- span=1,0,0,ccs,hdb3,crc4 span=2,1,0,ccs,hdb3,crc4 span=3,0,0,ccs,hdb3,crc4 span=4,0,0,ccs,hdb3,crc4 loadzone = us defaultzone= us -------------------------------------- When i modprobe wct4xxp, -------------------------------------- PCI: Found IRQ 11 for device 02:0b.0 PCI: Sharing IRQ 11 with