My setup is as follows:<div><br><div>Domain name is <a href="http://fs.my-domain.com">fs.my-domain.com</a>. This domain contains 2 A records pointing at IPs for <a href="http://fs1.my-domain.com">fs1.my-domain.com</a> and <a href="http://fs2.my-domain.com">fs2.my-domain.com</a>.</div><div><br></div><div>Each FreeSWITCH server, fs1 and fs2, runs the same config files and domains for the users are <a href="http://fs.my-domain.com">fs.my-domain.com</a>.</div><div>They share the same database on <a href="http://db.my-domain.com">db.my-domain.com</a>.</div><div><br></div><div>Calls going and out from each respective server, but when a user is trying to call a user who are on the same server calls fails.</div><div><br></div><div>It&#39;s random which server they land on as the dns is doing round robin dns between fs1 and fs2. </div><div>If two users lands on the same server everything works. </div><div><br></div><div>I will try and get debug info.<br><br>On Monday, November 23, 2015, Lyle Pratt &lt;<a href="mailto:lylepratt@gmail.com">lylepratt@gmail.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>We&#39;ve encountered something like this before and it ended up being a NAT issue. Users could receive calls from the server they are registered to because the registration would open a pinhole in their router. However, they could not receive calls from the other instance (no pinhole). We couldn&#39;t find a way around this.</div><div><br></div><div>I&#39;m not sure if this is your same issue, but maybe this will help debug.</div><br clear="all"><div><div><div dir="ltr">Regards,<div>Lyle Pratt</div></div></div></div>
</div>
</blockquote></div></div>