CallXML 2.0 Development Guide

| TOC

This documentation is for CallXML 2, which has been superceded by CallXML 3. The CallXML 2 language is not being updated any longer. CallXML 3, however, has many new features and is actively being enhanced. If you're writing a new CallXML application, you should use CallXML 3. Click here for the CallXML 3.0 documentation.

Introduction to Call Bridging

Writing a phone application isn't much good if we can't actually dial out and connect with another party within our app, right? Glad we are all in agreement. We have two methods to accomplish an outbound call by within the CallXML 2.0 markup, we can spawn another session via the <run> element and bridge the two together, (which we will cover in our next Lesson), or we can use the <transfer> element, (which is new to CallXML 2.0), as our method of placing an outbound call.

The Voxeo CallXML platform also has provisions for multiparty call conferencing, answering machine detection, (Call Progress Analyzer), and programmatic http token initiated outbound dialing, to further expand the functionality of your IVR applications. Details on these features are detailed thoroughly in the documentation section entitled 'Appendix B: Outbound Dialing'.

Regardless of how fancy we want to make our application, the starting point for bridging a caller into our application begins with the 'starter' tutorial on bridged calls via the <run/call> tags, which we will walk you through in our next Lesson. The greatest adventure begins with but one step...

ANNOTATIONS: EXISTING POSTS

0 posts - click the button below to add a note to this page

CallerID and CalledID

| TOC

Call Bridging