similar to: segmentation fault

Hi all- HELP! This is actually a revisit of a problem that I had earlier with E400P's at a customer site. Customer still gets locked up channel problem, but has learned to live with it (channels clear themselves after several minutes). The symptoms, which I believe are directly related: I'm having problems with tons of framing and "read" errors on my E1 connections (and

Hi! I have the chance to play with a couple of E400P cards, each installed in a IBM e330 XSeries servers (2 x 1GHz P-III CPU 2 Gb RAM, 36Gb SCSI HDD with RH8.0 2.4.18-smp kernel), and I'm trying to test/benchmark this e330/E400P combo generating calls thru /var/spool/asterisk/outgoing One e400P if doing the carrier work making calls and the other just receives the calls: Server#1

Hello all, I got a problem at an asterisk server, with dropping calls, losing all channels and reaktivating all channels and beeing back up. This problem seems to occure randomly over the whole day, when it gots traffic on the card. After looking @ google I found several hints but none did work fine. To avoid problems with the phone line (german E1) I called the provider, he did a 45 min. route

Dear List i have upgrade my * box with the latest CVS version of Asterisk Stable 1.0 and zaptel/libpri my system is MDK9.2 with 1 TE410P and seems work well for now but i have a little amount of traffic (25 IN/OUT calls) i only notice this Warning.. What kind of error is? ------------------------------- Apr 20 21:28:49 WARNING[147466]: chan_zap.c:5979 zt_pri_error: PRI: !! Got reject for

I managed to get Asterisk working with my PBX using T1, now I am moving on to trying to make PRI work. I have my zaptel.conf and zapata.conf configured as follows: Zaptel.conf: span=1,1,0,esf,b8zs bchan=1-23 dchan=24 loadzone=us defaultzone=us Zapata.conf: [channels] transfer=yes immediate=yes callprogress=yes language=en context=default switchtype=national signalling=pri_net group=1

Hi, I'm trying to install an E1 PRI, and I need it working by Monday, but although everything seems ok, I get no response to calls. When I make a pri extense debug on span 1, I repeatedly get the following: Sending Set Asynchronous Balanced Mode Extended [ 00 01 7f ] Unnumbered frame: SAPI: 00 C/R: 0 EA: 0 TEI: 999 EA: 1 M3: 3

I just had the same exact problem this morning. The only thing I've done in the last couple of days is update update zaptel. I rolled back my zaptel to 2/11/04 from 3/8/04. And kept my libpri from 3/8/04. I never had this error before updated. I had other issues, but not this one. -sb -----Original Message----- From: asterisk-users-admin@lists.digium.com

Hi, I've got an important question: I use an E100P directly connected to PSTN, but it does not *really* work as it should be: exten => 1000,1,Dial(Zap/1/1234) BUT: It does NOT dial "1234" but it says in debug mode: -- Called 1/72976451 Apr 26 00:53:00 WARNING[10251]: chan_zap.c:5979 zt_pri_error: PRI: !! Facility message shorter than 14 bytes -- Channel 1, span 1 got

Hi, I came back from a quiet weekend today and found my E400P box to have gone astray. Asterisk is loaded from inittab, and started crashing and reloading a couple of thousands of times, each time notifying my monitoring service :-P I remember there would be issues on old cvs stuff since the crash at digium so I made a clean checkout just now. Here is what happens when I load manually:

I've got a 4 port T1 card in my Asterisk box with a PRI from Qwest as my PSTN interface. I'm experiencing random dropped calls on the various SIP devices I have tested. Network connectivity to the SIP devices looks ok, and I have tried a variety of the devices including all of the following. Grandstream 286 Grandstresm 486 Sipura SPA 1000 Mediatrix 2102 Some example lines from my logs

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: p-c.gz Type: application/octet-stream Size: 11364 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20030716/396b706e/p-c.obj

Hi, I am running * with E100P board. At least every our I got an Error 500 message and ISDN-PRI restarts: Jan 10 12:53:02 WARNING[98311]: File chan_zap.c, Line 5758 (zt_pri_error): PRI: Read on 27 failed: Unknown error 500 Jan 10 12:54:27 WARNING[98311]: File chan_zap.c, Line 5758 (zt_pri_error): PRI: Read on 27 failed: Unknown error 500 Jan 10 13:33:01 WARNING[98311]: File chan_zap.c, Line

Hi, After temporarily pulling the T1 cable out of our Asterisk box, we ended up getting a strange error messages even after the cable was plugged back in. [...] Dec 10 09:01:11 WARNING[1192437440]: File chan_zap.c, Line 5683 (zt_pri_error): PRI: Read on 63 failed: Unknown error 500 Dec 10 09:01:21 WARNING[1192437440]: File chan_zap.c, Line 5683 (zt_pri_error): PRI: Read on 63 failed: Unknown

Hi, I am having some problems mentioned below, the box is in production live environment with traffic around 30 - 100 calls. I am running T/E410P in a Dual P4 xeon with HT disabled. I am using zaptel 0.9.0 and asterisk stable 1 release. There is no gui, just mysql, perl (small script) and asterisk. System runs very smoothly if the calls are around 40-50 and comes one by one , however sometimes

Hi- I've posted this on the bugs list, but I'd also like to see if others have had similar problems when connecting via E1 trunks (E400P). I'm getting numerous errors like the following during inbound calls to my E1 channels. These occur when the system is under medium load: WARNING[196621]: File chan_zap.c, Line 5404 (zt_pri_error): PRI: !! Got reject for frame 78, retransmitting

hi guys, I have a little problem maybe you can help ... I have an asterisk setup, with an E100P, and an ISDN-PRI 30 channel line from the telco going into it .. the E1 line is OK, because plugged into a Lucent Portmaster 4 it works OK .. plugged into the asterisk box I just get an engaged tone, and asterisk posts this message on screen : WARNING[1167272000]: File chan_zap.c, Line 5275

Greetings. Today I've installed a fresh new E100P on a EuroISDN PRI. It seems to work well, accepting calls, but, when I start *, I have the screen flooded with this message: PRI got event: 8 (or 6) If i look into /var/log/asterisk/messages i've this Error: File chan_zap.c, Line 5341 (zt_pri_error): PRI: Read on 35 failed: Unknown error 500 Repeated indefinitely. Also, i've a

Hello... Does anybody knows what is the meaning of thoose messages ? What i'm doing wrong here ? The * works fine , both incoming and outgoing services.. WARNING[163851]: File chan_zap.c, Line 5683 (zt_pri_error): PRI: Read on 47 failed: Unknown error 500 PRI got event: 8 WARNING[163851]: File chan_zap.c, Line 5683 (zt_pri_error): PRI: Read on 47 failed: Unknown error 500 PRI got event: 6

Hi, I'm installing E100P for isdn pri line. My configuration are like this. zaptel.conf ======================================= span=1,0,0,ccs,hdb3,crc4 loadzone = us defaultzone=us bchan=1-15 dchan=16 bchan=17-31 zapata.conf ================================================= [channels] context=default switchtype=euroisdn context=default signalling=pri_net usecallerid=yes

I have not been able to get two B-channel transfer to work on DMS100 PRI. I consistently get the following errors: [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: ROSE RETURN ERROR: [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: OPERATION: RLT_OPERATION_IND [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: ERROR: RLT Not Allowed I have tried on two