[asterisk-bugs] [LibPRI 0016909]: [patch] pritimer's in chan_dahdi.conf not honoured
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Mar 2 18:05:27 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16909
======================================================================
Reported By: alecdavis
Assigned To: rmudgett
======================================================================
Project: LibPRI
Issue ID: 16909
Category: Channels/chan_dahdi
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Asterisk Version: SVN
JIRA:
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1
SVN Revision (number only!): 248954
Disclaimer on File?: N/A
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2010-02-26 02:53 CST
Last Modified: 2010-03-02 18:05 CST
======================================================================
Summary: [patch] pritimer's in chan_dahdi.conf not honoured
Description:
configuring pritimer=>k,3 in chan_dahdi.conf is overwritten by libpri's
pri_default_timers, which defaults 'k' timer back to 7.
required to prevent pri lockups under heavy conditions where switch
doesn't like so many unacknowledge i-frames.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0002518 Provide configurable timers for PRI's
related to 0016790 [patch] !! Got reject for frame 41, ret...
======================================================================
----------------------------------------------------------------------
(0118804) alecdavis (manager) - 2010-03-02 18:05
https://issues.asterisk.org/view.php?id=16909#c118804
----------------------------------------------------------------------
Luckily I was able to determine what was wrong, and what needed to change,
after alot of digging and hairpulling. Seems quite simple now.
idea.
If the 'k' window size was to back off on successive retries, the apparent
'pri lockups' hopefully wouldn't appear, at least with our specific senario
anyway.
Issue History
Date Modified Username Field Change
======================================================================
2010-03-02 18:05 alecdavis Note Added: 0118804
======================================================================
More information about the asterisk-bugs
mailing list