IAUG Feature Request Tracker

The customer is looking for a report as follows: They would like a report that when they click on claims auto it should navigate to Director and Manager and their team members, we are able to create this in using sub departments but when coming to reporting it all listing in one tree as per below screen shot. We are looking for a report if we select OU then we should get an option to select Director then Supervisors under Director and when we select Supervisor we need to get the agent mail box which are under supervisor in mailbox list.

The ability of the team button on Avaya Workplace needs to be brought to the J100 Series phones to allow the two options for Audible Ringing and Visual Alert Notification to be toggled on or off depending on how the Team button is administered. Today this option only exists on Workplace and some of our users would like this feature available with their physical phones. This is a limitation is causing us to use Hunt Groups and in some cases setting up ACD's to find a solution to what already exists with Workplace.

No hold consult feature. Based on Avaya support. This feature is used only for DCP/IP hard phones. Why it is not included for soft phones.

Team, I was able to get the lab working, and I was able to reproduce the issue. To reiterate: the issue Agero is reporting is that when you are on a call the enter button on your keyboard mutes the call. This is absolutely true. More detail provided below, and yes this is something that Avaya developers are going to have to fix. This would be a request for a product feature enhancement; it is not a ticket with Avaya support. Read: do not approve charges with Avaya support. Here are the details that you could pass along to the Avaya Workplace product house if you wanted this to work in a different fashion: Behavior: when you are on an active call in Avaya Workplace the enter button on your keyboard mutes the call. Able to reproduce in recent version of Workplace 3.38.1.10 Why does it do this: You can clearly see in this screenshot "Exhibit A" that the "mute" button is "highlighted" (indicated by a dotted outline) upon answering a call. Therefor the "enter" button on the keyboard "activates" this highlighted section, thus muting the call. I suspect this was intentional, so that users can easily interact with the application without having to use the mouse. For example you can press tab, it will move the highlight over to the "end call" icon, and then hitting enter ends the call. Issue: Agent Users at CompanyA are accidentally hitting the enter button and muting their call, thus resulting in possible call avoidance Desired feature enhancement: make the "default highlighted item" configurable. Or add a configuration option that disables all keyboard interaction with the call control buttons. See Exhibit A attached

When we were using Skype, there was an option to prevent users from receiving calls if their computer screen was locked. This was helpful when someone stepped away from their desk or forgot to close the app. Could you add a similar feature to hunt groups so that users marked as "Away" on a locked screen don't receive calls?

At present, Ring Central has to ability to supply their customers with email notifications when outages happen automatically. At present this feature is not available within ACO, but could simply be added within the same menu selection. https://support.ringcentral.com/ca/fr/article-v2/Service-Status-Notifications.html?brand=RC_US&product=RingEX&language=fr_CA This would bring great value to the system and should be part of the standard offering.

Customer has an HA IX Messaging system installed with a secondary consolidated server. We found the secondary Consolidated server had not synched with the primary consolidated server in over a year. There is currently not an alarm or alert that would notify the customer the servers are out of synch and determining they are out of synch requires digging into the logs and SQL database, neither of which are something a typical customer can or should do.

In this crazy world of Telecom, we now have to worry about PKI/Certificates. It's very confusing, cumbersome, and painful managing ALL of the required Certificates for all the different Avaya Systems/endpoints. It would be NICE if Avaya had a better way, than through SMGR, to handle certificate requests in environments where there is not a strong PKI/Certificate structure in place and Self-Signed is the only option. Or at least make SMGR a bit easier to handle for certification management.

The Device manager feature is quite handy when checking to see if there are any critical outages on network that need immediate troubleshooting. However, the local IP address of the device does not show or register in the device manager information or in the profile of the phone when logged into the system. This would be helpful in case we need to debug to trouble shoot the information. It seems like this information should be available as it does broadcast its Public IP through the ISP. Can this information be captured for ease of use/checking when needing to debug call quality or other issues?

The ASBCE Incident Report should have a full export capability. Currently the PDF export is a summary of issues without the exact detail that is visible by clicking into the incident. Makes reporting/tracking very difficult. There should also be an API to capture incidents.