Office 365 (Cloud-Based Service)
Deployment
-
Office 365 users who are assigned to the cloud-based service (indicated in Cisco Webex Control Hub as on cluster "Cisco Webex Cloud") may show a persistent error message in Control Hub, "Could not find cluster with Calendar Connector. Select another Resource Group, or configure a new cluster with Calendar Connector." This error can be ignored.
-
The cloud-based service does not activate a user whose email address contains an apostrophe. If you are migrating users from the Expressway-based Calendar Connector, the Hybrid Calendar Service does not move these users to the cloud-based service. They remain on the Calendar Connector.
General Scheduling Issues (All Keywords)
-
In order for OBTP to work consistently on invited devices, you must ensure that the mail system does not have a policy to automatically delete meeting comments. The following PowerShell command ensures that comments are retained so that the Hybrid Calendar Service can use them to process meetings:
Set-CalendarProcessing -identity "room" -DeleteComments $false
-
Hybrid Calendar Service does not support shared calendars. The service can process meetings that a delegate schedules on behalf of others, as long as they schedule the meeting in the user's actual calendar, not a shared or group calendar.
-
A meeting that is scheduled more than 5 months in the future may not get immediately processed by the cloud-based Hybrid Calendar Service for Microsoft Office 365. The service processes meetings that are 5-6 months in the future on a daily basis using a sliding window, so once the meeting's scheduled date falls within the window, it will get processed and show the meeting join details.
-
If you add a scheduling keyword or supported video address to a single instance of a recurring meeting series, the meeting join details are not updated. As a workaround, add the keyword or video address to the entire meeting series.
-
Hybrid Calendar Service does not automatically add meeting join information to a meeting that's scheduled in the past.
Scheduling a Webex Personal Room Meeting (Keywords Including @webex, @meet:myroom)
-
Hybrid Calendar Service does not add Webex details if the meeting invitation already contains Webex join links (for example, added with Productivity Tools or manually by the meeting organizer). The meeting organizer can manually delete any previously added join links so that Hybrid Calendar Service can add the new join links.
-
Hybrid Calendar Service does not process meetings with more than 300 meeting invitees.
-
You cannot customize the meeting details template except to modify the line of text that is included if you check Use a Pilot Number in Webex Site Administration. For instructions, see Can I Customize the Email Template Used by the Cisco Webex Hybrid Calendar Services with @Webex?
Scheduling in a Cisco Webex Space (Keywords Including @webex:space, @meet, @spark)
-
Space keyword scheduling currently supports a maximum of 60 meeting participants. A meeting organizer who invites more than 60 participants will receive an email message indicating that they have exceeded the maximum.
-
Space keyword scheduling does not currently handle distribution lists. Individual members of the distribution list still receive the meeting invitation with details on joining the space, but are not automatically added to the space. As a workaround, the meeting organizer can expand the mailer on the TO line before sending the invite. That way, each user is individually added to the space.
-
Attachments that users add to meeting invites with space keywords are not added to the corresponding space.
-
The Hybrid Calendar Service no longer sends a separate email message to meeting invitees who are not Cisco Webex users, inviting them to sign up.
-
You cannot customize the meeting details template that is used for meetings scheduled in a space.
One Button to Push (OBTP)
-
For issues involving the Join button and meetings list in the Webex app, see the Known Issues for Cisco Webex Meetings article.
Cisco TMS Integration with Office 365
-
If the conference bridge that is scheduled to host an upcoming meeting becomes unavailable, Cisco TMS updates the meeting join details to use a different bridge. However, the meeting join details do not get updated in Office 365 unless the organizer makes a change to the meeting invitation. This can cause problems when invitees try to join the meeting from the invitation.
-
If a meeting scheduler's time zone in Office 365 does not match the scheduler's time zone in Cisco TMS, the system may have a problem scheduling recurring meetings. This can cause a mismatch between the instance dates in Office 365 and in Cisco TMS. As a workaround, make sure users' time zones in Office 365 match their time zones in Cisco TMS.
-
For a recurring meeting series, changes to the start and end dates or number of occurrences in Office 365 are not updated in Cisco TMS. (Changes to the start and end times of the entire series work as expected.) As a workaround, delete the series and create a new one.
-
When a recurring meeting series scheduled with @meet is edited multiple times, the series updates correctly in Office 365 but may not update correctly in Cisco TMS. The behavior is not consistent. For example, adding attendees to a single instance of the series and then changing the subject of the entire series may result in the subject changing only for the modified instance—or for all instances other than the modified instance.
-
If an endpoint is already booked in Office 365 for a given time slot for a non-@meet meeting, and an organizer schedules a recurring meeting with @meet which overlaps the booked time slot, the organizer gets a message saying that the endpoint declined the meeting, but Cisco TMS creates the recurring meeting anyway.
For such meetings, the Calendar Connector sends an extra meeting request and logs two different informational messages that each include one of the following strings:
-
status:MEETING_NOT_FOUND_ON_TMS
-
status:UN_EXPECTED_EXCEPTION
-
-
The Calendar Connector should raise an alarm if the organization to which the Expressway host is registered has the @meet keyword action set to Cisco TelePresence Management Suite but the Calendar Connector has not been linked to Cisco TMS on the Expressway page. This alarm has not been implemented.
-
If you remove the Cisco TMS configuration from the Expressway connector host, users can continue to schedule @meet meetings on Cisco TMS until the Expressway connector host is restarted. The workaround is to restart the Expressway connector host after removing the Cisco TMS configuration.