- Cisco And Microsoft Teams
- Microsoft Teams And Cisco Callmanager
- Cisco Jabber And Microsoft Teams
- Microsoft Teams And Cisco Phone
- Cisco Webex And Microsoft Teams
A) Webex Meetings integration with MSFT Teams Allows MSFT Teams users to schedule, start, or join Cisco Webex meetings and invite people to join Webex meetings or Webex Personal Room meetings directly from their Microsoft Teams clients. Cisco-Webex-Meetings-for-Microsoft-Teams article from help.webex.com. The Cisco CVI (Cloud Video Interop) is currently in trials and soon to be generally available. This will allow the Room Series video systems to join (including OBTP) a MS Teams meeting. For other platforms, the capability is there as long as the third part offers a standard SIP dial string to call. View solution in original post. Cisco Jabber Integration with Microsoft Teams For enterprises with a heavy investment in Cisco technology that want to maximize this investment for years to come, while also having a small population of users on Teams clients - is through a Cisco Jabber integration.
What You’ll Find in This Demo
The guide for this preconfigured demo includes two independent Cisco Calling and Meeting Integration demos: Microsoft Teams and Slack.
What’s New
The Microsoft Teams integration section has a new scenario: Cloud Video Interop (CVI) and WebRTC.
Overview
Microsoft Teams
Users demand interoperability with calendaring, ECM, workflow, telephony, meetings, video, devices, and more. Cisco meets this demand with client-based integration with Microsoft Teams.
The simple-to-deploy client/plug-in integration with Microsoft Teams works with your choice of Cisco clients — Cisco Jabber, Webex Calling, and Webex Meetings.
Calling
- Click to call with your existing phones from Microsoft Teams
- No compromise on calling features
- No dial plan and routing reconfiguration
Meetings
- Simple-to-implement Webex Meetings Bot
- Get your default website for Meetings
- Set your default Meetings website
And all this is at no additional license costs because of the following:
- Covered by your existing Cisco licenses/subscription
- No (E5) Microsoft Cloud PBX Phone system license is required
Cloud Video Interop (CVI) and WebRTC
- SIP-capable video endpoints can join Microsoft Teams meetings via CVI for a rich, seamless meeting experience, without requiring third-party interop using OBTP join with Calendar Service, direct dial in, or IVR join experience.
- WebRTC supports the OBTP join with Calendar Service for B2B meetings from a Cisco video endpoint that has Media Engine running. These devices support WebRTC: Cisco Webex Board, Room Devices, and DeskPro.
Slack
Cisco Jabber, Webex Call, and Webex Meetings integrated with Slack lets you collaborate seamlessly – whoever, whenever, however.
Calling
Cisco Jabber and Cisco Webex are simple-to-deploy plug-ins that can be cross-launched from within Slack when you want to call someone internally or externally.
With Cisco Jabber and Cisco Webex plugins, Slack users can:
- Call someone internal with their extension or SIP URI
- Call someone over PSTN
The simple-to-deploy client/plug-in Webex Meetings integration with Slack lets Slack users to schedule, start, or join Cisco Webex Personal Room meetings, and Cisco Webex scheduled meetings directly from Slack.
Meetings
With Cisco Webex Meetings plug-in, Slack users can:
- Start and join meetings directly in their channel
- Schedule a meeting and the meeting info card will be added to the conversation.
- Automatically get status alerts and, if your meeting has already started, see who has joined
- Preview your upcoming meetings and join from the list
- Edit a scheduled Webex meeting
- Play recordings, which are posted in the channel when ready
- See if other users are currently in a Webex meeting
Scenarios
The Microsoft Teams integration section has three independent scenarios:
- Scenario 1: Cisco Jabber and Webex Meetings Integration with Microsoft Teams
- Scenario 2: Cisco Calling and Webex Meetings Integration with Microsoft Teams
- Scenario 3: Cloud Video Interop (CVI) and WebRTC
The Slack integration section has two independent scenarios:
- Scenario 1: Cisco Jabber and Webex Meetings Integration with Slack
- Scenario 2: Cisco Webex Calling and Webex Meetings Integration with Slack
Get Started & Resources
- Schedule this demo and get the lab guide: Cisco Calling and Meeting Integration with Microsoft Teams and Slack v1
- Visit the Cisco dCloud help page: https://dcloud-cms.cisco.com/help
- Access all available Cisco dCloud content: https://dcloud.cisco.com
- Contact Us: https://dcloud-cms.cisco.com/help/dcloud-collaboration-contacts
- Talk about it on the dCloud Community
Microsoft Teams Rooms devices support a one-touch experience for joining third-party online meetings, also referred to as Direct guest join. When enabled, you can use a Teams Rooms device to join meetings hosted on Cisco WebEx and Zoom just as easily as you can join meetings hosted in Microsoft Teams.
Before you can join third-party meetings from a Teams Rooms device, you need to do the following:
- Configure the Teams Rooms device's Exchange Online room mailbox to process invites for third-party meetings.
- Make sure your organization doesn't have any policies that would prevent you from connecting to third-party meeting services.
- Configure your Teams Rooms devices to allow third-party meetings.
The following sections show you how to do each of these steps.
Step 1: Allow calendar invite processing for third-party meetings
The first thing you need to do to enable a one-touch join experience from a Team Rooms device is set the calendar processing rules for the device's Exchange Online room mailbox. The room mailbox needs to allow external meetings and keep the message body and subject so it can see the URL needed to join the third-party meeting. To set these room mailbox options using the Set-CalendarProcessing cmdlet, do the following:
Connect to Exchange Online PowerShell. For more information, see Connect to Exchange Online PowerShell with Basic authentication or Connect to Exchange Online PowerShell using multi-factor authentication, depending on your authentication method.
Get the User Principal Name (UPN) of the room mailbox if you don't know it by running the following command:
Find the name of the room mailbox associated with your Teams Rooms device and make note of its UPN.
After you find the room mailbox's UPN, run the following command. Replace
<UserPrincipalName>with the room mailbox's UPN:
Learn more about Exchange Online PowerShell.
Step 2: Configure Office 365 Threat Protection and link rewrite
Cisco And Microsoft Teams
To enable the one-touch join experience, meeting join link information from the third-party meeting needs to be present and readable in the meeting invite. If your organization uses the Office 365 Advanced Threat Protection Safe Links feature, or if you use a third-party solution that scans all incoming and outgoing URLs for threats, it may change the meeting join URLs and make the meeting unrecognizable by the Teams Rooms device. To make sure this doesn't happen, you need to add the third-party meeting service's URLs to the ATP Safe Links 'do not rewrite' list or the third-party URL rewrite exception list.
To add third-party meeting service URLs to the ATP Safe Links 'do not rewrite' list, follow the steps in Set up a custom do-not-rewrite URLs list using ATP Safe Links. If you use a third-party solution, refer to the instructions for that solution to add URLs to its URL rewrite exception list.
Microsoft Teams And Cisco Callmanager
Here are some example entries that you may need to add to your ATP Safe Links 'do not rewrite' list or third-party URL rewrite exception list:
- Cisco WebEx
*.webex.com* - Zoom
*.zoom.us*,*.zoom.com*,*.zoomgov.com*
For a complete list of URLs to add to your ATP Safe Links 'do not rewrite' list or third-party URL rewrite exception list, contact the third-party meeting service provider you want to accept meeting invites from.
Caution
Only add URLs that you trust to your ATP Safe Links 'do not rewrite' list or third-party URL rewrite exception list.
Step 3: Enable third-party meetings on device
The last step you need to do is allow each Teams Rooms device to join third-party meetings. Third-party meetings require a username and email address to join them. If the username and email address that you need to use is different than the device's room mailbox, you need to add them to your device. You can do this in the device settings or in the XML config file.
Use device settings
To configure the Teams Rooms device using its touchscreen, do the following:
- On the Microsoft Teams Rooms device, select More ....
- Select Settings, and then enter the device administrator username and password.
- Go to the Meetings tab and select Cisco WebEx, Zoom, or both.
- If you want to join meetings with the username and email address associated with the room mailbox, select Join with room info.
- If you want to join meetings with an alternate username and email address, select Join with custom info and enter username and email address you'd like to use.
- Select Save and exit. Your device will restart.
Use the SkypeSettings.xml configuration file
The following settings can be added to the SkypeSettings.xml file located in C:UsersSkypeAppDataLocalPackagesMicrosoft.SkypeRoomSystem_8wekyb3d8bbweLocalState. For more information about the SkypeSettings.xml file, see Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file.
Cisco Jabber And Microsoft Teams
To enable Cisco WebEx meetings, set the WebExMeetingsEnabled XML element to True, as follows.
To enable Zoom meetings, set the ZoomMeetingsEnabled XML element to True, as follows.
You can optionally specify a custom username and email address to join third-party meetings using the following XML elements. If the values you provide aren't valid, the Teams Rooms device will default to use room mailbox username and email address.
Microsoft Teams And Cisco Phone
Note
Cisco Webex And Microsoft Teams
To join Cisco WebEx meeting from a Teams Rooms device, the Cisco meeting needs to be hosted using Cisco WebEx web application version WBS 40.7 or later.