Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Created by: null on 03-05-2007 04:35:09 PM I was wondering if anyone has run into this before.... We are running CVP 3.1, Audium CS 3.6 and OSR 3.0. We just recently got our ASR/TTS configured and working with external grammars. One problem we are having is that whenever we change the external grammar, the changes are not reflected for at least an hour. We would like the changes to be reflected right away. Right now, renaming the external grammar is the only way of testing the changes right away. I am sure there is a cache somewhere that is not being refreshed, but I don't know where it is. Any thoughts on this will be appreciated. Thanks - Erhan.
Subject: RE: External Grammar Cache Replied by: null on 04-05-2007 03:12:49 PM Hi Erhan,
The external grammar cache could be on your gateway side. There is no external grammar cache on the Audium server side.
Regards,
Hong
Subject: RE: External Grammar Cache Replied by: Janine Graves on 10-05-2007 04:53:34 PM I know that OSR can retrieve and cache grammars on the ASR server. There are actually 3 different cache's on the OSR server. There's an 'inet' cache that holds everything retrieved from a server, there's an OSR disk cache, and an OSR memory cache. You may need to clear all of these. I don't know whether OSR retrieves its own grammars when you're using MRCP though.
Also, the VXML Gateway can cache files (audio, perhaps grammars). So there's a cache there also.
I don't know how to force a file to be cleared from the cache (other than rebooting!), do you?
Janine www.TrainingTheExperts.com
Subject: RE: External Grammar Cache Replied by: null on 17-05-2007 12:06:05 PM Yes you can reload gateway, to clear all, but one thing to consider is reduction of the cache clearing time.
Do a show run
show run 3 lines command related to amount of memory the cache takes up. You can modify the cache refresh value.
Look for 1500 default i think (15 mins). You can decrease, refresh every x amount. Say 100 which will clear every few seconds.
Subject: RE: External Grammar Cache Replied by: Janine Graves on 17-05-2007 06:57:20 PM I don't know if you'd want to refresh the entire cache every few seconds. What about all the audio files that are cached there, wouldn't there be a performance impact from this?
And isn't there a way to just clear one item at a time from the cache? I've seen this functionality with different voice browsers, but I don't know if IOS has this.
Also I know that web servers and app servers can assign expiration headers to files they serve, and the voice browser should then check for updates when the file's expired. Does anyone know if the IOS voice browser actually looks at expiry headers?
Finally, VXML has a way to specify the 'maxage' of a file needed - indicating to only use a certain file (or all files) from the IOS cache if they are less than that maxage value. Again, does anyone know if IOS obeys that (I believe it must to be a certified VXML platform, but haven't tested it). If IOS does obey this, then perhaps you can change the maxage to '0s' for certain grammars you are invoking or for a certain portion of the application.
Janine
Subject: RE: External Grammar Cache Replied by: null on 29-05-2007 07:32:10 PM We use Apache as our Media Server for both Audio (.wav) and Grammar files (.grxml or .gram). We are using Cisco voice gateways with Nuance OSR 2 speech recognition.
In all cases, we use the expiry information sent along in the header. For performance reasons, we set the .WAV and .GRXML expiration time to be 10 minutes. The .GRAM files are limited to very large pre-compiled grammars and we set the expiration to 30 days to limit the number of times it was re-loaded by OSR.
Configuring the web server hosting your grammar files to send expiry information is the likely solution to your problem. If your grammar files aren't loaded from a web server then you'll need to look into your OSR settings.
However, a word of caution. In a development environment having the files expire immediately is fine. When you deploy to a production environment then you'll want to look at the cost of reloading vs. the frequency of reloading. As I pointed out above, we have one very large (2M pre-compiled grammar file that we only re-fetch to the cache once every 30 days because of the performance impact on the OSR.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: