Hi Ahmed, My vars.xml file does not set the literal IP address (nor the server's DNS name), rather it uses the following line (so this should not cause a problem): <X-PRE-PROCESS cmd="set" data="domain=$${local_ip_v4}"/> Also, there are no references to hard-coded addresses anywhere in the other XML files. Also, line #3 of the pastebin "IP 192.168.72.29 Rejected by acl "domains" Falling back to Digest auth." just means it is authenticating the INVITE and then it does proceed with the call. The problem is down at line #71: "zap_io.c:1197 outgoing_call method not implemented!". What does this error mean? Thank you and Best Regards, Jerry _____ From: Ahmed Naji [mailto:a.alalousi@gmail.com] Sent: Tuesday, January 05, 2010 1:40 AM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] DESTINATION_OUT_OF_ORDER Hi Jerry, Looked at your log and your problem is quiet simple to resolve, but first here's what's happenning: 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 new server to the same domain used on your old server which would be fine, but the default domain settings used by FS is to use your primary IPv4 IP address as your domain. 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. You can see this on third line of your log: 192.168.72.29 Rejected by acl "domains" 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: <X-PRE-PROCESS cmd="set" data="domain=IP_ADDRESS_OF_NEW_SERVER"/> 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. In the limit, resolving those conflicts will also resolve your issues, unless there is something else that's wrong. Let's know how you get along. Regards, Ahmed. 2010/1/4 Jerry Richards <jerry.richards@teotech.com> Hello, I have one FS instance that is working well with a PRI and running FS version 1.0.5pre9. Originally, it was running FS version 1.0.4 and I then upgraded it. Now, I am trying to bring up another FS instance (basically a clone of the first), but the PRI does not work. When I attempt to make an internal-to-PSTN call, I get a "502 Bad Gateway" reply. I verified that both servers are using the latest Sangoma Wanpipe driver, and I copied the conf XML file tree from the old server to the new one. I think the problem has to do with the openzap module, but I'm having difficulty isolating the problem. Could it have built the openzap module incorrectly? Another difference is that I installed 1.0.5pre9 from scratch on the new server (i.e. it never had 1.0.4 running on it). I put the FS log into the pastebin when an outbound call attempt is made: http://pastebin.freeswitch.org/11675 Could someone give me a pointer on what to try next? Thanks and Best Regards, Jerry _______________________________________________ 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 -- Ahmed Naji