Hi Don,

You have mentioned two things
1. 405 method not allowed - is this resolved or you still face this issue, I am assuming this is solved
2. The error you pasted is for consultCall, can you paste the error log for hold

Can you enable fine logs and send the log for the entire call (from makeCall)
use the command 'ce dlogon EngagementCallControl' to enable fine logs

Thank You,
Dinesh

Hi,

Can you help me understand these

1. Is all the 3 stations used A, B and C are in the same CM or you have some external numbers used in the scenario
2. Can you explain what you mean as outbound call, is it like A calls B and using A you want to consult C and conference in C in the initial call or is it like A is getting a call from an external address?

you need to use the same connectionId which you used in the consultCall to perform the conference/transfer complete. You are using some Boolean to fix the connectionId and using it in both the consultCall and completeTransfer/Conference so that looks ok

Can you check the logs in /var/log/Avaya/dcm/pu/CSCService/CSC-csc-3.x.x.x.log and /var/log/Avaya/dcm/pu/CSCService/CSC-csc-3.x.x.x-CstaMsgs.log it will give some more details

Also it would be better if you can send the above 2 logs and EngagementCallControl snap-in log to us for the entire call

Thank You,
Dinesh

Hi Matthew,

Thanks for checking the logs but there is another module (snap-in) whose logs would be needed to debug further

Can you check the logs in /var/log/Avaya/dcm/pu/CSCService/CSC-csc-3.x.x.x.log and /var/log/Avaya/dcm/pu/CSCService/CSC-csc-3.x.x.x-CstaMsgs.log

Also do you get this error only during the consultCall or during other operations as well?

Thank You,
Dinesh

Hi,
Sorry for not mentioning the exact API name

You could also use UCID as the callId in getCallInformation API but ECC should know about the call in first place

ECC would know about the call on one of the below cases
1. If the call was made using the ECC makeCall API or
2. One of the station involved in the call is monitored using ECC (ECC call events should be subscribed for at least one of the station in the call)
Else ECC will not know about the call

Let us know if you have any further questions

Thank You,
Dinesh

Using the UCID you can first invoke getCallDetails which returns the connectionIds and connectionHrefs of the stations in the call. Using the connectionHrefs you can invoke getConnectionDetails which returns the connection details and operations url (hold url, dropUrl etc.,). You could also use the getCallDetails response to formulate the hold request url.

You can also subscribe for call events of a station using ECC once subscribed, the event listener will receive events and in the events the operations url are also sent which could be directly used.

Refer Engagement Call Control REST API document for subscribing and getCallDetails/getConnectionDetails responses

Thank You,
Dinesh

After the warn did it say any errors or it completed successfully

Can you please send me the full output (the output captured in the screenshot)?
Also in the error I see mvn is run in offline mode, can you tell the exact command you are using to build the project?
Also in the screenshot I see that target/java-gen folder is empty? If build gets successful you should see the Java classes (the ones you are looking for) will be in that folder? (Sometimes eclipse will not refresh the folders, try doing a refresh on that folder if the mvn build was success)


18-07-16 1:00:15 p. m. GMT-3: [WARN] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-dependency-plugin:2.1: Plugin org.apache.maven.plugins:maven-dependency-plugin:2.1 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-dependency-plugin:jar:2.1 has not been downloaded from it before.

Hi,

Are you able to build the WebCallController without any errors in the command line. (mvn clean install) from the command line/terminal

Is the error only in Eclipse? I believe it will be only from eclipse if so try the below and see whether it get resolved

1. Try doing right click (project) -> Maven -> update project -> choose all 4 WCC modules and click ok
2. The classes eclipse complaining not available are created from JSON schemas which are built and placed in target/java-gen folder. You would need add them to the class path. right click the war module -> build path -> source (tab) -> Add folder -> choose the target/java-gen folder

Mostly 2nd would solve the issue


Thank You,
Dinesh