[asterisk-bugs] [LibPRI 0017360]: LibPRI problem with restart of PBX processor (Testing SVN 1688)
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue May 25 09:59:50 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17360
======================================================================
Reported By: shawkris
Assigned To:
======================================================================
Project: LibPRI
Issue ID: 17360
Category: General
Reproducibility: have not tried
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.4.30
JIRA:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!): 1688
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2010-05-19 07:57 CDT
Last Modified: 2010-05-25 09:59 CDT
======================================================================
Summary: LibPRI problem with restart of PBX processor
(Testing SVN 1688)
Description:
Asterisk is connected to legacy Siemens PBX. PBX has dual CPU and switches
over active/passive processors at (or close to) 00:00.
During the switchover, the link stays up but the PBX sends SABME. Asterisk
should clear state to restart q921. A few seconds after the first call
comes in, we see the legacy PBX drops the link and tries to re-establish -
it normally does this after a protocol error (timer expiry etc).
I will try and reproduce with pri debugging enabled.
======================================================================
----------------------------------------------------------------------
(0122381) shawkris (reporter) - 2010-05-25 09:59
https://issues.asterisk.org/view.php?id=17360#c122381
----------------------------------------------------------------------
I have been testing the SVN version of Libpri (tag 1.4.11) and experienced
the PRI dropping again. It doesn't appear that the PBX switchover is
actually the problem, but some other protocol error. I have attached the
intense debug from the span connected to the PBX.
Issue History
Date Modified Username Field Change
======================================================================
2010-05-25 09:59 shawkris Note Added: 0122381
======================================================================
More information about the asterisk-bugs
mailing list