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