[asterisk-bugs] [LibPRI 0016909]: [patch] pritimer's in chan_dahdi.conf not honoured

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16909 
====================================================================== 
Reported By:                alecdavis
Assigned To:                
====================================================================== 
Project:                    LibPRI
Issue ID:                   16909
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
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:              
====================================================================== 
Date Submitted:             2010-02-26 02:53 CST
Last Modified:              2010-03-02 16:53 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0118801) alecdavis (manager) - 2010-03-02 16:53
 https://issues.asterisk.org/view.php?id=16909#c118801 
---------------------------------------------------------------------- 
uploaded bri-k3.txt and bri-k7.txt
With libpri patch applied.

Each of these traces are 2 calls into asterisk BRI port (B410P), with
different 'k' values set in chan_dahdi.conf.

Both k=3 and k=7 worked with a B410P as a TE, to our Jtec QBRM ETSI card.

When k=3 we get <pre><b>
Couldn't transmit I frame at this time due to peer busy condition or
window shut</b>
But thats OK, it's just waiting to send. It does get through.</pre>

With k=7, could not get any errors, but I'd only connected 1 BRI port (2
channels).

dialplan to cause excessive send traffic:
[b410p]
exten => _86XX,1,Proceeding()
exten => _86XX,n,Progress()
exten => _86XX,n,Ringing()
exten => _86XX,n,Answer()
exten => _86XX,n,Playback(echo-test)
exten => _86XX,n,Echo()
exten => _86XX,n,Playback(goodbye)
exten => _86XX,n,HangUp()

Summary. Testing seems good.
I hear your concerns regarding changing 'K' while a channel is active.

Off the cuff, maybe start_pri should be init_pri, then after all user
settings have been applied, finally start it. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-02 16:53 alecdavis      Note Added: 0118801                          
======================================================================