This is the command used to encrypt

openssl enc -aes-128-cbc -md SHA256 -salt -pass <password>

and to decrypt

openssl enc -aes-128-cbc -md SHA256 -salt -d -pass <password>

Is your ucaout in plaintext?
Can you try without the '-F c' option like mgmtdr -v -p 5433 -h localhost -U hadb -d uca_temp ucaout

one other info - the port on the cluster DB (DB for snap-ins) is running on 5433, so if you use any psql commands use the '-p 5433' option to it

Please answer the questions from Haani and the exact command you have used and the errorr message - these things can help us to proceed further

Thank You
Dinesh

We don't have a .net sample. Can you share what is the error you are seeing?

Thank You,
Dinesh

ECC supports only consult conference, which would be like,
1. A calls B
2. B/A consuls with C
3. B/A end the consult with conference option - so that all 3 (A, B, C) will be in the same call


If this doesn't work for you. for your next question - there is no other Breeze APIs for conferencing.

Avaya Breeze SDK contains a REST API doc explaining on the EFC REST services. You should see details on how to use the publish REST API and the subscribe REST API in that (the path inside the sdk is Avaya-Breeze-SDK/REST-API-Docs/index.html)

Hope that helps

Thank you,
Dinesh

Yes, looking at the EFC REST services is the right direction

These would be the steps
1. Use the Subscribe REST service to subscribe for events of a family - also you will be mentioning the call back url (http endpoint which can serve a multipart POST http requests)
2. Use the publish REST service to publish events with the same family as in step 1
3. The http endpoint will get the event which was published in step 2

Hi

ECC doesn't support Avaya C3000, it supports only AAM (Avaya Aura Messaging)

Thank You,
Dinesh

Please refer the Avaya Engagement CallControl (ECC) SDK which has a sample application using the ECC REST APIs. Also the SDK has the REST API document. These will help you out with the questions

https://www.devconnectprogram.com/fileMedia/download/ad8d0558-031d-451b-94c8-5e93f64ef2ac - ECC SDK

https://www.devconnectprogram.com/fileMedia/download/89d9e147-e56c-48e0-89f1-543c4665e841 - Snap-in Reference guide

Also, refer the ECC snap-in reference guide to install and configure the ECC snap-in's required. Once these are deployed you can access the ECC REST APIs from outside the Breeze cluster or from a Breeze snap-in

Thank You,
Dinesh

On providing this access to cust account - you may need to raise a GRIP to send the request to the product manager so that it gets addressed.

On the actual issue - can you share the details on the errors the snap-in is facing after the upgrade. Based on the error message will try to ask more details and try to fix the issue

Yes, direct access is supported only for root user and it is not supposed to be allowed for cust account.

You can use the below as root user to get into the cluster db

mgmtia -Uhadb -p5433

Hi,

ECC sends 202 accepted which indicates that ECC accepted to drop the call and it would take some time for ECC to pass the request to AES & CM. But it should be happening in less than a second. But if that request was failed by AES for some reason the call would not get dropped. Can you share us the logs (/var/log/Avaya/dcm/pu/CallServerConnector/) or check it to see whether there are some errors?

Also have you started ECC event subscription for station C?

ECC will be aware of the call, only if atleast one of the party in the call is subscribed or the call was initiated by ECC. Since you are getting 202 accepted, ECC is aware of the callId or it would have sent 404. So I believe you have subscribed for ECC call events for station C

You can check (or share us) these logs to dig further
/var/log/Avaya/services/EngagementCallControl/EngagementCallControl.log
/var/log/Avaya/dcm/pu/CallServerConnector/CSC-csc-1.log

Thank You,
Dinesh

Joel,

Yes its possible that HTTP subscription request returned with 200 OK but the subscription actually fails and only for those cases failure status event will be sent to the call back url. If the subscriptions request itself is failed, then there won't be any failure status event to the call back url

We can enhance the REST API doc eventing section to be more clear with these details

Thank You,
Dinesh

Hi,

The success/failure status message for the subscription will be sent to the call back url used in the subscription

In the subscription request, you would need to send a callbackurl, to that callbackurl an event would be sent back mentioning whether the subscription was successful or not.

Also, to the same callbackurl only the call events will be posted

Thank You,
Dinesh