<div><div class="gmail_quote">On Wed, Oct 7, 2009 at 5:12 PM, Tzafrir Cohen <span dir="ltr"><<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>Basically this branch intends to allow sending all the recorded<br>
(Monitor) files to a remote recording server instead of local files.<br>
This could be recorded by some remote recording server or even by<br>
a sniffer such as Wireshark.<br>
<br>
At the moment the code basically works and now I want to figure out how<br>
to best fit it in Asterisk.<br>
<br>
</blockquote><div><br></div><div>Hi Tzafrir,<div><br></div><div>This might be a silly question and I'm sure you had contemplated this option before, but I'd like to know what made you discard it (notice I am not familiar with res_monitor and this suggestion is more oriented to mix monitor/audio hooks). </div>
<div><br></div><div>From the very first time I saw your branch seemed like a cool project to me, something I did not understand though, is why not create a regular SIP call instead of a dummy call (that is calling ast_request(), ast_call() etc to a configured SIP peer), then anything read from the monitored channel would be sent using ast_write() and audio coming back from the SIP call would be silently discarded ( may be you decided is a waste? ). </div>
<div><br></div><div>As I said, however, this thought I had was more oriented to using it inside mix monitor with audio hooks sending the mixed audio already to the monitoring SIP call (or any other asterisk tech channel for that matter) instead of writing it to a file. <br>
</div></div><div><br></div></div>-- <br>Moises Silva<br>Software Developer<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">moy@sangoma.com</a><br>
</div>