|DEdwards at vertical.com
|Posted: Wed Feb 17, 2016 4:46 pm Post subject: [Freeswitch-users] Can FS offer both internal & external
|‘based on the request’ is what’s actually causing the problem. Since the requests come through a proxy, every ‘remote_ip’ is always the local IP, so FS cannot make a determination based on that. I added a deny to the local IP which caused FS to offer the external IP and we can make that work if our customers turn on the NAT reflection.
As a test, I modified switch_core_media.c:generate_m to throw in the local IP and that did fix our issue. I was hoping for a configuration option.
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Brian West
Sent: Wednesday, February 17, 2016 4:34 PM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] Can FS offer both internal & external IP address?
Actually no, what you do in this case is set the local-network-acl, it will then know which one to use based on the request.
On Wed, Feb 17, 2016 at 3:16 PM, Dan Edwards <DEdwards@vertical.com (DEdwards@vertical.com)> wrote:
I'm running FS behind Nginx, so I explicitly removed the local IP address from localnet.auto. This forces FS to always offer 'ext-rtp-ip'. Outside users work fine in that scenario.
Internal users also work, as long as we turn on NAT reflection in our router. I'm looking for a way to not require that router change.
If I can get FS to offer up both it's internal IP and 'ext-rtp-ip' as candidates in the initial INVITE, the browser could then use ICE to determine which IP address was correct.
Is there a way to offer both and allow ICE on the client side to figure out which one to use?
Professional FreeSWITCH Consulting Services:
Official FreeSWITCH Sites
FreeSWITCH-users mailing list
Twitter: @FreeSWITCH , @briankwest
Got Bugs? Report them here! | Reddit: /r/freeswitch
T:+19184209001 | F:+19184209002 | M:+1918424WEST (9378)
iNUM:+883 5100 1420 9001 | ISN:410*543 | Skype:briankwest