Plantronics + Polycom. Now together as Poly Logo

Soundstation IP 6000 outbound calling failure

SOLVED
Highlighted
Occasional Visitor

Soundstation IP 6000 outbound calling failure

Has anyone ever experienced an issue with outbound calls failing to complete after hanging up a previous call? We have an end user reporting an issue where they attempt to make an outbound call directly after hanging up an active call and the call just fails to complete regardless of the extension/number dialed. They have to wait up to a minute or more before they can make another outbound call. NOC engineers have advised they are not seeing the sequence number change on the second outbound call but unable to isolate what would be causing the issue. Firmware is 4.0.8 and we are unable to recreate using a different manufacturer conference unit in same location. 

Message 1 of 3
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Occasional Visitor

Re: Soundstation IP 6000 outbound calling failure

Thank you for the prompy reply and link to the suggested resource. Upgrading the firmware to Version: 4.0.10.0689 (RevD) resolved my issue. Thanks.

View solution in original post

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

Re: Soundstation IP 6000 outbound calling failure

Hello @TB2004 ,

 

welcome to the Poly Community.


Please check => 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

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

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: Soundstation IP 6000 outbound calling failure

Thank you for the prompy reply and link to the suggested resource. Upgrading the firmware to Version: 4.0.10.0689 (RevD) resolved my issue. Thanks.

View solution in original post

Message 3 of 3