IAUG Feature Request Tracker

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.

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.

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.

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.

CM SIP trunk optimization groups several signaling groups together to avoid having to create redundant trunks to SM. However, the outbound routing scheme is load balanced only. Please consider creating an option for priority based routing so calls only land on a secondary SM when the primary is unavailable. This makes routing behavior more predictable and simplifies troubleshooting.

Customer is using Pindrop as recording solution. Pindrop is a security company that focuses on voice security and fraud detection. The current call flow is as follows: The call enters the RW SBC from Lumen IP, then to SM and finally to Pindrop. From SM, the call also routes to the non-RW SBC and then to West IVA SBCE. The call then returns from West IVA to the non-RW SBC, back to SM, and a refer is sent to the SW SBC, where the call is moved to the agent. The more meaningful conversation occurs between the customer and the agent (i.e., after the REFER message)., which is currently recorded separately after the transfer. Desired Outcome: SIP-REC - Have a recording that captures the entire process: when the user dials in, hears the IVR, makes a selection, waits in a queue (possibly with some music), and finally speaks with an agent—all in the same recording.

So that call centers can make routing decisions based on the stir/shaken attestation level, a vector variable should indicate the 4 levels (A, B, C or none). This would allow call centers to do things like queue possible scam calls at a lower priority, or send them to voicemail instead of queuing.

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.

Our future plans call for wireless network devices to have 802.1ax with 6ghz capability. Please consider a new wifi module for J100 with this capability and backwards compatibility with existing environments.

Add the capability to blacklist devices based on MAC address. On occasion, users will lose their remote worker phone or not return it after leaving the firm. This would allow us to blacklist those specific devices.