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

CVP Queue music issue

I have ipcc 7.1 with cvp 3.1(h323) with gatekeeper, my issue with the Queue music which is less than 500k some time it doesnot play it took 16 day playing fine and suddenly it stops playing and I do rename the file every time I got this error after that it works fine for a while, when I checked the application server log it says(ERROR:Media Fetch Error for url=http://10.0.232.15/en-us/app/zainsd/Queue_Mu.wav), please advice

1 ACCEPTED SOLUTION

Accepted Solutions
Green

Re: CVP Queue music issue

The gateway settings are OK.

FYI, I set "ivr prompt memory 16384 files 1000".

If you have a lot of RAM in the gateway you can raise the memory pool. We have a lot of RAM and have the HTTP memory max'd out to 50000.

The "memory file" setting of 500 means a prompt bigger than 500 kbytes (approx 50 sec) will not be cached. No problem here.

Now why do you have no lifetime set on the web server?

This means that whenever a prompt is required to be played, the router checks the cache to see if it's stale. In your case, the prompt will always be stale and will be fetched from the HTTP server.

When multiple calls are in action at the one time (under load), each is requesting to fetch the file from the HTTP server, and since this is quite a big file, you get time-outs.

If you set content expiration to say 1 day, then the first call for the day fetches the file since it is stale, plays the prompt and then puts it into the HTTP client cache.

During the rest of the day, requests for that prompt will check the age of the file against the lifetime (1 day) and will not need to fetch the file - it will be played out of memory.

Poor caching can drop performance by 30% - you are seeing the effects of that.

You can read the Cisco document "IVR HTTP Client White Paper" for more details.

Regards,

Geoff

11 REPLIES
Green

Re: CVP Queue music issue

Chop it up into shorter sections. I keep mine under 30 seconds.

Regards,

Geoff

Re: CVP Queue music issue

Does it stop working during high call volume?

david

New Member

Re: CVP Queue music issue

yes

Green

Re: CVP Queue music issue

Describe you caching technique on the voice gateway. How is the lifetime set on the Web server?

Regards,

Geoff

New Member

Re: CVP Queue music issue

dear Geoff

find the attached

New Member

Re: CVP Queue music issue

and please explain more regarding the caching on the gateway.

Green

Re: CVP Queue music issue

I don't understand the relevance of that screen shot of the Application Server.

What is in the gateway in the "http client cache" section and the "ivr prompt" section.

What is the lifetime on the web server for the WAV file (Content Expiration in IIS)?

Regards,

Geoff

New Member

Re: CVP Queue music issue

ivr prompt memory 16384

ivr prompt streamed all

http client cache memory pool 15000

http client cache memory file 500

http client cache refresh 864000

no http client cookie

http client connection timeout 60

http client response timeout 30

and the Content Expiration in IIS is disabled

Re: CVP Queue music issue

Any reason as to why you have your content expiration disabled in IIS? Usually 12 to 24 hours is a good rule of thumb.

david

Green

Re: CVP Queue music issue

The gateway settings are OK.

FYI, I set "ivr prompt memory 16384 files 1000".

If you have a lot of RAM in the gateway you can raise the memory pool. We have a lot of RAM and have the HTTP memory max'd out to 50000.

The "memory file" setting of 500 means a prompt bigger than 500 kbytes (approx 50 sec) will not be cached. No problem here.

Now why do you have no lifetime set on the web server?

This means that whenever a prompt is required to be played, the router checks the cache to see if it's stale. In your case, the prompt will always be stale and will be fetched from the HTTP server.

When multiple calls are in action at the one time (under load), each is requesting to fetch the file from the HTTP server, and since this is quite a big file, you get time-outs.

If you set content expiration to say 1 day, then the first call for the day fetches the file since it is stale, plays the prompt and then puts it into the HTTP client cache.

During the rest of the day, requests for that prompt will check the age of the file against the lifetime (1 day) and will not need to fetch the file - it will be played out of memory.

Poor caching can drop performance by 30% - you are seeing the effects of that.

You can read the Cisco document "IVR HTTP Client White Paper" for more details.

Regards,

Geoff

Green

Re: CVP Queue music issue

As I was typing, David. ;-)

Regards,

Geoff

361
Views
0
Helpful
11
Replies
CreatePlease to create content