asterisk users - May 2004 - Losing my PRI Interface every 20-30 minutes???

Dear All,

I'm having a problem with my Asterisk + E100P Installation in UK (BT PRI). 

The system functions as expected, and my dial plan works as expected. 30
minutes (or so) after starting the asterisk service I lose the PRI line, and
only get this back after a service asterisk restart or reboot. During the
failure there is no alarm on zttool, ztcfg show all 31 lines and there are
no 'stuck' channels when I do a zap show channels. 

I'm using version 0.7.1 (need some agent features that I have patched into
this copy), on Red Hat 9.0. I have had this combination system working in my
data center in the USA since December with no problems.

I'm not sharing an IRQ cat /proc/interrupts and there are no warnings in
/var/log/messages.

Here is a copy of my Zapata and Zaptel.conf files;

The following options are switched on in my zaptel.conf;

#loadzone = us
#loadzone=it
#loadzone=fr
#loadzone=de
loadzone=uk
#loadzone=fi
#loadzone=jp
#loadzone=sp
#loadzone=no
defaultzone=uk

#Dornoch ISDN
span=1,1,0,ccs,hdb3,crc4
bchan=1-15,17-31
dchan=16

I have the following options in my Zapata.conf;

language=en
switchtype=euroisdn
;
; PRI Dialplan:  Only RARELY used for PRI.
;
; unknown:        Unknown
; private:        Private ISDN
; local:          Local ISDN
; national:	  National ISDN
; international:  International ISDN
;
; I have tried both national and unknown 
pridialplan=unknown 
; 
overlapdial=yes 
signalling=pri_cpe 
; 
usecallerid=yes 
; 
threewaycalling=yes ; 
transfer=yes echocancel=yes 
;
echocancelwhenbridged=yes 
; 
rxgain=0.0 
txgain=0.0 
;
group=1
;
callgroup=1
pickupgroup=1
immediate=no

; added this following a posting in news group
busydetect=1
busycount=7
;
context=inbound
channel => 1-15,17-31

I do see these messages in the CLI, but from what I hear they are common?

CLI error messages;

May 13 03:27:51 WARNING[1192437440]: chan_zap.c:5834 zt_pri_error: PRI: Read
on 49 failed: Unknown error 500
May 13 03:27:53 WARNING[1192437440]: chan_zap.c:5834 zt_pri_error: PRI: Read
on 49 failed: Unknown error 500
May 13 03:27:55 WARNING[1192437440]: chan_zap.c:5834 zt_pri_error: PRI: Read
on 49 failed: Unknown error 500

I would appreciate any insights from anyone who may have had and resolved a
similar problem.

Thanks

Shad Mortazavi
---------------------------------------------------
Nexus Technical Manager
n|m Nexus Management Inc 
Sydney

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20040513/4b25e010/attachment.htm

On Wed, 2004-05-12 at 23:07, Shad Mortazavi wrote:
> May 13 03:27:51 WARNING[1192437440]: chan_zap.c:5834 zt_pri_error:
> PRI: Read on 49 failed: Unknown error 500
> May 13 03:27:53 WARNING[1192437440]: chan_zap.c:5834 zt_pri_error:
> PRI: Read on 49 failed: Unknown error 500
> May 13 03:27:55 WARNING[1192437440]: chan_zap.c:5834 zt_pri_error:
> PRI: Read on 49 failed: Unknown error 500
> 
> I would appreciate any insights from anyone who may have had and
> resolved a similar problem.
This is where google is your friend. I don't know if there is a
solution, but the problem has been discussed.
http://www.google.com/search?q=Unknown+error+500+site%3Alists.digium.com


-- 
Steven Critchfield <critch@basesys.com>

I am using chan_capi 0.3.1 and I am experiencing a strange problem,


I have # transfer enabled for inbound calls to * however the * does not 
detect the
# being pressed, it is just passed out as a tone, inbound calls # transfer 
works fine.

and with every tone sent a warning appears in the console log

Unknown RTP codec 109 received


Is this a  bug in chan_capi ?



Jason Williams

Just read my own message and it is not clear.

An inbound call to * via a BRI

when the caller presses # asterisk detects # and plays transfer message

when the call recipient (on SIP) presses # the tone is sent out over the 
BRI rather than detected by *

and the error displayed as below.


Jason

At 07:32 13/05/2004 +0100, you wrote:
>I am using chan_capi 0.3.1 and I am experiencing a strange problem,
>
>
>I have # transfer enabled for inbound calls to * however the * does not 
>detect the
># being pressed, it is just passed out as a tone, inbound calls # transfer 
>works fine.
>
>and with every tone sent a warning appears in the console log
>
>Unknown RTP codec 109 received
>
>
>Is this a  bug in chan_capi ?

On Wed, 2004-05-12 at 23:07, Shad Mortazavi wrote:
> May 13 03:27:51 WARNING[1192437440]: chan_zap.c:5834 zt_pri_error:
> PRI: Read on 49 failed: Unknown error 500
I call this The Dreaded 500 Error.  You didn't search the mailing list
archives before you posted did you?  Most people do NOT get this error,
a few do.  I don't recall seeing a solution to the problem, but check
the mailing list archives.

To search the Asterisk mailing list archive go to www.google.com and put
site:lists.digium.com in addition to your other query terms.
-- 
Useful Asterisk Docs (BOOKMARK THEM!):
http://www.digium.com/index.php?menu=documentation (look at the
"Unofficial Links") and http://www.voip-info.org/wiki-Asterisk and
http://www.fnords.org/~eric/asterisk/ (my site) and
http://asteriskdocs.org/