[asterisk-bugs] [LibPRI 0017360]: [patch] LibPRI problem with restart of PBX processor (Testing SVN 1688)
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat Sep 4 12:41:12 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-09-04 12:41 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.
======================================================================
----------------------------------------------------------------------
(0126605) shawkris (reporter) - 2010-09-04 12:41
https://issues.asterisk.org/view.php?id=17360#c126605
----------------------------------------------------------------------
I have applied the patch 1.4.11.4 and been running with with Asterisk
1.4.35 for the past few days. I haven't seen any line drops like I
previously saw, although I will keep testing.
I don't know if it's because of the patch, or just because I've got
debugging turned on, but I am seeing some protocol errors that look like
messages are bunching up. Perhaps it is just timing coincidences of user
hangups etc. I've seen a few of these. The PBX recovers OK without dropping
the pri and just increments a protocol error counter.
This is an summarised trace between the PBX and Asterisk.
[Sep 4 13:01:30] VERBOSE[16600] logger.c: > Message Type: SETUP (5)
[Sep 4 13:01:30] VERBOSE[12600] logger.c: < Message Type: ALERTING (1)
[Sep 4 13:01:52] VERBOSE[16600] logger.c: > Message Type: DISCONNECT
(69)
[Sep 4 13:01:52] VERBOSE[12600] logger.c: < Message Type: CONNECT (7)
[Sep 4 13:01:52] VERBOSE[12600] logger.c: > Message Type: CONNECT
ACKNOWLEDGE (15)
[Sep 4 13:01:52] VERBOSE[12600] logger.c: < Message Type: RELEASE (77)
[Sep 4 13:01:52] VERBOSE[12600] logger.c: > Message Type: RELEASE
COMPLETE (90)
[Sep 4 13:01:52] VERBOSE[12600] logger.c: < Message Type: STATUS (125)
[Sep 4 13:01:52] VERBOSE[12600] logger.c: < Cause (len= 5) [ Ext: 1
Coding: CCITT (ITU) standard (0) Spare: 0 Location: Private network
serving the local user (1)
[Sep 4 13:01:52] VERBOSE[12600] logger.c: < Ext: 1
Cause: Message not compatible with call state (101), class = Protocol Error
(e.g. unknown message) (6) ]
[Sep 4 13:01:52] VERBOSE[12600] logger.c: < Cause data 1: 0f (15, CONNECT
ACKNOWLEDGE message)
[Sep 4 13:01:52] VERBOSE[12600] logger.c: > Message Type: RELEASE
COMPLETE (90)
Issue History
Date Modified Username Field Change
======================================================================
2010-09-04 12:41 shawkris Note Added: 0126605
======================================================================
More information about the asterisk-bugs
mailing list