Seeing an is on the Trio8800 with 5.4.2.5400.
When in a multiparty call hosted on a Lync / SfB AVMCU, when someone in the call shares content the Trio8800 disconnectes from the call.
This behaviour is not presnet in 5.4.1.17597
I’ve opened case # 1-2602870131
James
Solved! Go to Solution.
I was advised yesterday that this issue will be resolved in the "...next 5.4.3 maintenance release. The release should be out the end of this week or the beginning of next."
James
Hello James,
Have you got a few more details ?
We would need SIPT at debug Level and Support Object at Event 2 to begin with as logs.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
I've been able to reproduce the issue with 3 endpoints joined to a schedueld call where the Trio8800 is one of the 3.
I've see but not reproduced with Lync 2013 client.
I've see but not reprodiced with more Lync clients and PSTN callers.
I've forwarded the logs to the reseller who as added them to the open ticket.
Any update on this? I'm experiencing the same exact issue. Rolled back the software and the TRIO is stable for now.
Sean
Hello Sean,
welcome to the Polycom Community.
I assume James ticket is 1-2602870131 and it is still with Engineering.
I can only encourage you to open a ticket in parallel.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
I was advised yesterday that this issue will be resolved in the "...next 5.4.3 maintenance release. The release should be out the end of this week or the beginning of next."
James
Hello James,
thanks for providing this update on your case and it should be released noted as VOIP-116579
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
Thanks James, much appreciated.
This issue has been redsolved in 5.4.3.2007 / 5.4.3 Rev AA