We are a windows shop, using Skype for business with BToE. Our Polycom's are VVX 411's. We suddenly have a rash of computers losing connection to network and phones. We have updated the BToE to 3.8 and the Polycom firmware to the 5.8.0.12848. However, this doesn't seem to be working. We are having to put in a switch and power injector at each station and provide network and phone separately. I have had to do this at 5 stations already. Is there a fix? Is there a Microsoft Update that is causing this?
Hello @cshane,
welcome to the Polycom Community.
I have not had any similar reports so I suggest you enable the logs to be a bit bigger and once you replicate the issue escalate this into a support ticket.
Once it happens:
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
If official support is required please check how to phone or open a case here
----------------Hello @cshane,
If your latest phones come via Amazon simply post the MAC of the phone so I can lookup who can support you.
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
If official support is required please check how to phone or open a case here
----------------Hello Steffen,
Here is a list of MAC addresses that are reporting the same issue.
I suspect that we have more.
Melea: 64:16:7f:0e:83:de
Chelsea: 64:16:7f:17:a8:4e
Lauren: 64:16:7f:17:95:5b
Victoria: 64:16:7f:17:aa:b0
Marquis: 64:16:7f:0e:80:16
Chris: 64:16:7f:17:a9:99
Corey: 64:16:7f:0e:8a:ad
Hello @cshane,
64167f0e83de SCANSOURCE COMMUNICATIONS 26/12/2016
64167f17a84e Westcon-Comstor Americas 14/05/2017
64167f17955b Westcon-Comstor Americas 14/05/2017
64167f17aab0 Westcon-Comstor Americas 14/05/2017
64167f0e8016 SCANSOURCE COMMUNICATIONS 26/12/2016
64167f17a999 Westcon-Comstor Americas 14/05/2017
64167f0e8aad SCANSOURCE COMMUNICATIONS 26/12/2016
I recommend to contact Westcon-Comstor Americas as the dates shown is usually when we ship to them so we add usually a 3 month grace period so they are just about in warranty.
They are also able to open the PPI ticket in case they are classed out of warranty.
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
If official support is required please check how to phone or open a case here
----------------Hi Steffen,
I believe we have discovered our issue.
We started using the Polycom BToE version 3.8.0 which only work with Polycom Phone Firmware 5.8.0.12848. Unfortunately, Microsoft has not approved the 5.8.0.12848 and our phones are automatically rebooting and rolling back to 5.7.0.14430. Firmware 5.7.0.14430 does not work with BToE 3.8.0. In addition, there seems to be some sort of automatic updater that is causing all of the phones to update to 5.7.0.14430. We have people on BToE 3.5.0 or lower, which doesn't work with Firmware 5.7.0.14430. So we are getting hit on two fronts, the auto-update to 5.7.0.14430 and the forced rollback to 5.7.0.14430 and not having the correct BToE.
This would have been good information to have here in your forums, along with the way to disable the automatic updates (like how this article describes:
http://blog.schertz.name/2016/07/device-updates-with-skype-for-business-online/). Or an ETA on when 5.8.0.12848 will be approved by Microsoft. Or that older versions of BToE will not work with the latest approved and forced firmware.
Thanks,
Chris
And also for the chain, here is the link for accessing the sfb for global adjustments.
For changing EnableDeviceUpdate from $True to $False. Also ones we made were EnableBetterTogetherOverEthernet from the default of $False to $True. Along with BetterTogetherOverEthernetPairingMode from Manual to Auto.
If official support is required please check how to phone or open a case here
----------------