IAUG Feature Request Tracker

For unknown reasons, Agent Greetings on the J-series can only be recorded via a wired headset. However, smaller call centers might not use headsets. Please allow the agent greeting to be recorded via handset, speaker and Bluetooth headset as well.

Move the option to reset the J1xx phones so that it is not adjacent to the reboot option in the admin menu. This will prevent devices from being reset when the tech meant to reboot. Doing so means a wifi device must be re-enrolled while connected to an ethernet port which wastes approximately 30-45 minutes of tech time.

Crisis Alert is a critical life safety feature that we use with 911inform to notify the SOC when someone dials 911 - The SOC's Avaya phones are programmed with the Crisis Alert button that beeps, flashes, displays, and allows the SOC to passively monitor emergency calls as it goes out to the local PSAP, giving the SOC advanced situational awareness to respond as quickly as possible and to assist local public safety responders. Avaya offers this functionality as a Special Application (SA8654), which, by a disclaimer, is unsupported for general use and is not fully supported, making Avaya deficient in the expectation that we can deliver critical life safety 911 service– which poses a severe risk to our telecom operations. Avaya must promote SA8654 as an unsupported feature to a fully supported feature.

To enhance the auto-answer related to intercom, it would be great if the J-series could be set to auto-answer (on speaker) by contact. The contacts would have to be enhanced to support the setting. This would allow the end-user to setup auto-answer without the need for CM, the the more complex i-com group/setting, nor the caller remembering to push specific buttons to initiate an intercom call. It would also allow inter-system intercom.

Please add support for 5GHz UNII-2 Channels in J100 Wireless Module.

When a SIP phone get the SIP Controller List successfully from the settings file, it should forget all previously learned values. It seems like some caching must be going on. If I set a group on my phone, for example, that causes the phone to register to my lab Session Managers, the SIP proxy list still contains the IPs for my production SMs. This causes unnecessary traffic to the production SMs and sometimes some registration issues. This also happens when a phone is taken home by the customer. They might set the correct group to get SBC addresses, but the phone still remembers and tries the internal SM addresses, which aren't reachable and causes sluggishness signing the phone in. The should use cached previous values when it's unable to reach the file server, or maybe when it's unable to login to the SM that are in the controller list (and thus should try a cached BSM IP).

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.

Please add an item in the telephone's web interface indicating WiFi signal strength in DB in the status page.

For the purpose of properly determining the phone's location and providing the correct ELIN, the J100 series phone, when using WiFi, should make the BSSID ID available. I can think of two ways to make the information available: Make the info available via SNMP. The ELIN server could query for it after receiving a registration PUBLISH, then use that to provide back the correct ELIN. The phone should push BSSID via PPM to ASM and ASM should make that info available in the PUBLISH message sent to the ELIN server. Suggestion 1 seems like it wouldn't be too hard. Suggestion 2 involves both a new firmware on the phone and changes to ASM, so it may take longer.