actually, on the contrary, I needed to add to it rather than reduce it. It now works with Telecom.dbo.Breeze.

thanks for everyone's help.

Andy

yes, same command in db works fine. see attached picture.

It doesn't allow me to go to input mapping. It shows 'Syntax error in schema'.
I've attached a picture of the Update DB data.
I'll get the LOGS and attach in a bit.

I can connect to the DB from Breeze. The test connection shows completed successfully.
attached is my WF (stripped down the Auth info). It is only a test WF for validation purposes.

I have built out the connection to the DB per the documentation. I am now trying to use the Update DB in a WF. I select the DB server from the dropdown profile name and enter the following SQL Query (format per example in EDDeveloperGuide page 80)
INSERT INTO dbo.Breeze (OriginalANI, OriginalVDN) VALUES ('18015555898',?)

The OriginalANI and OriginalVDN are field names in the DB i'm trying to update. I get the following when Retrieving the input schema:

error getting input schema for update DB task: java.lang.illegalstateexception: Failed to get parameter metadata from SQL

what is the best way to grab only the time from the CallEvent ["timeOfEvent"].

the format is 'timeOfEvent':'2018-12-06 13:13:27

I am pretty sure this regex \d{2}:\d{2}:\d{2} will get me 13:13:27 but not sure how to get this and save it in a new variable.
I tried this:

CallEvent["timeOfEvent"].replace(\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}, \d{2}:\d{2}:\d{2})

also tried
currentTime["TimeOfDay"]==Call["timeOfEvent"].replace(\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}, \d{2}:\d{2}:\d{2})

the currentTime["TimeOfDay"] is a separate variable.

I am trying to figure out a way to route in ED based on time of call compared to time of day. maybe there is an easier way.

syntax on either of those is wrong. doing this in Engagement Designer.

what is the best way to grab only the time from the CallEvent ["timeOfEvent"].

the format is 'timeOfEvent':'2018-12-06 13:13:27

I am pretty sure this regex \d{2}:\d{2}:\d{2} will get me 13:13:27 but not sure how to get this and save it in a new variable.
I tried this:

CallEvent["timeOfEvent"].replace(\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}, \d{2}:\d{2}:\d{2})

also tried
currentTime["TimeOfDay"]==Call["timeOfEvent"].replace(\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}, \d{2}:\d{2}:\d{2})

the currentTime["TimeOfDay"] is a separate variable.

I am trying to figure out a way to route in ED based on time of call compared to time of day. maybe there is an easier way.

syntax on either of those is wrong. doing this in Engagement Designer.

andywfinlay wrote:I have a workflow that will call back a customer if they disconnect first and the agent selects to call them back. If they don't select to call them back I have a 'Drop Call' module that drops the call and works fine. If they select to call back the customer the call goes out (via 'Add Participant) and connects but when either the customer or agent disconnect after that call the other end stays up. looks like i'm missing call supervision or something to notify either end when the other end disconnects. I see the callflow hit the 'End' module as the WF is completed after the agent calls the customer back. I've also tried 'Terminate' but still the same issue. What am I missing?

So after a bit of trial and error I was able to figure this out. In order to make sure the call doesn't disconnect when the caller hangs up on their end (or loses cell connection) I had a 'Set Call Policy' at the start of my workflow set to 'Drop call when no participants remain'. This is great when the customer hangs up it allows the agent to stay connected and re-connect with the caller. however, when the 'add participant' step brings back on the customer it's still under the original 'Set Call Policy' so it will drop the call only when 'NO' participants remain. I ended up adding a new 'Set Call Policy' after the 'add participant' and set it to 'Drop Call If One Participant Remains' and that seemed to do the trick.
As always, hope this helps someone out!

Andy

I have a workflow that will call back a customer if they disconnect first and the agent selects to call them back. If they don't select to call them back I have a 'Drop Call' module that drops the call and works fine. If they select to call back the customer the call goes out (via 'Add Participant) and connects but when either the customer or agent disconnect after that call the other end stays up. looks like i'm missing call supervision or something to notify either end when the other end disconnects. I see the callflow hit the 'End' module as the WF is completed after the agent calls the customer back. I've also tried 'Terminate' but still the same issue. What am I missing?

I have created a workflow that needs to include an OAuth Token to work properly. I can execute the initial POST API token request in Postman and get the Token however I cannot get it to work in ED. I assume my fields aren't mapping correctly.

Additionally, the next REST API call requires the Token to be included in the call for OAuth. I have added a custom header for auth_type which is in my original POST call for the token since there is not a default field for that. I put in all the OAuth name, password, Client ID, and Secret and then add the Oauth URL (for the initial Token request) I get an error saying unable to obtain the OAuth Token.

To test the Workflow I took the Token I get in Postman and cut/paste it into the OAuth Token field and it actually works. No errors when I create an Instance and I get the correct data back. Obviously I can't do that in my normal workflow so wondering how to get this to work. Happy to make two different API calls (one for token and populate it into a variable and the other to add the Token and call the other URL) if I had to but would prefer getting this to work with just one CallRESTService.

Getting the 'CertPathValidatorException: Certificate chaining error' when running through my Instance (see attachment). I get results and no errors in Postman or running through a web browser. I saw some previous posts on installing trust cert in Breeze. We don't use 3rd party certs for SMGR so I installed the SMGR trust cert into Breeze but made no difference.
I've had success with some other API workflows although this one is HTTPS rather than HTTP. I will admit certs are not an area I am overly familiar with so I wouldn't doubt something may still be missing.

RajeshChandrashekar wrote:Hi,
The Call variable gets populated in case of call intercept workflows, for outbound calls, we need to create a variable and map the output from make call to this variable.
Attached is the workflow draft, please import and execute and let us know if you still face any issues.

Thanks,
Rajesh

that worked but wondering why the output mapping was going from the appid rather than the UCID?

andywfinlay wrote:I was able to get past the InetAddress by disenrolling the AAMS and then re-enrolling it with SMGR.
It still isn't working but the logs show it can't connect to the AAMS and that it is not unlocked. I have confirmed it is unlocked.
also see some cert errors. I will open new thread with these specific issues and include recent logs.

to help out someone looking for how this was resolved. the AAMS (media server) wasn't authenticating due a missing REST login and password (required for 3.4). this is configured in both the AAMS (Signaling Protocols) and Breeze (Cluster Configuration). To resolve the cert errors I reissued new SMGR certs and assigned them to the individual service profiles in the Key Store on the AAMS Certificate Management page.

adding a little at a time as I grow my basic make call workflow, i've added a 'play announcement' event and after it calls me it just stops with an error on the play announcement. it says Invalid Argument! CallID cannot be empty..
I have mapped the UCID in input mapping and assigned a valid announcement in cstore. attached is my workflow and a jpeg of the error.

andywfinlay wrote:

PrakashN wrote:So is there a workflow that gets kicked off? I do see the certificate errors in the ED log attached, but I dont see a workflow getting kicked off in the log. The Make Call snap-in - the workflow containing Make Call - do you see an instance getting created in the ED Admin Console?

yes, the instance gets created with an instance number. I also go in to the instance and it shows 'active'.

On another note, I resolved the cert issues but see the following in my new logs:

2018-08-07 15:48:42,604 [WorkManager.MediaServerThreadPool : 0] com.avaya.AamsConnectorLibrary FINE - [raiseAlarm::] Alarm Alarm: Type: CRITICAL, Description: Connection to AAMS failed, Message: Failed to connect to AMS: Invalid Credentials,
AAMS HostName: pvo-aams-ad1.apex.local, AAMS ip: 172.16.254.155, initialOccurance: 1533678035615, lastOccurrance: 1533678516603 | MediaServer:
inetAddress: pvo-aams-ad1.apex.local/172.16.254.155, port: 7151

I reset the SMGR AAMS user password (AAMS user you configure when you setup the AAMS) but that didn’t make any difference. Do you know what credential this is referring to?

in order to help others the resolution for this 'invalid credentials' is setting up the REST login/password in Breeze and the Media Server.