[Freeswitch-users] DESTINATION_OUT_OF_ORDER

[Jerry Richards]

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 at teotech.com] 
Sent: Wednesday, January 06, 2010 11:52 AM
To: 'freeswitch-users at 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 at teotech.com] 
Sent: Wednesday, January 06, 2010 10:00 AM
To: 'freeswitch-users at 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 at freeswitch.org] 
Sent: Tuesday, January 05, 2010 4:33 PM
To: freeswitch-users at lists.freeswitch.org
Subject: Re: [Freeswitch-users] DESTINATION_OUT_OF_ORDER




On Mon, Jan 4, 2010 at 3:49 PM, Jerry Richards <jerry.richards at 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 at 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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20100106/00306c1f/attachment-0002.html