Jason, I have no idea either but if I assign an IP address to the network interface, say 10.0.0.3 then I may have another problem. I have a Voxeo Prophecy ASR server being assigned to 10.0.0.2. Actually both FS and Prophecy were being assigned by Windows to 10.0.0.2 but this was causing audio transfer problems when I bridged FS to Prophecy. So I wanted to assign FS to something else but I *believe* that Windows only uses one adaptor. What I need to do next I don't know (create another adaptor) and probably I've never done.

mszlazak@aol.com <mszlazak@aol.com> wrote:

> 

> I tried changing $${local_ip_v4} to a static IP in the vars.xml and internal

> and external sip_profiles files. This didn't work.



Make sure that one of your network interfaces - the one that you want

FreeSWITCH to use - is assigned that address first, otherwise there will be

nothing for FreeSWITCH to bind to when it starts.



I don't know much about Windows, so if you're running FreeSWITCH on Windows,

I'm sure there will be others on the list who are in a position to help.



If you're using Linux, just make sure that the address you want is associated

with an interface, e.g., using ifconfig, then start FreeSWITCH with the

pre-processor variable $${local_ip_v4} set appropriately.





_______________________________________________

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