[asterisk-bugs] [Asterisk 0015681]: Sip reload fails to erase old peers
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat Aug 8 08:27:40 CDT 2009
The following issue has been SUBMITTED.
======================================================================
https://issues.asterisk.org/view.php?id=15681
======================================================================
Reported By: falves11
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15681
Category: Channels/chan_sip/CodecHandling
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2
SVN Revision (number only!): 211122
Request Review:
======================================================================
Date Submitted: 2009-08-08 08:27 CDT
Last Modified: 2009-08-08 08:27 CDT
======================================================================
Summary: Sip reload fails to erase old peers
Description:
I noticed that my Asterisk was rejecting calls, but based on peer
definition that no longer existed. There was a peer of that name, with only
one codec, and Asterisk was finding it and comparing it to the new call,
wrongly, because that peer was not defined after the last sip reload, and
furthermore, it does not appear when I do a "sip show peers". This fault
will lead to unauthorized calls.
Please notice in the dialog below that peer "g723.208.78.161.210" does not
exists at that moment.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-08-08 08:27 falves11 New Issue
2009-08-08 08:27 falves11 Asterisk Version => SVN
2009-08-08 08:27 falves11 Regression => No
2009-08-08 08:27 falves11 SVN Branch (only for SVN checkouts, not tarball
releases) => 1.6.2
2009-08-08 08:27 falves11 SVN Revision (number only!) => 211122
======================================================================
More information about the asterisk-bugs
mailing list