[asterisk-bugs] [LibPRI 0015797]: RR storm on libpri 1.4.10.1
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Aug 31 03:52:03 CDT 2009
The following issue has been SUBMITTED.
======================================================================
https://issues.asterisk.org/view.php?id=15797
======================================================================
Reported By: tzafrir
Assigned To: mattf
======================================================================
Project: LibPRI
Issue ID: 15797
Category: General
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Asterisk Version: 1.4.26.1
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2009-08-31 03:52 CDT
Last Modified: 2009-08-31 03:52 CDT
======================================================================
Summary: RR storm on libpri 1.4.10.1
Description:
The following was tested on libpri 1.4.10.1 .
Symptom: after a while RR-s are sent frequently. More frequently than once
per 10 seconds. This is most common on BRI where providers tend to
occasionally take the connection down. But can also be reproduced by
disconnecting the line, reconnecting and allowing libpri to recover.
Note that the issue may not easily reproduce on a local [bp]ri loopback
setup, probably due to timing considerations. The problem is also
reproduced with two Asterisk servers connected through PRI.
Timer t203 is automatically scheduled at end of __q921_receive() function.
Therefore it is scheduled for example after receiving DISC, UA etc. Those
timer events are not removed and automatically rescheduled again and again
that causes eventually RR exchange each seconds instead of each 10 seconds.
Ref the attached log.
The problem was introduced in libpri 1.4 r680 (a while after 1.4.9 was
released) after call to "q921_reset(pri)" was removed from the beginning of
the "q921_dchannel_up()" function.
The problem is that the old T203 timer was never reset. Once the
connection is up, triggering it will still yield sending an RR. After a
second disconnect/reconnect we will have three timers trigerring sending
RRs, and so forth.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-08-31 03:52 tzafrir New Issue
2009-08-31 03:52 tzafrir Status new => assigned
2009-08-31 03:52 tzafrir Assigned To => mattf
2009-08-31 03:52 tzafrir Asterisk Version => 1.4.26.1
2009-08-31 03:52 tzafrir SVN Branch (only for SVN checkouts, not tarball
releases) => 1.4
2009-08-31 03:52 tzafrir Disclaimer on File? => N/A
======================================================================
More information about the asterisk-bugs
mailing list