This tab covers software upgrades to the Expressway-based Calendar Connector for Microsoft Exchange and Office 365.

Use Control Hub to manage connector software upgrades and schedule when they are performed. Connector software is automatically downloaded to and installed on the Expressway.

For Cisco Spark Hybrid Services, X12.5 is the minimum supported version of Expressway for new connector host registrations to the cloud. X8.11 is the minimum version for existing registrations to the cloud.

8.11-1.0.7675

October 13, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7666

October 6, 2020

  • Fixed another issue which may cause proxy authentication failures.

8.11-1.0.7655

September 29, 2020

  • Fixed an issue where processing of a meeting invitation resulted in a processing loop and an increase in overall meeting processing time.

  • Change to address an issue where @meet or @webex may not work properly after changing the default behavior settings in Control Hub.

8.11-1.0.7626

September 14, 2020

  • Fixed an issue where the Calendar Connector is unable to register due to proxy authentication issues.

8.11-1.0.7607

September 1, 2020

  • Changes for upcoming attendee-based processing support.

8.11-1.0.7589

August 25, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7505

July 29, 2020

  • For meetings scheduled using the Webex Productivity Tools plug-in, fixed an issue where meeting attendees would receive 2 meeting invitations in their email inbox. With this fix, meeting attendees should now only receive 1 meeting invitation.

8.11-1.0.7453

July 13, 2020

  • Increased the number of days stored in the calendar from 28 to 31 days into the future.

  • Performance optimizations.

8.11-1.0.7379

June 23, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7323

June 16, 2020

  • Reverted to this version due to the installation issue below.

8.11-1.0.7339

June 15, 2020


An installation issue has been discovered in version 8.11-1.0.7339. To correct the issue, version 8.11-1.0.7323 has been redeployed. Calendar Connectors which attempt to upgrade to 8.11-1.0.7339 may see the following alarm: "Could not download connector Calendar Connector from https://binaries-test.webex.com/CalendarConnectorStable/20200615233010/calendar-production-stable.tlp". This alarm can be ignored.

  • Fixed an issue where the meeting join link may no longer appear in the Webex Teams app for meetings which are in the past.

8.11-1.0.7323

June 2, 2020

  • Added a fix for a deadlock which may have caused the Calendar Connector to stop processing when debug logging level is enabled.

8.11-1.0.7317

May 26, 2020

  • Removed an extra '\' character in the French @webex meeting invitation template.

  • Fixed initialization issue with the Cisco TMS integration.

8.11-1.0.7285

May 4, 2020

  • Includes a change that allows joining a Webex meeting using the join URL even if the join URL is not available in the body of the meeting invitation.

    This change uses the SIP URI dial-in number (if found) to look up and retrieve the associated join URL. When a user attempts to join such a meeting from Webex Teams, the join URL is used to join the meeting instead of the SIP URI dial-in number.

8.11-1.0.7277

April 22, 2020

  • Includes scalability enhancements.

  • Includes a fix for the "Meeting Processing Queue Limit Reached" alarm.

8.11-1.0.7238

April 7, 2020

  • Includes COVID-19 scalability change.

  • Change to properly handle the scenario where a user converts a recurring meeting series to a single instance meeting.

  • Change to properly remove a meeting from the Webex Teams meetings list when a meeting is cancelled while organizer is not subscribed to a connector.

8.11-1.0.7162

February 25, 2020

  • Includes support for organizations in the European region.

8.11-1.0.7057

February 11, 2020

  • Fixed an issue where attempting to log into the Expressway admin interface results in "Login expired: Invalid cookie", due to the disk filling up with GSSAPIBindRequest-JAAS-Config configuration files in the tmp folder. We have improved how we delete these files.

  • Updated the copyright date from 2019 to 2020 in the @meet and @webex meeting templates.

8.11-1.0.7046

January 13, 2020

  • Updated heartbeat mechanism calendar connector uses to check connectivity with the cloud.

  • When an organizer creates a meeting from an existing Webex Teams space (either from the schedule button or by copying and pasting the space information into the meeting invitation) and adds attendees who are not Webex Teams users, the Hybrid Calendar Service no longer sends an error email to the organizer indicating that these attendees couldn’t be added to the space.

8.11-1.0.6252

November 25, 2019

  • Fixed a crash in the Calendar Connector which was triggered by an internal metrics process.

8.11-1.0.6185

October 28, 2019

  • Fixed an issue where meeting invitations with @meet in the location field may result in multiple lines of text "When it's time, join the Webex Teams meeting here." appearing in the meeting body.

  • Fixed an issue which is causing the "Meeting Processing too long" alarm to be raised and lowered repeatedly.

  • Updated text font used for call-in number country labels for @meet and @webex meeting invitations.

8.11-1.0.6155

October 7, 2019

  • The Hybrid Calendar Service can now parse Cisco Webex Personal Room links in a format like site.webex.com/meet/<userid> (the https:// prefix is no longer required). The service can parse the link from either the location or body of a meeting invitation and use it to provide join notifications (One Button to Push).

  • Fixed an issue with the TMS integration where the Calendar Connector could encounter a proxy error and fail to initialize after a restart. When this happens, the administrator sees the alarm "Conferencing Connector initialization failed."

  • On the Calendar Connector administration page on Expressway, removed the redundant “Configure Cisco Webex Meetings Site” link from the Related Tasks section.

8.11-1.0.6104

September 12, 2019

  • No release notes for this maintenance upgrade.

8.11-1.0.6078

September 2 / August 30, 2019

  • September 2, 2019: Re-release of 8.11-1.0.6078 to fix issue with installs and upgrades with version released on August 30.

  • Improved subscription error handling. The internal service URL will be retried if the external service URL fails during the user subscription process.

  • Fixed an issue where a large number of auto-discovery retries were being attempted for users with no mailboxes.

  • Combined the Applications > Hybrid Services > Calendar Service > Cisco Webex Meetings Site Configuration menu option with the Cisco Conferencing Services Configuration menu option on the Cisco Expressway connector host.

8.10-1.0.5848

August 8, 2019

  • Updated @meet and @webex meeting templates to version 2.2.0.0.

8.10-1.0.5817

July 22, 2019

  • Updated the @webex meeting template to list the join-by-phone call-in numbers in the correct order.

8.10-1.0.5798

June 28, 2019

  • Deployed to the cloud on June 24, 2019: Change for issue where, when a user specified two toll numbers or two toll-free as their Webex call-in number preferences, only one number was being shown in the @webex meeting invitation. The change allows both toll or toll-free call-in numbers to be shown in the @webex invite.

8.10-1.0.5744

June 5, 2019

  • Fixed an issue where the join notification is still shown in Webex Teams even after the @webex keyword is removed from the meeting location field and the join links are removed from the meeting body.

8.10-1.0.5720

May 24, 2019

  • Fixed an issue where meeting attendees may receive multiple meeting updates in their inbox each time an attendee accepted or declined the meeting invitation..

8.10-1.0.5713

May 8, 2019

8.10-1.0.5609

April 2, 2019

  • Fixed an issue where the Calendar Connector may become non-operational if the administrator selects Calling in Webex Teams (Unified CM) as their Calling Behavior method in Control Hub.

  • Addressed an issue where @meet invitations with join links copied and pasted into the invite body may create a new space instead of reusing the existing space.

  • Addressed an issue where user accounts are stuck in pending activation status due to XML parsing error.

  • Added support for cases when a double “sip:sip:” format is detected in meeting invitation join links (in addition to single “sip:” format).

  • Addressed an issue which resulted in no join notification (no OBTP) for some 1:1 space meetings.

  • Updated the copyright date to 2019 in @meet and @webex meeting template.

8.10-1.0.5545

February 20, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.5533

January 25, 2019

  • Fixed CSCvo03678 Autodiscover fails for accounts with redirectURL.

  • Backed out an OBTP join notification change from December for Cisco TMS/TMSXE integrations. The change had caused removal of the bridge for meetings that were scheduled on TMS after they were processed by the Hybrid Calendar Service.

  • On the Microsoft Exchange Configuration page, added an Enable SCP record lookup option in the Discovery section. When unchecked, the Calendar Connector will not attempt an SCP lookup in Active Directory during the Autodiscover process. (See the January 4, 2018 entry in What's New with Cisco Webex Hybrid Services for more information.)

  • On the Microsoft Exchange Configuration page, the maximum length of the Service Account Password field has changed from 120 to 128 characters.

  • Cisco TMS/TMSXE systems will now send OBTP join notifications if there is a non-Cisco SIP URI in the location field of the meeting invitation.

  • Fixed one scenario which may cause the “Meeting processing time too long” alarm to be raised.

8.10-1.0.5475

December 7, 2018

  • Updated @meet and @webex meeting invitation template to version 2.1.0.0. Changes include adding the Meeting Number field towards the top of the template, consistent placement of the global call-in number links and consistent font size formatting.

  • If a meeting organizer invites an attendee who is not a Webex Teams user to a meeting with @meet in the location field, the Hybrid Calendar Service will no longer create an account for that user and add them to the Teams space. Instead, the meeting organizer receives an email notifying them that an attendee could not be added to the space.

  • The Hybrid Calendar Service now detects join links with the *@meetup.webex.com format for One Button To Push (OBTP) join notifications.

  • Previously, the Calendar Connector could fill the disk with GSSAPIBindRequest-JAAS-Config configuration files in the tmp folder. We now delete these files as they are created, to avoid filling the disk space.

  • Previously, if an Exchange environment used a generic redirect for invalid URLs (for example, autodiscover.example.com/autodiscover/autodiscover.xml) and the redirect resulted in a browser response with data, the Hybrid Calendar Service would keep retrying the URL in step 2 of the Autodiscover process. This could cause excessive requests to the web server. Now, the Hybrid Calendar Service marks the redirect as invalid if it doesn't recognize the data.

  • Fixed an issue where TMS/XE systems would not send OBTP join notifications if there was a Webex Teams space meeting link URL detected in the meeting body of the meeting invitation.

8.10-1.0.5328

October 12, 2018

8.10-1.0.5279

September 14, 2018

  • Added an Expressway configuration page that administrators can use to allow or block Autodiscover redirection URLs. Running an Autodiscover test automatically adds URLs to the list in pending state, or administrators can add URLs to the list manually. Pending URLs are blocked unless an administrator chooses to allow them.

8.10-1.0.5260

September 7, 2018

  • Updated the Calendar Connector version numbering from 8.8.-1.0.xxxx to 8.10-1.0.xxxxx.

  • Fixed an issue where join notifications (also known as One Button to Push, or OBTP) for meetings with both @spark in the meeting location field and Webex Productivity Tools in the meeting body may not appear on all supported Webex Teams platforms.

  • Fixed an issue where the Skype for Business join link doesn't appear in @webex meeting invitations if the Webex site has not been linked to Control Hub or the Personal Room setting is not configured for users in the Webex Teams app. (This issue was fixed in the cloud and does not require a Calendar Connector upgrade.)

8.8-1.0.5219

August 17, 2018

  • We've introduced @meet as a new keyword, and new keyword modifiers :space and :myroom to control the behavior of the @meet and @webex keywords.

    The keyword @meet and the compound keywords @meet:space or @webex:space all create a space in Cisco Webex Teams.

    The compound keywords @meet:myroom and @webex:myroom work the same way as @webex, using the user's Cisco Webex Personal Room. Each option adds the appropriate join details to the body of the meeting invitation.

    Users with multiple Cisco Webex sites can still use @webex:<site> for the time being, but we strongly recommend configuring the My Personal Room setting in the Cisco Webex Teams app to specify which site @webex uses. This setting also indicates which site the app should monitor for participants entering the user's Personal Room lobby.

    The @spark keyword will also continue to work for the time being. However, if your organization is currently using @spark, we recommend instead using @webex:space or @meet because @spark will eventually be removed at a future time once usage drops.

  • Fixed issue present in Calendar Connector build 5201 where the Calendar Connector may stop operating if the hybridservices.c_cal logging level is set to DEBUG.

  • Fixed an issue where join notifications (also known as One Button to Push, or OBTP) may not work when using @webex with FedRAMP, telephony service provider (TSP), or CMR Hybrid Webex sites. (This issue was fixed in the cloud and does not require a Calendar Connector upgrade.)

8.8-1.0.5194

August 3, 2018

  • Fixed issue to allow parsing of SIP URI join links from meeting invitations using both the "sip%3A" and "sip:" formats. Previously "sip%3A" was not recognized and would not result in a join notification appearing in the Webex Teams app.

  • Fixed issue where in some cases @spark or @webex meetings mistakenly had double sip:sip:<URI> in the SIP URI joinable link. This caused failures when attempting to join these meetings. To address this issue, we no longer add sip: if it already exists.

8.8-1.0.5158

July 19, 2018

  • Fixed the top priority issue configuring the Calendar Connector on Expressway X8.11, which was causing two problems:

    • Entering an email address in the Discovery section of the Microsoft Exchange Configuration page causes the configuration to fail. Until we fix this issue, the only way to configure a new Calendar Connector or change the Exchange configuration is by leaving the Email Address field blank, which means that you will not be able to test your configuration as you save it. As a workaround, you can use the steps in Test Microsoft Exchange Autodiscovery and Impersonation to try to simulate the test, from a machine that has network conditions as similar as possible to the Expressway-C.

    • On the Webex Configuration page, using the Test Connection button causes the same failure. The workaround is to click Save without testing.

  • Rebranding updates for the user email notification template.

  • Added German localization for "Join using Microsoft Skype for Business" text in meeting invitations.

  • Fixed the integration of @spark meetings with TMS/XE (added sip: protocol prefix to SIP URIs).

  • Fixed an issue where cancelled meetings occasionally would not be removed immediately from the Webex Teams meetings list.

  • Added retry logic to help ensure meeting join notifications appear when other backend services are busy.

8.8-1.0.5077

June 15, 2018

  • For meeting invitations which only include a Webex Personal Room URL in the meeting body (with no SIP URI), clicking the join notification (OBTP) in the Webex Teams app will now join the meeting through the Webex Teams app. Previously, clicking the join notifications for these meetings would cross-launch the meeting in a Webex browser window.

  • Updated text strings in email notifications for Webex Teams rebranding.

  • Updated text strings in the Expressway user interface for Webex Teams rebranding.

8.8-1.0.5045

June 8, 2018

  • No release notes for this maintenance upgrade.

8.8-1.0.5037

June 1, 2018

  • Updated the join link text in the @spark meeting invite from "Join Cisco Spark meeting" to "Join Cisco Webex Teams meeting"

  • Fixed an issue where users who are not enabled for Hybrid Calendar Service may not receive meeting join notifications (OBTP).

8.8-1.0.5008

May 18, 2018

  • Fixed one cause of the "Meeting processing time too long" alarm, which would sometimes be triggered due to processing a high volume of attendee responses.

  • Fixed scenario where invitees who declined a meeting were counted against the maximum attendee limit. Because of this scenario, some attendees would not receive the meeting join notification (OBTP).

8.8-1.0.4985

May 11, 2018

  • No release notes for this maintenance upgrade.

8.8-1.0.4979

May 4, 2018

  • For @webex meeting invitations, added "Join using Microsoft Skype for Business" link and localized text translations

  • Fixed an issue where users with mixed-case email addresses could experience a period of time in which updates to their Outlook calendar meetings aren't detected.

  • Fixed an issue where 1-1 meetings created from a Cisco Spark space always get added to the private 1-1 space instead of the space from which the meeting was created.

  • Fixed an issue where some meeting join links were not parsed properly if the user did not enter a carriage return after the join link.

  • Fixed an issue where a copied and pasted Cisco Spark space URL was not being detected in the Outlook meeting location field.

  • Updated the @spark and @webex template copyright year to 2018.

  • If an autodiscovery URL for a user's email domain was found via SCP lookup in Active Directory and the initial autodiscovery response from Exchange returned a RedirectTarget address, the Calendar Connector reused the original autodiscovery URL that was retrieved via SCP rather than a new URL based on the RedirectTarget address. This could cause a flow loop where the actual user settings were never retrieved and that user could never be assigned to a Calendar Connector or activated. This is now fixed so that the email domain of the RedirectTarget address is always used to acquire the next autodiscovery URL in the flow.

  • Fixed how the TLS configuration is applied for the Microsoft Exchange Autodiscover process. In the Calendar Connector Exchange configuration, there are two different settings that can dictate whether certificate validation is performed when making a secure connection. Each of these settings has an option of On or Off. If set to On, certificate validation is performed. If set to Off, no certificate validation is performed. The settings and their intended scopes are as follows:

    1. TLS Verify Mode—This setting is used when making a connection to Exchange.

    2. LDAP TLS Verify Mode—This setting is used when making a connection to an LDAP server to search for Exchange Autodiscover SCP records.

    Prior to the fix, the LDAP TLS Verify Mode was used for all connections during the Exchange Autodiscover process, regardless of whether performing an LDAP query or an Exchange request. So if LDAP TLS Verify Mode was On and TLS Verify Mode was Off, certificate validation was always performed when connecting to Exchange during Autodiscover. Conversely, if LDAP TLS Verify Mode was Off and TLS Verify Mode was On, certificate validation was not performed when connecting to Exchange during Autodiscover.

    After the fix, LDAP TLS Verify Mode is used only when making a connection to an LDAP server during Autodiscover, and TLS Verify Mode is used for all other connections involved in the Autodiscover process.

  • Fixed how the Calendar Connector searches for SCP pointers.

    Autodiscover flow steps are explained in https://msdn.microsoft.com/en-us/library/office/ee332364%28v=exchg.140%29.aspx?f=255&MSPPError=-2147217396.

    For step 1 (SCP lookup), further detail is provided in https://msdn.microsoft.com/en-us/library/office/dn467395(v=exchg.150).aspx.

    The second link explains the difference between the two types of SCP objects for Autodiscover provided by Exchange:

    • SCP pointers—These objects contain information that points to specific LDAP servers that should be used to locate Autodiscover SCP objects for the user's domain. SCP pointers are stamped with the following GUID: 67661d7F-8FC4-4fa7-BFAC-E1D7794C1F68.

    • SCP URLs—These objects contain URLs for Autodiscover endpoints. SCP URLs are stamped with the following GUID: 77378F46-2C66-4aa9-A6A6-3E7A48B19596.

    Prior to the fix, the Calendar Connector search for SCP pointers was not working properly. However, search for SCP URLs was working properly all along, and SCP URLs are the common type necessary for successful Autodiscover. There were no known reports of Calendar Connector Autodiscover failing due to unsuccessful SCP pointer lookup; the problem was only found by means of code review. With this fix, the Calendar Connector search for SCP pointers now works properly.

8.8-1.0.4896

March 29, 2018

  • Logging cleanup

  • Fix to address a possible split meeting occurrence when a meeting is scheduled with Productivity Tools and @webex.

  • Partial fix for participants whose email addresses are enclosed in single quotes. For @spark invitations, the Calendar Service now adds these participants to the Cisco Spark space. However, we are awaiting a fix from Microsoft to be able to update these participants' meeting invitations with the join details.

  • Fix to no longer falsely raise the alarm "Cisco Collaboration Meeting Rooms (CMR) service unreachable or access denied."

  • Addressed an issue seen at one customer, where users were stuck in pending activation state due to network latency reaching the Cisco Collaboration Cloud. Increased a timeout value to allow user activation.

8.8-1.0.4724

February 2, 2018

  • When a proxy is configured, the Calendar Service > Cisco WebEx Configuration page on Expressway no longer enforces DNS resolution.

  • Fix to address alarm: "Meeting processing time too long; Calendar Service meeting processing time exceeds a threshold of 5 minutes for at least one user."

8.8-1.0.4703

January 20, 2018

  • Fix for the Expressway Calendar Connector User Subscription status page. Users without subscriptions that are waiting to retry subscription are now counted in the users with failed subscription totals.

8.8-1.0.4696

January 12, 2018

  • Improved the configuration options on the Calendar Connector - Microsoft Exchange Configuration page for hybrid Exchange On-Premise / Office365 deployments by allowing both NTLM and Basic authentication types to be selected. Now if one method fails then the other method is attempted.

  • Enabled Cisco Spark desktop join notifications for meetings where the meeting organizer puts someone else’s WebEx Personal Room link in the meeting location field.

  • Change to reduce number of "Retrieving key from encryption service failed" alarms raised.

  • Fix to allow Calendar Connector to return to an operational state after a cloud connectivity interruption (reported on the Expressway as a "mercury error").

8.8-1.0.4646

December 1, 2017

  • Updated the "Join Cisco Spark meeting" URL within @spark 1-1 meeting invites. The new join URL will now launch the Cisco Spark app instead of launching the Cisco Spark web client.

  • Fixed scenario where some declined meetings were still appearing in the meeting list on Cisco spark desktop apps. If the user declines the entire meeting series, all instances of the meeting should now be removed from the meeting list.

8.8-1.0.4636

November 24, 2017

  • Fixed issue where Exchange configuration test fails but changes are saved and success is reported.

  • Enhanced SIP URI parsing algorithm to detect new patterns such as sip:jdoe@company.com or 18005251234@example.com for Cisco Spark app desktop join notifications.

  • Removed the every-10-minute check for alarm “Cisco Collaboration Meeting Rooms (CMR) service unreachable or access denied.” The alarm was raised too frequently and was not actionable.

8.8-1.0.4596

November 16, 2017

  • Removed support for using both @spark and @webex in the meeting location field. If @spark and @webex are used together, @spark will be ignored and only @webex will be processed. A Cisco Spark space will not be created.

  • Fixed issue where a WebEx user account error is not raised in the Cisco Spark Control Hub user status.

  • Fixed issue where OBTP join notification is not appearing for meetings scheduled by users who have not been enabled for Hybrid Calendar Service.

  • Fixed issue where web proxy configuration prevents users from being assigned to Calendar Connector.

  • Fixed issue where SIP URI dial strings are not correctly parsed from meeting invitations for OBTP join notifications.

8.8-1.0.4535

November 9, 2017

  • Alarms which only apply to specific users will no longer be raised as system-level alarms (such as user subscription errors or WebEx user account issues). These user-specific conditions will now be reported as user errors in the user status.

  • Improvements to allow certain OBTP Join notifications to connect to the meeting through the Cisco Spark app instead of cross-launching WebEx.

8.8-1.0.4521

November 3, 2017

  • Addressed ErrorTokenSerializationDenied errors caused by CAS proxy when trying to service user mailboxes.

  • Performance optimization: reduced calendar synchronization activity with Microsoft Exchange.

  • Performance optimization: reduced calendar requests to Cisco Spark Conversations service.

8.8-1.0.4486 - Urgent upgrade (will automatically upgrade within 24 hours, at the scheduled time)

October 18, 2017

  • Fix for Cisco Spark Hybrid Calendar Service Information Disclosure Vulnerability. See Cisco Security Advisory for details: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20171023-spark

  • Fixed issue where join notification (OBTP) does not appear for forwarded meetings or for meetings where a recipient has been added.

  • Fixed issue where extra join notifications (OBTP) are appearing for a meeting while it is in progress.

  • Fixed issue where some Calendar Connectors may still be communicating with the old data center when there is a Cisco Spark data center switch.

8.8-1.0.4456

October 13, 2017

  • Logging and performance optimizations.

8.8-1.0.4429

October 6, 2017

  • Improved calendar subscription error handling.

  • Reduced the amount of connector logging on Expressway.

  • Performance optimizations.

8.8-1.0.4414

September 29, 2017

  • For meetings scheduled using WebEx Productivity Tools, the OBTP join button now joins the meeting in the Cisco Spark app instead of in the WebEx browser client.

  • Fixed an OBTP issue that occurred after changing the start time of a recurring meeting. Before this fix, the OBTP join button would appear just before the original meeting start time. Now the join button appears only before the new meeting start time.

8.8-1.0.4402

September 9, 2017

  • Added a fix for a Calendar Connector crash.

  • Added a fix for a Calendar Connector deadlock.

  • Fixed issue where the Office 365 Exchange configuration record save test using the service account UPN was not a valid test.

  • Added a fix to prevent Calendar Service from getting stuck in initializing state while in maintenance mode.

  • Fixed issue where autodiscovery via SRV record lookup fails due to FQDN dot.

  • Performance optimizations.

8.8-1.0.4354

August 2, 2017

  • Fix to remove OBTP for meetings which are cancelled within 5 minutes of the meeting start time.

  • Changed the default setting for Discovery to Use Active Directory on the Microsoft Exchange Configuration window.

  • Reduced volume of email sent when the meeting organizer includes a distribution list in the meeting invitation. The email is now only sent if the meeting organizer is enabled for Cisco Spark meeting list and OBTP trials.

  • Added a fix for a calendar connector crash.

  • Removed excessive technical details in end user email notifications.

  • Fixed formatting problems when changing a meeting's Location from @spark to @webex.

  • Fixed formatting problems when updating @spark 1-to-1 meetings.

8.8-1.0.4256

June 30, 2017

  • Fixed formatting problems when updating @spark 1-to-1 meetings.

  • Fixed formatting problems with custom text in @webex meeting invitations, for example characters such as ( ) or @ will be rendered correctly.

  • Enhancements and fixes for Cisco Spark meeting list and One Button To Push (OBTP) Trials sites.

  • For Cisco Spark meeting list/OBTP users, added email notification for meeting organizers who have included distribution lists in their @webex or @spark meeting invites, informing them that attendees included as a part of distribution lists will not receive meeting notifications in Cisco Spark.

  • Fixed issue where "You updated the agenda…" text was incorrectly posted into your Spark space. This artifact is no longer posted to Cisco Spark spaces.

8.8-1.0.4160

May 24, 2017

  • @webex scheduling is now supported for a Cisco Collaboration Meeting Room that is configured with Cisco Spark-integrated single sign-on (SSO). Your Cisco WebEx site version must be WBS31 or later.

  • Added a fix for a calendar connector crash.

  • Changed the first line of the @spark meeting information to "Join Cisco Spark Meeting."

  • Localization of the "Video address" text in the @spark meeting information.

8.8-1.0.4125

May 19, 2017

  • Reduced the amount of connector logging on Expressway.

  • The openJDK framework will be updated for upcoming signed connector support. The openJDK update on the stable channel is scheduled for Saturday night (May 20). Be aware that the calendar connector will restart after this update. If the calendar connector stops or does not restart, then restart it manually.

8.8-1.0.4115

May 12, 2017

  • The SIP URI (video address) is now added to @spark group meeting invites. (For example, sip:12345678@meet.ciscospark.com.)

  • Provided a fix for localized @spark and @webex meeting information that is added to an invitation. The new video address line in @spark is not yet localized. See here for a list of languages that Cisco Spark supports. (Indonesian is not yet supported. Also, the calendar connector supports Spanish (Mexico) instead of Spanish (Latin America)).

8.8-1.0.3966

April 10, 2017

  • The Calendar Connector status page on Expressway-C shows the connectivity status of all configured WebEx sites.

  • Minor bug fixes and enhancements.

8.8-1.0.3855

March 3, 2017

Fixed an issue where entering username@domain.com long format in the Username field was not accepted in the Calendar Connector WebEx configuration page.

8.8-1.0.3826

February 28, 2017

  • Updated "Cisco WebEx Configuration" page on Expressway as described in the updated documentation. The username and password fields are now optional (for upcoming support of Cisco Spark/CI-enabled WebEx sites), and a "Test Connection" button was added.

  • Added support for Cisco Spark space URL detection in @spark meetings. If a space URL (such as https://web.ciscospark.com/meet/…) is detected in an @spark meeting, then the meeting is associated with the Cisco Spark space instead of creating a new one.

  • Fixed an issue that caused a long Calendar Connector startup time.

8.7-1.0.3704

January 20, 2017

  • The proximity link was removed from the @webex meeting information.

  • The "Join Now" link in the @spark meeting information is updated with the new Cisco Spark space URL.

  • Fixed issue where adding the Exchange Service Record for Office 365 errors out in certain scenarios.

  • Fixed issue where users without mailboxes get assign to a connector and appear as "activated."

This tab covers software updates to the cloud components of the Hybrid Calendar Service and to the cloud-based service for Office 365 and Google Calendar.

July 21, 2020 (updated August 19, 2020)

Domain and Address Requirements for Webex Room Devices (Google Calendar)

Webex room devices will no longer display the meetings list from Google Calendar unless you have verified your domains in Cisco Webex Control Hub, including the domain of the account that manages access control lists. We’re also requiring that Google email addresses for Webex room devices match the @resource.calendar.google.com format.

For example, if your room device email format uses a domain prefix and your email domain is company.com, you’ll need to verify the company.com domain and make sure that all Workspaces have an email address that uses the Google room resource format:

Example:
company.com__3130313639353739333032@resource.calendar.google.com

Newer resource email addresses may not include a domain prefix, as in the following example:

c_0803348627605091471198@resource.calendar.google.com

This change does not affect the ability to schedule meetings with keywords (@webex or @meet) or video addresses, and does not impact users' meetings lists in the Webex Teams app.

September 17, 2019

  • We've updated the email templates for the Hybrid Calendar Service to match the email template redesign and simplification that was introduced for Webex Meetings in WBS39.5.