Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

IOS pre-fetch from CVP prompts

Gateway 12.4.11T2 work fine then stops after some time. I suspect after 24 hours when it's time to re-cache there is a problem.

I've attached the debug http client all with the cache errors from CVP. Do you see anything in the debug? I've never looked at this type of debug.


Re: IOS pre-fetch from CVP prompts

From a peer, would below cause the problem?

Reviewing my cvpmedia folder I see;

Total cache size for all prompts: 25MB

Total cache size for the largest prompt: 1211K

Based on these numbers, I believe I should change the settings in the gateway to the following:

http client cache memory pool 26000

http client cache memory file 1200

Do you agree? Once the settings have been changed, will the gateway need to be rebooted? Prior to making any changes I would appreciate any advice on how to proceed and what (if anything) these changes could impact

Cisco Employee

Re: IOS pre-fetch from CVP prompts

Hi Jason,

similar scenarios are lot better discussed in a TAC SR then on the newsgroup have you tried raising one on this topic? Generally speaking I would recommend smaller prompts if possible making use of concatenation since it would help on the caching side. There is also an expiry element on the CVP side for the caching, I suspect that when that element is expiring then you will see the slowdown in performance registered.

Deciding how to set the memory cache will be the final stage of a similar review.



Re: IOS pre-fetch from CVP prompts

TAC case has been open, so far I think the SE is having difficulty understanding the issue, but has a full set of debugs/logs. I'm wondering if this is a caveat versus design issue. Email me offline and I can send you the TAC SR number if helpful.


Re: IOS pre-fetch from CVP prompts


I agree with the previous poster that you should split the prompts up and just change the VXML application. Is this an Audium app or done through microapps?

It's easy in Audium to have a single audio element play a number of prompts in sequence - just add audio items.

You should keep the prompts under about a minute - 600K. Personally, I like to keep them shorter than that. The performance of the http client cache is paramount to good CVP performance.

Are you aware that a long prompt that is never heard in entirety is never cached by the gateway and the gateway will always be fetching it from your media store?

What is the lifetime configured on your media stores?

Have you arranged different lifetimes on different directories? Say Emergency messages have a 1 hour lifetime, Announcements have a 1 day lifetime and Queue messages have a 30 day lifetime. You get the idea.