This information is helpful. Are you still able to create an Agent and Supervisor experience with the Communication Services? We want to be able to create a role system and is it possible to create this without Oceana?

For the project I am working on, I want to be able to handle audio calls, text messages, and video calls. Which service should I mainly use for functions calls when dealing with the Client SDK? Communication Services or Customer Interaction Services? My main overall question I guess is what is the difference between the two types of services as they appear to use similar function calls.

I am using Avaya Breeze with Client SDK with release 3.2.1 But I dont believe this is a real question anymore. Thank you for the response.

I have seen the examples but all of them have a login screen. I was wondering what might be credentials to get past this. Looking at the code it doesn't appear that it is hard coded.

Also may you provide a link to where I can find all the information. What I am looking at is pre-release examples.

I am currently using Client SDK and I am trying to figure out what the exact workflow of functions need to be done to log in, authenticate through SSO, then put a call taker in the ready state to take calls. Then also to a point going to a work day and following it up with logging out. Currently I have login() -> authenticate() -> newAgent() -> activate() -> goReady() -> logout(). Any answer on this would be helpful. Where I am on the right track, missing functions, or have it completely wrong. Trying to put a UML diagram together to better understand what all needs to be done and in what order.

We will be building our own Client using the Breeze and Oceana SDK.

Joel, would it be possible to have this feature through Oceana and/or Workspaces and WebRTC? This is what we will be mainly working with in the future. We are currently using ECC to get basic call understanding.

I looked at the code and I got a "generic error":

2016-11-09 09:18:27,317 [GS-SimplePollingEventListenerContainer-1] EngagementCallControl ERROR - EngagementCallControl-3.1.1.1.311102 - onError: requestId: 1002f91f-7bc2-465e-94ae-2ebab82d4cdf class com.avaya.ucm.command.response.CreateConsultContactResponse with error GENERIC_ERROR


Any indication that might be going on here?? On a similar question, any idea what "GENERIC_ERROR" is?

When i try to perform call functions using the ECC, sometimes it works well, other times I get a 500 error (Internal Server Error). I was wondering what might be causing this and how I can prevent it. Is it just the system overloading and not being able to take multiple function calls consecutively or is it just the code on our end? If it is overloading, is there a way to configure it to be able to take more? I am currently using Context Store to store call information, then using the info perform functions with the call to a certain station. Any help is appreciated.

Thanks John, that helped me in the right direction. But in the documentation it talks about Installing the Streams SVAR. I was wondering where I would find that file. I currently don't have that service on my cluster.

Hello, I am currently working with the context store in storing phone data. I am using the context store in both Engagement Designer and java snap ins. In research I have found a snap-in called Screen-Pop. It was brought to my attention that there is also a snap-in called "Context Store Stream". I was told that this is a way to have more simultaneous updates for the current call status to be sent to my UI compared to Screen-Pop. I was wondering if there is an SDK or API or any form of information on what Context Store Stream is or how to use it.

Hello,

I am currently building an application using HTML5 and Angularjs for the front end and java to build Avaya snap-ins. I am currently wondering how I am able to use the Client SDK to connect the front end of my project to the back end. Any help on this topic is appreciated. Just not fully understanding where to get started and what the exact connections have to be.