VVX 601 5.8.0 Issues with Plantronics Hookswitch

[techlogik]

After updating to 5.8.0, my Plantronics headset, when you would lift it out of the cradle, would go offhook and you would get dial tone and could make a call.

Now, you lift it off hook, nothing happens.  Didn't see anything in the Release notes about changes in Hookswitch.

If already off hook, you put the headset back into the cradle, it will hang up though.  It is just the lifting part out of the cradle that doesn't go off-hook any longer.

Any ideas?

[techlogik]

Wouldl like to also add:  Rolled back to 5.7.0 and 5.7.2, both work normal again with the Plantronics EHS headset, lift headset, goes offhook, green headset lights up.

Also, on 5.8.0, when you would manually turn the headset on, after 10 seconds, it would turn itself back off...call would stay connected, but headset turned itself off.

5.8 has EHS headset issues obviously.

[SteffenBaierUK]

Hello @techlogik,

welcome back to the Polycom Community.

Please open a ticket for this.

In order to raise a support ticket you need to work with your Polycom reseller as they need to do this for you.

End Customers are unable to open a ticket directly with Polycom support.

If this is some sort of an Internet discounter please post either your phone's MAC address or your Polycom devices serial so I can look up who would be able to support you. This may not be who you purchased the Polycom device from.

If the unit is no longer within warranty please be prepared to Pay Per Incident / PPI. This is all outlined in detail 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

[techlogik]

64167f0a1962

Thx

[SteffenBaierUK]

I am currently on holiday so please wait for my return in case you need information on who to contact for support.

Replied via a mobile device

[techlogik]

Sorry for the late reply.  I ended up rolling the firmware back to the previous version.  Then let it update to the latest again.  Now it is working normal.  Something must have gone wrong during the original update that is now fixed.

All working fine now.