CVP and ISDN

RE: CVP and ISDN

2013-01-25T23:19:43Z

[quote=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: 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?[/quote] Hi Paul, Seems to be running fine for this time, and as you said it's a nice enhancement. I appreciate your help. Regards, Claudio.

RE: CVP and ISDN

2013-01-25T16:16:55Z

[quote=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: 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?[/quote] 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.

RE: CVP and ISDN

2013-01-25T09:20:48Z

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: 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?

RE: CVP and ISDN

2013-01-25T02:43:47Z

[quote=Paul Tindall]Turn on "deb voip appl script" so we can see what event it's getting.[/quote] here is the other file Paul. Regards, Claudio.

RE: CVP and ISDN

2013-01-25T02:42:34Z

[quote=Paul Tindall]Suggest you also turn on "deb gtd detail"[/quote] Here is the log file Paul, thank you.

RE: CVP and ISDN

2013-01-24T18:01:51Z

Suggest you also turn on "deb gtd detail"

RE: CVP and ISDN

2013-01-24T14:16:23Z

Turn on "deb voip appl script" so we can see what event it's getting.

RE: CVP and ISDN

2013-01-24T14:12:50Z

Hello Paul i have been working with Claudio on this and for debug q931 we got this .. for rejection call trough isdn to pstn R2 carrier we get 931: TX -> DISCONNECT pd = 8 callref = 0x00D8 Cause i = 0x8090 - Normal call clearing, working all flow correctly, but in the link to cellular carrier we got this RX <- DISCONNECT pd = 8 callref = 0x80DA Cause i = 0x839F - Normal, unspecified , and flow stuck on step MakeCall wating for respond , is there a way to identify on vxml script this disconnection code ( 0x839F) Thanks Jaime

RE: CVP and ISDN

2013-01-24T13:44:50Z

Simply start with a deb isdn q931 and deb voip appl script to see what the gateway is doing.

CVP and ISDN

2013-01-24T12:46:42Z

Hi, Currelntly i'm on a deployment for a CVP Standalone using a Outbound like script. I noticed that when i'm ussing a ISDN link to to a cellular carrier and if the callee rejects the call it rings again without the script intervention, and if the callee rejects twice or more times, the call keeps as calling and active on the CVP (VXML session keeps standby) for 5 minutes. I've tryied with an R2 link to other carrier and this behavior never shows up, what could be doing the difference on this behavior? Regards, Claudio.