Hi,

Is there a way to handle the disconnect event, where caller disconnects and application can itself handle that event and follow the exit path.

I am using Interrupt event but doesnt seem to be working.

please let me know if there are any other events which we can use.

Regards,
Rohit

Hi Rohit,
when caller disconnects , the call ends or the other party is still on call ? if the call ends then you can listen for call end event.
You can chose MessageBoundary Event or Receive task based on your workflow.
Select Family as Call, Type as CALL_ENDED, version 1.0 , criterion as call and use input mapping and map the callID to call String Filter.

Else if only the caller ends then use
Family as Call, Type as PARTICIPANT_DROPPED, version 1.0, criterion as User and use input mapping for the task and map user value in Filter


When the call ends the above is invoked and you can model your workflow accordingly

Thanks,
Rajesh

thanks Raj,

My flow is simple as play announcement get input from caller and then send email. If anytime between caller drops the call, application should handle the call and disconnect instead it just sits there when I see the instance.

Regards,
Rohit

Hi,
could you please attach your workflow ?

Hi raj,

Please find the attached callflow.

Regards,
Rohit

Hi,
for your use case, after the call is dropped you want the workflow to stop further execution and take specific path to handle call end. for that please find the screen shot attached , let us know if that helps.

In the image when the call ends during play and collect operation I am catching call end in global event (interrupt task) followed by just doing a log message(you could model your use case) and then terminate which will stop the further execution of main workflow.

Hope this helps, let us know if you still need any info.

Thanks,
Rajesh

That’s great help. I was just wondering if we have to set any family for interrupt or terminate ?

yes you need to set the family type and version, PFA of wfd used.

Hi Rajesh,


I have made the changes as per your recommendation but still workflow instance remains in error state if call is hungup in between.

Can you please let me know if there is anything I need to do.

Regards,
Rohit

Hi Rohit,

Can you please export the workflow and send us. We will try to debug at our end.

Regards,
Shikha

Hi shikha,

Here you go.

Thanks,
Rohit

Hi Rohit,

"NoInputAnn" task is giving error when I am executing it.

Can you please open instance and check that which node is giving you error.

Rajesh, I have attached logs also for the same.

Hi Shikha,

I am actually not having an issue at that point, I can get my announcement played and everything. However on any point if caller decides to hung up the call, Work flow instance receives the error and just stucks there until we manually purge or delete the instance.

regards,
Rohit

Can you send the picture of Workflow instance? Does interrupt event triggers or not?

Which node do you see in red color?

Here is the attached screen shots for few places.