Cisco Cisco Customer Voice Portal 8.0(1)
C-93
Cisco Customer Voice Portal (CVP) Release 3.1(0) Configuration and Administration Guide
Appendix C Customer Voice Portal Deployment
Configuring Customer Voice Portal for Locations-based Call Admission Control
•
·http client cache memory file 500
•
·http client cache memory pool 15000
Note
The ‘http client cache memory file’ represents the largest size prompt file (in Kbytes) that can be cached.
In general, customer prompts larger than 500K (about a minute in length) should be broken up into
smaller, more manageable pieces to facilitate loading and caching. For example, queue music could be
a repetitive loop of a 30 second prompt. Note also that because the prompts are streamed, the prompt
will not be cached unless the whole prompt is played. Therefore, it is recommended that you make
prompts a manageable size.
In general, customer prompts larger than 500K (about a minute in length) should be broken up into
smaller, more manageable pieces to facilitate loading and caching. For example, queue music could be
a repetitive loop of a 30 second prompt. Note also that because the prompts are streamed, the prompt
will not be cached unless the whole prompt is played. Therefore, it is recommended that you make
prompts a manageable size.
Step 2
Synchronize the datetime between the gateway and the HTTP media server.
Note
Synchronization does not have to be exact, but at least within a minute or two. Times that are not
synchronized can cause prompts to never refresh or they will refresh with every call, both of which are
undesirable behaviors.
synchronized can cause prompts to never refresh or they will refresh with every call, both of which are
undesirable behaviors.
Step 3
On the media server, set the content expiration (for example 15 minutes)
Note
In IIS, this is done under the “HTTP Header” tab. The gateway prompt will be refreshed after this time
period. The period chosen should reflect how oftener r re-record prompts and how long you are willing
to wait to have the new prompt load after modification.
period. The period chosen should reflect how oftener r re-record prompts and how long you are willing
to wait to have the new prompt load after modification.
How to determine if the gateway is caching properly
To determine if you have properly configured gateway caching, do the following:
•
The IIS log on the media server records every time a client requests a prompt. If caching is set up
correctly, these requests should appear approximately every X minutes (X is whatever was defined
as the refresh interval in Step 3 above) for any particular prompt. The log is located at:
C:\WINNT\system32\LogFiles\W3SVC1\ex*
correctly, these requests should appear approximately every X minutes (X is whatever was defined
as the refresh interval in Step 3 above) for any particular prompt. The log is located at:
C:\WINNT\system32\LogFiles\W3SVC1\ex*
or
•
Do ‘show http client cache’ on the gateway. The “Fresh Time’ column should equal the refresh time
period set on the HTTP media server. For example, it the refresh period was set to 15 minutes, this
should say 900 seconds. The ‘Age’ column shows how many seconds have passed since the prompt
was last refreshed. In general, this number will be less than the “Fresh Time’. However, if no call
has ever accessed the prompt recently, this number could be greater than the fresh time. Prompts
are only refreshed when triggered by a call *and* the prompt ‘Fresh Time’ has expired. If the Fresh
Time is a very high value, the only way to remove the prompt from cache (other than the ‘hidden’
commands) is to reload the gateway.
period set on the HTTP media server. For example, it the refresh period was set to 15 minutes, this
should say 900 seconds. The ‘Age’ column shows how many seconds have passed since the prompt
was last refreshed. In general, this number will be less than the “Fresh Time’. However, if no call
has ever accessed the prompt recently, this number could be greater than the fresh time. Prompts
are only refreshed when triggered by a call *and* the prompt ‘Fresh Time’ has expired. If the Fresh
Time is a very high value, the only way to remove the prompt from cache (other than the ‘hidden’
commands) is to reload the gateway.