Cisco Cisco Customer Voice Portal 8.0(1) Guida Dello Sviluppatore

Figure 11: Voice Element Interaction With the VXML Server and the Voice Browser

The diagram shows a typical exchange between the voice browser, VXML Server, and several
voice elements as follows:

1. The voice browser makes an HTTP request for a VoiceXML page to VXML Server.

2. According to its record of the application call flow, VXML Server accesses the voice

element Foo. The voice element Foo is shown on the right. The element is coded to contain
within it a small call flow with three possible exit states. It can produce three separate
VoiceXML pages, A, B, and C. In step 2, the scratch space is empty, indicating that the
element is being visited for the first time. Foo therefore needs to produce the VoiceXML
page A.

Note: The A contains in it a submit that points back to VXML Server and includes two
arguments arg1 and arg2.

3. Foo produces the VoiceXML page by assembling VFC objects and passes those objects

back to VXML Server. Before exiting, it puts in the scratch space information indicating
that page A was completed. Foo returns a 

 exit state, indicating to VXML Server

that the voice element is not done.

4. VXML Server converts the VFC objects into a complete VoiceXML page that is sent back

to the voice browser.

5. The voice browser has parsed the VoiceXML and makes a new request for the next

VoiceXML page. The request contains the two arguments specified in the VoiceXML
page A.

6. VXML Server knows to go back to Foo because it previously returned a 

 exit state.

It revisits Foo, passing along the two arguments. Since VXML Server maintains the session

Programming Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio Release 8.0(1)