Paul Tindall:
I see there's no signaling event reported after the call progress. The requesting end times-out after 5 mins and will return a "dialer_resp_timeout" back to your VoiceXML session assuming you've got the application timeout set to more than 5 mins. You should be able to see that in the activity log. I'm not sure what your application is doing on return from the Makecall element but as the outbound call is ending with ls_008 (near-end disconnect) I assume you're exiting the application and clearing the call.
20:19:27.301 CVP_OBCALLREQ: sent dialer record to CVP_OUTBOUND.TCL, waiting for call outcome ...
20:19:27.309 CVP_DIALER: assumed control of call with argument: <dnis=90453339558244 cli= rna=10 id=1861 uui="3122">
20:19:27.353 CVP_DIALER: event ev_proceeding on call leg 37975
20:19:29.133 CVP_DIALER: event ev_alert on call leg 37975
20:19:31.773 CVP_DIALER: event ev_progress on call leg 37975
20:24:27.301 CVP_OBCALLREQ: ERROR: timed-out waiting for dialer response, returning leg to VXML
20:24:27.329 CVP_DIALER: ID = 1861: call to 90453339558244 failed, status ls_008 (ls_008)
In the sample we provide, the response timeout is set in cvp_obcallreq.tcl to 300 secs so you can edit that to increase or decrease the time it takes to report back if that helps. Being able to set that timeout on the Makecall element might be a useful enhancement. What is the behaviour you're trying to achieve in the case the called destination doesn't respond?
Hi Paul,
I'm trying to retry the same number after a no answer, busy or whatever is diferent to "connected", or in case the stop condition insert the next number (this last action is controlled by the script).
Regards,
Claudio.
