Search results for query: *

@Stinney, thank you very much for all this.

@Stinney, Thank you very much. Again, much appreciated.

I'm okay with those requirements and risks. Thank you!!

@Stinney Thanks again. The more I think about it and the more research I do, more use a custom solution rather than the rt_socket. Is your solution "open source" or is your code available so we can support our customers ourselves with it? How would I go about getting your solution? Gilles

Thanks. This is great info. The fact that we need items like Acceptable is as you pointed as if we are looking for cumulative, and that is true, but we need to show items that can show realtime like calls waiting, agent staffed, and also show cumulative ones like Service levels, aban rate etc...

That's wonderful. Thank you. We will look at this and if we have more questions, I hope you won't mind that I come back. In the meantime, I am very grateful for your help. Regards Gilles

Thanks Montyzummer That is helping. We do need the "current" data. I need to refresh the data every 3-5 seconds. So it sounds like the RT_Socket would be the advisable way to go. Well, I'm also now intrigued by your comment about Stinney solution. The fields (items) we need to be sure to have...

Thanks Stinney, We have been able to do what you have in link, but there are fields (items) that are not in some of the reports that could be accessed via some other way. I heard RT-Socket can provide more fields (items). Are you familiar with RT-Socket? Thanks again for the quick response...

Hello A little bit of context: No Avaya system available to me. Potential customer is a financial entity and getting access at this stage for Dev/Tests is out of the question. So we're pretty much in the dark as we know nothing about Avaya, and CMS. Their system is Avaya Elite 6.3 with CMS R18...