Hello François,<div><br></div><div><div class="gmail_quote">On Tue, Jan 19, 2010 at 2:09 PM, <span dir="ltr"><<a href="mailto:devel@thom.fr.eu.org" target="_blank">devel@thom.fr.eu.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="FR" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span lang="EN-US">So I finally could find a fix.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Then problem is the ring_on and ring_off
length as defined by wp_globals in ozmod_wanpipe.c</span></p>
<p class="MsoNormal"><span lang="EN-US">For France (and I guess all other European countries),
the ring on and off length shall be 1700ms and 3300ms.</span></p>
<p class="MsoNormal"><span lang="EN-US">That correspond (at least for Europe) to the
length of the ringing tone.</span></p>
<p class="MsoNormal"><span lang="EN-US">So I was wondering I it would not be a good
idea to take these values from the tones.conf file.</span></p>
<p class="MsoNormal"><span lang="EN-US"></span></p></div></div></blockquote><div>I just committed the fix to configure ring on / off from the configuration file (wanpipe.conf), given that these values are wanpipe specific. There are other wp global values already taken from the configuration, see wanpipe_init() in the same file. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="FR" link="blue" vlink="purple"><div>
<p class="MsoNormal"><span lang="EN-US">Could anybody indicate if there is any diagram
of how each module in openzap calls the other, then that could be a good
starting point (I don’t really get the interactions/calls between ozmod_wanpipe.c
and ozmod_analog.c).</span></p></div></div></blockquote></div><div>This diagram is all we have AFAIK:</div><div><br></div><div><a href="http://wiki.freeswitch.org/wiki/OpenZAP" target="_blank">http://wiki.freeswitch.org/wiki/OpenZAP</a></div>
<div><br></div><div>OpenZAP ( which is being renamed to FreeTDM as we speak) provides abstraction to both signaling and board I/O APIs. In short, you have therefore 2 type of modules, signaling and I/O modules.</div><div>
<br></div><div>I/O modules are the low level modules that use the driver-specific API to talk to the board, either Sangoma, PIKA or Zaptel-based boards. Therefore, the use can execute I/O commands using openzap API and does not have to care about which type of board is talking to. For example, ozmod_analog does this: zap_channel_command(zchan, ZAP_COMMAND_GENERATE_RING_ON), the openzap core will then check which type of I/O module is associated to the channel (wanpipe, zt, pika etc) and ask the IO module to execute the command using the specific API for the board.</div>
<div><br></div><div>The signaling module is supposed to abstract the telephony signaling (PRI, R2, FXO/FXS, SS7 etc). So, if a user wants to place a call, regardless of the signaling, it will only issue zap_channel_open() and then zap_channel_outgoing_call() which will take care of checking which signaling module is associated to the span where that channel belongs and ask the signaling module to place the call.</div>
<div><br></div><div>There are some I/O features that may not be available in some drivers (like flash in wanpipe) and are therefore emulated by the software layer of the I/O wanpipe module.</div><div><br></div>-- <br>
Moises Silva<br>Senior Software Engineer<br>Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada<br>t. 1 905 474 1990 x 128 | e. <a href="mailto:moy@sangoma.com" target="_blank">moy@sangoma.com</a><br>
</div>