Beta Disclaimer

Beta releases of hybrid service connectors are not at the level of performance and compatibility of a final, generally available, product offering. Beta releases may not operate correctly and may be substantially modified prior to their general availability. Cisco is not obligated to make any version of Beta releases commercially available.1

For Cisco Webex 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.7737

November 23, 2020

  • Fixed an intermittent issue where room devices may not display meeting information due to a timeout reaching services in the cloud.

8.11-1.0.7735

November 20, 2020

  • Fixed an intermittent issue where the @meet or @webex meeting join information may appear in the wrong language.

8.11-1.0.7723

November 13, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7716

November 6, 2020

  • Fixed an issue where @webex meeting join links are not re-added to the meeting invite if the meeting organizer deletes them from the meeting body.

8.11-1.0.7713

November 4, 2020

  • Fixed another issue which may cause proxy authentication failures.

8.11-1.0.7711—Urgent upgrade (will automatically upgrade within 24 hours, at the scheduled time)

November 2, 2020

  • Fixed an internal null pointer exception observed in meeting processing with null location meetings.

8.11-1.0.7708

October 30, 2020

  • Fixed an issue related to handling relative redirects during the Microsoft Exchange Autodiscover process.

8.11-1.0.7705—Urgent upgrade (will automatically upgrade within 24 hours, at the scheduled time)

October 27, 2020

  • Fixed an issue where the user may intermittently see partial or inaccurate meeting join information added to their @meet or @webex:space meeting invitation.

8.11-1.0.7700

October 23, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7691

October 16, 2020

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

8.11-1.0.7680

October 9, 2020

  • Set the EXTERNAL_CONFERENCE_DATA for Microsoft Teams based meetings for the Cisco TMS integration and the Webex video integration for Microsoft Teams.

8.11-1.0.7675

October 2, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7666

September 25, 2020

  • Fixed another issue which may cause proxy authentication failures.

8.11-1.0.7655

September 18, 2020

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

8.11-1.0.7652

September 11, 2020

  • 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

August 27, 2020

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

8.11-1.0.7607—Urgent upgrade (will automatically upgrade within 24 hours, at the scheduled time)

August 24, 2020

  • Changes for upcoming attendee-based processing support.

8.11-1.0.7589

August 14, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7537

July 24, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7505

July 17, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7483

July 10, 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 2, 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 12, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7339

June 5, 2020

  • 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

May 21, 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 13, 2020

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

8.11-1.0.7308

May 7, 2020

  • Fixed initialization issue with the Cisco TMS integration.

8.11-1.0.7298

May 1, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7285

April 24, 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—Urgent upgrade (will automatically upgrade within 24 hours, at the scheduled time)

April 20, 2020

  • Includes scalability enhancements.

8.11-1.0.7255—Urgent upgrade (will automatically upgrade within 24 hours, at the scheduled time)

April 14, 2020

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

  • Includes scalability enhancements.

8.11-1.0.7238—Urgent upgrade (will automatically upgrade within 24 hours, at the scheduled time)

April 6, 2020

  • Includes COVID-19 scalability change.

8.11-1.0.7213

March 27, 2020

  • 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.7179

March 6, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7166

February 28, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7162

February 21, 2020

  • Fixed an issue in which some recurring meeting instances were removed from the Webex Teams meeting list if there were deleted occurrences in the series. This issue was introduced in BETA release 1.0.7079, but not released to the STABLE channel.

8.11-1.0.7100

February 6, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7079

January 25, 2020

  • No release notes for this maintenance upgrade.

8.11-1.0.7057

January 10, 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

December 20, 2019

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

8.11-1.0.7035

December 13, 2019

  • 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.7022

December 6, 2019

  • No release notes for this maintenance upgrade.

8.11-1.0.6252

November 14, 2019

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

8.11-1.0.6231

November 8, 2019

  • No release notes for this maintenance upgrade.

8.11-1.0.6185

October 26, 2019

  • No release notes for this maintenance upgrade.

8.11-1.0.6170

October 18, 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.

8.11-1.0.6162

October 11, 2019

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

8.11-1.0.6155

September 27, 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."

8.11-1.0.6114

September 13, 2019

  • 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 6, 2019

  • No release notes for this maintenance upgrade.

8.11-1.0.6078

August 30, 2019

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

8.11-1.0.6075

August 23, 2019

  • 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 1, 2019

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

8.10-1.0.5829

July 19, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.5817

July 12, 2019

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

8.10-1.0.5798—Urgent upgrade (will automatically upgrade within 24 hours, at the scheduled time)

June 25, 2019

  • Fixed an issue introduced in 8.10-1.0.5783 where scheduled meetings were not appearing on room systems.

8.10-1.0.5783—Urgent upgrade (will automatically upgrade within 24 hours, at the scheduled time)

June 19, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.5744

May 21, 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 10, 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 3, 2019

  • Performance optimizations.

8.10-1.0.5685

April 26, 2019

  • Performance optimizations.

8.10-1.0.5680

April 19, 2019

8.10-1.0.5666

April 12, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.5647

April 5, 2019

  • Updated @meet join details to support two join-by-phone toll numbers. If two toll numbers are configured in Webex, both should now show up in @meet invitations.

8.10-1.0.5609

March 22, 2019

  • 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 8, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.5533

January 18, 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.

8.10-1.0.5513

December 14, 2018

  • 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.

  • 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

November 30, 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—Urgent upgrade (will automatically upgrade within 24 hours, at the scheduled time)

October 10, 2018

8.10-1.0.5282

September 14, 2018

  • No release notes for this maintenance upgrade.

8.10-1.0.5279

September 7, 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

August 31, 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.5234

August 17, 2018

  • No release notes for this maintenance upgrade.

8.8-1.0.5219

August 10, 2018

  • 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.5201

August 3, 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.

8.8-1.0.5194

July 27, 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 17, 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.

8.8-1.0.5144

July 11, 2018

  • Rebranding updates for the user email notification template.

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

8.8-1.0.5100

June 22, 2018

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

8.8-1.0.5091

June 15, 2018

  • 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 8, 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 1, 2018

  • No release notes for this maintenance upgrade.

8.8-1.0.5037

May 24, 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.5012

May 18, 2018

  • No release notes for this maintenance upgrade.

8.8-1.0.5008

May 11, 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 4, 2018

  • No release notes for this maintenance upgrade.

8.8-1.0.4979

April 27, 2018

  • Added localized text translations for "Join using Microsoft Skype for Business" link to @webex meeting invitations.

  • 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.4963

April 20, 2018

  • Added "Join using Microsoft Skype for Business" link to @webex meeting invitations. This text currently only appears in English. Support for other languages will be released shortly.

8.8-1.0.4945

April 13, 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.

8.8-1.0.4942

April 6, 2018

  • 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 some cancelled meetings may still appear in the Cisco Spark meetings list.

  • 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.

8.8-1.0.4896

March 23, 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."

8.8-1.0.4811

February 16, 2018

  • 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.4786

February 9, 2018

  • No release notes for this maintenance upgrade.

8.8-1.0.4747

February 2, 2018

  • No release notes for this maintenance upgrade.

8.8-1.0.4724

January 26, 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.4704

January 20, 2018

  • No release notes for this maintenance upgrade.

8.8-1.0.4703

January 12, 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 5, 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.

8.8-1.0.4670

December 14, 2017

  • 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

November 24, 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 meetings 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 meetings list.

8.8-1.0.4636

November 17, 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.

  • Enhanced @spark group meeting invitations to include PSTN telephone numbers.

  • 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 10, 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 3, 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

October 27, 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 16, 2017

8.8-1.0.4467

October 13, 2017

  • 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 6, 2017

  • Logging and performance optimizations.

8.8-1.0.4429

September 29, 2017

  • Improved calendar subscription error handling.

  • Reduced the amount of connector logging on Expressway.

  • Performance optimizations.

8.8-1.0.4414

September 22, 2017

  • 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.4408

September 13, 2017

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

8.8-1.0.4402

September 5, 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.

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

8.8-1.0.4363

August 8, 2017

  • Fix to prevent Calendar Service from getting stuck in initializing state while in maintenance mode.

  • Performance optimizations.

8.8-1.0.4358

August 4, 2017

  • Added a fix for a calendar connector out-of-memory crash.

8.8-1.0.4354

July 27, 2017

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

8.8-1.0.4341

July 21, 2017

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

8.8-1.0.4331

July 14, 2017

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

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

  • 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 meetings 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.

8.8-1.0.4256

June 23, 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 meetings list and One Button To Push (OBTP) Trials sites.

  • For Cisco Spark meetings 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 19, 2017

  • 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.4080

May 1, 2017

  • The openJDK framework will be updated for upcoming signed connector support. The openJDK update on the beta channel is scheduled for Saturday night (May 13). Be aware that the calendar connector will restart after this update.

8.8-1.0.3994

April 10, 2017

  • The Cisco Spark space URL is now added to @spark invites that are scheduled directly between two people.

8.8-1.0.3984

April 7, 2017

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

8.8-1.0.3930

March 22, 2017

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

  • Minor bug fixes and enhancements

8.11-1.0.8131

November 20, 2020

  • Resolved Call Connector restarts by fixing the dependent library versions.

8.11-1.0.8098

August 21, 2020

  • Improved performance for Call Connector AXL caching.

8.11-1.0.8071

April 15, 2020

  • Fixed an intermittent issue where Call Connector failed to start.

  • Fixed CSCvq07214—"Apache Xerces-C XML Parser Library External DTD Paths Denial of Service Vulnerability"

8.10-1.0.7252

March 29, 2019

  • Fixed an issue where a remote destination (Webex SIP address) wasn't updated if a Place with Webex devices was renamed in Control Hub.

8.10-1.0.7240

March 14, 2019

  • Added enhancements to avoid consuming extra AXL sessions

  • Added the following error message:

    • Title—Failed to create the user's remote device

    • Message—Call Connector did not create a remote device for the user. Some required configuration is missing.

    • Resolution—Check the required user configuration on Unified CM as detailed in the Prepare and Deploy chapters in www.cisco.com/go/hybrid-services-call.

    Further troubleshooting details can be found in the deployment guide.

8.10-1.0.7224

February 7, 2019

  • As part of the upcoming changes to improve the deployability and reliability of Hybrid Call Service (announced here), we've removed CTI monitoring from the Call Connector.

  • Note the following impacts to Hybrid Call Service:

    • Removal of support for the instantly available screen share feature for Call Service Aware users.

    • Call history in the Webex Teams app may be incomplete or incorrect for calls that are placed or answered on a Connect user's deskphone.

8.10-1.0.7217

January 31, 2019

  • Enhanced an error message for when you enable Call Service Connect for Webex Devices in a place where the directory number in Unified CM has auto-answer enabled:

    • Title: Failed to Add Hybrid Call Service to Webex Devices in a Place

    • Description: Call Connector cannot create a Cisco Spark remote device in Unified CM because auto-answer is enabled on the directory number.

    • Solution: Disable auto-answer for the directory number in Unified CM. Then wait for the call connector to pick up changes or restart the connector.

  • Added an update so that Call Connector uses AXL to configure remote destinations on Unified CM.

8.10-1.0.7178

January 18, 2019

  • Added a new error message that appears when there are 15 or more characters in a device name for a Place with Hybrid Call Service.

8.11-1.0.321394

April 9, 2019

  • No release notes for this maintenance upgrade.

8.11-1.0.321369

March 25, 2019

  • No release notes for this maintenance upgrade.

8.11-1.0.321368

March 7, 2019

  • Works around an issue caused by uninstalling Java from Expressway when deregistering it from Cisco Webex.

  • (Second attempt) Fixed an issue where, in some cases, the Expressway interface incorrectly reported that connector software was not installed.

8.11-1.0.321365

February 25, 2019

  • Fixed an issue where, in some cases, the Expressway interface incorrectly reported that connector software was not installed.

8.10-1.0.321364

February 14, 2019

  • No release notes for this maintenance upgrade.

8.11-1.0.321362

February 7, 2019

  • Updates the branding of Cisco Collaboration cloud to Cisco Webex cloud.

  • Prepares for a new registration flow with future versions of Expressway.

8.10-1.0.321355

January 14, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.321352

November 16, 2018

  • No release notes for this maintenance upgrade.

8.10-1.0.321351

November 12, 2018

  • Reliability improvements.

8.10-1.0.321350

October 30, 2018

  • No release notes for this maintenance upgrade.

8.10-1.0.321349

September 4, 2018

  • No release notes for this maintenance upgrade.

8.10-1.0.321348

August 28, 2018

  • No release notes for this maintenance upgrade.

8.10-1.0.321345

July 27, 2018

  • The minimum supported version of Expressway is now X8.11 for new registrations and X8.10 for existing registrations. if your connector hosts are on an earlier version, you see an alarm indicating that you must upgrade to a supported version.

8.9-1.0.321344

July 4, 2018

  • Added a fix to address a situation where the connector crashed.

  • The Cisco Webex cloud now retrieves some configuration information with logs that it collects. We collect this information only for the purpose of helping to fix your system, and we remove all personally identifiable information and passwords before the data leaves the system.

8.9-1.0.321342

June 1, 2018

  • No release notes for this maintenance upgrade.

8.9-1.0.321341

May 29, 2018

  • Reworded some alarms to provide more detailed information (including actions).

8.9-1.0.321340

May 2, 2018

  • Updated terminology for Cisco Spark rebranding to Webex Teams.

8.9-1.0.321339

May 1, 2018

  • No release notes for this maintenance release.

8.9-1.0.321338

April 27, 2018

  • Removed unused CA-signed certificates

8.9-1.0.321333

March 28, 2018

  • On the connector pages, disabled the Save button for when the connector is not yet configured.

8.9-1.0.321331

March 9, 2018

  • Added an enhancement so that configuration files are included when you create a log snapshot to submit to Cisco.

8.9-1.0.321330

February 22, 2018

  • Added new connector operational statuses for the xStatus CLI command: operational, impaired, and outage.

8.9-1.0.321322

February 8, 2018

  • A prompt with a status spinner now appears while an Expressway is registering to the cloud. Registration can take up to 5 minutes depending on the configuration of the Expressway and whether it's a first-time registration.

8.9-1.0.321319

January 2, 2018

  • No release notes for this maintenance release.

8.9-1.0.321326

November 30, 2017

  • The alarm text "Contact your Cisco Collaboration Cloud administrator" was replaced with "If the error remains, use admin.ciscospark.com to open a case for further investigation"

8.9-1.0.321314

November 24, 2017

  • Added a new notification that indicates an Expressway version will soon be unsupported for hybrid services, and to plan to upgrade to the latest version.

8.9-1.0.321310

November 14, 2017

  • No release notes for this maintenance release.

8.9-1.0.321305

October 24, 2017

Added a link to Expressway Connector Host Support documentation. There, you can read about version support and how to download the latest Expressway software build.

8.9-1.0.321303

October 10, 2017

  • No release notes for this maintenance release.

8.9-1.0.321302

October 2, 2017

  • Updated the help links to redirect to the latest hybrid service documentation.

8.9-1.0.321299

September 21, 2017

  • No release notes for this maintenance update.

8.9-1.0.321292

August 10, 2017

  • Added confirmation dialog boxes when you roll back to a previous connector release.

8.9-1.0.321288

July 31, 2017

  • Minor bug fixes and enhancements.

8.9-1.0.321284

July 20, 2017

  • Added a local deregister confirmation before you remove a node from a hybrid services resource

  • Bug fixes

8.8-1.0.321279

July 7, 2017

  • Added button to deregister a node from a cluster when maintenance mode is enabled from the cloud and the node is removed from the Expressway cluster.

  • Added a confirmation step for the rollback feature

  • Added a step to download and install the latest version of management connector before registering with the cloud

8.8-1.0.321275

July 4, 2017

  • Fixed the issue where administrators received password reset emails.

8.8-1.0.321273

June 28, 2017

  • No release notes for this maintenance update.

8.8-1.0.321271

June 21, 2017

  • Minor bug fixes and enhancements.

8.8-1.0.321267

June 13, 2017

  • No release notes for this maintenance update.

8.8-1.0.321263

May 24, 2017

  • No release notes for this maintenance update.

8.8-1.0.321257

May 18, 2017

  • No release notes for this maintenance update.

8.8-1.0.321255

April 26, 2017

  • No release notes for this maintenance update.

8.8-1.0.321254

April 24, 2017

  • Fixed the issue where sending logs always showed an error message to the user

  • Support for maintenance mode

8.8-1.0.321252

April 20, 2017

  • Bug fixes

  • Improved wording on the upgrade alarm

8.8-1.0.321250

April 7, 2017

  • Alarms relating to crashes are no longer included in the connector status table on the hybrid services connector management page.

8.8-1.0.321248

March 30, 2017

  • Stability improvements.

8.8-1.0.321245

March 14, 2017

  • Minor bug fixes and enhancements.

8.8-1.0.321240

March 8, 2017

  • Added DigiCert root CA to the managed Hybrid Services certificates

  • Bug fixes and improvements.

8.8-1.0.321235

March 1, 2017

  • The Expressway now shows the certificates that the management connector added.

  • Bug fixes and improvements.

8.10-1.0.1275

November 9, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1262

October 27, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1252

October 19, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1249

October 13, 2020

  • Fixed an XCP session failure issue.

8.10-1.0.1227

October 5, 2020

  • Fixed an AXL status connectivity issue for multi server deployments.

  • Improvements around conversation quality.

  • Added new metrics for XCP sessions.

8.10-1.0.1214

September 28, 2020

  • Improvements around conversation quality.

8.10-1.0.1209

September 21, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1208

September 14, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1202

September 3, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1200

August 31, 2020

  • No release notes for this maintenance upgrade.

  • Fixes a connection issue at IM&P

8.10-1.0.1197

August 24, 2020

  • Fixes an issue when a user is moved between IMP clusters. Message Connector can detect this and will send the updated cluster information to the Webex Teams Cloud.

  • Logging enhancements.

8.10-1.0.1180

August 5, 2020

  • Logging improvements for XCP and JSM sessions.

  • Improvements around conversation quality.

8.10-1.0.1164

July 27, 2020

  • Logging enhancements.

8.10-1.0.1152

July 20, 2020

  • Improvements to message and presence logging.

8.10-1.0.1137

July 6, 2020

  • Logging improvement for AXL Audit, XCP and JSM sessions.

8.10-1.0.1098

June 11, 2020

  • Updated the Message Service Status information page to show AXL connectivity issues when the AXL connection is down.

8.10-1.0.1087

June 4, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1080

May 26, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1079

May 7, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1074

April 30, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1064

April 16, 2020

  • Fixes a customer issue with intermittent crash occurring after Message Connector upgrade.

8.10-1.0.1063

April 7, 2020

  • Updated the Message Service Status information page to show the new presence transition of 72 hours.

8.10-1.0.1062

April 2, 2020

  • The presence transition from Away to Offline is extended.

  • Further improvements to encryption health monitoring.

8.10-1.0.1059

March 26, 2020

  • Improves health monitoring around encryption.

8.10-1.0.1057

March 19, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1055

March 5, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1050

February 26, 2020

  • Improved fix for customer issue when retrieving encryption keys in a deployment that is fronted by a proxy.

8.10-1.0.1048

February 20, 2020

  • Updated fix for retrieving encryption keys in a deployment that is fronted by a proxy.

8.10-1.0.1046

February 12, 2020

  • Fixes a customer issue with retrieving encryption keys in a deployment that is fronted by a proxy.

  • Improves scheduled polling of IM&P servers.

  • Fixes a customer issue with Message Service connector heartbeat connection.

8.10-1.0.1033

January 27, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1029

January 17, 2020

  • No release notes for this maintenance upgrade.

8.10-1.0.1017

December 9, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.1016

November 25, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.1010

November 6, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.951

October 11, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.941

September 10, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.921

July 23, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.910

July 9, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.884

June 24, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.876

June 6, 2019

  • New alarm for failure to send messages from Teams to Jabber.

8.10-1.0.862

May 24, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.860

May 22, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.832

May 3, 2019

  • The presence of a Hybrid Message Service user, as seen from Jabber, now indicates that the user is "@ Cisco Webex Teams" as well as the usual amber or green dot. The extra text does not show when the presence overlay is red (do not disturb).

  • Continued preparation for next phase of Data Locality feature.

8.10-1.0.829

April 26, 2019

  • New alarm for failure to send messages from Jabber to Teams.

  • User assignment improvements.

8.10-1.0.824

April 15, 2019

  • Extends presence mapping from Teams to Jabber. If a user manually sets "Do Not Disturb" in Teams, their Jabber presence automatically updates to the same state within 10 minutes.

  • Prepares Message Connector for the next phase of the Webex Teams Data Locality feature.

8.10-1.0.815

April 5, 2019

  • No release notes for this maintenance upgrade.

8.10-1.0.807

March 29, 2019

  • New alarm if unsupported IM and Presence Service version is detected.

  • Serviceability improvements.

8.10-1.0.793

March 22, 2019

  • Fixes an issue with Message Connector status logic.

8.10-1.0.781

March 15, 2019

  • Fixes an issue that prevents the connector from discovering users from the IM and Presence publisher. This issue manifests as alarm ID 60612 on previous Message Connector versions.

8.10-1.0.780

March 14, 2019

  • Fixes an issue where connector status was reported as "initializing" when no users were provisioned.

  • Fixes an issue where the XMPP connection may drop.

8.10-1.0.776

March 12, 2019

  • Enhances logging for presence changes.

  • Improves security.

8.10-1.0.771

March 7, 2019

  • Prepares Message Connector for the first phase of the forthcoming Data Locality feature of Cisco Webex Teams.

8.10-1.0.751

March 1, 2019

  • Improves performance by refactoring presence update code.

  • Retries connection on HTTP error 503 Service Unavailable from Webex.

8.10-1.0.747

February 27, 2019

  • Adds filtering by module name "hybridservices.messageconnector", to help diagnose Message Connector issues on the host Expressway.

  • Improves security.

8.10-1.0.743

February 26, 2019

  • Fixes potential issue with messaging from Teams to Jabber for some conversations.

  • Fixes an issue with unexpected logging at connector startup.

8.10-1.0.739

February 22, 2019

  • Fixes a JSON parsing race condition discovered by internal testing.

  • Enhances logging.

  • Fixes a customer found issue with user assignment.

  • Improves security.

  • Improves error handling.

8.10-1.0.718

February 15, 2019

  • Connector logging enhancements.

8.10-1.0.700

February 4, 2019

  • A new alarm for AXL syntax errors in connections with IM and Presence nodes.

8.10-1.0.688

January 31, 2019

  • Fix an issue with Teams to Jabber message failures, caused by deleted IM and Presence sessions.

8.10-1.0.680

January 23, 2019

  • Add metrics on inbound messaging link from Webex Teams.

8.10-1.0.667

January 21, 2019

  • Update the Webex Teams USS client library.

  • Fix an issue with reconnecting to Webex Teams after interrupted connection.

  • Add capability to user audit, to recreate a user's XMPP session if it is required but does not exist.

  • Improve scalability by reducing AXL polling and user auditing during failover/fallback events on IM and Presence nodes.

  • Increase user auditing speed by preventing unnecessary session assignments.

  • Show users in error state in Control Hub if their Mail ID is duplicated on IM and Presence clusters.

8.10-1.0.665

January 16, 2019

  • Reduce frequency of Key Management System (KMS) requests to improve performance.

  • Make communications with KMS more robust.

  • Improve error handling for connections that are attempted to unresolved IM and Presence hosts.

  • Optimize connector tasks to improve performance and reduce recovery time.

  • Improve quality metric by checking that Control Hub organization exists for entitled users.

  • Improve user session creation.

8.10-1.0.630

December 11, 2018

  • No release notes for this maintenance upgrade.

8.10-1.0.623

November 30, 2018

  • Increased speed of user discovery.

  • Fixed AXL timeout issue that occurred when connecting Hybrid Message Connector to Unified CM IM and Presence.

  • Fixed issue with Message Connector sending null cluster id to the Cisco Webex cloud.

8.10-1.0.598

November 14, 2018

  • Fixed intermittent issue of AXL alarms persisting when they should clear.

  • Improved high availability of Message Service by enabling the connector to respond to automatic failover of IM and Presence nodes.

  • Decreased timeout on the AXL connection to Unified CM IM and Presence.

8.10-1.0.593

November 9, 2018

Message Connector - enables messaging interop between Jabber and Webex Teams. Answer your instant 1-1 messages from Webex Teams or Jabber!

c_serab_8.11-1.626

March 11, 2019

No release notes for this maintenance upgrade.

c_serab_8.11-1.611

February 20, 2019

Removes a previously documented limitation on the maximum number of managed devices. The limitation was previously approximately 15 devices, and we now support up to 150 managed devices per Serviceability Connector.

c_serab_8.11-1.576

January 21, 2019

No release notes for this maintenance upgrade.

c_serab_8.11-1.573

January 16, 2019

This is the first release of the Serviceability Connector.

This connector increases the speed with which Cisco technical assistance staff can diagnose issues with your infrastructure. It automates the tasks of finding, retrieving and storing diagnostic logs and information into a Service Request (SR), and triggering analysis against diagnostic signatures so that TAC can more efficiently identify and resolve issues with your on-premises equipment.

The Serviceability Connector is a small piece of software hosted on an Expressway in your network ('connector host'). It receives TAC-initiated requests via Cisco Webex, and uses the APIs of your on-premises equipment to collect the requested data. It then securely uploads the requested data to the SR file store, where it is attached to your Service Request.

Managed Devices

Serviceability Connector can work with the following devices:

  • Cisco Unified Communications Manager

  • Cisco Unified CM IM and Presence Service

  • Cisco Expressway Series

  • Cisco TelePresence Video Communication Server (VCS)

Related Reading

1 THE BETA RELEASE IS PROVIDED "AS IS". CISCO DISCLAIMS ANY WARRANTIES IN CONNECTION WITH THE BETA RELEASE, WHETHER EXPRESS, IMPLIED, OR STATUTORY. CISCO SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE.