This message was deleted.
# _general
s
This message was deleted.
m
u
Depends on the softphones too 🙂
r
I just went through the Avaya part vdi communicator according to avaya is no longer used. Vdi equinox now.
Not knocking the doc. Great doc.
m
Looks like even Avaya is not sure about that (notice the question mark 🙂 ) :
r
Haha yea i pointed that out as well to avaya. But its the same principal
m
@Allen Furmanski You OK with me fixing name to Avaya Equinox and changing link to https://support.avaya.com/products/P1706/avaya-equinox-vdi?
r
These tech zone docs are truly amazing. I just read through the software one. Great jobs 👍👌
j
Thanks guys, the softphone is Gamma Horizon which I have never used. I dont believe it’s supported in Citrix so it may be a non-starter. The infrastructure is on-premises next to the endpoints and the client is licensed for Premium. I wonder if the local app access feature could be leveraged here? Something I haven’t used or tested, cheers
a
@Martin Zugec Sure I am ok with updating to the new Avaya naming.
r
John, you might be able to tweak the policies and with edt. You still can get good audio in my experience. The trade of with be resources on the backend. Chances are no optimized usb channel and no vdi client integration. So you might have to place with audio policy and force udp with a GPO on cwa and or edit the strofront configure to do it. But it might still be wonky. Hopefully you using SIP. We have Avaya, and its H.323 and no Vdi communicator (equinox) it still works but im playing with it still.
j
@Ray Davis thanks buddy. Some good ideas to chew on here :)
m
@Ray Davis Thanks for your help! I've just updated the article with new names and link
r
Anytime guys, anything i can do to help, count me in.
m
If you can enable UDP audio in the environment it’ll make a big difference
Won’t work for non windows machines though