Cisco Cisco MediaSense Release 9.1(1) Guia Do Desenho

machine does not exactly match one of the rows below, the server is considered to be "Unsupported", and the capacities in the "Unsupported"
category are used.

400 

15 + 10 queued 

60 

3 + 3 queued 

a few 

1 + 1 queued 

Cisco MediaSense also adjusts a number of other internal parameters based on the profile selected.

Cisco MediaSense can record calls which are up to eight hours in duration.  Beyond that duration, some sessions may end up being closed
with an error status, and HTTP Download and MP4 conversion functions may not succeed.

The amount of storage space required depends on a number of factors, such as the mix of codecs in use, the number of such calls,
the call arrival rate, duration and duty cycle, and the retention period desired. Since most of these parameters are very difficult to estimate, we
will focus here on only the number of recording session hours, and the retention period. Essentially, we will answer this question, "How much
disk space do I need in order to retain   hours of recordings for   days?"

We begin by selecting the codec. We will assume g.711, which requires about 1MB per minute of dual-stream recording. g.722 also requires
roughly 1MB per minute of dual-stream recording.  g.729 uses a variable rate compression, which means that the space requirement depends
on the content, which is not predictable. On the other hand, for estimation purposes it is generally safe to assume that it requires about one
eighth the space needed by g.711, or 128 kilobytes per minute of dual-stream recording. H.264 video is even less predictable; not only does it
use a variable rate compression, but it also depends on video resolution, screen dimensions, and a number of other factors. This is best
evaluated empirically.

Given g.711 then, we have a rate of 1MB per minute, or 60MB per hour. Assuming the maximum direct-attached storage, 4TB of disk space
therefore can store about 70,000 hours of dual-stream recordings. If you have 100 phones which are in active use 80% of the time, 24 hours a
day, then you are recording at a rate of 80 hours per hour of elapsed time. That will use up 70,000 hours in 875 hours of elapsed time, or a
little over 36 days, after which the oldest calls will need to be pruned. Therefore, your retention period will be 36 days.

Let's say all of the same parameters apply, except that your business is only open 12 hours per day. That will give you a retention period of 72
days.

If you only have 50 agents, active 12 hours a day, then your retention period rises to 144 days.

Finally, all of the above assumes 4TB of storage space available. If you deploy five Cisco MediaSense servers, each with its maximum SAN
storage allocation, then you have in effect, 60TB available. In that scenario, the retention period for 50 agents at 12 hours per day with an 80%
active usage ratio would be 2160 days, or about six years.

Here is the formula:

Codec bit rate (B) in MB/hour 

 two streams

for

 of phones (P)

Number

Average Usage ratio of each phone (U) in hours per day

o Write Rate (W) = B * P * U, in hours of storage per hour of of elapsed time

Total Storage available across all servers (S) in GB

o Retention (R) in hours = S * 1024 / W

There is one more factor to consider however: conversions into .mp4. If you expect to be converting a significant number of recorded sessions
to .mp4 and leaving them on the server, then you must increase the Write Rate (W) to account for it. In anecdotal trials, .mp4 averaged about
18 MB/hour for dual-channel audio, and about 180 MB/hour for audio+video. (Note that the .mp4 files use AAC, which is another variable rate
encoding, so the actual space used may vary considerably.) If you convert and retain an average of 50% of your recorded sessions for
example, then you must increase the Write Rate by 50% times the .mp4 bit rate in MB/hour, which obviously reduces the retention period.
Thus the Write Rate now becomes: