[asterisk-bugs] [Asterisk 0014250]: [patch] Incoming calls from registrations and peer matching
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Sep 10 22:05:55 CDT 2009
The following issue has been RESOLVED.
======================================================================
https://issues.asterisk.org/view.php?id=14250
======================================================================
Reported By: Nick_Lewis
Assigned To: oej
======================================================================
Project: Asterisk
Issue ID: 14250
Category: Channels/chan_sip/General
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Asterisk Version: 1.6.0
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: no change required
Fixed in Version:
======================================================================
Date Submitted: 2009-01-15 05:58 CST
Last Modified: 2009-09-10 22:05 CDT
======================================================================
Summary: [patch] Incoming calls from registrations and peer
matching
Description:
If there are multiple sip trunks with the same ITSP then an incoming call
is arbitarily matched to the last peer with the same host IP address. This
is not a serious problem because the DID is still correct but it does have
many insidious effects due to the incorrect channel name
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
has duplicate 0014340 [patch] Calls are not matched to correc...
======================================================================
----------------------------------------------------------------------
(0110549) russell (administrator) - 2009-09-10 22:05
https://issues.asterisk.org/view.php?id=14250#c110549
----------------------------------------------------------------------
I'm closing this out since there does not appear to be anything else to do
here. It is clear that there are architecture issues to be worked on.
However, we should work on those outside of a bug report.
Thanks guys.
Issue History
Date Modified Username Field Change
======================================================================
2009-09-10 22:05 russell Note Added: 0110549
2009-09-10 22:05 russell Status assigned => resolved
2009-09-10 22:05 russell Resolution reopened => no change
required
======================================================================
More information about the asterisk-bugs
mailing list