Summary:ASTERISK-21694: Peer with outbound proxy is resolved in DNS
Reporter:Olle Johansson (oej)Labels:
Date Opened:2013-04-25 14:09:43Date Closed:
Versions: 13.18.4 Frequency of
is related toASTERISK-21231 When outboundpoxy is set, asterisk should not attempt to resolve DNS
is related toASTERISK-22666 Outbound proxy ignored after initial invite
Environment:OS/XAttachments:( 0) ASTERISK-21694.diff
Description:Defining a peer with


Asterisk still tries to resolve "oej.digium.com" - it should not. This is just a domain to use as text when creating messages, it should not be resolved. This is something I fixed a long time ago.

[Apr 25 21:08:20] ERROR[48717]: netsock2.c:269 ast_sockaddr_resolve: getaddrinfo("oej.digium.com", "(null)", ...): nodename nor servname provided, or not known
[Apr 25 21:08:20] WARNING[48717]: acl.c:590 resolve_first: Unable to lookup 'oej.digium.com'
[Apr 25 21:08:20] DEBUG[48717]: chan_sip.c:28565 build_peer: Not an IPv4 nor IPv6 address, cannot get port.
Comments:By: Joshua C. Colp (jcolp) 2013-09-13 08:54:43.026-0500

I now have a patch up for review at https://reviewboard.asterisk.org/r/2851/ which removes this requirement and returns outbound proxy support to a working state. Once complete and shipped this will be merged into all current branches. If you have time though please give this a go. I've tested it myself but more eyes on it are always good.

By: Joshua C. Colp (jcolp) 2013-11-27 18:28:14.055-0600

I've attached a patch which resolves this issue but due to lack of feedback/testing and potential regressions I am not going to commit it. If the situation changes and we become more comfortable then we can re-visit this.