403 - Avaya Workplace 3.39.2 on CM 10.2 bridged appearances
Tim Mack
This is more of a PSA and bug fix request than a feature request. We have found that after upgrading to UC Release 10.2 calls to bridged appearances that ring on Avaya Workplace, if the call forwards to SIP trunks (in our case Avaya Messaging), the call continues to ring on the Workplace App. SIP messaging back to CM is not occurring or is being ignored, that would tell CM that the call has been answered by Voicemail. The call will continue to ring on Workplace until the user selects the red hangup button. One user allowed it to ring for an entire day. If the Workplace user attempts to answer the call on Workplace using the green answer button, they are presented with a pop up message stating "Unable to connect to the call, call has either forwarded, terminated......" We have upgraded Avaya Workplace to the latest release, 3.39.2, but the problem still persists. A ticket has been opened with Avaya Support.
Tina Martin
I had (have) this on 10.1, and Avaya said it was a configuration problem.
Chris Rosenstock
We have a current ticket open on this now. It's happening on Workplace and also DES remote phones. The engineer working on this believes it has to do with our remote worker SBC because all our workplace applications and our DES phones go through our remote worker. He found a write up about remote desktop causing this and believes the remote worker SBC may be the problem.
Michael Jones
We had this issue with an earlier release of Workplace, and had a ticket open with Avaya - the fix was supposed to be in 3.39.2 (which we're currently rolling out), and at least in our environment the reports have quieted with our test users.
Sam Osheroff
I had a ticket open for this very thing! They told me it was working as designed.