On Thu, Sep 23, 2010 at 11:23 PM, Govind, Mahesh (NSN - IN/Bangalore) <mahesh.gov...@nsn.com> wrote: > The reason is when doing a load balancing , We cannot confine the > recording to a particular asterisk machine ( If we have more than one > asterisk machine in the topology ).
Yes you can. You can record the file wherever the call takes place. In fact, you can make the recording on any network segment the packet traverses as well. > So a centralized mechanism might be better . So that any machine can > access the recording . > Regards > Mahesh Recordings are formatted data, typically stored as files. You can put them into a database, but you haven't provided a reason why that would be a good idea. There are these things called shared filesystems. You should take a look at them. They work well. Options include NFS, iscsi, sans, etc. Or you can record the file in-place, and when the recording completes, copy it off to your shared filesystem. That's what I do. Or you can take a look at something like OrecX, which let's you do network spanning on your entire subnet, and it doesn't matter where your call takes place because all RTP streams get written to disk. None of what you've explained would be a good reason to put your recordings into a database. Don't do that. -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users