User Community Feedback

Submitted ideas will be evaluated by our product teams for upcoming releases and will be responded to so you know where things stand. For product support, please use the community forums or contact TAC.

NOTE: All Cisco employees & Channel Partners must enter Ideas through this Ideas Portal.

OBTP breaks if Join meeting link URL contains redirect header.


Many of our externally received WebRTC based meeting invites now contain a redirect header to the SafeLinks service, part of Office 365 Advance Threat Prevention.


e.g Join hyperlink https://eur03.safelinks.protection.outlook.com/ap/t-59584e83/?url=https%3A%2F%2Fteams.microsoft.com%2Fl%2Fmeetup-join%.....


This breaks OBTP whereby meeting invites forwarded to outlook room accounts and read by Webex Hybrid calendar connector display the correct meeting date/time on room kits, but show no Join button.

This presumably is due to the hybrid calendar connector not being correctly read the Join URL in the meeting invite.


At the moment IT administrators manually edit the Join hyperlink using https://www.o365atp.com/ and paste the decoded URL back into the link, before sending to the outlook room calendar account.

It would be good if Cisco could automatically inject the same logic to automatically strip the redirect header [if it exists] via the hybrid calendar connector.


This issue makes the use of OBTP in VC meeting rooms highly unreliable in our company for ordinary users as they book meetings themselves without knowing if the join button will appear.


  • Sanjay Patel
  • Mar 8 2022