IAUG Feature Request Tracker

We're receiving more and more requests from our government accounts to support pure IPv6 networking for self-service platforms such as Experience Portal aligned with OMB Memorandum M-21-07. It would be highly beneficial to add an out-of-the-box configuration for pure IPv6 for customers such as these who in most cases need to stay on-prem. Thank you for your consideration.

I’d like to request more flexibility for coverage answer groups—specifically, the ability for users to join or leave the group from their soft clients or desk phones, similar to the “busy out” option in hunt groups. Currently, that control isn’t available, but it would be a valuable improvement. Our teams want all employees to ring, but also need the flexibility for individuals to opt out when needed.

I know this was already brought up and closed, but I'd like to bring it back to light because it seems crazy that the Media Server does not support T.38. With Avaya moving to software based DSPs, and offering the Avaya Media Server as a suitable replacement, I am shocked to learn that it doesn't support T.38 faxing. I would strongly suggest they work on getting T.38 support on the next release of Avaya Media Server to make it more future proof.

Aux Work Codes have been assigned for RONA, ROOF and IP Failures in System Features, page 14. These 'redirection' features are based on RONA redirection functionality and each may result in incrementing CMS counts for Redirection on No Answer, causing confusion as to the actual cause of high RONA counts. Separate CMS count metrics are required for each.

Currently, there are ways to implement user templates to augment the profile settings. Security features are left out of these templates and should be excluding this: When adding multi-site locations, and adjusting the site settings for data access, the application does not update until a sign out has been made. With 2000+ users, this would be untenable to do individually. I would like to ask that the "Sign-out from All Sessions" option be allowed to be applied to all or a group of users via a template.

We are attempting to implement the Avaya Calling Integration and have encountered two items that are making this a non-starter. We are wanting to utilize the free option because the other options involve substantial cost. The two issues are as follows: When you place an inbound call you have to have Workplace logged in to have the call pass to Teams. Can we have this integration do the same as a mobile phone that allows it to pass the call through without being logged in. The other issue is that there is no way to hang up the call in Teams except for key shortcuts or Avaya Workplace. Can this be changed to allow Teams to hangup, put on hold, or transfer the call. Thanks!

Figuring out where a workplace client is today, for emergency calling purposes, is difficult. It would be great if the Workplace client could communicate locality detection data (BSSID, LLDP, CDP data) somewhere, similar to the J-series phone. This could be done via a web call, like the J-series, or by sending that info down to SM and have SM send it in the ELIN PUBLISH message.

Workplace is really horrible design (mobile and desktop) Needs to be fully redesigned They should start by exact copy of RingCentral (and avaya Cloud Office) app Those are 5,000% better than Workplace!!! Plus, support for bridge call appearances and multiple call appearances. just like hard phones have. This would be for AURA AND IP OFFICE

Remote Agents can use the MDA feature to have the 'same looking' station at the office and at the remote work site. Hybrid agents may work from either site. The agent's Extension and Login ID will be the same. There is no simple way to discern a remote agent from one working at the enterprise in CMS reporting. Including the IP address of the station being used by the agent will enhance the use of CMS data in evaluating agent performance as well as troubleshooting. Please add it into real-time cagent table and historical call_rec, ag_actv and hagent tables.

In EMS, under Status, we can see User Registration information. Please add the capability to export this information, which should include everything in the Details section.