In layman's terms, if you read the OP's post, they want a <b>recording server</b>. With no mention of any other functionality.<br><br>Asterisk <b>COULD</b> be used as a recording server but that is really not the proper tool, on the other hand OrecX <b>IS</b> a recording server, therefore the proper tool.<br>
<br>I <b>COULD</b> use a butter knife for a screw driver, but the screw driver <b>IS</b> the proper tool for the job.<br><br>Believe me, I have used the butter knife and it worked OK sometimes, other times it did not work at all, but the proper screwdriver did the job perfectly.<br>
<br>I would dare say that using Asterisk simply for recording is heavy handed.<br><br>Thanks,<br>Steve Totaro<br><br><div class="gmail_quote">On Mon, Sep 7, 2009 at 12:29 AM, Steve Totaro <span dir="ltr"><<a href="mailto:stotaro@first-notification.com">stotaro@first-notification.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Did you push it past 300 on two year old hardware and software? Core 2 Duo Dell Dimension desktop as proof of concept?<br>
<br>Port mirroring is basic on almost any newer switch. Login, enable port monitoring, write mem, done. <br>
<br>With a GUI, it takes all of thirty seconds. I don't see how this is "heavy handed"<br><br>I build robust and redundant systems, separate server for DB, recording, gateways, in an all HA configuration.<br>
<br>Again, how many calls were you able record using RAMdisk? Anywhere 300?<br><br>Bookmark my post, so when you reach your RAMDisk limit, you can join the big league.<br><br>Thanks,<br><font color="#888888">Steve Totaro</font><div>
<div></div><div class="h5"><br><br><div class="gmail_quote">
On Mon, Sep 7, 2009 at 12:05 AM, David Backeberg <span dir="ltr"><<a href="mailto:dbackeberg@gmail.com" target="_blank">dbackeberg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Sun, Sep 6, 2009 at 11:46 PM, Steve<br>
Totaro<<a href="mailto:stotaro@asteriskhelpdesk.com" target="_blank">stotaro@asteriskhelpdesk.com</a>> wrote:<br>
> A dedicated recording server is recommended if you are going to be recording<br>
> a good deal of calls.<br>
><br>
> You certainly would not want to run out of hard drive space on your Asterisk<br>
> server and bring it down.<br>
<br>
</div>Bring it down, really?<br>
<br>
I think monitor would just complain that it couldn't write to a<br>
device. I suppose you could have problems if your recording partition<br>
was also your system partition, but that would be true for any<br>
application, such as apache web activity logs.<br>
<div><br>
> Also, with Asterisk (last I knew) ~60 simultaneous calls, the audio starts<br>
> breaking up very badly due to I/O.<br>
<br>
</div>This would be channel and system independent. For instance i/o<br>
blocking could cause problems but why would it affect simple non-mixed<br>
audio, like simple bridged Dahdi channels?<br>
<div><br>
> OrecX can do over 300 simultaneous calls and only need port mirroring<br>
> enabled on your switch. Even if it crashes or HD fills, call go on<br>
> normally.<br>
<br>
</div>If a non-system hd fills, calls will go on normally.<br>
Port mirroring seems like a pretty heavy-handed way to do call recording.<br>
<br>
How about asterisk, writing to a ramdisk for recordings, and every<br>
five minutes or so syncing off the completed recordings to a SAN? (You<br>
may have guessed I did this, and pushed it past 60 simultaneous<br>
recordings).<br>
<div><div></div><div></div></div></blockquote></div></div></div></blockquote></div><br><br clear="all"><br>-- <br>Senior Systems and Network Administrator<br>Triple Canopy, Inc.,<br>2250 Corporate Park Drive, Suite 300<br>
ph. +1.703.673.5191<br>mob.+1.240.938.1212<br>FAX.+1.703.673.1279<br><a href="mailto:steve.totaro@triplecanopy.com">steve.totaro@triplecanopy.com</a><br>