Webex Teams Developer



Enabling Integration via Webex Teams and Cisco DNA, SD-Wan, Intersight, Thousand Eyes via Cloud API Gateway

I was really excited to have a unique opportunity to put together a team of my fellow engineers to work on a Collaboration hacking contest within Cisco. This annual event is usually in-person for a day or two in San Jose, making it out of reach for my nomadic desert comrades located in Arizona. This year, however, remote is the new normal. This unique situation made it possible for my ragtag band of misfits to participate in events regardless of our geography. So we embarked on a mission to enable webhook integration for Webex teams, so that our products can send notifications into Teams, just as they can into email.

Cisco Webex is the leading enterprise solution for video conferencing, webinars, and screen sharing. Web conferencing, online meeting, cloud calling and equipment. Install Cisco Webex Meetings or Cisco Webex Teams on any device of your choice. Get step-by-step instructions for scheduling your own Webex meetings, real-time group messaging,. The Webex application can be used with Windows or Linux thin-client. The different Webex VDI plugins can be found on this page. For more information, please refer to the Webex VDI Release Notes.

A cloud native yet cloud agnostic solution

In order to do this we decided to make sure this wasn’t only able to support diverse products, but also, diverse clouds. A cloud native, yet cloud agnostic solution based upon serverless infrastructure supporting standard webhooks and HTTPS Post messages. We decided on Google Cloud platform and Amazon Web Services for our multi cloud endeavor.

Webex teams app download

The initial idea was actually for a separate use case – I have esp8266 modules integrated with Teams for the use case of being notified when my garage door is opened/closed, my bearded dragon’s cage is hot, etc. As these scale in number, if I ever were to change my security bot token or room ID, I would have to go re-flash all of my IoT Sensors to match. So, it creates an operational problem for leveraging Teams as a IoT device receiver or third party integrator.

Learn why Python is the high-demand software language for network programmability, and use it with developer tools like JSON and Postman. Develop first application on a real-world cloud collaboration platform with Webex Teams. Join developer professional communities such as Cisco DevNet, GitHub, and Stack Overflow. Search Github 'webex teams' DevNet Creations Cisco Code Exchange Youtube Channel: Webex Teams Integrations Video problem reporting to Wx Teams Hospital wait times Webex Teams articles by WWT (partner) Webex App Hub UCS Director integration App: Talk 2 Webex Teams mobile app for audio/video/TTS: WIDGETS & SDK: LIBRARIES & FRAMEWORKS.

Enable cloud as an API gateway

The idea was to enable cloud as an API gateway to accept requests, do advanced security checks, and decouple the Webex Teams security and context information from what is flashed onto the sensors to better manage the lifecycle. But extending this to webbooks was a natural evolution that seemed to have the most immediate impact to customers. When Demo’ing some of our cloud technologies (Intersight, Meraki), customers saw that notifications can go to webhook or email, and naturally inquired about their Webex Teams integration.

Webex

By enabling the webhook capability, we immediately added support for all of our product sets that support webhooks to integrate with Webex Teams. And do so without requiring any change on either the product, or Webex Teams. We did want to have native “handlers” in the code to handle differences in webhook formatting between different products. For our project we created handlers for Cisco DNA Center and Meraki. We had started work on Thousand Eyes but didn’t have the lab instance able to send webhooks at the time we finished the project. The amount of effort to create and modify a handler is as simple as 20 minutes worth of effort ensuring that the JSON fields that you care about, are included in what is sent to Teams.

The code is available on Github

Of note, while the code should have been very consistent between solutions, there is a difference in how Google integrates their API with their cloud functions compared to AWS. The API gateway on GCP has been out for a while, but right now integration of the API gateway on Google for cloud functions is in Beta and does require a bit more lift to setup. I expect this will normalize as it is brought to market. I also want to caveat that by noting I was seeking a functional product, closer integration with GCP teams probably would have helped with how I managed some error handling in Cloud Functions to make it integrate with API GW.

Related resources



Microsoft Teams and Cisco Webex: Building Bridges

To serve business needs, enterprises often end up installing custom software or using multiple tools to fulfil requirements.

Many tools offer freedom to avail distinct features, but accessing those features from different resources can be a daunting task.

That’s where interoperability makes sense.

When two or more applications interoperate, they offer users to have access to all features.

The co-existence of two tools not only provides an extensive list of functionalities but also makes the workplace productivity, and the business process twice as efficient.

Messaging interoperability: Microsoft Teams and Cisco Webex

The number of messaging users is rapidly growing.

From around 1.6 billion users in 2014 to 3.8 billion users in 2018, the growth of messaging provides an insight into the need and challenges on interoperability between messaging and collaboration tools.

To meet the distinct demands of the company, more and more enterprises are seeking means to bridge the features of multiple tools in one system.

While many applications can be bridged together, this article mainly addresses the interoperability of Microsoft Teams and Cisco Webex.

Here, we will highlight the best medium of connecting these two tools, and making the most of it.

Why Microsoft and Cisco is a great combination

Here’s why Microsoft Teams and Cisco Webex make for a perfect interoperability combination:

  • With Microsoft Teams, the users can avail Microsoft Licenses, Skype for Business features, and integrate natively with Office 365 features
  • Given Cisco’s legacy, users get access to hardware like Cisco Webex boards, VoIP handsets, and telepresence solutions
  • Microsoft Teams and Cisco Webex interoperability is the optimum solution for company acquisitions and mergers where one company’s resources are on Microsoft Teams, and the other one uses Cisco Webex.
  • Where Cisco Webex offers core hardware, Microsoft allows integration with leading third-party tools like Adobe Creative Cloud, Trello, Slack, Outlook, Survey Monkey, Wrike, Jira, Folly, and many more

Microsoft Teams and Cisco Webex interoperability options

1 – Cisco Webex and Microsoft Teams Office 365 integration

Recently, Cisco announced the compatibility of Webex with Office 365. With such an alliance, the users can easily access OneDrive, SharePoint, and even G-Suite applications within the Webex app.

Pros
1. You no longer require signing off from Webex to access Office 365 productivity tools like MS words, MS Excel, and Powerpoint

2. Since Office 365 assures robust security to your company’s data, Webex integration will allow you to benefit data governance have to keep your files encrypted

3. Content Created in MS tools can be easily transferred to Webex storage space

Cons
1. This combination works fine with different Microsoft Office tools, but the integration of Microsoft Teams is not possible

2. Webex users cannot make changes to Microsoft files

Author Verdict
The MS Office 365 and Webex team’s integration is perfect for users who need to access Office 365 tools within Webex, but it’s not a great pick for those looking for MS team’s collaboration too.

2 – Bot integration

IFTTT (If This Then That) allows the collaboration of applications and devices.

Through IFTTT, a rule or function is established for one device or app based on the action or behavior on another device or app.

One example is syncing an Instagram account with Twitter so the photos display on Twitter rather than a link.

In the business world, a similar process is followed when setting IFTTT for both Cisco and Microsoft. So, when a Webex contact sends a text, the bot in Microsoft Teams also gets a notification.

Pros
1. Users have the freedom to add customized actions

2. Bot integration has several pre-built activities to choose from across an extensive range of devices and applications

Webex Teams Developers

3. The familiar feel and design of IFTTT applications in the business world, that you may be used to from a consumer world

Cons
1. Administrative time for adding custom options is lengthy

2. With new users, the administrator is asked to add further actions or recipes

3. Limited features across platforms

Author Verdict
Bot integration can facilitate collaboration across Webex and Teams, but the cross-platform experience is not as seamless since notifications are not received in a native app, instead of in the bot itself.

3 –Cisco Webex Meetings for Microsoft Teams

Microsoft users who wish to host live meetings can integrate with Cisco Webex.

You don’t have to switch to a different tool since the interoperability allows Microsoft users to host Cisco Meetings directly.

Webex Developer Api

Pros
1. Users can host and schedule Cisco meetings without signing out of Microsoft Teams

2. The meeting app is available for Workplace from Facebook and Slack too

Cons
1. During the Webex meeting, from Microsoft Teams, you cannot exchange chats, messages, or files

2. Webex Meetings for Microsoft Teams does not support accounts on meetingsIn.webex.com and webex.meetings.com

Author Verdict
Cisco Webex Host Meetings for Microsoft is an excellent integration, but you’ll have to compromise with limited meeting functionality.

Bridging the gap

Interoperability between Microsoft Teams and Cisco Webex is simple.

You don’t need a technical developer, and no longer do you need to shoehorn one app into another. There’s only one tool you need: Mio.

Mio is the only platform to fully sync Cisco Webex and Microsoft Teams.

Mio operates through APIs and runs in the background to offer seamless messaging interoperability across channels and messages.

To start connecting your Microsoft and Cisco software, you don’t even need to download a new app, as it’s an entirely native experience.

How to Make Cisco Webex and Microsoft Teams Interoperable

You don’t need administrative support or a ton of training to get started. The way Mio allows collaboration across platform is simple.

Here’s how a non-techie can do it:

Step 1: Getting Started

Request a demo here (will open in a new tab).

Sign up by entering your email address and name. A Mio account rep will send you a verification link for account authentication for web-based interoperability experience.

Once your account is registered with Mio, you will need to add basic details that’ll help the system learn which programs or applications you want to sync. Once you have shared account details, Mio will scale to fit your business requirements.

Cisco Webex Teams Developer Portal

Step 2: Channel mapping and User mapping

The next step involves administering your team and adding the channels of your choice. For example, you can sync the ‘Project Management’ channel in Cisco Webex with the ‘PM’ channel of Microsoft Teams.

If you have dozens of linked channels, you can use the search feature to make the process super efficient.

Step 3: Message Routing

Once you’ve linked your channels, Mio can provide interoperability between these specific teams. There’s also an option to sync all channels in one go. You can also enable future sync so any new channels are automatically synced.

Step 4: People Sync

Mio isn’t restricted to just syncing channels. People Sync allows you to send direct messages between Webex and Microsoft Teams.

Once People Sync is active, Auto Prompt sends automatic prompts to users whenever they receive a message from anyone using Mio so they can start receiving messages from other platforms.

Bridging the gap between Microsoft Teams and Cisco Webex in your company

With Mio as a bridging tool, you can easily make your favorite messaging tools interoperable. You no longer need a complicated development or migration strategy if your team’s different applications.

This is a guest post provided by Md Mohsin Ansari, Marketing Manager at Troop Messenger. Troop Messenger is a business messenger that is spreading its wings across all industries by bringing all internal communication to one place. Connect with him on Linkedin.

You must be logged in to post a comment.