CVP 8.0 Media Server Configuration- bad fetch error

While setting up a UCCE- CVP 8.0 lab, I encountered a "bad fetch" error causing prompts not to be played to caller. I discovered that after a basic CVP (all-in-one-box) installation additional configuration is needed for proper media server operation.

Here are my findings while troubleshooting:


Ingress/VXML gateway:

debug voip application vxml

Snippet

 //75//AFW_:/vapp_play_done: evID=178 reason=12, protocol=2, status_code=404, dur=0, rate=0
   CALL_ERROR; fail with vapp error 2, protocol_status_code=404
   CALL_ERROR; *** error.badfetch.http.404 event is thrown
*Jan 16 15:19:56.843:    expr=var _event='error.badfetch.http.404'

CVP Error Logs:

Media Fetch Error for URL=http://10.10.210.22/en-us/sys/Friday.wav (Client: 10.10.33.2) [id:3023]
520: 10.10.210.22: Jan 16 2014 05:09:43.893 -0600: %CVP_8_0_IVR-3-CALL_ERROR:  RunScript Error from 10.10.33.2 [MEDIA_FILE_NOT_FOUND(9)] CALLGUID: 9ABE08F2100001435354B2E90A0AD216 DNIS=811111111135 {VRUScriptName: 'PM,Friday,S' ConfigParam: ''} [id:3023]

IIS logs

Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status

 10.10.210.22 GET /en-us/sys/Friday.wav - 80 - 10.10.33.2 Cisco-IOS-C2801/15.1 404 0 3
 10.10.210.22 GET /en-us/sys/Friday.wav - 80 - 10.10.33.2 Cisco-IOS-C2801/15.1 404 0 3

1. I entered  the URL on a web browser and also received a 404 error message.
2. I browsed to the path C:\Cisco\CVP\MediaFiles\en-us\sys and confirmed the Friday.wav file was there.
3. I checked the ICM script in monitor mode and notice the run ext. script node was failing to play the file.
4. I checked the IIS logs C:\WINDOWS\system32\LogFiles\W3SVC1 which ultimately proved that IIS was not finding the file.

Solution:

Configured the IIS home directory to match the location of the files(C:\Cisco\CVP\MediaFiles\)  from the default (C:\Inetpub\wwwroot.)

Added Permissions to Everyone to the file location folder.