Plantronics + Polycom. Now together as Poly Logo

BToE not signing in after user moved from s4b 2015 to 2019 pool

Highlighted
Frequent Advisor

BToE not signing in after user moved from s4b 2015 to 2019 pool

Hi,

 

I have migrated my on prem S4b 2015 server to 2019.

 

users are unable to sign in using BToE

 

users can sign in using the vvx 600 web UI (username / password)

 

BToE version 4.3

 

VVX 600 firmware is 5.9.6.2327

 

when user tries to sign in with BToE on the WIndows 10 desktop there is an alert that says UNPAIDED then PAIRED

 

then the user is prompted for their BToE password again

 

does the BToE client need to be reset when the user changes pool?

 

thanks

 

jack

 

 

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

Re: BToE not signing in after user moved from s4b 2015 to 2019 pool

Hello @guideclothing ,

 

Welcome back to the Poly Community.

This would need to come into support.


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

End Customers are usually unable to open a ticket directly with Poly support. Available End User Poly services offerings are detailed here

If this is some sort of an Internet discounter providing your MAC address or your Poly devices serial will enable us to look up who would be able to support you. This may not be who you purchased the Poly device from.

If the unit is no longer within the 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

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

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
Frequent Advisor

Re: BToE not signing in after user moved from s4b 2015 to 2019 pool

in case it helps anyone else i needed to set these parameters  in the config file

<web sec.TLS.protocol.ldap="TLSv1_2"
sec.TLS.protocol.sip="TLSv1_2"
sec.TLS.protocol.webServer="TLSv1_2"
sec.TLS.protocol.xmpp="TLSv1_2" />

 

i had set the minimum TLS level on the S4b 2019 Server

Message 3 of 3