Let's not confuse capabilities or issues here. Your table displays the maximum number of CDR records that can be contained in the DB as well as the maximum size of the actual DB combined with what that equates to in terms of BHCA. This means the CDR database can hold a TON of records. However, you asked about how many records can be retrieved via the web interface - this is much different. Essentially, for performance reasons your searches are truncated at 100 results. Can you imagine how long it would take to retrieve let's say 10,000 records via the web if there happened to be 1 or even 2 million records (max) in the CDR database? It would take an extremely long time - which equates to customers would complain about the speed at which CDR queries are returned. So, it's a catch 22 for Cisco in that regard. If you have more robust needs for CDR lookup, it would be in your best interest to look at a 3rd party CDR collection tool (e.g., Metropolis, Avotus, etc). This would basically become a situation where you are offloading CDR's to a "billing server" and then you could search for whatever you needed to via the 3rd-party application. At that point, you'd be limited to whatever the limitations are for searches within the 3rd party tool (likely greater than 100 records but not guaranteed). So, long story short - if you're using the CDR tool on CUCM, it will truncate searches to 100 records so the Cisco recommendation is that if this doesn't work for you that you get more specific in your search criteria to limit potential matches - but this is still independent of what the CDR database can hold at max capacity. The next recommendation is that if the inherent search tools don't meet your needs or are too limiting, then you need to consider a more robust 3rd-party CDR management tool.
Hailey
Please rate helpful posts!
