I was going to suggest this too, but if it's on a LAN I'm guessing there won't be a server and serving it from httpd on the localhost would only see 127.0.0.1

...although you could lookup the current IP of the LAN interface from a script on the local webserver.

-Steve


On 15 August 2013 13:14, Raymond Chandler <intralanman@freeswitch.org> wrote:

Alternatively, you could use xml_curl to serve your configs so that you don't actually need local_ip_v4 as you can figure it out based on the IP hitting the web server. Doing that will allow you to set the IP in all of the configs that need it using functionality that already exists in FreeSWITCH today.

-Ray


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org