Does the architecture only support SIP communication or can it also support PRI? If so, how does that work since the breeze architecture diagram only shows communication between Session Manager and SIP entities.

JoelEzell wrote:Thanks for the update. By "MySQL Connector", do you mean a MySQL JDBC driver as installed through System Manager?

that is correct. We removed the JDBC source, and the provider. Reinstalled and the issue went away.

JoelEzell wrote:Have you been given a SR# or PEA#?

Joel,

I was contacted by support again yesterday and Anitha assisted me looking through the logs. Breeze was throwing an unhandled exception which prevented EventCallControl from initializing. The exception was caused due to breeze looking for a property in the MySQL connector and for some reason it couldn't find it. I uninstalled the MySQL connector and reinstalled it and the problem went away.

Thanks for your assistance.

JoelEzell wrote:Sorry that you're getting the runaround here. The very first thing that I would need to do in order to try to diagnose this problem is look at logs. We shouldn't be collecting logs here in the forum; that's an ACS thing. I really think ACS is the way to go. I'll alert Tier IV to this issue as well so they can try to follow up.

I haven't heard back from Level 4 support and I tried contacting them a couple of times but no luck. Any idea why the CallEventControl throws this error. When I select CM as the termination application sequence for the pattern in Session Manager the call works fine, but as soon as I add breeze as the termination sequence, the call continues to ring and it goes through, but it does not get intercepted and this error is thrown.

JoelEzell wrote:Sorry that you're getting the runaround here. The very first thing that I would need to do in order to try to diagnose this problem is look at logs. We shouldn't be collecting logs here in the forum; that's an ACS thing. I really think ACS is the way to go. I'll alert Tier IV to this issue as well so they can try to follow up.

thanks Joel. Tier 4 support reached out to me but I do have a question for you regarding the eventcallcontrol. I came across this thread from a year ago where you provided some explanation about it.

https://www.devconnectprogram.com/forums/posts/list/21296.page#p150596

looking at the logs, the 500 server internal error is thrown by the eventcallcontrol which is internal to breeze. this wasn't happening before the upgrade.

comparing older log to the current log, I am not seeing the CECS being invoked. are there certain call intercept cases where this CECS is invoked, for example, intercepting calls from DIDs?


thanks

JoelEzell wrote:Hi, is there a service contract for this system? If so, please open a ticket with Avaya Client Services.

I contacted client services prior to posting here. We were told that it maybe a configuration issue which is not covered by the support contra t. All that was done was the system manager and session manager upgrade. Prior to the upgrade call intercept worked fine

After upgrading system manager and session manager to 7.1.3, call intercept fails for breeze 3.4

looking at a traceSM we see a 500 server internal error. is there a comparability issue?

After upgrading system manager and session manager to 7.1.3, call intercept fails for breeze 3.4

looking at a traceSM we see a 500 server internal error. is there a comparability issue?

PrakashN wrote:Can I see the following please:
The tasks.json for your new task
The Engagement Designer log captured at fine level while validating.

I am getting the same error when testing with the example in the Creating Dynamic Tasks for Avaya Engagement Designer R3_3_I1_GA_176733.pdf document.

1 Error(s)

:Unknown nodes are found in the workflow! Please verify that you have installed all the necessary snap-ins required to run this workflow!

1buckeyefan wrote:I've installed the EmailConnector and configured the settings. However, when I open ED I do not have a task on the left to send email or the notification group. What am I missing?

can you take a screenshot of the task buckets that you have on the left side?

bbailey wrote:Where can we see the SQL that is generated by the 'update db' or 'read from db' tasks? No matter the logging level I set for Engagement Designer, there is not logging of the SQL.

From the oracle side, if you use Toad for Oracle, you can view the sessions and the incoming sql as for ED logs, I am interested to know the answer as well if there is a way to see the sql from the logs.

WalterJacob wrote:Anyone know how to get the System Time within Engagement Designer? I have a workflow that is not a Call Intercept. I trigger it with a RESTful web service call. I need to get the current time when the workflow is kicked off. I also have a workflow that runs continuously monitoring a database. Again I would like a node (or anything) that can return to me the current time of the Breeze Server (or an NTP server)

I will speak for version 3.4.

There is no support for dates/date functions, but you have two options:

1- write a dynamic task using the SDK to provide you with that functionality.
2- use a REST API to get the date time. (either a service or create your own)

porterk wrote:Hi Wilder,

Could you please confirm if this issue has now been resolved?

Thanks,
Kezzia

Yes. Thank you very much.

Wilder wrote:

porterk wrote:Hi Wilder,

Please check the value of 'Only allow secure web communications' in SMGR->Cluster Attributes ->select your cluster.
I'm on a training course this week, however we could arrange an online session next week to try to resolve this issue?

Regards,
Kezzia

This setting solved the http issue, so now both http and https requests work, but the context store task in ED still returns the error. I will get those logs and post them soon. Thanks

Now i am able to add context using postman and Get context using ED context store task. I am unable to add a context through ED but I think that has to do with the parametesr (ContextId, GroupID, and key/value pairs) being passed as a context.


I am passing ContextId, Group ID, and key/value data. The sample workflow is attached. Get Context works fine, but not Add Context


2018-09-13 18:00:29,911 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Store WFD in data grid: wfdName = debug_1536876025534 wfdVersion = 1; date = 2018/09/13 18:00:29
2018-09-13 18:00:29,916 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Adding debug_1536876025534_1_customer com.avaya.app.entity.WFDSvar@cc0c605d
2018-09-13 18:00:29,979 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Adding 1413 com.avaya.app.entity.Instance@e6da570c
2018-09-13 18:00:29,979 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Publishing event for create instance with payload: null
2018-09-13 18:00:32,247 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - eval is: {"key2_name":"asdfsa3234","key1_name":"asdfas3343","key3_name":"asdfas12312"}
2018-09-13 18:00:32,249 [WebContainer : 1] rest.ContextStoreHttpsRESTClientService INFO - [M:postContext][T:null]. Request URI = https://11.242.143.53:443/services/ContextStoreRest/cs/contexts/?lease=7200&rules=false
2018-09-13 18:00:32,255 [WebContainer : 1] response.ResponseDataUtilsForHttpsClient ERROR - [M:processHttpResponseStatusCode][T:null]. BAD_REQUEST request error when running the http request, statusLineCode = 400
2018-09-13 18:00:32,255 [WebContainer : 1] EngagementDesigner ERROR - EngagementDesigner-3.4.0.0.32008 - Invalid request, BAD_REQUEST
2018-09-13 18:00:32,255 [WebContainer : 1] EngagementDesigner ERROR - EngagementDesigner-3.4.0.0.32008 - The request failed response = BAD_REQUEST
2018-09-13 18:00:32,256 [WebContainer : 1] rest.ContextStoreHttpsRESTClientService INFO - [M:getData][T:test3242]. Request URI = https://11.242.143.53:443/services/ContextStoreRest/cs/contexts/test3242
2018-09-13 18:00:32,276 [WebContainer : 1] response.ProcessHttpResponseUtils ERROR - [M:processHttpResponseForGetData][T:test3242]. Exception: Error occurred extracting data - "No data found."
2018-09-13 18:00:32,277 [WebContainer : 1] EngagementDesigner ERROR - EngagementDesigner-3.4.0.0.32008 - Invalid request, ERROR
2018-09-13 18:00:32,277 [WebContainer : 1] EngagementDesigner ERROR - EngagementDesigner-3.4.0.0.32008 - The request failed response = ERROR
2018-09-13 18:00:32,294 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Removing 1413
2018-09-13 18:00:32,313 [WebContainer : 1] EngagementDesigner INFO - EngagementDesigner-3.4.0.0.32008 - Adding 1413 com.avaya.app.entity.Instance@b63d0b29

porterk wrote:Hi Wilder,

Please check the value of 'Only allow secure web communications' in SMGR->Cluster Attributes ->select your cluster.
I'm on a training course this week, however we could arrange an online session next week to try to resolve this issue?

Regards,
Kezzia

This setting solved the http issue, so now both http and https requests work, but the context store task in ED still returns the error. I will get those logs and post them soon. Thanks