On 1/19/2016 4:13 PM, Jason Bedward wrote:
Sorry I'm confused is it working now?The way I have things is opensips ip is the proxy. When freeswitch see it its like hey, I know you, I need to look out for the other ip you have X-Auth and process that. Freeswitch then looks up the X-Auth ip as it that was the IP that initiated the session....On Tue, Jan 19, 2016 at 9:10 PM, Tim King <t...@triton.net <mailto:t...@triton.net>> wrote:This is the intended behavior I was requesting. The purpose of the ACL setup is to only allow calls through that are in the list of IP's set to allow. The same way you would with Freeswitch without a proxy. The relationship I was looking for that apparently does not exist is where you tell freeswitch which list to use for the proxy-acl. Apparently there is no relationship between them it just searches all the lists to see if ti finds a match? I'm not really sure all I know is at this point if I put the IP's of the addresses I wish to allow in the last list in my acl.conf which happens to be names opensips the calls are allowed. If I take the IP out they are rejected... Thank you very much for your help. _______________________________________________ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<<attachment: tim.vcf>>
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
