Summary:	ASTERISK-03698: outboundproxy not working
Reporter:	ruok (ruok)	Labels:
Date Opened:	2005-03-17 17:50:22.000-0600	Date Closed:	2011-06-07 14:05:06
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	The global setting of 'outboundproxy' does not actually do anything. The variable is set in the code, but nothing ever uses it. Also per peer outboundproxy does not seem to be implemented right. The code indicates you cannot use host=dynamic with an outboundproxy. There are cases where this is can be useful, such as NAT traversal. What happens is that the host part of the URI is filled with the outboundproxy's IP and not the IP that the user registered with, so when the outboundproxy gets the packet, it thinks its for itself and doesnt know who to forward it on to. What I believe should be done is build the packet like normal (no outboundproxy) and when its time to send the packet on the wire, send to the outboundproxy IP instead of the registered ip. Setting the outbound proxy should not influence the content of the packet before its sent, just what IP its actually sent to. This is how chan_sip2 worked which seemed like correct behavior.
Comments:	By: Brian West (bkw918) 2005-03-17 20:49:22.000-0600 What is not working?  Please try not to post bugs like this please include some sip debug from working vs. non-working in your opinion! /b By: ruok (ruok) 2005-03-17 23:01:24.000-0600 I can't post a working config, because outboundproxy in the current chan_sip doesnt work! In chan_sip there is a variable, outboundproxyip, that is set based on the global 'outboundproxy' setting, but that variable is never used. The other part of the bug is more about methodology than a specific config example. I can show you how its putting the outboundproxy IP in the host portion of the request uri instead of the registration IP if you like? By: Olle Johansson (oej) 2005-03-18 01:11:56.000-0600 Outboundproxy was never implemented fully, that's why there's no documentation on it in sip.conf.sample. There's another bug report with a patch that I will re-open soon and start a new discussion with Mark about. By: Mark Spencer (markster) 2005-03-18 01:27:47.000-0600 if someone is directly registered to asterisk, there is clearly no need for a proxy, and using one would defeat the NAT traversal since the registration would be coming directly from the endpoint and would only open a direct path.   The global outbound proxy option is not implemented at this time.