IAUG Feature Request Tracker

Add a pre-capture filter to Session Manager for the traceSM tool. This capability already exists in the SBC using traceSBC, bring this capability to Session Manager's traceSM as well.

It would be great to be able to get a stand-alone traceSM/SBC/CE tool that we can use to parse avaya logs and captures, offline, without affecting the performance of the existing production servers. I would imagine that the tool would only be used to parse logs captured/saved from the existing tools (and not in-line), in an offline mode. This would also allow larger shops to be able to have multiple people doing diagnosis sessions without stepping on each other, particularly if they are using logs from the ASBCe. I could imagine this tool being distributed via Docker or WSL2 for local desktop support.

I would like the option to have a volume slide for instant messages similar to the ringer volume. I would like them separate instead of being one slide that controls both volumes. Since IM is very quiet unless you have the ring volume up all the way and then calling is to loud.

The current system is set up so that if you call into a coverage answer group and person A answers all other users in the coverage answer group show a missed call. Can we add functionality to the coverage answer group so that this does not show as a missed call? This adds confusion in our environment on who needs to be called back and makes the call history difficult to navigate through. Thank you

We are adding a conference line as an AUTO-DIAL for our Crisis Management Team. What we did was take an audio bridge line from SPACES. We have it automatically connect with the AUDIO-DIAL, so no passwords or space IDs are needed to be remembered by the team. This is a solution I like to present to our CMG committee. We are doing some testing and it works great on the desktop client and hardware. The ONLY hang up is that if you are using the workplace app on your mobile device (either iOS or ANDROID) the auto-dial feature is not available. FROM THE SUPPORT TEAM: 'Auto dial feature is not supported by Mobile client but only auto dial feature supported for Windows and Mac WP clients. Exclusion feature button supported for both Mobile and Windows clients. Please verify the configuration in CM side as suggested below table. Kindly add a different feature buttons like “call-fwd, call-pkup, etc.,” in Feature button and verify the same in Mobile client.' This unfortunately does not work. So I asked if Avaya would consider adding this functionality. 'Hi Anna, I fully understand the use case but this need to be put in as product enhancement via GRIP which the product manager can then decide on. Your AVAYA account manager can get this written and put it in the system for product managers review.' So I sent it to my AM and thought I would put the request here as well.

Per documentation, J-series that support background images only support 5. This is frustrating low. We have multiple departments/campuses that want their own background. While we could control the list that via GROUP, that's not user selectable. Please support more, maybe 10 or 15. The 96x1 phones don't have a documented limit.

The Agents tab of the SLAMon UI would be more helpful with a column chooser or, at the very least, an additional column displaying the zone that the agent resides in.

When a user has setup the SSO to allow a Workplace or J100 series phone to login using the corporate IAM rather than a known username and password, there should be an option to allow AADS to scramble or reset the password on each successful login attempt. Business Case: New requirements of PCI-DSS require passwords to be rotated on a regular basis, including those device-to-machine and user-to-machine passwords that aren't set by a user themselves. By rotating the password on each successful login, the password will remain new. The SSO login portion of AADS allows the user to login with their known credentials; they are not given or exposed the actual internal password used by ASM/SMGR/AADS. This request would enhance security and will for compliance while still allowing the enterprise to manage the user's password separately.

Provide a report that shows which server and client profiles reference each identity and each CA certificate. This will reduce work and uncertainty involved with certificate renewals.

Currently when running the document createCA.sh script on SMGR, the script prompts for CN but leaves the DN defaulted to "OU=MGMT,O=AVAYA". Additionally, the script has a bug in that the DefaultCRLDistPoint and CaDefinedFreshestCRL values is NOT properly updated to reflected the user specified CN. Expand the script to prompt for other standard certificate properties such as O, OU, ST, L, C (or just allow me to specify the entire DN as a string) so the CA properly reflects my organization. Additionally, the ROOTCA Certificate Profile, used by the createCA.sh script, should be updated to disallow insecure key lengths, etc.. Or even better, allow any Certificate Profile be used to create CAs in the web UI, which is currently prohibited by the web UI, which blocks saving profiles with validity periods longer than 2 years. Instead of blocking the save of the certificate profile, block usage of the profile to create identity certificates if its validity date too long.