CallXML 3.0 Development GuideHome  |  Frameset Home

<oncallfailure>  element

DEPRECATED ELEMENT -- use the <on> handler element instead
This event occurs when the session determines that the attempted call cannot be completed because the dialed number is busy, a circuit is unavailable, a SIT tone was detected or other detectable call failure mode. The call is not automatically disconnected; rather, this element allows the developer to catch the event and attempt another action.


usage
<oncallfailure next="(navigation identifier)" value="(busy|unreachable|rejected|unknown)">


attributes
nextData Type: (navigation identifier)Default: none - attribute is optional
The 'next' attribute sets the URL the CallXML platform will go to when the container ends.
valueData Type: (busy|unreachable|rejected|unknown)Default: none - attribute is optional
The value attribute defines the possible type of call failure encountered by the CallXML application. This can be useful in determining how to proceed when differnt responses are returned from the call destination The type given in an <onCallFailure> element will be compared against the actual failure type and, if identical, any CallXML contained within the <onCallFailure> element will be executed.

The possible values for this element are:
  • busy - destination number returned a busy signal
  • unreachable - this is returned when the destination number returns a SIT tone;( 'doo doo dee, the number you have dialed is not in service at this time'), most often, the dialed number is either employing a call screening device, or is indeed out of service

  • rejected - this event will very rarely get returned. In some circumstances, a switch or PSTN  might return a series of codes to the CallXML browser, informing it that the destination number has been rejected at the Telco level

  • unknown - the call was rejected for unknown reasons



code samples
<DEPRECATED ELEMENT IN CALLXML3.0>
<?xml version="1.0" encoding="UTF-8"?>

<callxml version="3.0">
  <!--

    In CallXML 3.0, this element has been deprecated in favor
    of the more modular 'on' element.

    While we retain backwards compatibility for this particular
    tag in the CallXML3.0 markup, it is advisable to use the 'on'   
    element in your code.

  -->
</callxml>



additional links
none


  ANNOTATIONS: EXISTING POSTS
0 posts - click the button below to add a note to this page

 login


© 2008 Voxeo Corporation  |  Voxeo IVR  |  VoiceXML & CCXML IVR Developer Site