[asterisk-bugs] [LibPRI 0017360]: LibPRI problem with restart of PBX processor (Testing SVN 1688)
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Aug 31 12:20:02 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17360
======================================================================
Reported By: shawkris
Assigned To: rmudgett
======================================================================
Project: LibPRI
Issue ID: 17360
Category: General
Reproducibility: have not tried
Severity: minor
Priority: normal
Status: assigned
Asterisk Version: 1.4.30
JIRA: SWP-1680
libpri Version: I did not set the version. :(
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-08-31 12:20 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.
======================================================================
----------------------------------------------------------------------
(0126478) shawkris (reporter) - 2010-08-31 12:20
https://issues.asterisk.org/view.php?id=17360#c126478
----------------------------------------------------------------------
I've done some more testing with the latest SVN of LibPRI
(SVN-branch-1.4-r1929 I think) and Asterisk 1.4.35. Although it ran OK with
our PBX out of hours, it soon failed again once the call traffic increased.
I can't see from the log which message caused the PBX to drop the link.
When the link came up, it looks like LibPRI tried to resend a message that
perhaps it shouldn't after a SABME, with the wrong N(S).
Issue History
Date Modified Username Field Change
======================================================================
2010-08-31 12:20 shawkris Note Added: 0126478
======================================================================
More information about the asterisk-bugs
mailing list