caspos.blogg.se

It's as if the phones just quit communicating properly with the FE pool. Set SCHANNEL on FE servers to not send the list of trusted roots, rebooted them, still no effect. Wireshark captures show the phone talking to NTP server, FE pool address (TLS etc, and cylcing through the same communication twice), and then talking to Edge external IP doing the same exact TLS and certificate negotiating as the pool address (this also happens twice).īeen through all of Jeff Schertz's blogs, setup DHCP (although we had not used it before) and can successfully test configuration with test-csphonebootstrap. We came in on Monday with the phones in the currently described condition. The only change that occurred in our Lync environment more or less prior to this problem occurring is that the Lync Edge external certificate was updated on. 1000 - Right out of box returns "Sign-in Error" This is the same error another phone gives that was flashed to factory default

4413 - Cycles back and forth between downloading certificate, installing certificate, and contacting Lync server (endless loop) Lync 2103 Enterprise pool load balanced with Kemp Loadmaster These phones worked for 6 months and then just stopped. We recently ran into a situation where our Polycom phones will no longer work with our Lync 2013 implementation.