On Tue, Jun 4, 2019, at 11:43 AM, Dennis Buteyn wrote:
One of our customers stumbled on this old bug in chan_sip and now we're
trying to address the problem.
It is currently tracked in Jira (ASTERISK-21231
<https://issues.asterisk.org/jira/browse/ASTERISK-21231>,
ASTERISK-21694
<https://issues.asterisk.org/jira/browse/ASTERISK-21694>) and has a
proposed patch on the review board.
We're wondering if the patch is any good and whether it can be used as
a base for finally fixing this issue on Asterisk 13?
When I made the change it did work, but it did cause behavior changes. I know
of at least one deployment that used the patch and ran into problems as a
result of the behavior change. I'd still hesitate to see it included as it
could cause even more ripples for people.
We ended up changing the trunk configuration instead, using the proxy
itself as the destination host and setting fromdomain to the
non-resolvable domain.
Dennis Buteyn
Xorcom Ltd
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
