Article ID:	259
Last updated:	November 02, 2006

Would you like to...

Print this page

Post a comment

User Opinions

No users have voted.

---

How would you rate this answer?

Helpful

Not helpful

Thank you for rating this answer.

SUMMARY

This article explains how you can use a web browser to test Hotlinks in a deployed Audium application.

SYMPTOMS

Developer is testing their application in a web browser (e.g. Internet Explorer, Firefox, etc.) but does not know how to test Hotlinks, which normally rely on an event being thrown by a voice browser.  Since web browsers cannot throw these events, it may not be immediately apparent how to replicate this behavior for testing purposes.

RESOLUTION

To test a Hotlink, you should send a request using a URL of the following format:

http://IP:PORT/Audium/Server?audium_hotlink=HOTLINK_NAME

where IP is the address of your application server and PORT is the port it is listening on. HOTLINK_NAME is the name of the Hotlink that you would like to trigger from within your voice application.  Note that in order to issue this request, you should already have accessed your voice application via a web browser and be familiar with how to navigate through your app using the web browser.  For details on this, please see the article "How to test deployed Audium applications in a web browser", there is a link to this article below.

You can simulate the throwing of any event that is defined in your application's root document in a similar manner.  To do so, you should examine the root document, and look for the <submit> that exists within the desired event's <catch> block.  An example you may already be familiar with is throwing a hangup event.  The following VoiceXML can be found in the root document of your applications:

<catch event="telephone.disconnect.hangup">
<var name="audium_action" expr="'hangup'"/>
<submit next="/Audium/Server" method="post" namelist=" audium_vxmlLog audium_action"/> </catch>

From this VoiceXML, you can construct a web browser request that will simulate this event (note that below we are passing the required audium_action variable, as seen in the submit; the audium_vxmlLog variable is always optional and we have omitted it):

http:/IP:PORT/Audium/Server?audium_action=hangup

When Audium Call Services receives this request, it will assume that a hangup event has occurred on the voice browser side and act accordingly.

Note that you can view your application's root document by requesting the following URL:

http://IP:PORT/Audium/Server?audium_root=true&calling_into=YOUR_APP_NAME

where YOUR_APP_NAME is the name of your voice application.