Summary:	ASTERISK-01562: [design] Outbound Proxy Implementation in chan_sip
Reporter:	khb (khb)	Labels:
Date Opened:	2004-05-08 05:17:07	Date Closed:	2011-06-07 14:05:26
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/NewFeature
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	This track is for the discussion and posting of forthcoming patch for outbound proxy support in chan_sip
Comments:	By: khb (khb) 2004-05-08 05:26:35 twisted  wrote (in another track): >This is nice, but what about a per-peer/user override? This would be >uber-helpful when dealing with places that try to lock you into their device based on UA. I am not sure what you mean by per peer OVERRIDE. it is configurable on an individual basis for each provider, is that what you mean?  What do you mean by "locking you into their device based UA". Would you elaborate please. There are several possible different outbound proxy configurations/situations. That's why this implementation should be discussed and planned and all needed specifications collected. By: Olle Johansson (oej) 2004-05-08 14:41:18 I don't think twisted comments was about outbound proxy. khb: For outbound proxy, we need it settable both as a [general] setting and a [peer] setting both for registers and normal peers. As stated before, there's a non-tested and propably non-complete implementation of outbound proxy support in chan_sip2. I think the right way is to only apply outbound proxy for outbound INVITEs and REGISTERs. The rest of the transactions should be handled by record-routes etc. We could also have a general setting that sets "use outbound proxy only for hosts not on our local network".