u:p:
« prevnext »

getMediaPlatformErrorsFromAVoiceObjectsApplication

Symptoms

When there is no specific Event Handling defined in VoiceObjects, VoiceObjects will anyway render some event handlers into the VXML.

Now some media platforms like Prophecy won't log the error in their logs when there are event handlers which should take care of the VXML. To now get the data from the media platform we will need to get a log entry into the event handler.

As VoiceObjects doesn't directly allow to put VXML into an event handler, we will use the Event handling together with an output which then injects the log statement into the VXML.


Environment

VoiceObjects + any Media Platform like e.g. Prophecy


Cause

VoiceObjects VXML contains default error handlers and some media platforms don't log errors which have been handled in the VXML application already.


Resolution

  • Open the object which causes issues.
  • Add a new Event Handler for Media Platform errors (Occurrence => 1) linking to an output. In case there is already an error handler, please replace it for this test.

  • Then change to output to generate VXML rather than a prompt by adding the following in the output field:
    </prompt> 
        <log expr="'#### LOG event:' + _event + ';message:' + _message"/> 
        <disconnect/> 
    <prompt> 

  • Redeploy your changes.
  • Assure that tracing is enabled for this service and you can gather the logs from your media platform
  • Perform a test call and collect all logs - now you should be able to map the VXML from the VoiceObjects trace file to the messages of the media platform.
Was this page helpful?  
Last edited by:RickG on: 1/20/2011 4:41 PM (EST)

Tags:
Edit  | Tags | Files | Info | Options | Subscribe |


©2002-2012 Voxeo Corporation  -  VoiceXML Hosting  -  VoiceXML Servers  -  Site Map  -  Terms of Use  -  Privacy Policy  -  Covered by U.S. Patent No. 6,922,411