[asterisk-bugs] [LibPRI 0012153]: [patch] librpi: Data link layer does not re-establish connection as described in section 5.8.9 of Q.931

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Oct 16 14:27:22 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12153 
====================================================================== 
Reported By:                alerios
Assigned To:                mattf
====================================================================== 
Project:                    LibPRI
Issue ID:                   12153
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-03-05 15:21 CST
Last Modified:              2008-10-16 14:27 CDT
====================================================================== 
Summary:                    [patch] librpi: Data link layer does not
re-establish connection as described in section 5.8.9 of Q.931
Description: 
I'm having incoming call drops in different systems, all with the same
pattern:   

The call is established normally, with STETUP, CALL_PROCEDING, CONNECT,
and CONNECT_ACK, but then after a random while we get a DISCONNECT (cause
27) from the Telco, followed by our RELEASE and RELEASE_COMPLETE.

According to section 5.8.9 of ITU-T Q.931 (05/98), the DISCONNECT message
with cause 27 (destination out of order) is sent by the Telco wen its
internal T309 timer expires after trying to re-establish layer 2
connection.  Looking at the Q921 supervisory messages, it seems that no
frame errors are detected by libpri, or at least they are not shown.

This may be a telco side-issue related to their t309 timer, but I still
believe asterisk+libpri have something to do with it because when using an
ISDN tester or a legacy PBX the calls don't get dropped.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012861 [patch] TBR4 conformance
====================================================================== 

---------------------------------------------------------------------- 
 (0093844) alerios (reporter) - 2008-10-16 14:27
 http://bugs.digium.com/view.php?id=12153#c93844 
---------------------------------------------------------------------- 
mattf: I've using Ringing all these days and it has worked fine (The
ALERTING is sent well and call drops are now seldom seen). 

I'd say you can close this issue anytime. Thanks 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-16 14:27 alerios        Note Added: 0093844                          
======================================================================




More information about the asterisk-bugs mailing list