Do you mean you're making 100 RTD client connections or you have 100 agents logged into the server? If it's 100 RTD connections then, you've hit the limit (see P8 of RTD Programmer Guide) and you'll need to look at RSM. If 100 agents and 1 RTD stream then, no, there's no setting it should just work.

That should have read

"""
Feel free to raise a DevConnect ticket too but since that's paid support it may be less attractive.
"""

apologies.

Original query is old but this shouldn't be an issue; RTD should be fully tested for production (i.e. thousands of agents) and is utilized by the AACC MA real-time reporting. Suggest you have a look at that to see if it operates correctly. I would look to Avaya Support for assistance on this.

Feel free to raise a support ticket too but since that's paid support it may not be attractive.

So it's essentially because the CRM is external and can't be customised (even though in your case it's not about the presence of the data but the indexing on it); that's interesting. In your opinion, in a scenario without that constraint, would pushing the contactID be more effective?

Regarding the contactID, I agree, it's not perpetually unique and thus would need to be muxed with other data for use as key, however, it should be adequate for look-up within the time-frames we're thinking about. I guess that also implies a need for two additional CRM integration features (1) the ability to expire / timeout the contactID to a NULL in the event that contact is dropped for some reason and (2) the ability to trigger an update to the contactID upon handling.

I agree that parity between voice and multimedia contacts would be more intuitive but ,*personally*, I don't believe that (generally speaking) propagating data via call intrinsics is "correct" (if you'll excuse the shortness of expression).

Simon, this has come up before and I'm personally curious why the opposite approach isn't valid; so, for example, you associate some data in the CRM from the call intrinsics and then recall that data based on the available information? Would this have a beneficial side effect of recording the contact, even if it never reaches an agent for some reason?

I'm afraid that's the only chat service / API that DevConnect support. Apologies, but you should revert to support or your BDM for clarification.

Current AACC SDKs are available at the following location

https://devconnect.avaya.com/public/dyn/d_dyn.jsp?fn=742#downloads

The web-chat SDK and reference implementation is available there as "Web Communications SDK and Reference Implementation"

I understand now. This forum is for developer support and we're not well placed to assist with this particular problem. I believe you may need service support for the issue (as I'm not aware of how/if DB2 stored procedures are supported)
https://support.avaya.com/products/P0793/avaya-aura-contact-center/
but you could also try the AACC applications forum
https://support.avaya.com/forums/forumdisplay.php?f=3

Really not sure how the problem relates to AACC from the description. It looks (with a lot of speculation) like you have a 3rd party HDX application that connects to a DB2 database and produces an error, is that correct? If so, that problem would be outside of our expertise. Perhaps if we had better context but, realistically, they should raise a support ticket for a problem this involved.

Probably best raise a support ticket as this'll take some investigation, I suspect.

I have not; it looks like an internal error on your AACC. Do the RefClients still work?

That's correct; I believe this is an error in the documentation. I'm looking to verify that and will post back if it turns out to be incorrect but, in either case, the alleged value has no use.

Not really sure about this one Edward, don't think this really relates to AACC at all; we don't have any VXML interfaces so I'm not familiar. The CCT web-services won't (really) expose the type of information you're talking about, not in the manner that you're talking about. If I was to stretch I'd suggest that you may be able to get information using CCT in hot-desking mode but I'd put a chunk of money that's barking up the wrong tree. Have you tried the voice portal or interactive response people? You could also try on the orchestration forum, you could get the calls intrinsics during call routing -- that doesn't really fit into our CCT APIs either (although they can see the call instrinics that's really an end-point -- i.e. when the call's received by an agent).

Yeah, that's normal; basically, it's always "Passive". If you have a development issue with it you can always raise a support ticket.

Yeah, seems a little screwey. Just looking at the config and logs and the REST interface fails to launch it's jetty server cause of the conflict. Can you raise a support ticket on that? I need the ticket in order to escalate a WI on it.

NB: obviously there's no support cost to you for helping us.