Cisco, a few years ago introduced the ability for Webex Devices to dial into Microsoft Teams meetings. When first introduced, it had a name of Cloud Video Integration also known as CVI. It was later renamed to to Video Integration Microsoft Teams, which is also known as VIMT. This allows businesses in a hybrid environment to dial Microsoft Teams meetings from Webex devices and get a similar experience to regular Webex calls. No additional infrastructure needed. Calls using VIMT, would be able to dial into a Microsoft Teams meeting using the following format .@m.webex.com. This is generally done using One Button To Push (OBTP) and the user does not need to dial it manually. Below is high level illustration presented at Cisco Live on the architecture:
The example URI used above ends with m.webex.com - This indicates that the device will be dialling into the Webex/Teams Gateway Service. You can think of m.webex.com as a "special" Control Hub that is controlled by Webex. It serves all customers who have a VIMT license. Since a specific Control Hub is used for this, which serves multiple customers, you will not see the Call in the Control Hub UI or via the Control Hub API. Which is why Vyopta is not able to capture those calls via the Control Hub Connector only.
Vyopta however is able to capture VIMT calls using the Vyopta Data Collector and the endpoints are added to Vyopta. Since the device is dialling the URI containing m.webex.com, that data is collected and visible to you using CPM Monitoring and CPM Analytics. With a recent firmware update on the Webex devices, the URI no longer shows when the call is in progress, a ID however is visible. That ID will be visible in Vyopta instead of the URI. Vyopta is currently working on the ability to capture those calls after it ends which then should be visible in CPM Analytics. We do not have an ETA on this feature yet.
Newer Webex devices, have the ability to join Microsoft Teams calls using a standard feature called WebRTC. The are able to use the URL of the meeting to dial in, this is also generally done via OBTP. WebRTC calls use a built-in browser engine to perform the calls and do not use the core endpoint features to dial in. WebRTC are also calls that are not visible in Control Hub nor the Control Hub API. Below is high level illustration presented at Cisco Live on the architecture:
Vyopta is not able to see live WebRTC calls, however once a call is ended, the call should be visible for us to collect. This will also include the Microsoft Teams meeting ID! Vyopta is currently working on the ability to capture those calls after it ends which then should be visible in CPM Analytics. We do not have an ETA on this feature yet.