Alex,<br><br>Thanks for your updates. Yes, when using libpri one must use the libpri-ish notations, like "network" vs. "net". Thanks for confirming the status of the wiki. I will make any updates needed.<br>
<br>-MC<br><br><div class="gmail_quote">On Sun, Jun 28, 2009 at 8:18 PM, Alex Green <span dir="ltr"><<a href="mailto:alexg@etherstack.com">alexg@etherstack.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thank you very much Michael, that would have been tricky to figure out..<br>
I originally tried libpri but was not able to get it to work. I have<br>
tried again and sorted it out. For anybody searching the list in future<br>
here is how I got it working.<br>
<br>
1. For openzap.conf: use [span zt], not [span libpri].<br>
<br>
2. When calling zap_configure_span() use something like this:<br>
zap_configure_span("libpri", span_PRI_1, on_signal, "node", "network",<br>
"switch", "dms100", "dp", "unknown", "l1", "ulaw",<br>
"debug", NULL, "opts", 0, TAG_END)<br>
See mod_openzap.c -> load_config(void) and ozmod_libpri.c -><br>
zap_libpri_configure_span() for inspiration on the values.<br>
<br>
3. Finally, the node type argument for network signalling MUST be<br>
"network", not "net". I am guessing that this also applies to the<br>
openzap.conf.xml file. If so, the wiki needs to be updated:<br>
<a href="http://wiki.freeswitch.org/wiki/Openzap.conf.xml_Examples#Using_with_PRI_.28libpri_compatibility_stack.29" target="_blank">http://wiki.freeswitch.org/wiki/Openzap.conf.xml_Examples#Using_with_PRI_.28libpri_compatibility_stack.29</a><br>
<br>
Thanks again, -alex<br>
<div class="im"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
Michael Collins wrote:<br>
> Alex,<br>
><br>
> The stock OpenZAP PRI handler doesn't do net, it only does terminal.<br>
> You'll need to use the ozmod_libpri method if you want to have FS be a<br>
> PRI/Net:<br>
> <a href="http://wiki.freeswitch.org/wiki/OpenZAP#Adding_libpri_Support" target="_blank">http://wiki.freeswitch.org/wiki/OpenZAP#Adding_libpri_Support</a><br>
><br>
> -MC<br>
><br>
> On Fri, Jun 26, 2009 at 12:02 AM, Alex Green <<a href="mailto:alexg@etherstack.com">alexg@etherstack.com</a><br>
</div><div><div></div><div class="h5">> <mailto:<a href="mailto:alexg@etherstack.com">alexg@etherstack.com</a>>> wrote:<br>
><br>
> Summary: After having a play with analogue openzap, I have moved to a<br>
> TE210p and am having some trouble getting a test PRI to PRI call<br>
> working.<br>
><br>
> For the analogue card I had written an app where you give it a number<br>
> via the command line, it will calls you and by pressing digits you can<br>
> either record or playback PCM. Using openzap was fairly straight forward<br>
> if you knew what you are doing (first time was tedious trying to figure<br>
> out the calls, values and state transitions). But it works fine.<br>
><br>
> For the two span PRI card I am having a bit less luck. I have the RX<br>
> connected to the TX for both spans. I have the config set up correctly<br>
> (according to ztscan and openzap load messages). This is how I start the<br>
> PRI call. I do this for both spans with error checking and for<br>
> zap_configure_span() I use "net" instead of "te" on the second span.<br>
><br>
> >===========================================<br>
> // Configure the span:<br>
> zap_configure_span("isdn", span_PRI_1, on_signal, "mode", "te",<br>
> "dialect", "q931", TAG_END)<br>
> // Start the span:<br>
> zap_span_start(span_PRI_1)<br>
><br>
> // Make an outgoing call<br>
> zap_channel_outgoing_call(span_PRI_1->channels[1]);<br>
> <===========================================<br>
><br>
> This gives me the following output:<br>
> >===========================================<br>
> [DEBUG] src/ozmod/ozmod_isdn/ozmod_isdn.c:1029 state_advance() 5:1 STATE<br>
> [DIALING]<br>
> [DEBUG] src/ozmod/ozmod_isdn/ozmod_isdn.c:1757 q931_rx_32() WRITE 32<br>
> --------------------------------------------------------------------------------<br>
> [08 02 00 02 05 04 03 80 90 a3 18 03 a1 83 81 1e 02 80 83 28 00 6c 02 01<br>
> 80 70 01 81 7d 02 91 81]<br>
><br>
> [DEBUG] src/ozmod/ozmod_isdn/ozmod_isdn.c:993 zap_isdn_921_23() READ 32<br>
> --------------------------------------------------------------------------------<br>
> [08 02 00 02 05 04 03 80 90 a3 18 03 a1 83 81 1e 02 80 83 28 00 6c 02 01<br>
> 80 70 01 81 7d 02 91 81]<br>
><br>
> [DEBUG] src/ozmod/ozmod_isdn/ozmod_isdn.c:997 zap_isdn_921_23() 931<br>
> parse error [-3002] [Q931E_ILLEGAL_IE]<br>
> <===========================================<br>
><br>
> The second channel is reading the data that is being written, which I<br>
> guess is a good start. But, how do I go from here to actual calls?<br>
><br>
> I am sure it is something simple that I am overlooking. Any help is<br>
> really appreciated. Thanks,<br>
><br>
> Dr Alex Green.<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Freeswitch-dev mailing list<br>
> <a href="mailto:Freeswitch-dev@lists.freeswitch.org">Freeswitch-dev@lists.freeswitch.org</a><br>
</div></div>> <mailto:<a href="mailto:Freeswitch-dev@lists.freeswitch.org">Freeswitch-dev@lists.freeswitch.org</a>><br>
<div class="im">> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
><br>
><br>
><br>
</div>> ------------------------------------------------------------------------<br>
<div><div></div><div class="h5">><br>
> _______________________________________________<br>
> Freeswitch-dev mailing list<br>
> <a href="mailto:Freeswitch-dev@lists.freeswitch.org">Freeswitch-dev@lists.freeswitch.org</a><br>
> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
> <a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br>
_______________________________________________<br>
Freeswitch-dev mailing list<br>
<a href="mailto:Freeswitch-dev@lists.freeswitch.org">Freeswitch-dev@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br>