Post End Call Action on CFD

[AndersonNunes]

Hello everyone!

I need a help for a CFD application that I'm desining. I have a simple IVR running and when the user press a digit, the CFD runs to a HTTP Request component when I send a API URL for external call treatment third party system. After this HTTP Request component, the CFD transfer the call to my 3CX user, with the attendant screen of the third party system's opened. My question is if I can do anything about the call after the hangup, when I need to send another API URL for complete the call on the external third-party system.

Best Regards.

 

[edossantos]

Yes, you have the Disconnect Handler flow for that. Please check this:
https://www.3cx.com/docs/manual/cfd-workspace/#h.iatsfl3rjfoo

 

[AndersonNunes]

Even if the call was already transfered from the CFD to another user? The CFD follow the call and knows the end of it?

 

[edossantos]

The Disconnect Handler flow is executed always, once the call is disconnected from the app. No matter what was executed on the Main flow, it's always executed. If what you need to do in the Disconnect Handler flow depends on what was executed on the Main flow, then you need to set variables and use conditions to decide when you execute what you need.

 

[VoIPTools]

Ernesto, I think he wants to perform an action when the 3CX user ends the call rather than when the call is transferred. It is my understanding that when the call is transferred to the 3CX user, this ends the call from the perspective of the CFD. The Disconnect Handler is invoked as soon as the call is transferred.

In other words, no, you cannot capture when the 3CX user disconnects the call. For that, you can use the CDR files that 3CX can optionally create, but that is not straightforward. It would require a custom service that monitors the creation of the files, and you would have to match the original call to the specific CDR file.

There is no easy way to do this that I can suggest.

 

[edossantos]

Ernesto, I think he wants to perform an action when the 3CX user ends the call rather than when the call is transferred. It is my understanding that when the call is transferred to the 3CX user, this ends the call from the perspective of the CFD. The Disconnect Handler is invoked as soon as the call is transferred.

You're right, I didn't understand this. Yes, this is correct, the Disconnect Handler flow is executed when the call is disconnected from the CFD app. So if the call is transferred, this flow is executed when the transfer succeeds, and the CFD app will not know when this call finally ends.

In other words, no, you cannot capture when the 3CX user disconnects the call. For that, you can use the CDR files that 3CX can optionally create, but that is not straightforward. It would require a custom service that monitors the creation of the files, and you would have to match the original call to the specific CDR file.

You're absolutely right.

 

[AndersonNunes]

Can anyone of you explain better how the Disconnect Handler works? Ernesto mentioned that when the call transfer succeeds, the disconnect handler acts, But if don't? The flow ends in the main flow and drop the call?

 

[edossantos]

Can anyone of you explain better how the Disconnect Handler works? Ernesto mentioned that when the call transfer succeeds, the disconnect handler acts, But if don't? The flow ends in the main flow and drop the call?

Then at that point the call is disconnected and the Disconnect Handler flow is executed. The only case in which the Disconnect Handler flow is not executed is in case of an error in the Main flow, in that case the Error Handler flow is executed.

 

[AndersonNunes]

Great! Reading other topics in the forum, I found very mentions of a script GetActiveConnectionsByCallID(). How can I use it to monitor the calls and send the end request?