Hi Karthik,
I learned from Breeze team that the alarms would be only send if the nodes in the cluster are in accepting services state. Please check if the cluster or any of the node in that cluster is in "deny services" state. If so then that would cause the alarms not showing up in SMGR.

Regards,
KK

Hi Karthi,
This may an issue between Breeze platform and SMGR. Could you please raise a support ticket on Breeze platform.

Thanks,
KK

Hi Karthik,
There is a SetAlarm task in the notification category that can be used to send alarm to SMGR. I am not sure if there something in SMGR to send emails for the alarm. Please check SMGR documentation. Alternatively, you could use SendEmail task in the workflow if the Breeze is setup for sending EMail with email connector snapin.

Hi Louise,
When are you getting this error? What is the version of ED?

Thanks,
Krishnakumar

Hi Karthik,
There is no task in ED to get call status.
You could use global interrupt event handler to wait for CALL_ENDED event and perform post call activities. Just make sure you map the UCID to the call property in the input mapping. Otherwise the CALL_ENDED event will be broadcasted to all the instances and interfere with other calls.

I have attached a simple example workflow that does this.

Hope this helps!
KK

Hi Chris,
Could you please share the workflow you are designing and provide more information on what you are trying to do with references to the tasks in the workflow.

Thanks,
Krishnakumar

Hi Marcus,
Thanks for the file. I think it is solution design issue. If I understand the workflow correctly, you are creating the instance for the incoming calls and trying to make a new call to the number retrieved from the DB.
This is what I believe is happening,
Incoming call comes to Breeze. Breeze sends CALL_INTERCEPT_TO_CALLED_PARTY event to ED. ED creates the workflow instance. In the workflow, you are reading a number from DB and making a new call to this number. If this is internal call then it might be coming to Breeze as a new call and Breeze is sending the CALL_INTERCEPT_TO_CALLED_PARTY to ED. ED creates a new workflow instance. And this becomes a loop.

What is your intent for the incoming calls? If you need to forward to the internal number then you should use forward call task. MakeCall task is only be used to create a new call.

Hi Marcus,
What is the version of ED?
Has the exported file been modified/saved by any other editor after the export?
Could you please export it again by selecting "export as" then select "Export as XML" and attach it. Please dont open this in any editor and save it.

Thanks!

Hi Marcus,
Screen shot would not help. Please use the "Export as" option to export the workflow and attach it here.

Thanks

Hi Kishore, please post this question in the Breeze platform forum.

Hi Marcus, could you please export the workflow and share it. Thanks!

Hi Marcus,
"Telephony Communications" is part of EngagementDesigner task bundle. Please make sure you have the task bundle deployed in admin console.

Hi Markus,
Could you please check if the following properties are available for the missing datasources.

Url
Validation query
Username
Password

If anyone of them is missing/blank then that datasource will not be added to the list.

Hi LeeMarvin,
The Breeze services logs are located under,
/var/log/Avaya/services

And ED logs are under,
/var/log/Avaya/services/EngagementDesigner

You could use vi editor or any other editor to view the logs.

Hi,
Have you tried "OAuth 2.0" option for http authentication? This option would either use the oAuth token if provided or try to get the OAuth token using the parameters you provide and use it for the http request.

If you have tried with this option and did not work, could please share the error you are getting?

Thanks!