[asterisk-bugs] [LibPRI 0017360]: [patch] LibPRI problem with restart of PBX processor (Testing SVN 1688)
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Aug 31 17:00:25 CDT 2010
The following issue has been UPDATED.
======================================================================
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 17:00 CDT
======================================================================
Summary: [patch] 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.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-08-31 17:00 rmudgett Summary LibPRI problem with
restart of PBX processor (Testing SVN 1688) => [patch] LibPRI problem with
restart of PBX processor (Testing SVN 1688)
======================================================================
More information about the asterisk-bugs
mailing list