ive a lot of install which are purely Zap or IAX2.<br><br>Why i do create such todos, when i've like 939993? :)<br><br><br><br><div><span class="gmail_quote">On 4/4/07, <b class="gmail_sendername">Olle E Johansson</b> <
<a href="mailto:olle@voop.com">olle@voop.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>4 apr 2007 kl. 21.47 skrev Clod Patry:
<br><br>> hi,<br>> is there any reason why the rtp is in the core and not possibly a<br>> module?<br>> I mean, if your * just receive and throw zap channels, having this<br>> rtp in the core is really pointless.
<br>><br>> The problem is that for embeded system, the final bin is pretty<br>> huge, since it has so much stuff built-in (rtp is just one).<br>><br>> Could we port rtp.c to a module (res_rtp.c, maybe), which would
<br>> offer the possibility to unload it in some setups, where rtp isnt<br>> implicated.<br>><br><br>I agree that it would be a good thing for those systems that has no<br>RTP based channel. The issue would be all the hooks that
<br>go from other modules to RTP, it's not a simple interface to have<br>stubs for.<br><br>Code on, code on.<br><br>But honestly, Asterisk without SIP? Come on, it's like ABBA without<br>Frida !<br><br>/O ;-)<br><br>
_______________________________________________<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-dev mailing list<br>To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br></blockquote></div><br><br clear="all"><br>-- <br>Clod Patry