I went back to the 7.0 media and nothing, I don't have any 4.0 media or I would check that too. Honestly, I'm out of ideas except for contacting PDI or your Cisco sales person. Hopefully someone on these forums has run into a similar issue.
You will likely need to record your own messages. All the user.microapp.locale variable does is set the base directory for microapp files. You can create whatever "locale" directory structure you like as long as the user.microapp.locale variable is long enough to hold the directory names, but the recommendation is of course to use the standard 5-letter "en-us", "en-gb", "fr-fr", etc. You need to create the directories on the media server yourself. I think the default "en-us" directories are just meant to be a working example.
When recording new files, just make sure they're in the right format:
Play back types for voice data Configuring how voice data is presented to a caller is an important part of setting up your Unified CVP IVR. The "Data Play Back Types" table below describes each type, along with sample valid values and formats for the supported locales when NOT using TTS:
Unified CVP micro-applications • en-us. English (United States) • en-gb. English (Great Britain) • es-mx. Spanish (Mexico) • es-es. Spanish (Spain) Locale is selected by setting the user.microapp.locale variable.
and BTW - my prompts are ALAW - I don't know if you have faced this issue before or not - my service provider from whom we have the SIP trunk - send ALAW and 729 capabilities - CVP didn't play any prompts - I were to hard code alaw on the CVP & NVRU dialpeer on the CUBE and convert all my prompts to ALAW :-)
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.