Plantronics + Polycom. Now together as Poly Logo

BToE pairing to random phones over wireless

SOLVED
Highlighted
Visitor

BToE pairing to random phones over wireless

VVX 411s on 5.9.0.9373 firmware

BToE v4.3 client on Windows 10 PCs using Teams.  We applied 4.3 so Teams would recognize the paired Poly as an audio device, which is great having just migrated from SfB to Teams company-wide.

 

Issue: User joins a Teams meeting and sees participants in Teams.  Audio is on another phone across the office.  Suspected BToE might be paired with the phone playing audio.  Remoted into her PC and checked the BToE client and it was paired, showing the IP of the other phone across the office.

 

Found that the user's docking station network cable was disconnected, not plugged into the 411s PC port.  Laptop was connected over wireless.  I restarted the BToE client several times and it paired to the rogue 411 every time.  The rogue 411 had no laptop connected at that desk and was signed in with another user's credentials.

 

Corrected the problem by having the user connect the docking station to her 411 PC port.  Restarted BToE client on her laptop and phone paired to the 411 on her desk.  Her problem solved.

 

Later today, I went back to document the details and now the original rogue 411 had paired to yet another laptop in the office, all while still signed in as another user.  I've emailed the latest user to check her cables but she has left for the day.

 

Question #1:  If there's no wired ethernet connection to a Poly phone, does BToE search the network and attach to the first phone it finds?

Question #2: other than the obvious of correctly connecting the cables, how do we prevent this behavior? 

Question #3:  What prevents the BToE client from randomly connecting to phones when a user takes their laptop to another office and connects to wifi? All of our offices are equipped with 411s.

 

We have similar symptoms in 2 other offices but this is the first where I've been able to nail down the issue.  

 

Thanks in advance.

Message 1 of 4
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Polycom Employee & Community Manager

Re: BToE pairing to random phones over wireless

Hello @PASSR ,

 

Welcome to the Poly Community.


First of all, you are on an unsupported version as the phone should be running UC Software 5.9.6 instead.

 

Secondly, the only reason I would know from experience this would happen is:

 

  • Someone in your organisation plugged the PC port of the phone back into a switch port and therefore broadcasts all the BToE Traffic into your network
    or
  • Someone has powered the phone via an external PSU and plugged the switch port into the PC port

 

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

View solution in original post

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

Re: BToE pairing to random phones over wireless

Hello @PASSR ,

 

Welcome to the Poly Community.


First of all, you are on an unsupported version as the phone should be running UC Software 5.9.6 instead.

 

Secondly, the only reason I would know from experience this would happen is:

 

  • Someone in your organisation plugged the PC port of the phone back into a switch port and therefore broadcasts all the BToE Traffic into your network
    or
  • Someone has powered the phone via an external PSU and plugged the switch port into the PC port

 

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

View solution in original post

Message 2 of 4
Visitor

Re: BToE pairing to random phones over wireless

Thanks for the reply Steffen.  I'll plan the firmware upgrade on the 411s.  We've been working closely with Poly during our Teams transition and this is the first 5.9.6 has been suggested.  We're currently testing 6.3.0.14929 pushed to specific sites via PDMS Site profiles.

 

I'm sure the cables are reversed on the 411 that keeps pairing to other laptops in the office.  It's a remote site so I'm working with a local user this morning to check the cables. The 411 was paired to yet a 3rd laptop this morning.

 

Your scenario makes perfect sense.  The phone only broadcasts the discovery packet on the PC port so if it's correctly connected to a PC it pairs.  If the PC port is connected to nothing, the 411 is not "discovered".  If the PC port is connected to the switch, it's broadcasting discovery packets across the network and any BToE client on the same network can pair with it.

 

Thanks for helping me see the distinction that discovery packets broadcast only thru the PC port!  I've read many times and seen the situation myself where the reversed cables cause issues but your explanation clarifies the "why".  I had assumed the phone acted as a switch and altered network traffic in the reversed cable setup but that's not it at all.

 

I'll post back when we've verified and corrected the reversed cables.

Message 3 of 4
Highlighted
Visitor

Re: BToE pairing to random phones over wireless

You were right.  The phone that kept pairing with random BToE clients had the cables reversed.  The user had returned to the office after an extended work form home and not connected correctly.

 

Thanks.

Message 4 of 4