I did a sudo /etc/init.d/freeswitch restart. That should be enough correct?<div><br><div class="gmail_quote">On Thu, Jun 28, 2012 at 4:08 PM, Joshua Nankin <span dir="ltr"><<a href="mailto:jnankin@gmail.com" target="_blank">jnankin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">sip-ip and rtp-ip in both external.xml and internal.xml were set to $${local_ip_v4}. I figured that setting the ip in vars.xml would be enough.<div>
<br></div><div>I manually set sip-ip and rtp-ip and both of those files, but that still did not solve the problem.</div>
<div><br></div><div>Any other ideas?<div><div class="h5"><br><br><div class="gmail_quote">On Thu, Jun 28, 2012 at 3:41 PM, Joshua Nankin <span dir="ltr"><<a href="mailto:jnankin@gmail.com" target="_blank">jnankin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have two interfaces on my machine, eth0=10.0.2.15 and eth1=192.168.1.7. I'm trying to get freeswitch to only use eth1. I've put the following at the top of my vars.xml:<div>
<br></div><div><X-PRE-PROCESS cmd="set" data="local_ip_v4=192.168.1.7"/></div>
<div><br></div><div>However, this does not seem to be working. When I originate a call, I see that the initial invite is originating from 10.0.2.15, but incoming packets from my sip provider are going to 192.168.1.7 and are not being responded to by freeswitch. Shouldn't freeswitch be listening on 192.168.1.7 and sending packets from there as well?</div>
<div><br></div><div>What am I doing wrong?</div><div><br></div><div> </div>
</blockquote></div><br></div></div></div>
</blockquote></div><br></div>