The application has been made available for download again here

The cache is most likely in your browser or the nginx config file, and not WebSphere.

When your snap-in VoiceBiometricsService got deployed on Breeze node, http_VoiceBiometricsService_80.conf and https_VoiceBiometricsService_443.conf get created under /etc/nginx/ce_conf.d/. These two file include a line that will redirect http/https request containing “services/VoiceBiometricsService” to “services/VoiceBiometricsService-” where your snap-in is actually provide REST service.

Uninstall version 218 and install version 219 via SMGR should update the two config files with the new version for redirection. Given the fact that you got the same error even when your snap-in is not install at all let me believe that the cach is in your browser. You can run traceSM on Breeze node to see what is coming in on the REST request from the browser. It’s likely that you’ll see “services/VoiceBiometricsService-1.0.0.0.218” in the URL even when you actually have version 219 installed. To solve this, you’ll need to clear out the cache on your browser.

It sounds like you have verified the settings in the console, but just wanted to double check if you had seen this and verified

https://www.ibm.com/support/pages/how-diagnose-error-srve0255e-webgroupvirtual-host-handle-0-has-not-been-defined

Have you had a look at the SystemOut.log file to make sure everything is starting up successfully?

Hi Rahul, can you send a screen shot of the webpage when you get that error. Or just the URL that you are using. I found one resolution was that if you are using http://127.0.0.1/Services/SnapInName to actually put a slash at the end of the URL like this http://127.0.0.1/Services/SnapInName/

Please open a Technical Support ticket, and we can discuss your DevConnect support options for this issue.

Sounds like you are talking about the Customer Interaction Utilities package. If that is the case have you seen this page? There are some helpful links there. The cluster IP is just the IP of the Breeze cluster that is setup in System Manager. If you just have one Breeze node you can also just use that IP. I am not seeing CLIENT_ID and SSOToken, so I may need more information on the exact package and file you are looking at.

I wasn't aware that the UnifiedAgentController had an API. What document are you referencing that explains this programming interface?

Is it forwarding you to the AuthorizationService? If so you would need setup an Authorization Mechanism. Chapter 8 of the Avaya Breeze® platform Snap-in Development Guide explains Authorization.

The snap-in is deployed on Breeze and then you use the SDK JS to integrate your web pages with the Co-Browse snap-in. Since your web server is on a different server than Breeze I think the answer to your question is yes based on my understanding of what you are asking.

Please go to the Webtext SMS snap-in on our Snapp Store and click the "Request Info" Button and fill out your information.

Hi Patrick, the supported devices and browsers are listed in the Co-Browsing snap-in reference guide. This does not include any mobile app support at this time.

Just wanted to let you know that I am trying to get some help for you on this. That message you are seeing looks to be pointing toward a certificate problem as you already have suspected. From what I can find it looks like you need to trust the certificate in the browser as you have done already. Have you also gone through the Avaya Aura Contact Center Commissioning document as there is some certificate instructions in there as well? I will try to get some additional assistance on this as well.

Hi, the ANI II digits would come from the CSC, which connects to Application Enablement Service via DMCC. Unfortunately the CSC does not expose the private data parameter that carries the ANI II information. Further I am uncertain if it is even provided to DMCC in a SIP scenario as I tried just some DMCC scenarios myself and do not see that parameter. Sorry I don't have a more positive answer.

The actual DTMF tones come from Communication Manager. In that case I would look at the Communication Manager Screen Reference (on the Avaya Support site) for your version and look for any references to volume of DTMF. In the 8.0 version Chapter 139 looks like the closest thing I can find. You could try playing with the decibels for touchtone there and seeing if that will help. But no, JTAPI is not going to be able to adjust the volume of DTMF.

Are you using Experience Portal? Since there isn't a forum for that you would need to open a DevConnect technical support ticket and see if someone can point you at the answer. I think there is a CTIConnector that would be used for that I just don't support it so couldn't tell you for sure.

If monitoring the hunt group you will only get the loggedon and loggedoff events. All other Agent State events don't come in unsolicited, you have to poll for them.