Plantronics + Polycom. Now together as Poly Logo

Polycom Trio 8800 to Trio 8800 SfB calls dropping

Highlighted
Occasional Visitor

Polycom Trio 8800 to Trio 8800 SfB calls dropping

We've intermittent issues with Trio to Trio SfB calls dropping video, audio or both. They're on 5.4.4AB (5.4.4.7609) firmware at both ends.

 

Other than monitoring the network traffic during the call, where else can we troubleshoot this? 

 

We've seen some errors during the call in the system log, but are unsure what they mean. Example:

 

01-31 14:38:57.480 E/PLCM    (  375): 0131143857|ssps |4|00|sspsPktChanSimpleVidJBCheckForStuckReadThread - ERROR: video JB has not been read for 55 ms and will fill. The tSspsMain thread is stuck.  This is not a JB problem.

Message 1 of 3
2 REPLIES 2
Highlighted
Polycom Employee & Community Manager

Re: Polycom Trio 8800 to Trio 8800 SfB calls dropping

Hello John_TTL,

welcome to the Polycom Community.

The community's skype and VoIP FAQ contains these post here:

Jan 19, 2012 Question: How to troubleshoot Polycom VoIP related Issues?

Resolution: Please check => here <=

 

and

 

Jan 17, 2017 Question:How can I troubleshoot simple Skype for Bussines, LYNC or Office365 issues?

Resolution: Have a look => here <=


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

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 2 of 3
Highlighted
Occasional Visitor

Re: Polycom Trio 8800 to Trio 8800 SfB calls dropping

Thanks for the links.

 

The issue we're facing isn't dealt with in these posts but at least we've managed to increase our logging level so can look at the logs more closely next time the issue occurs.

Message 3 of 3