direct transfer to Vector step. In One-X Agent, you can type in the VDN number, then a comma and the step in the vector associated and it will send the caller directly to that step in the vector

warm transfer option. Currently you cannot do a warm transfer in Workplace, it sends the caller directly to the extension you select to transfer to

With the upgrade and migration from H.323 stations to SIP endpoints, we lose the ability to add/use abbreviated dialing for deskphones. Current Avaya recommendation - "You cannot assign abbreviated dialing buttons to SIP deskphones. SIP deskphone users can program the FAC and dial code number against a Contact or against a Speed Dial entry."

Change Avaya Messaging to send MWI OFF when a mailbox is deleted. Per SOLN359354 , currently when you delete a mailbox that still has an unread message, AM sends MWI ON. This requires a clear amw all command to be sent before the station can be deleted in CM. It makes no sense to send an MWI ON when the mailbox is being deleted. There are no messages waiting if the mailbox does not exist.

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.

Can you add a description field for the Coverage Path? This would help identify why the coverage path was created and would eliminate numerous coverage path entries simply because you now have a description of why the coverage path was created so that you are not creating coverage path that do the same thing..

i would like to have the possibility to make in the SBC Templates for the Trunks. It would save many work time because you can export and Import it to an other SBC.

As reported in 1-19084196342, J-series phones, when on WiFi, do not properly report their model and firmware info to Session Manager. This is because sometimes the J-series uses the wired MAC and sometimes with WiFi MAC when sending the device detail PPM info to SM. The model and firmware info gets sent with the WiFi MAC but at that point SM has already keyed off the wired MAC sent earlier and the model/firmware info is discarded. Tier 4 indicates "working as designed". Having the model/firmware info not show up properly makes it difficult to manage J-series phones from SMGR when they're on WiFi.

In testing the new J Series SIP Phones, one annoying thing that keeps occurring is if you set the phone to Half Screen, the button assignments do not make sense (i.e. how they Line up in CM as a SIP phone vs a H.323 phone). When you look at a H.323 phone in half screen, the buttons in CM go up and down from left to right (1 thru 4 on the Left - 5 thru 8 on the right) and it repeats all the way down. In a J Series SIP Phone it doesn't work that way, the buttons in CM have to be staggered with Odd and Even going left to right (1, 3, 5, 7 is on the left - 2, 4, 6, 8 is on the right) and repeat this all the way down INCLUDING button Mods. It's a real pain to have to match up CM button to SIP Phone placement. Can this be adjusted to be like for like between H.323 and SIP phones in CM?

When q-call buttons are put on a SIPCC phone, they don't work as expected until an agent logs into the phone. The phone then subscribes to the avaya-cm-cc-info event package, which includes notifications for the q-call status.. This should be changed in CM so q-call buttons can function with the avaya-cm-feature-status subscription (and likewise work on a type "SIP" phone vs having the "SIPCC" requirement). Many call center supervisors don't handle agent calls. Also note, upon agent logout from the SIPCC desk phone, the phone does not unsubscribe from the avaya-cm-cc-info event package. The q-calls buttons continue to work until the phone or CM are rebooted. That's probably a bug in the phone's firmware.