Hi Jerry,<br><br>Looked at your log and your problem is quiet simple to resolve, but first here's what's happenning:<br><br>You copied the conf/ subtree to your new server. As such, you have also duplicated your vars.xml. By doing so, you have set the domain on the <b>new server</b> to the same domain used on your old server which would be fine, <b>but</b> the default domain settings used by FS is to use your primary IPv4 IP address as your domain.<br>
<br>By duplicating the conf subtree from the old server, you have effectively bound the new instance of FS to a domain that is the IP address of the old server, if this makes sense.<br><br>You can see this on third line of your log:<br>
<br><b><u><span class="re0"><span class="nu0">192.168</span><span class="nu0">.72</span><span class="nu0">.29</span> Rejected by acl "domains"</span></u></b><br><br>To resolve this, modify your vars.xml on the new server to reflect whatever domain it is you want to route, or set the domain to the new server's IP address like so:<br>
<br> <X-PRE-PROCESS cmd="set" data="domain=IP_ADDRESS_OF_NEW_SERVER"/><br><br>You also need to check that any other files (e.g. the conf/sip_profiles, conf/directory/ and conf/dialplan/ hierarchy) are modified to reflect the new server settings as well.<br>
<br>In the limit, resolving those conflicts will also resolve your issues, unless there is something else that's wrong.<br><br>Let's know how you get along.<br><br>Regards,<br><br>Ahmed.<br> <br><br><div class="gmail_quote">
2010/1/4 Jerry Richards <span dir="ltr"><<a href="mailto:jerry.richards@teotech.com">jerry.richards@teotech.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Hello,<br>
<br>
I have one FS instance that is working well with a PRI and running FS<br>
version 1.0.5pre9. Originally, it was running FS version 1.0.4 and I then<br>
upgraded it.<br>
<br>
Now, I am trying to bring up another FS instance (basically a clone of the<br>
first), but the PRI does not work. When I attempt to make an<br>
internal-to-PSTN call, I get a "502 Bad Gateway" reply. I verified that<br>
both servers are using the latest Sangoma Wanpipe driver, and I copied the<br>
conf XML file tree from the old server to the new one. I think the problem<br>
has to do with the openzap module, but I'm having difficulty isolating the<br>
problem. Could it have built the openzap module incorrectly? Another<br>
difference is that I installed 1.0.5pre9 from scratch on the new server<br>
(i.e. it never had 1.0.4 running on it).<br>
<br>
I put the FS log into the pastebin when an outbound call attempt is made:<br>
<br>
<a href="http://pastebin.freeswitch.org/11675" target="_blank">http://pastebin.freeswitch.org/11675</a><br>
<br>
Could someone give me a pointer on what to try next?<br>
<br>
Thanks and Best Regards,<br>
Jerry<br>
<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Ahmed Naji<br>