Oct 17 2018 03:48 AM
Oct 17 2018 03:48 AM
We have been using s4b online together with Cisco Meeting Server (CMS) on prem for some time. We are able to dial a CMS virtual meeting room from s4b via a federated connection, however when we try to call the same rooms from Teams then the connection fails to complete. We suspect that there are still some issues with Teams Federation and would like to know if there are any specific configuration settings that need to be made for Teams.
Oct 21 2018 01:36 PM
Currently, to my knowledge Teams only supports federation to Skype Online or other Teams users, your Cisco platform will be representing an on-premises Skype user. This federation is coming soon.
Having said that, Cisco in this case are impersonation a Skype user rather than being a supported client, even when its working it would be up to Cisco to assure the reliability of their service, it's not certified or supported by Microsoft.
Sep 19 2019 01:23 AM
Do Microsoft have any plans to make Teams compatible with CISCO systems? The lack of integration is causing us numerous problems with the release of Teams as we have to keep Skype for Business running for VC and Audio collaboration. Teams is a dead duck as a client in a Cisco world! Come on Microsoft we need this sorting out. I am not buying the argument that we have to use Polycom, Bluejeans or Pexip. We have huge investments in CISCO and we have to bridge the two environments. I also understand the Surface Hub 2s only come with Teams, which compounds the issue even more! We have spoken to Cisco and there appears to be some light on the horizon but Microsoft, while claiming to be open, seem to be doing nothing to help!
Sep 19 2019 04:11 AM
In the old times it was easier to build "bridge" between these two ecosystems as both were using SIP based communication (Cisco Telepresence and S4B) so it was more about where and how the media will get mixed and how to solve the interop talking about screen sharing etc.
Teams is different in that matter as it does not use the SIP for communication and signalling with other systems. That brings into game mentioned Cloud Interop Teams gateway providers because they got access to APIs.
At the end it is about money and market. All Microsoft partners will be happy to get your huge investments into their solution for Teams room systems instead of Cisco devices. And as Teams is improving as meeting platform too I do not believe they will open their cloud environment via SIP natively as they would cut three big partners for Teams gateway plus they would not force customers to move away from other platforms like webex, zoom and other.
Sep 19 2019 04:25 AM
@DaveChomi I agree with your sentiments. We know Cisco's plans via our account team but I haven't seen any real movement from Microsoft other than to keep the Teams client tightly tethered to their back-end cloud platform. The CISCO Webex Rooms (aka MX700) devices are still arguably best for the bigger meeting rooms (8+ seats). We currently use on-prem CMS bridges & Expressway C&E to link in Skype for Business. Right now we have no option but to stay as is. Hopefully there is some light at the end of the tunnel coming soon on this one!
May 10 2021 09:15 AM
Jun 15 2021 03:07 AM
Jun 15 2021 03:21 AM
We went PEXIP CVI for a while which worked great during Covid in 2020 and now we've just switched over the Cisco CVI as we're getting better video quality on our room-based Cisco systems. For voice integration we moved directly to Teams conferencing and we've also oved many users over to Teams voice. We've decommissioned CMS. Right now the Cisco and Microsoft worlds are working well over CVI so long as meetings are all curated through Teams.
Jun 15 2021 05:14 AM
@DaveChomi Just like Dave did, we did the same after evaluating MST Rooms and options. Just purchased Cisco CVI subscription and we still offer CMS as our audio bridge for those that don't require video for their meetings however still have the option to join via video from room system or WebRTC. I'm keeping an eye on CMS and EOL/EOS and what Cisco's solution or replacement might be if any (assuming Webex).