May 25 2022 05:06 PM
May 25 2022 05:06 PM
The Poly CCX 500 was recently added to the list of devices supported by the Teams SIP Gateway. Presumably this is because they do not function properly with the Teams app installed on them. I am eager to resolve the issues my users are facing, but I haven't had any success enrolling these devices.
When I put the device on my VLAN with the SIP Gateway provisioning server URL set in the DHCP option 160 and perform a factory reset, the device appears to get successfully provisioned, but after setting the admin password, accepting the EULA, and selecting the language and time zone, I'm prompted to choose between "Skype for Business", "USB Optimized" and the "Microsoft Teams" profile (which is obviously not what I want, since that would put the Android Teams app back on it).
If I choose USB Optimized. the device briefly shows the USB Optimized interface, and then reboots. After that, it does show the Teams logo wallpaper, so that seems promising. However, there is no sign-in code displayed, and if I try to provision the device with the verification code generated in the Teams Admin Center by dialing *55* and the code, I just get a fast busy signal.
We've successfully onboarded a VVX 411 device, so I don't think it's a firewall issue. Others are reporting the same issue in the Poly forums. Has anyone successfully deployed a Poly CCX 500 device with the Teams SIP Gateway?
May 27 2022 12:37 PM - edited May 27 2022 12:44 PM
Your experience is exactly the same as ours. Still haven't figured out how to get one of these signed in.
Can you link me some of the poly forum posts you are seeing?
May 27 2022 01:20 PM
@southwick Here is the Poly forum post I was referring to: CCX 500 / 600 Issues - Question for other users - Poly Community
Oct 20 2022 07:49 AM
Oct 20 2022 08:42 AM
@AdamK_DC They pulled it off the supported device list about a week after adding them. I don't expect them to come back after my talks with Microsoft.
Oct 20 2022 08:46 AM
Oct 20 2022 11:06 AM - edited Oct 20 2022 11:07 AM
I don't think it's fair to lay the blame entirely at Poly's feet. They built the device to Microsoft's specifications, and Microsoft certified it. Almost immediately, Microsoft allowed the app to get too bloated to run well on the device. Instead of working with Poly to address the issues, Microsoft barged ahead with adding new features.
We support the community offices of the elected representatives for the citizens of our province, and these users need desk phones—they need to be able to do things like place a call on behalf of a constituent and hand over the receiver. Fortunately, the SIP Gateway seems to be the answer to our prayers, especially now that there are cordless phone options available.
The ironic thing is that we bought the Teams Phones to replace our 3PIP phones due to issues with Skype for Business Online, and now we're essentially going back again.
Oct 21 2022 07:28 AM
@Ryan Steele Here is an older VVX500 connected to the Teams SIP Gateway. Normal dial pad with physical buttons. Dial Tone. Used a Common Area License as it's in a reception area.
Everything old is new again.