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
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
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
On Mon, Jan 4, 2010 at 3:49 PM, Jerry Richards <jerry.richards@teotech.com>wrote:
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?
Jerry, I noticed this line: (OpenZAP/1:1/3491028@g1) Is your carrier wanting full ten digit phone numbers? Try adding the area code on this and see what happens. The error usually would be something like "invalid number format" but I've seen carriers do stupid things like this. Try that first and see if it makes a difference. If not you'll need to turn on Q931 debugging as per the Sangoma wiki. (See http://wiki.freeswitch.org/wiki/OpenZAP#Debugging_PRI_With_wanpipemon for the link.) -MC
When I attempt an internal-to-PSTN call, there are no Q931 packets sent out the PRI (I confirmed this using the Sangoma wanpipemon utility). I suspect this has something to do with my XML configuration. Below are my openzap/wanpipe configurations (which should all be defaulted). Do you seen anything wrong with these defaults, which might cause the following FS console error? zap_io.c:1197 outgoing_call method not implemented! openzap.conf: [span wanpipe smg_prid] name => smg_prid trunk_type =>t1 b-channel => 1:1-23 autoload_configs/openzap.conf.xml: <configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="9"/> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> </settings> <boost_spans> <span id="smg_prid"> <!--<param name="hold-music" value="$${moh_uri}"/>--> <param name="dialplan" value="XML"/> <param name="context" value="default"/> <!-- regex to stop dialing when it matches --> <!--<param name="dial-regex" value="5555"/>--> <!-- regex to stop dialing when it does not match --> <!--<param name="fail-dial-regex" value="^5"/>--> </span> </boost_spans> <analog_spans> </analog_spans> </configuration> wanpipe.conf: [defaults] codec_ms => 20 wink_ms => 150 flash_ms => 750 Thanks and Best Regards, Jerry _____ From: Michael Collins [mailto:msc@freeswitch.org] Sent: Tuesday, January 05, 2010 4:33 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] DESTINATION_OUT_OF_ORDER On Mon, Jan 4, 2010 at 3:49 PM, Jerry Richards <jerry.richards@teotech.com> wrote: 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? Jerry, I noticed this line: (OpenZAP/1:1/3491028@g1) Is your carrier wanting full ten digit phone numbers? Try adding the area code on this and see what happens. The error usually would be something like "invalid number format" but I've seen carriers do stupid things like this. Try that first and see if it makes a difference. If not you'll need to turn on Q931 debugging as per the Sangoma wiki. (See http://wiki.freeswitch.org/wiki/OpenZAP#Debugging_PRI_With_wanpipemon for the link.) -MC
I have an A104D on a box here. I'll need some time but I will see if I can reproduce your symptoms. I'll let you know what I find out. -MC On Wed, Jan 6, 2010 at 9:59 AM, Jerry Richards <jerry.richards@teotech.com>wrote:
When I attempt an internal-to-PSTN call, there are no Q931 packets sent out the PRI (I confirmed this using the Sangoma wanpipemon utility). I suspect this has something to do with my XML configuration. Below are my openzap/wanpipe configurations (which should all be defaulted). Do you seen anything wrong with these defaults, which might cause the following FS console error?
zap_io.c:1197 outgoing_call method not implemented!
*openzap.conf: *[span wanpipe smg_prid] name => smg_prid trunk_type =>t1 b-channel => 1:1-23
*autoload_configs/openzap.conf.xml:* <configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="9"/> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> </settings> <boost_spans> <span id="smg_prid"> <!--<param name="hold-music" value="$${moh_uri}"/>--> <param name="dialplan" value="XML"/> <param name="context" value="default"/> <!-- regex to stop dialing when it matches --> <!--<param name="dial-regex" value="5555"/>--> <!-- regex to stop dialing when it does not match --> <!--<param name="fail-dial-regex" value="^5"/>--> </span> </boost_spans> <analog_spans> </analog_spans> </configuration>
*wanpipe.conf:* [defaults] codec_ms => 20 wink_ms => 150 flash_ms => 750
Thanks and Best Regards, Jerry
------------------------------ *From:* Michael Collins [mailto:msc@freeswitch.org] *Sent:* Tuesday, January 05, 2010 4:33 PM *To:* freeswitch-users@lists.freeswitch.org *Subject:* Re: [Freeswitch-users] DESTINATION_OUT_OF_ORDER
On Mon, Jan 4, 2010 at 3:49 PM, Jerry Richards <jerry.richards@teotech.com
wrote:
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?
Jerry, I noticed this line: (OpenZAP/1:1/3491028@g1)
Is your carrier wanting full ten digit phone numbers? Try adding the area code on this and see what happens. The error usually would be something like "invalid number format" but I've seen carriers do stupid things like this. Try that first and see if it makes a difference. If not you'll need to turn on Q931 debugging as per the Sangoma wiki. (See http://wiki.freeswitch.org/wiki/OpenZAP#Debugging_PRI_With_wanpipemon for the link.)
-MC
_______________________________________________ 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
I capured logs of my FS startup and put them into the pastebin (http://pastebin.freeswitch.org/11692). At line 722, I see some errors: 2010-01-06 11:42:49.907861 [ERR] zap_io.c:2562 Error loading /usr/local/freeswitch/mod/ozmod_sangoma_boost.so [/usr/local/freeswitch/mod/ozmod_sangoma_boost.so: cannot open shared object file: No such file or directory] 2010-01-06 11:42:49.907883 [ERR] zap_io.c:2722 can't find 'sangoma_boost 2010-01-06 11:42:49.907902 [ERR] mod_openzap.c:2379 Error starting OpenZAP span 1 error 2010-01-06 11:42:49.907929 [CONSOLE] switch_loadable_module.c:890 Successfully Loaded [mod_openzap] Do you know why I would get this? Where is the ozmod_sangoma_boost.so file supposed to come from? Thanks, Jerry _____ From: Jerry Richards [mailto:jerry.richards@teotech.com] Sent: Wednesday, January 06, 2010 10:00 AM To: 'freeswitch-users@lists.freeswitch.org' Subject: RE: [Freeswitch-users] DESTINATION_OUT_OF_ORDER When I attempt an internal-to-PSTN call, there are no Q931 packets sent out the PRI (I confirmed this using the Sangoma wanpipemon utility). I suspect this has something to do with my XML configuration. Below are my openzap/wanpipe configurations (which should all be defaulted). Do you seen anything wrong with these defaults, which might cause the following FS console error? zap_io.c:1197 outgoing_call method not implemented! openzap.conf: [span wanpipe smg_prid] name => smg_prid trunk_type =>t1 b-channel => 1:1-23 autoload_configs/openzap.conf.xml: <configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="9"/> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> </settings> <boost_spans> <span id="smg_prid"> <!--<param name="hold-music" value="$${moh_uri}"/>--> <param name="dialplan" value="XML"/> <param name="context" value="default"/> <!-- regex to stop dialing when it matches --> <!--<param name="dial-regex" value="5555"/>--> <!-- regex to stop dialing when it does not match --> <!--<param name="fail-dial-regex" value="^5"/>--> </span> </boost_spans> <analog_spans> </analog_spans> </configuration> wanpipe.conf: [defaults] codec_ms => 20 wink_ms => 150 flash_ms => 750 Thanks and Best Regards, Jerry _____ From: Michael Collins [mailto:msc@freeswitch.org] Sent: Tuesday, January 05, 2010 4:33 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] DESTINATION_OUT_OF_ORDER On Mon, Jan 4, 2010 at 3:49 PM, Jerry Richards <jerry.richards@teotech.com> wrote: 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? Jerry, I noticed this line: (OpenZAP/1:1/3491028@g1) Is your carrier wanting full ten digit phone numbers? Try adding the area code on this and see what happens. The error usually would be something like "invalid number format" but I've seen carriers do stupid things like this. Try that first and see if it makes a difference. If not you'll need to turn on Q931 debugging as per the Sangoma wiki. (See http://wiki.freeswitch.org/wiki/OpenZAP#Debugging_PRI_With_wanpipemon for the link.) -MC
You need to make sure you have SCTP libs installed and dev env to compile it. /b On Jan 6, 2010, at 1:52 PM, Jerry Richards wrote:
I capured logs of my FS startup and put them into the pastebin (http://pastebin.freeswitch.org/11692). At line 722, I see some errors:
2010-01-06 11:42:49.907861 [ERR] zap_io.c:2562 Error loading /usr/local/freeswitch/mod/ozmod_sangoma_boost.so [/usr/local/freeswitch/mod/ozmod_sangoma_boost.so: cannot open shared object file: No such file or directory] 2010-01-06 11:42:49.907883 [ERR] zap_io.c:2722 can't find 'sangoma_boost 2010-01-06 11:42:49.907902 [ERR] mod_openzap.c:2379 Error starting OpenZAP span 1 error 2010-01-06 11:42:49.907929 [CONSOLE] switch_loadable_module.c:890 Successfully Loaded [mod_openzap]
Do you know why I would get this? Where is the ozmod_sangoma_boost.so file supposed to come from?
Thanks, Jerry
By the way, I posted another pastebin log (http://pastebin.freeswitch.org/11694) that shows the output of the "make" and "make install sounds-install moh-install..." commands. Just prior to these makes I executed "make clean" and "make distclean". You will notice in the makefile output that ozmod_sangoma_boost.c never appears to get compiled. Shouldn't everything be compiled in this case? I also confirmed that my working server does have the ozmod_sangoma_boost.so file located in the right place, which is why it's working. Could version 1.0.5pre9 introduced this bug? Could that be why the older server (which original ran with 1.0.4) works and the new one doesn't? Thanks and Best Regards, Jerry _____ From: Jerry Richards [mailto:jerry.richards@teotech.com] Sent: Wednesday, January 06, 2010 11:52 AM To: 'freeswitch-users@lists.freeswitch.org' Subject: RE: [Freeswitch-users] DESTINATION_OUT_OF_ORDER I capured logs of my FS startup and put them into the pastebin (http://pastebin.freeswitch.org/11692). At line 722, I see some errors: 2010-01-06 11:42:49.907861 [ERR] zap_io.c:2562 Error loading /usr/local/freeswitch/mod/ozmod_sangoma_boost.so [/usr/local/freeswitch/mod/ozmod_sangoma_boost.so: cannot open shared object file: No such file or directory] 2010-01-06 11:42:49.907883 [ERR] zap_io.c:2722 can't find 'sangoma_boost 2010-01-06 11:42:49.907902 [ERR] mod_openzap.c:2379 Error starting OpenZAP span 1 error 2010-01-06 11:42:49.907929 [CONSOLE] switch_loadable_module.c:890 Successfully Loaded [mod_openzap] Do you know why I would get this? Where is the ozmod_sangoma_boost.so file supposed to come from? Thanks, Jerry _____ From: Jerry Richards [mailto:jerry.richards@teotech.com] Sent: Wednesday, January 06, 2010 10:00 AM To: 'freeswitch-users@lists.freeswitch.org' Subject: RE: [Freeswitch-users] DESTINATION_OUT_OF_ORDER When I attempt an internal-to-PSTN call, there are no Q931 packets sent out the PRI (I confirmed this using the Sangoma wanpipemon utility). I suspect this has something to do with my XML configuration. Below are my openzap/wanpipe configurations (which should all be defaulted). Do you seen anything wrong with these defaults, which might cause the following FS console error? zap_io.c:1197 outgoing_call method not implemented! openzap.conf: [span wanpipe smg_prid] name => smg_prid trunk_type =>t1 b-channel => 1:1-23 autoload_configs/openzap.conf.xml: <configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="9"/> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> </settings> <boost_spans> <span id="smg_prid"> <!--<param name="hold-music" value="$${moh_uri}"/>--> <param name="dialplan" value="XML"/> <param name="context" value="default"/> <!-- regex to stop dialing when it matches --> <!--<param name="dial-regex" value="5555"/>--> <!-- regex to stop dialing when it does not match --> <!--<param name="fail-dial-regex" value="^5"/>--> </span> </boost_spans> <analog_spans> </analog_spans> </configuration> wanpipe.conf: [defaults] codec_ms => 20 wink_ms => 150 flash_ms => 750 Thanks and Best Regards, Jerry _____ From: Michael Collins [mailto:msc@freeswitch.org] Sent: Tuesday, January 05, 2010 4:33 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] DESTINATION_OUT_OF_ORDER On Mon, Jan 4, 2010 at 3:49 PM, Jerry Richards <jerry.richards@teotech.com> wrote: 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? Jerry, I noticed this line: (OpenZAP/1:1/3491028@g1) Is your carrier wanting full ten digit phone numbers? Try adding the area code on this and see what happens. The error usually would be something like "invalid number format" but I've seen carriers do stupid things like this. Try that first and see if it makes a difference. If not you'll need to turn on Q931 debugging as per the Sangoma wiki. (See http://wiki.freeswitch.org/wiki/OpenZAP#Debugging_PRI_With_wanpipemon for the link.) -MC
Again if you did not have the SCTP libs and dev headers installed when you did ./configure you'll never get this working SCTP is required to have boost work. Also don't use Pre9 get the latest from latest.freeswitch.org and run with that please. /b On Jan 6, 2010, at 4:22 PM, Jerry Richards wrote:
By the way, I posted another pastebin log (http://pastebin.freeswitch.org/11694) that shows the output of the "make" and "make install sounds-install moh-install..." commands. Just prior to these makes I executed "make clean" and "make distclean". You will notice in the makefile output that ozmod_sangoma_boost.c never appears to get compiled. Shouldn't everything be compiled in this case? I also confirmed that my working server does have the ozmod_sangoma_boost.so file located in the right place, which is why it's working.
Could version 1.0.5pre9 introduced this bug? Could that be why the older server (which original ran with 1.0.4) works and the new one doesn't?
Thanks and Best Regards, Jerry
Brian, Thank you. The issue did have to do with SCTP package installation. Apparently, after I installed the SCTP packages yesterday, I did not re-run ./confgure. Anyway, now my PRI is working on the new server. Thank You and Best Regards, Jerry _____ From: Brian West [mailto:brian@freeswitch.org] Sent: Wednesday, January 06, 2010 2:33 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] DESTINATION_OUT_OF_ORDER Again if you did not have the SCTP libs and dev headers installed when you did ./configure you'll never get this working SCTP is required to have boost work. Also don't use Pre9 get the latest from latest.freeswitch.org and run with that please. /b On Jan 6, 2010, at 4:22 PM, Jerry Richards wrote: By the way, I posted another pastebin log (http://pastebin.freeswitch.org/11694) that shows the output of the "make" and "make install sounds-install moh-install..." commands. Just prior to these makes I executed "make clean" and "make distclean". You will notice in the makefile output that ozmod_sangoma_boost.c never appears to get compiled. Shouldn't everything be compiled in this case? I also confirmed that my working server does have the ozmod_sangoma_boost.so file located in the right place, which is why it's working. Could version 1.0.5pre9 introduced this bug? Could that be why the older server (which original ran with 1.0.4) works and the new one doesn't? Thanks and Best Regards, Jerry
Thank you for your suggestions. Yes, I have the series of three lksctp-tools-1.0.6 (SCTP) packages installed, and I do have the Development Tools installed because the rest of the system is building okay. Regarding the openzap.conf file, we have only 1 D-channel and 23 B-channels and the openzap.conf file is auto-generated without a D-channel line, so I don't think this is the issue. Just to be sure, I did try adding a D-channel line (d-channel => 1:1), but this produced another error (failed to open wanpipe device span 1 channel 1) and the original error still exists. So I am trying to figure out why the openzap make is not compiling the ozmod_sangoma_boost.c source file (http://pastebin.freeswitch.org/11694). And I don't know why yet? Thank You and Regards, Jerry _____ From: Jerry Richards [mailto:jerry.richards@teotech.com] Sent: Wednesday, January 06, 2010 2:22 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] DESTINATION_OUT_OF_ORDER By the way, I posted another pastebin log (http://pastebin.freeswitch.org/11694) that shows the output of the "make" and "make install sounds-install moh-install..." commands. Just prior to these makes I executed "make clean" and "make distclean". You will notice in the makefile output that ozmod_sangoma_boost.c never appears to get compiled. Shouldn't everything be compiled in this case? I also confirmed that my working server does have the ozmod_sangoma_boost.so file located in the right place, which is why it's working. Could version 1.0.5pre9 introduced this bug? Could that be why the older server (which original ran with 1.0.4) works and the new one doesn't? Thanks and Best Regards, Jerry _____ From: Jerry Richards [mailto:jerry.richards@teotech.com] Sent: Wednesday, January 06, 2010 11:52 AM To: 'freeswitch-users@lists.freeswitch.org' Subject: RE: [Freeswitch-users] DESTINATION_OUT_OF_ORDER I capured logs of my FS startup and put them into the pastebin (http://pastebin.freeswitch.org/11692). At line 722, I see some errors: 2010-01-06 11:42:49.907861 [ERR] zap_io.c:2562 Error loading /usr/local/freeswitch/mod/ozmod_sangoma_boost.so [/usr/local/freeswitch/mod/ozmod_sangoma_boost.so: cannot open shared object file: No such file or directory] 2010-01-06 11:42:49.907883 [ERR] zap_io.c:2722 can't find 'sangoma_boost 2010-01-06 11:42:49.907902 [ERR] mod_openzap.c:2379 Error starting OpenZAP span 1 error 2010-01-06 11:42:49.907929 [CONSOLE] switch_loadable_module.c:890 Successfully Loaded [mod_openzap] Do you know why I would get this? Where is the ozmod_sangoma_boost.so file supposed to come from? Thanks, Jerry _____ From: Jerry Richards [mailto:jerry.richards@teotech.com] Sent: Wednesday, January 06, 2010 10:00 AM To: 'freeswitch-users@lists.freeswitch.org' Subject: RE: [Freeswitch-users] DESTINATION_OUT_OF_ORDER When I attempt an internal-to-PSTN call, there are no Q931 packets sent out the PRI (I confirmed this using the Sangoma wanpipemon utility). I suspect this has something to do with my XML configuration. Below are my openzap/wanpipe configurations (which should all be defaulted). Do you seen anything wrong with these defaults, which might cause the following FS console error? zap_io.c:1197 outgoing_call method not implemented! openzap.conf: [span wanpipe smg_prid] name => smg_prid trunk_type =>t1 b-channel => 1:1-23 autoload_configs/openzap.conf.xml: <configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="9"/> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> </settings> <boost_spans> <span id="smg_prid"> <!--<param name="hold-music" value="$${moh_uri}"/>--> <param name="dialplan" value="XML"/> <param name="context" value="default"/> <!-- regex to stop dialing when it matches --> <!--<param name="dial-regex" value="5555"/>--> <!-- regex to stop dialing when it does not match --> <!--<param name="fail-dial-regex" value="^5"/>--> </span> </boost_spans> <analog_spans> </analog_spans> </configuration> wanpipe.conf: [defaults] codec_ms => 20 wink_ms => 150 flash_ms => 750 Thanks and Best Regards, Jerry _____ From: Michael Collins [mailto:msc@freeswitch.org] Sent: Tuesday, January 05, 2010 4:33 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] DESTINATION_OUT_OF_ORDER On Mon, Jan 4, 2010 at 3:49 PM, Jerry Richards <jerry.richards@teotech.com> wrote: 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? Jerry, I noticed this line: (OpenZAP/1:1/3491028@g1) Is your carrier wanting full ten digit phone numbers? Try adding the area code on this and see what happens. The error usually would be something like "invalid number format" but I've seen carriers do stupid things like this. Try that first and see if it makes a difference. If not you'll need to turn on Q931 debugging as per the Sangoma wiki. (See http://wiki.freeswitch.org/wiki/OpenZAP#Debugging_PRI_With_wanpipemon for the link.) -MC
ya, you should not use make distclean with any of our code, we do not have it properly implemented since we have a very large and challenging build system/ On Wed, Jan 6, 2010 at 5:37 PM, Jerry Richards <jerry.richards@teotech.com>wrote:
Thank you for your suggestions. Yes, I have the series of three lksctp-tools-1.0.6 (SCTP) packages installed, and I do have the Development Tools installed because the rest of the system is building okay.
Regarding the openzap.conf file, we have only 1 D-channel and 23 B-channels and the openzap.conf file is auto-generated without a D-channel line, so I don't think this is the issue. Just to be sure, I did try adding a D-channel line (d-channel => 1:1), but this produced another error (failed to open wanpipe device span 1 channel 1) and the original error still exists.
So I am trying to figure out why the openzap make is not compiling the ozmod_sangoma_boost.c source file (http://pastebin.freeswitch.org/11694). And I don't know why yet?
Thank You and Regards, Jerry
------------------------------ *From:* Jerry Richards [mailto:jerry.richards@teotech.com] *Sent:* Wednesday, January 06, 2010 2:22 PM
*To:* freeswitch-users@lists.freeswitch.org *Subject:* Re: [Freeswitch-users] DESTINATION_OUT_OF_ORDER
By the way, I posted another pastebin log ( http://pastebin.freeswitch.org/11694) that shows the output of the "make" and "make install sounds-install moh-install..." commands. Just prior to these makes I executed "make clean" and "make distclean". You will notice in the makefile output that ozmod_sangoma_boost.c never appears to get compiled. Shouldn't everything be compiled in this case? I also confirmed that my working server does have the ozmod_sangoma_boost.so file located in the right place, which is why it's working.
Could version 1.0.5pre9 introduced this bug? Could that be why the older server (which original ran with 1.0.4) works and the new one doesn't?
Thanks and Best Regards, Jerry
------------------------------ *From:* Jerry Richards [mailto:jerry.richards@teotech.com] *Sent:* Wednesday, January 06, 2010 11:52 AM *To:* 'freeswitch-users@lists.freeswitch.org' *Subject:* RE: [Freeswitch-users] DESTINATION_OUT_OF_ORDER
I capured logs of my FS startup and put them into the pastebin ( http://pastebin.freeswitch.org/11692). At line 722, I see some errors:
2010-01-06 11:42:49.907861 [ERR] zap_io.c:2562 Error loading /usr/local/freeswitch/mod/ozmod_sangoma_boost.so [/usr/local/freeswitch/mod/ozmod_sangoma_boost.so: cannot open shared object file: No such file or directory] 2010-01-06 11:42:49.907883 [ERR] zap_io.c:2722 can't find 'sangoma_boost 2010-01-06 11:42:49.907902 [ERR] mod_openzap.c:2379 Error starting OpenZAP span 1 error 2010-01-06 11:42:49.907929 [CONSOLE] switch_loadable_module.c:890Successfully Loaded [mod_openzap]
Do you know why I would get this? Where is the ozmod_sangoma_boost.so file supposed to come from?
Thanks, Jerry
------------------------------ *From:* Jerry Richards [mailto:jerry.richards@teotech.com] *Sent:* Wednesday, January 06, 2010 10:00 AM *To:* 'freeswitch-users@lists.freeswitch.org' *Subject:* RE: [Freeswitch-users] DESTINATION_OUT_OF_ORDER
When I attempt an internal-to-PSTN call, there are no Q931 packets sent out the PRI (I confirmed this using the Sangoma wanpipemon utility). I suspect this has something to do with my XML configuration. Below are my openzap/wanpipe configurations (which should all be defaulted). Do you seen anything wrong with these defaults, which might cause the following FS console error?
zap_io.c:1197 outgoing_call method not implemented!
*openzap.conf: *[span wanpipe smg_prid] name => smg_prid trunk_type =>t1 b-channel => 1:1-23
*autoload_configs/openzap.conf.xml:* <configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="9"/> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> </settings> <boost_spans> <span id="smg_prid"> <!--<param name="hold-music" value="$${moh_uri}"/>--> <param name="dialplan" value="XML"/> <param name="context" value="default"/> <!-- regex to stop dialing when it matches --> <!--<param name="dial-regex" value="5555"/>--> <!-- regex to stop dialing when it does not match --> <!--<param name="fail-dial-regex" value="^5"/>--> </span> </boost_spans> <analog_spans> </analog_spans> </configuration>
*wanpipe.conf:* [defaults] codec_ms => 20 wink_ms => 150 flash_ms => 750
Thanks and Best Regards, Jerry
------------------------------ *From:* Michael Collins [mailto:msc@freeswitch.org] *Sent:* Tuesday, January 05, 2010 4:33 PM *To:* freeswitch-users@lists.freeswitch.org *Subject:* Re: [Freeswitch-users] DESTINATION_OUT_OF_ORDER
On Mon, Jan 4, 2010 at 3:49 PM, Jerry Richards <jerry.richards@teotech.com
wrote:
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?
Jerry, I noticed this line: (OpenZAP/1:1/3491028@g1)
Is your carrier wanting full ten digit phone numbers? Try adding the area code on this and see what happens. The error usually would be something like "invalid number format" but I've seen carriers do stupid things like this. Try that first and see if it makes a difference. If not you'll need to turn on Q931 debugging as per the Sangoma wiki. (See http://wiki.freeswitch.org/wiki/OpenZAP#Debugging_PRI_With_wanpipemon for the link.)
-MC
_______________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
Jerry Richards wrote:
Regarding the openzap.conf file, we have only 1 D-channel and 23 B- channels and the openzap.conf file is auto-generated without a D-channel line, so I don't think this is the issue. Just to be sure, I did try adding a D-channel line (d-channel => 1:1), but this produced another error (failed to open wanpipe device span 1 channel 1) and the original error still exists.
Channel 1 is already assigned to a B channel.
b-channel => 1:1-23
You can't also assign it to a D channel. You can assign it to channel 24. d-channel => 1:24 That's the same example that you will find on the wiki under "Wanpipe mode". http://wiki.freeswitch.org/wiki/OpenZAP -- Russell Mosemann
On Wed, Jan 6, 2010 at 6:30 PM, Russell Mosemann <Russell.Mosemann@cune.org>wrote:
You don't define any d-channels when using boost.
Thanks for the clarification.
FYI, I started the boost section under Sangoma on the wiki but got distracted before finishing. I will get on that ASAP as soon as I have a minute to get a boost setup all configured and running. Also, a tip o' the hat to Moy at Sangoma who has been extremely responsive to my boost questions in the past. Thanks, MC
participants (6)
-
Ahmed Naji
-
Anthony Minessale
-
Brian West
-
Jerry Richards
-
Michael Collins
-
Russell Mosemann