On Sat, Jun 19, 2010 at 2:10 PM, Tony Graziano <[email protected]> wrote: > Good to know. It certainly varies site to site. I think Ranga was > considering conference recordings, so a 90 minute recording could > easily be around 100MB (+/-). 10 per month is a gig, and 12 months is > 12GB. So depending upon use cases, I see how it could get very large > indeed.
10 conferences per month is easy to envision. Perhaps a good middle ground could be that voicemail is not compressed whereas conference recordings are compressed. Another middle ground could be to run an archiver that compresses conference recordings and voice mails after a few days. If the user wanted to play archived recordings, he would need to download them, unzip and play. Ranga > > On Sat, Jun 19, 2010 at 1:20 PM, Josh Patten <[email protected]> wrote: >> I have 200 or so users on mine and I haven't even reached 500 MB yet >> including prompts. >> >> Andy Spitzer <[email protected]> wrote: >> >>>Woof! >>> >>>On Fri, 18 Jun 2010 20:34:11 -0400, M. Ranganathan <[email protected]> >>>wrote: >>> >>>> Can be done in the background when system load is low by a low priority >>>> thread. >>> >>>Well, zipping (or MP3 encoding) could be. But what about when someone >>>calls in to check their messages? The unzipping/MP3 decoding must be done >>>in realtime, on demand, and on the server. >>> >>>I agree with Tony's argument for MP3 when sent via e-mail or downloaded >>> from the user portal. But even if sipX did MP3 encoding for this purpose, >>>I'd suggest keeping the original linear files around for when users are >>>retrieving messages via the telephone to avoid the need to decode in >>>realtime. >>> >>>Is anyone out there running a 'large' sipX/SCS system willing to publish >>>their voicemail usage specs? I'd love to see the average number of >>>messages per mailbox, and the average length of each message, and the >>>total disk space used by voicemail. Every system I've ever looked at was >>>using a tiny fraction of the disk space for voicemail. Average message >>>length was under 30 seconds. Logs were taking up WAY more space then >>>voicemail ever did. >>> >>>And for the record, I think sipX should support MP3, but only when someone >>>finds a way around the licensing issues. >>> >>>--Woof! >>>_______________________________________________ >>>sipx-dev mailing list [email protected] >>>List Archive: http://list.sipfoundry.org/archive/sipx-dev >>>Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev >>>sipXecs IP PBX -- http://www.sipfoundry.org/ >> _______________________________________________ >> sipx-dev mailing list [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev >> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev >> sipXecs IP PBX -- http://www.sipfoundry.org/ >> > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > Why do mathematicians always confuse Halloween and Christmas? > Because 31 Oct = 25 Dec. > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
