We have been told by Microsoft that the update has been delayed until July.
We have low also being badly affected by call drops in the latest firmware on both the CCX500 and Yealink phones so have been forced to migrate some critical phones to zoom running on the ccx 500 phones. So fare they are running good but it is early days.
This is so problematic, Poly and Microsoft are some of the biggest names in technology and this has absolutely been the worst rollout of any technology product in my entire career.
I suppose I should have known better, Microsoft hasn't exactly had the best reputation when it comes to phones, but the predecessor (Lync) was amazingly stable so I thought they had redeemed themselves.
Every time I have hope that there is a work around (SIP), even that doesn't work... we still can't even authenticate a SIP device....
I've actually made a small amount of progress on this. I realized that the CCX 500 devices I am testing with were still listed in the TAC under Teams devices > Phones. After deleting them from there and then performing another factory reset, I am now able to complete the CAP phone provisioning under Teams devices > SIP Devices > Actions > Provision devices.
After creating a provisioning code and dialing *55*xxxxxx, the phone appears on the "Waiting for sign in" tab. However, when I click on the "Signed out" link to perform a sign in, the activation code never appears. And, of course, there still appears to be no way for an end user to sign in.
Hello @rgsteele , @CBTECH and @nharwood
any feedback or updates from our Partner Microsoft on the SIP gateway and CCX if you tried?
If official support is required please check how to phone or open a case here----------------
We have 1500 Poly phones. A combination of CCX 400, 500, 600 and C60 phones. None are working at the office for us yet. Because we are a financial services company we have more security requirements than most Enterprise companies. Are current network requires Proxy SSL with internal certificates. The phones do not support installing our internal certificates into the android system area. Long term we are looking at new network security topology. Short term we are trying Teams SIP gateway option that these phones also support. We were informed verbally that this is now supported on a conference call. Note the documentation has not been updated yet. Note this is not working yet either....
On a whim, I tried provisioning a CCX 500 with the Teams SIP Gateway again and... it actually worked! It still does not display a "Sign in" button on the home screen, but I was able to sign in using remote provisioning as documented in the "Provision and enroll SIP devices as common area phones" section of Configure SIP Gateway - Microsoft Teams | Microsoft Learn.
The CCX 500 has not returned to the list of devices supported by the Teams SIP Gateway so I don't know whether this will keep working or not.