Author Message
FrankGuthrie
Joined: Apr 25, 2005
Messages: 43
Offline
We have a CCXML application that launches an outbound call and in the connection.connected event we start two VXML dialogs. One is our custom VXML that delivers a message to a caller and the second VXML application loads up a Lumenvox grammar to detect an answering machine.

If the answering machine tone is detected by Lumenvox then we need to terminate the custom VXML dialog that is running and start a new dialog. But when we do "dialog.terminate", the CTI executes a call end command and the connection is lost. We see in the AES connector logs that the call was disconnected. Since the call is no longer there, the second dialog fails to start.

So we want to know is if dialog.terminate will cause the call to be disconnected? If so, is there another way to terminate a dialog without disconnecting the call?
RossYakulis
Joined: Nov 6, 2013
Messages: 2652
Offline
Why are you not using the call classification that is in CCXML? That is my initial question.
RossYakulis
Joined: Nov 6, 2013
Messages: 2652
Offline
Here are other comments from team members:

"I agree about the call classification. On the AESC side, they can set the web.xml property: sage.cti.autoinvoke.callinfo to false and manually do a callinfo if they detect a live caller. That way it won't automatically end when the dialog returns."

and

"The <dialogterminate> will not end the connection unless their ccxml application uses <exit> after <dialogterminate>"
Go to:   
Mobile view