[asterisk-bugs] [LibPRI 0012558]: releasing incoming calls with cause 34 in spite of available b-channels

noreply at bugs.digium.com noreply at bugs.digium.com
Fri May 2 02:09:48 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12558 
====================================================================== 
Reported By:                fastbusy
Assigned To:                mattf
====================================================================== 
Project:                    LibPRI
Issue ID:                   12558
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 114120M 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-30-2008 12:31 CDT
Last Modified:              05-02-2008 02:09 CDT
====================================================================== 
Summary:                    releasing incoming calls with cause 34 in spite of
available b-channels
Description: 
Seemingly during higher load, machines are not processing incoming (PRI
from pstn) calls correctly. The issue does not surface on all (identically
placed)calls, only on some.

of ten test calls made from the pstn to the machine, up to four will be
"dropped."

The machine is releasing with cause 34, even though b-channels are
available. Hopefully relevant Pri debug attached.

The failed calls never reach the dialplan, or the verbose console. (no
"Accepting Incoming call.") They only appear in PRI Intense Debug.
====================================================================== 

---------------------------------------------------------------------- 
 fastbusy - 05-02-08 02:09  
---------------------------------------------------------------------- 
version info
zaptel 1.4.10
libpri  1.4.3

Additionally, restarting zaptel/asterisk "fixes" the problem, it
resurfaces again after a day or two. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-02-08 02:09  fastbusy       Note Added: 0086302                          
======================================================================




More information about the asterisk-bugs mailing list