This method initiates an outbound call on an available MPP, then starts the specified VoiceXML application. If successful, it returns the:
Experience Portal session ID for the new session
Total number of outbound resources available, both used and unused
Total number of unused SIP outbound resources
Total number of unused H.323 outbound resources
The actual launch of the VoiceXML application is handled by the default CCXML page, which is also responsible for returning success or failure back to the Application Interface web service.
When the VoiceXML application is invoked, the first VoiceXML page is prepared. If this succeeds, the outbound call is placed by the system. If the call connects and the dialog starts without error, then the VoiceXML application returns a successful launch code. Otherwise, the application returns an appropriate error code.
Note:
If the initial VoiceXML page cannot be prepared for any reason, the Application Interface web service does not place the outbound call. Therefore a customer will never be bothered by an outbound call that cannot possibly start correctly.
For information about the status codes returned by the CCXML page, see Returning the status of a LaunchCCXML request.
Note:
If a CCXML application launches multiple VoiceXML applications, each of these applications can use a different speech server. Prior to Experience Portal 7.0, multiple applications used only one speech server. This feature comes into play if you have different languages loaded onto different speech servers.
When a CCXML application launches a VoiceXML dialog by name, the configured ASR or TTS is used. If the configured ASR or TTS changes, the current ASR or TTS resources are released and new resources are seized before the dialog starts.
For example, a CCXML application can launch a dialog with English ASR or TTS. The application can determine that the caller prefers Spanish and so, the second dialog is launched with Spanish ASR or TTS.