<div>Moises i can help you with </div>
<div> </div>
<div>3. DTMF/R2 support (Venezuela users mostly).<br> </div>
<div>I am from venezuela, and i have R2 e1 with Movistar To test</div>
<div> </div>
<div>Thnaks Alexis Gavidia<br><br> </div>
<div><span class="gmail_quote">On 11/19/08, <b class="gmail_sendername">Moises Silva</b> <<a href="mailto:moises.silva@gmail.com">moises.silva@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Probably some of you already know it, the first release candidate for<br>openr2 is out there in google code:<br>
<a href="http://code.google.com/p/openr2/downloads/list">http://code.google.com/p/openr2/downloads/list</a><br><br>Also, I'd like to ask for opinions and probably any volunteer coders<br>here. Currently there is a couple of activities that I have in mind.<br>
<br>1. Windows and/or Mac OS build.<br>2. Asterisk patches.<br>3. DTMF/R2 support (Venezuela users mostly).<br><br>The number one is about making openr2 code to build in Windows or Mac<br>OS. Or both :)<br><br>The second project is less time consuming (I think), the idea is<br>
create a doc/asterisk/patches directory where other directories will<br>exists, one directory for each major release of Asterisk. 1.2, 1.4 and<br>1.6. Now that we have the first release candidate of openr2 it would<br>be easier to have patches for Asterisk and not just the SVN branches I<br>
have been providing. So, one directory could be:<br><br>doc/asterisk/1.4/1.4.22/<br><br>And put the required patches, or even better, an already modified for<br>R2 chan_dahdi.c/chan_zap.c along with a Makefile to compile using the<br>
Asterisk headers. That way a user can easily do this:<br><br># cd doc/asterisk/1.4/1.4.22/<br># make<br># make install<br><br>And that make install would copy the created R2-enabled chan_dahdi.so<br>to /usr/lib/asterisk/modules replacing the old and not-R2 enabled<br>
chan_dahdi.so included with Asterisk.<br><br>The other option is not include chan_zap.c or chan_dahdi.c modified<br>there, but just include a patch for users to apply.<br><br>The advantage of having the modified chan_zap.c/chan_dahdi.c with a<br>
Makefile is that no patching is required, users just replace their old<br>chan_zap.so/chan_dahdi.so with "make install" with the R2-enabled one.<br>The disadvantage is that a directory would be needed each time a new<br>
Asterisk release goes out. But I really like this approach better over<br>the patching.<br><br>The advantage with the patch, is that as long as the patch applies<br>cleanly to newer Asterisk versions, there is no need to do anything,<br>
but in any moment a patch does not apply or causes undesired<br>side-effects (like segfaulting) there will be needed to create a new<br>directory with a new patch for the new Asterisk version.<br><br>Comments, ideas?<br><br>
If there is anyone willing to work in some of this sub-projects, it<br>will be my pleasure to provide access to an SVN branch in the<br>development openr2 repository to work on.<br><br>Moy<br><br>--<br>"I do not agree with what you have to say, but I'll defend to the<br>
death your right to say it." Voltaire<br><br>_______________________________________________<br>--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--">http://www.api-digital.com--</a><br><br>asterisk-r2 mailing list<br>
To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-r2">http://lists.digium.com/mailman/listinfo/asterisk-r2</a><br></blockquote></div><br>