[asterisk-bugs] [LibPRI 0016790]: [patch] !! Got reject for frame 41, retransmitting frame 41 now, updating n_r!
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Mar 2 01:06:51 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16790
======================================================================
Reported By: alecdavis
Assigned To: mattf
======================================================================
Project: LibPRI
Issue ID: 16790
Category: General
Reproducibility: random
Severity: block
Priority: high
Status: assigned
Asterisk Version: SVN
JIRA:
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1
SVN Revision (number only!): 243988
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2010-02-09 01:25 CST
Last Modified: 2010-03-02 01:06 CST
======================================================================
Summary: [patch] !! Got reject for frame 41, retransmitting
frame 41 now, updating n_r!
Description:
Random lockups of pri.
All calls are lost for this period.
recovery requires CLI 'dahdi restart'
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0016909 [patch] pritimer's in chan_dahdi.conf n...
======================================================================
----------------------------------------------------------------------
(0118739) alecdavis (manager) - 2010-03-02 01:06
https://issues.asterisk.org/view.php?id=16790#c118739
----------------------------------------------------------------------
closing this as https://issues.asterisk.org/view.php?id=16909 fixes it.
Summary. If our Jtec ISDN switches reported a REJ I-frame, libpri goes
into retransmission, if 4 or more i-frames were sent from asterisk in quick
succession, the 1st sometimes got through.
The result was continuous retries of 4 or more i-frames, with the switch
rarely accepting the first, thus very slowly recovering, but in busy
periods it never recovered.
Issue History
Date Modified Username Field Change
======================================================================
2010-03-02 01:06 alecdavis Note Added: 0118739
======================================================================
More information about the asterisk-bugs
mailing list