If you are reading this post, I hope you are proficient enough with editing the registry with out blowing it up.Ĭlose the BToE Connector, if it’s currently running, open up RegEdit and drill down to the following key: HKEY_LOCAL_MACHINESOFTWAREWOW6432NodePolycomPolycom BToE Connector There should be a DWORD value called: IP_PAIRING_EN, set it to 1.įorthly, we need to add the following entries to the phone configuration as they are not exposed in the Web GUI. 3.4.1 was released yesterday, so far so good. Second, you need to have installed the Polycom BToE Connector, 3.4.x. 5.2 was released yesterday and so far so good with this new version. I do not have a VDI environment to test this with and see if it works in that scenario, but I’ve had a few customers who have separate LAN ports for IP phones, with PoE gear, and are very anxious to have IP based BToE pairing become available.įirst off, your VVX phone MUST be running 5.6 or higher code.

My configuration is with two separate LAN drops, one for my tower and one for my VVX 600. Test/try this at your own peril, and certainly do not use with your Receptionist… I have not encountered any issues, but I’m not a hard core handset user.

As it’s not in the released documentation we can assume this may not be meant for production. Hiding in the VVX 5.5.1 and BToE 3.4.x builds is some nifty code allowing for IP based phone pairing.

Polycom btoe client