Water Mark

Known Issues and Limitations for the Webex Meetings Desktop Application

view(s) people thought this was helpful

Mac Outlook Plugin in the Cisco Webex Desktop App Requires Upgrade to Version 39.5.1

The Webex Mac Outlook plugin doesn’t recognize Webex meetings in Mac Outlook 16.23 or later for Microsoft Office 365, with the controls still showing Add Webex Meeting when users open an appointment and try to edit it.

To restore this interoperability between the Webex Mac Outlook plugin and Windows Outlook plugin, you must upgrade your Webex Outlook plugin to WBS39.5.1 or later.

For these changes:

  • The site administrator must check Automatically link users with this Webex site if their Webex account email address matches their Microsoft Office 365 email address in the Cisco Webex Site Administration’s Configuration > Common Site Settings > Third-Party Integration.

  • The administrator must authorize Webex access to Microsoft Office 365 in Webex Site Administration. Select Add New Authorization to start the process.

  • For more information on deploying and configuring the Cisco Webex Meetings Scheduler for Microsoft Office 365, see Deploy and Configure the Cisco Webex Meetings Scheduler for Microsoft Office 365.

  • Ensure the email address that's used in Webex is the same as Office 365 account, and that the email address is verified in Webex.

For more information on email verification, see:

Known Issues with the Webex Outlook plugin WBS39.5.1

  • Interop issue on Personal Room meeting: The Webex Personal Room meeting information can't be deleted when selecting Cancel Webex Meeting in Mac Outlook if the meeting is created or updated by the Webex Outlook plugin for windows. A workaround for this is to cancel the Outlook appointment.

  • Interop issue on PCN meeting: The button still shows Add Webex Meeting when users open the appointment in Mac Outlook if the meeting is created or updated by Webex Windows Outlook plugin. There’s no workaround.

  • Schedule on behalf of the issue on MAC outlook version 16.25(19051201): A Mac Outlook defect is identified and it impacts the Webex Scheduler. This Outlook defect was fixed in the Microsoft Office slow channel 16.26 (19053000) and Microsoft Office fast channel 16.27(19060500). This defect is that when an assistant opens another person’s calendar, and tries to create an appointment for that person, the appointment is created for the assistant. The workaround is to upgrade to Mac Outlook 16.26 or later.

Dependencies

Sites that have upgraded to the new Webex Mac Outlook plugin 39.5.1, but don't meet the preconditions receive an error message when trying to update or edit a Webex meeting.

Backward compatibility

This new version doesn’t fix previous meetings that were scheduled by the old Webex Windows or Mac Outlook plugins. The same error message appears when users try to update or edit a Webex meeting.

Notes

  • Cisco Webex is redirecting the primary service to GSB for this change.

  • Without this upgrade, users are unable create and update Webex meetings using the Webex Mac Outlook plugin.

  • Sites receive this update automatically only if the Auto Update is enabled.

General Cisco Webex Meetings Desktop App Known Issues and Limitations

  • After the Webex desktop app is installed, there are two items in the Windows application list. Selecting either for uninstallation removes both of them.

  • After users start a meeting from desktop app, there are two Webex icons on the task bar. These will be merged later.

  • The user interface display may appear distorted after DPI is change on Microsoft Windows. To correct it, sign out of Windows and sign in again.

  • Scheduling in Microsoft Outlook with an account set up from Google Calendar isn’t supported.

  • The desktop app can only read the meeting list when Microsoft Outlook is installed and logged in. Mac users must configure their Outlook account email address and password the first time they use the application.

  • For Windows 7 and Outlook 2016 users, the desktop app may not be able to scrape the meeting list from the Outlook calendar because Windows 7 doesn’t have some library files that Outlook 2016 needs. See the Microsoft website to download the Visual C++ Redistributable Packages. Windows 7 and Outlook 2013 don’t have this issue.

  • Windows users may receive a MAPI error when the desktop app attempts to read the meeting list from the Outlook calendar. Exit the Outlook application and restart.

  • When users try to start or join Webex meetings which require authentication on a different site, the meeting application will redirect user to the browser first. Cisco Webex Events and Cisco Webex Training users are also redirected to the browser first.

  • When users try to join a meeting on a Webex site which is different from the site that signed in through the desktop app, the start and join flows are redirected to the browser first instead of launching the Webex Meetings application.

  • The proximity pairing function of the desktop app only uses exclusive mode to try to pair with Cisco video devices when users click Connect to a Device on Windows. This means that other applications running in exclusive mode blocks or impact the pairing.

  • The proximity pairing function may not work on Windows if the setting Enable Audio Enhancements is enabled. To prevent this, follow these steps:

    From the Recording tab of your Windows Sound configuration screen, select Properties, then disable (uncheck) Enable audio enhancements.

  • If a PC has multiple screens, only the content on the main screen is shared to the paired Cisco video devices.

  • If the PC has a headset that's plugged in, Cisco video devices won't be detected through proximity.

  • When the endpoint is paired with desktop app, "Share On Device" means project your desktop to the video system screen wirelessly without Webex Meetings.

Mac Outlook Plugin in the Cisco Webex Desktop Application Requires Upgrade to Version 39.5.1

The Webex Mac Outlook plugin doesn’t recognize Webex meetings in Mac Outlook 16.23 or later for Microsoft Office 365, with the controls still showing Add Webex Meeting when users open an appointment and try to edit it.

To restore this interoperability between the Webex Mac Outlook plugin and Windows Outlook plugin, you must upgrade your Webex Outlook plugin to WBS39.5.1 or later.

For these changes:

  • The site administrator must check Automatically link users with this Webex site if their Webex account email address matches their Microsoft Office 365 email address in the Cisco Webex Site Administration’s Configuration > Common Site Settings > Third-Party Integration.

  • The administrator must authorize Webex access to Microsoft Office 365 in Webex Site Administration. Select Add New Authorization to start the process.

  • For more information on deploying and configuring the Cisco Webex Meetings Scheduler for Microsoft Office 365, see Deploy and Configure the Cisco Webex Meetings Scheduler for Microsoft Office 365.

  • Ensure the email address that's used in Webex is the same as Office 365 account, and that the email address is verified in Webex.

For more information on email verification, see:

Known Issues with the Webex Outlook plugin WBS39.5.1

  • Interop issue on Personal Room meeting: The Webex Personal Room meeting information can't be deleted when selecting Cancel Webex Meeting in Mac Outlook if the meeting is created or updated by the Webex Outlook plugin for windows. A workaround for this is to cancel the Outlook appointment.

  • Interop issue on PCN meeting: The button still shows Add Webex Meeting when users open the appointment in Mac Outlook if the meeting is created or updated by Webex Windows Outlook plugin. There is no workaround.

  • Schedule on behalf of the issue on MAC outlook version 16.25(19051201): A Mac Outlook defect is identified and it will impact the Webex Scheduler. This Outlook defect was fixed in the Microsoft Office slow channel 16.26 (19053000) and Microsoft Office fast channel 16.27(19060500). This defect is that when an assistant opens another person’s calendar, and tries to create an appointment for that person, the appointment is created for the assistant. The workaround is to upgrade to Mac Outlook 16.26 or later.

Dependencies

Sites that have upgraded to the new Webex Mac Outlook plugin 39.5.1, but don't meet the preconditions will receive an error message when trying to update or edit a Webex meeting.

Backward compatibility

This new version doesn’t fix previous meetings that were scheduled by the old Webex Windows or Mac Outlook plugins. The same error message appears when users try to update or edit a Webex meeting.

Notes

  • Cisco Webex is redirecting the primary service to GSB for this change.

  • Without this upgrade, users are unable create and update Webex meetings using the Webex Mac Outlook plugin.

  • Sites will receive this update automatically only if the Auto Update is enabled.

Windows and Mac

The issues noted here affect all Webex services unless indicated otherwise.

Known interoperability issues between Windows and Mac

If a meeting series has exceptions that were scheduled or updated with the Windows version of the desktop app, Mac desktop app users can't update the meeting series.

Any meeting that is scheduled or updated with the Windows version of the desktop app can’t be canceled with the Mac version of the desktop app.

Lockdown

The desktop app doesn’t support to lockdown to a specific version once automatic upgrading is enabled.

Some customers may stay on a specific desktop app version by disabling the automatic upgrade option. However, Cisco may ask all desktop app users to upgrade to a minimum version if security compliance is necessary. This is an option that can be enabled by Cisco administrators.

Missing meeting links

The meeting link doesn't appear when opening an ICS invitation in a Windows text editor if the meeting was scheduled using the desktop app for Mac. This is a known issue acknowledged by Microsoft.

Windows

The issues noted here affect all Webex services unless indicated otherwise.

Address button on the desktop app panel

On the desktop app panel, the address button that allows you to select email addresses from your Microsoft Outlook address book isn't supported for the 64-bit version of Microsoft Outlook.

Cross-platform support

The desktop app available for the Microsoft Windows and Mac platforms only. Linux, Unix, and Solaris platforms aren't supported.

Customized email templates

A site administrator can customize Microsoft Lync links in the email templates Invitation to a Meeting in Progress_PR(Productivity Tools) and MC MeetingInfo For Attendee(Productivity Tools). The customized link is available for all users, so the link is invalid in invitations sent by users without Webex Video Conferencing. The site administrator should be aware of this and should add a reference when customizing the templates.

If a site administrator customizes host and attendee email templates to be the same, only attendee versions are sent to hosts and attendees.

%MeetingDate% isn't a supported parameter when scheduling Personal Room meetings from the desktop app.

Email invitation templates

  • Attendee version only (without host information)

  • Host and attendee email versions both sent out

If a site has video device-enabled meetings enabled, only one email invitation template is available. Attendee versions don't contain host information like the host key and access code.

The Mac version of the desktop app still uses a single email template. If a Mac user edits meetings that were created on the Webex Productivity Tools version WBS29.13 or later for Windows, a new template is generated. The content's based on the unified email template for hosts and attendees.

Sometimes, if a host forwards a Webex meeting invitation, an attendee email is sent instead.

Hosts can cancel an individual meeting that's an exception to a series and then edit that meeting series. Sometimes, the cancellation notice to attendees would actually contain updated information for the updated meeting series.

If a host creates a video device-enabled meeting series, changes an occurrence, and then updates the series to Webex meetings, the exception email changes to plain text.

The desktop app doesn't support the %MeetingDate% parameter in the invitation email body. The meeting date and time is handled by the calendar system.

IBM Lotus Notes integration

If a user has IBM Lotus Notes as the default email application opens the desktop app, enters an email address of an invitee, and then selects Meet Now, the meeting invitation that's sent to that invitee is empty and doesn't include any meeting information.

Adding HTML content in the Webex calendar invitation results in an error in IBM Lotus Notes version 8.5.

Lotus Notes can only display plain text content of iCalendar mail. Formatting that's done in HTML isn't supported.

The IBM Lotus Notes integration supports only limited rich text format features, such as hyperlinks and images.

It isn't possible to specify TSP telephony while scheduling a Webex meeting using the IBM Lotus Notes integration.

The IBM Lotus Notes integration requires a script to be inserted on the Domino database for each user. As a result, a user with editor privileges can't install the IBM Lotus Notes integration by just running an MSI available from the Support page. For an IBM Lotus Notes user with editor privileges, a Domino administrator must insert a Webex script into the IBM Lotus Notes database using the administrator tool.

Using the IBM Lotus Notes integration MSI file, only an IBM Lotus Notes user with manager or designer privileges can install the Integration.

If a single occurrence of a recurring Webex meeting is deleted or rescheduled, the meeting information isn't updated on the Webex site. The host's and attendees' IBM Lotus Notes calendars, however, display the meeting correctly.

When a recurring Webex meeting is scheduled to recur on alternate weeks in an IBM Lotus Notes calendar, the recurring meeting appears to be scheduled on the Webex service site as occurring weekly instead. The host's and attendees' IBM Lotus Notes calendars, however, display the meeting correctly.

Attendee registration can't be enabled for recurring Webex meetings scheduled using the IBM Lotus Notes integration.

If an email template has the Mute on Entry option enabled, users still hear a sound as attendees join the meeting.

If IBM Lotus Notes is using a different time zone compared to the one on the Webex site, a meeting that's scheduled with the IBM Lotus Notes integration don't appear correctly on the Webex site. On the host's and attendees' IBM Lotus Notes calendars, the time zones for the meeting still appears correctly.

Since Lotus Notes Integration doesn't use an email template, it isn't possible to configure the content of the host's and attendees' email invitations for Webex meetings that are scheduled using the IBM Lotus Notes integration.

Webex events that are scheduled with the IBM Lotus Notes integration has the following limitations:

  • Hosts can't assign a program.

  • Hosts can't assign multiple time zones to an event.

  • Hosts can't add event options like uploading a host or presenter's image, uploading event material, or UCF auto play options.

  • Hosts can't add presenters and panelists.

  • Hosts can't edit email template options for an event.

  • The option to join a meeting before the host isn’t available for recurring events.

Webex training sessions that are scheduled with the IBM Lotus Notes integration has the following limitations:

  • Hosts can't specify Listed for authorized users only.

  • Hosts can't reserve Hands-on Lab computers.

  • Hosts can't specify a registration close date or maximum number of registrations.

  • Hosts can't invite attendees as presenters into the training session.

  • Hosts can't assign attendee privileges.

  • Hosts can't edit the type of email messages to want to send when different training sessions happen.

  • Hosts can't tests and course material.

  • The option to join a meeting before the host isn't available for recurring training sessions.

If a user schedules a meeting using IBM Lotus Notes and then changes the meeting on their Webex site, the changes don't appear in IBM Lotus Notes.

If a user selects multiple meetings in IBM Lotus Notes and then deletes or moves them at the same time, those changes don't appear on their Webex site.

If a user schedules a new meeting in IBM Lotus Notes by copying an existing meeting, a new meeting isn't created on their Webex site. Instead, the same Webex meeting link is shown on the original and is copied with the meeting.

The attendee access code isn't displayed for conferences scheduled with the IBM Lotus Notes integration.

If a host edits an already-scheduled meeting and adds an attendee, the attendee information isn't posted to the Webex site site. As a result, for such attendees, this meeting doesn't appear in the My Meetings list.

Installation privilege errors

If a user manually installs the desktop app using an MSI package, the user must have Windows administration privileges to complete the installation.

If an IT user mass deploys the desktop app using MSI packages, the IT user must have Windows administration privileges to complete the installation.

Windows administration privileges are mandatory for automatically upgrading the desktop app.

Microsoft Outlook integration

The desktop app doesn't support having more than one version of Microsoft Outlook installed on the same device.

Attendee registration can't be enabled for recurring Webex meetings scheduled using the Microsoft Outlook integration.

If an email template has the Mute on Entry option enabled, users still hear a sound as attendees join the meeting.

If Microsoft Outlook is using a different time zone compared to the one on the Webex site, a meeting that's scheduled with the Microsoft Outlook integration don't appear correctly on the Webex site. On the host's and attendees' Microsoft Outlook calendars, the time zones for the meeting still appears correctly.

If a host schedules a meeting using Microsoft Outlook and then changes the meeting information on the Webex site, the changes don't appear in Microsoft Outlook.

If a user selects multiple meetings in Microsoft Outlook and deletes or moves them at the same time, the changes don't appear on the Webex site.

If a host schedules a new meeting in Microsoft Outlook by copying an existing meeting, a new meeting isn't created on the Webex site. Instead, the same link is shown on both the original and copied meeting.

The attendee access code isn't displayed for audio conferences scheduled using the Microsoft Outlook integration.

Importing a company address book into the Webex contacts isn't supported with the 64-bit version of Microsoft Outlook 2010.

You can't edit a meeting that's in progress.

The settings in the Scheduled Meetings tab aren't used- the default settings from the Webex site meeting template are used instead. Users can still leverage the settings that are set while scheduling the meeting in Microsoft Outlook.

Webex events that are scheduled with the Microsoft Outlook integration has the following limitations:

  • Hosts can't assign a program.

  • Hosts can't assign multiple time zones to an event.

  • Hosts can't add event options like uploading a host or presenter's image, uploading event material, or UCF auto play options.

  • Hosts can't add presenters and panelists.

  • Hosts can't edit email template options for an event.

  • The option to join a meeting before the host isn’t available for recurring events.

Webex training sessions that are scheduled with the Microsoft Outlook integration has the following limitations:

  • Hosts can't specify Listed for authorized users only.

  • Hosts can't reserve Hands-on Lab computers.

  • Hosts can't specify a registration close date or maximum number of registrations.

  • Hosts can't invite attendees as presenters into the training session.

  • Hosts can't assign attendee privileges.

  • Hosts can't edit the type of email messages to want to send when different training sessions happen.

  • Hosts can't tests and course material.

  • The option to join a meeting before the host isn't available for recurring training sessions.

Sometimes scheduled meeting information isn't included in the body of the email. This may be due to Microsoft Word settings that prevent web pages from being displayed in Microsoft Outlook for Windows. As a workaround, users on Microsoft Word can go to File > Options > Trust Center > Trust Center Setting > File Block Settings. Then, in the Open column, disable Web Pages.

Links generated by the desktop app and recording services

As part of our updates to improve security, Cisco is making changes to improve the management of cryptographic keys used to generate URLs used across Webex services. As a result, existing links have been updated. Some users may need to request new links.

Mass uninstallation

Mass deploying the desktop app requires the mass uninstallation of the previously installed version. For users who have multiple versions of the desktop app installed, please see the IT Administrator Guide for Mass Deployment of Webex Productivity Tools.

Microsoft Lync 2013

Microsoft Lync 2013 doesn't allow the desktop app to change a user's status.

Embedding the Webex menu item into the right-click menu also isn't supported.

Microsoft Outlook support

Although the Webex Meetings desktop app supports Microsoft Outlook 2016 as of version WBS29.13.70, the desktop app supports only one email invitation template for meetings. The email template that's supported is the attendee version that doesn't contain the host key and access code. Similar to the Mac experience, hosts can view their host key or access code by signing in to their Webex site when joining their meeting.

The desktop app for Microsoft Outlook 2013 and earlier supports two email invitation templates. One template is for attendees, and the other which includes the host key and access codes for hosts. The Mac version of the desktop app has always supported only one email template for all supported versions of Microsoft Outlook.


Users with Webex Productivity Tools with Microsoft Outlook 2016 should install the latest version of the desktop application. Changes in Microsoft Outlook 2016 cause the older version of Productivity Tools to send the host email invitation template to attendees.

Hosts can use Microsoft Outlook to edit meetings created with supported versions of Microsoft Outlook in Webex Productivity Tools. A new email template is generated based on the unified email template for hosts and attendees.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2013. However, the email invitation shows Webex information for the original meeting and edited meetings.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2013. The user editing the meeting receives a message that Webex Meetings can't locate the meeting because it's being edited. Selecting OK or Cancel updates the meeting with incorrect information.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2007. The user editing the meeting receives a message that they don't have the appropriate permissions to edit and save the meeting.

Hosts can create recurring Webex meetings in Microsoft Outlook 2016 for Mac, change one occurrence, and then cancel the Webex portion of the meeting. However, the appointment can't be canceled in Microsoft Outlook 2016 for Windows if the calendars are in different time zones. Even if the email body is updated, the appointment can't be canceled.

Recurring meetings

If a user cancels a Webex recurring meeting in Microsoft Outlook that has an exception, and the user is using the Microsoft Exchange server version 2013 or later, the Webex information isn't completely removed from the cancelation email notification.

In Microsoft Outlook 2013 (15.0.4823.1000), updating a meeting series overwrites the email message of exception meetings.

Meeting times aren't displayed correctly in email invitations for a meeting series. This is because the %MeetingDate% parameter isn't supported. We recommend that you don't add this parameter to display the meeting date when customizing email templates.

Silent installation or mass deployment of the desktop app

If an administrator performs a silent installation or mass deployment of the desktop app, users can't edit any of the settings on the Tools panel. Performing a silent installation may cause some settings on the desktop app page of Webex Site Administration to be ignored.

For administrators who mass installed the desktop app and are trying to upgrade to a new version, we recommend that you perform a silent uninstallation first.

In some silent upgrade cases, the version of the desktop app on the control panel is reflected incorrectly. This problem doesn't impact features and should be fixed in a future update.

For more information about deploying the desktop app, see the IT Administrator Guide for Mass Deployment of Webex Productivity Tools.

Video call-in port setting for video device-enabled meetings

If a site administrator reduces the default video call-in number from ten to five, all scheduled video device-enabled meetings can still be updated.

Video device-enabled (Webex-enabled TelePresence) integration issues

For video device-enabled meetings, email templates are only supported in English only on Windows and Mac devices.

  • Scheduling video device-enabled meetings

    If an administrator turned on the TelePresence integration for a Webex site, users can schedule video device-enabled (Webex-enabled TelePresence) meetings with Microsoft Outlook for Windows. This option is only available for sites with TelePresence integration turned on. Once this option has been turned on, users may have to upgrade their desktop apps and restart Microsoft Outlook. The Allow people to join using Webex option in the Meeting Options dialog for video device-enabled meetings doesn't stay enabled if it was for a previous meeting. To allow users to join using Webex, this option must be enabled every meeting.

    Hosts who have video device-enabled meetings enabled but don't have the Webex setting in their Cisco TelePresence Management Suite (Cisco TMS) can't schedule TelePresence-only meetings with the desktop app.

  • Adding resources

    When users schedule a Webex meeting with Microsoft Outlook, if they add TelePresence rooms or extra video call-in participants, a Webex-enabled TelePresence meeting is automatically scheduled. If they don't include these resources, the meeting is a Webex-only meeting. Status indicators show that a TelePresence meeting was booked if these resources were added.

  • Email invitation templates for CMR Hybrid meetings

    CMR Hybrid meetings still only support one email invitation template, which is the attendee version that doesn't contain the host key and access codes. To view the host key and host access code, video device-enabled meeting hosts must sign in to their Webex site to see the Meeting Details Page. They can also sign in to their site on through the desktop app to view the information in their Advanced Webex Settings dialog.

    The desktop app for video device-enabled meetings doesn't support sending HTML email invitations. The email invitations are only available in plain text format.

    The desktop app email templates for video device-enabled meetings don't contain the %ConfCallParticipant% variable, so audio-only callers can join the audio conference from a mobile device. Instead, mobile device users can select the Join Webex meeting link or URL in their invitation, and join the meeting using the Webex Meetings mobile app. Users can also pick up or manually dial the call-in number and meeting ID number or access code in the invitation from their mobile device.

  • Time zone and Daylight Savings Time

    The time zone for a Webex site must match the time zone for the Cisco TMS; otherwise the meeting time isn't synchronized. When Daylight Savings Time changes are made between a Webex site and the Cisco TMS, it's possible that meetings might be an hour off schedule. If this happens, rescheduling is required. If this problem occurs with a meeting series where some instances occur before Daylight Savings Times begins and some occur after, we recommended that hosts create two meeting series: one meeting series that ends before the Daylight Savings Time begins and a second meeting series that starts after Daylight Savings Time begins.

  • Cisco Unified MeetingPlace Audio

    The desktop app that supports the Webex integration with Cisco TelePresence doesn't support Cisco Unified MeetingPlace Audio. Users with Cisco Unified MeetingPlace and the desktop app installed who want to schedule a combined Webex and TelePresence meeting with Webex or TSP audio, must use the Smart Scheduler in the Cisco TMS. A user can't have two versions of the desktop app installed at the same time.

  • Telephony service provider (TSP) audio

    For some TSP audio accounts, if a host with a TSP account schedules two adjacent video device-enabled or Webex video conferencing meetings, with the second one scheduled to start immediately after the first one ends, and if the TelePresence scheduling system automatically extends the first meeting past the scheduled end, the second meeting will end automatically because the host because the same TSP audio account can’t be used for both meetings at the same time. To work around this problem, hosts can set up two different TSP audio accounts with different host access codes, and use one account for the first meeting and the other account for the second meeting. Another option is the administrator to turn off the option for the TelePresence systems to automatically extend the meeting.

  • Support for Microsoft Office 365, Microsoft Outlook 2010, and Windows 8 and 8.1

    Webex sites that have the video device-enabled meetings enabled may require the latest versions of the Cisco TMS and Cisco TMSXE to support Microsoft Office 365, Microsoft Outlook 2010, or Windows 8 and 8.1. For more information, go to Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide > Cisco Webex Features and Important Notes > Prerequisites on the Cisco TelePresence Management Suite (TMS) Configuration Guides page.

  • Instant Meetings and Personal Room meetings

    Users can't start instant video device-enabled meetings; only schedule them. When users start instant meetings, they are Webex-only meetings and don't include TelePresence integration.

    Instant meetings that started with the Meet Now command are held in Personal Rooms by default. This option can be changed in a user's Preferences. In order to have a Personal Room meeting that users can join from a video conferencing system or app, the Webex site and host account must be enabled for it.

    A workaround for an instant meeting that uses both Webex and TelePresence is to start a meeting from a TelePresence system and then the named host has selects Instant Webex Meeting on the meeting detail page to generate a URL that allows external participants to join the TelePresence meeting from a desktop or mobile app.

  • Scheduling Webex-only or TelePresence-only meetings

    Webex sites that have video device-enabled meetings enabled require Cisco TMSXE in order for users to schedule Webex-only or TelePresence-only meetings with the desktop app.

  • Maximum of two simultaneous meetings per host

    Webex sites that have video device-enabled meetings enabled can't have a host have more than two meetings started at the same time.

  • Personal and audio conferences

    Although a video device-enabled meeting user can schedule a Personal Conference meeting for sites that have Webex Audio or an audio conference for sites that have TSP audio, it's a Webex-only meeting type and doesn't include video device-enabled meetings.

  • No branding or customizing of video device-enabled meeting features

    Site administrators can't change the branding for the video device-enabled meeting Options panel, hide info, and can't limit the number of video call-in participants that users can enter.

Webex One-Click, instant messenger, and Microsoft Office integrations

If users use personalized join links to automatically populate attendee names and email addresses on the Join Meeting page, some email gateways may truncate the links. Attendees can still click the links, but the links don't automatically allow them to join the meeting. Instead, they must enter their name and email address before joining the meeting. There’s no current known workarounds.

If the instant messenger integration was installed using a silent installer, users must restart their instant messenger to see the desktop app integration features.

Webex site URL change

If a user signs in to the desktop app with a new Webex site URL after the site was renamed, they can't edit the meetings that were scheduled with the previous URL.

Mac

The issues noted here affect all Webex services unless indicated otherwise.

Installation privilege errors

Users manually installing the desktop app using a DMG package must have iOS administration privileges.

iOS administration privileges are mandatory to automatically upgrade the desktop app.

Mass deployment of the desktop app isn't supported on the Mac.

Microsoft Outlook support

The desktop app for Mac doesn't support Microsoft Insider preview versions.

Hosts can create recurring Webex meetings in Microsoft Outlook 2016 for Mac, change one occurrence, and then cancel the Webex portion of the meeting. However, the appointment can't be canceled in Microsoft Outlook 2016 for Windows if the calendars are in different time zones. Even if the email body is updated, the appointment can't be canceled.

The desktop app support having more than one version of Microsoft Outlook installed on the same computer.

Meetings from Webex Meetings server aren't supported.

Some known issues may occur with the desktop app using Microsoft Exchange Server 2007 and Microsoft Outlook for Mac.

If a user is updating the Webex meeting on the Outlook calendar view instead of the editing window of the occurrence, some issues occur because some Microsoft Outlook behaviors aren't under the desktop app's control in the calendar view.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2013. However, the email invitation shows Webex information for the original meeting and edited meetings.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2013. The user editing the meeting receives a message that Webex Meetings can't locate the meeting because it's being edited. Selecting OK or Cancel updates the meeting with incorrect information.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2007. The user editing the meeting receives a message that they don't have the appropriate permissions to edit and save the meeting.

Meeting times aren't displayed correctly in email invitations for a meeting series. This is because the %MeetingDate% parameter isn't supported. We recommend that hosts don't add this parameter to display the meeting date when customizing email templates.

In Microsoft Outlook 2016, an exception meeting opens when a user right-clicks an exception and selects Open > Open Series.

Cisco TelePresence Management Suite (TMS) sign in window

If the TMS sign in window doesn't appear after upgrading to the latest version of the desktop app, restart the device.

Default meeting templates

If the First attendee to join will be presenter option is enabled in Webex Site Administration, this option is enabled by default in a Webex site's meeting scheduler. The setting is also be enabled in the default meeting template that's used by the desktop app for scheduling Webex meetings. Custom meeting templates that have been created by users aren't be impacted. If a host schedules meetings with custom templates and wants the first attendee to become the presenter, the host must manually enable the setting.

IBM Lotus Notes integration

IBM Lotus Notes isn't supported in the desktop app.

Sign in and sign out processes

Sometimes, the desktop app might redirect a user to their Webex site to sign in again and change their password.

The desktop app supports enterprise single sign-on users; however, because there’s no single sign-out service from the enterprise site, users can only switch their account when the single sign-on token has expired.

Before single sign-on users first sign in to the desktop app, they must go to the Webex site to accept the site certification manually with Safari.

Video device-enabled meeting issues

For video device-enabled meetings, email templates are supported in English only.

The same issues that exist for the Webex-enabled TelePresence integration (CMR Hybrid) for the Windows version of the Desktop Application also apply to the Mac version. For more information about these issues, see CMR Hybrid (Webex-enabled TelePresence) integration issues in Known Issues/Limitations for Windows.

If a host using the desktop app schedules a video device-enabled meeting and schedules a TelePresence room, and then the host drags the meeting to a new start time on the calendar or add a new Telepresence room, there may be a problem if the TelePresence room is already booked. As a result, the Cisco TelePresence Management Suite server can't update the meeting because of the conflict. In addition, the Webex meeting can’t be moved back to the original start time.

Webex Site Administration options from the desktop app

In the Site Administration, on the desktop app, the options under Installation Options and Integrations apply only to the Windows version of the desktop app, not the Mac version. In addition, the only integration that's available for the Mac version of the desktop app is the integration to Microsoft Outlook.

Water Mark

Known Issues and Limitations for Cisco Webex Productivity Tools

view(s) people thought this was helpful

See the Known Issues and Limitations for the Webex Meetings Desktop Application (WBS39.10 and Later) for more info on the desktop app.

Windows and Mac

Can't edit migrated meetings scheduled with Webex Productivity Tools

After installing the Microsoft Office 365 add-in, users may see two Webex icons in their Microsoft Outlook window. The icon in the Webex section uses Productivity Tools, and the icon in the Cisco Webex section uses the Cisco Webex Meetings Scheduler.

If a user signs in to the Cisco Webex Meetings Scheduler, meetings scheduled with Productivity Tools are migrated so that the Cisco Webex Meetings Scheduler can edit them. However, users can't edit Webex meeting options such as the alternate host, join before host time, or audio type with Productivity Tools or the Cisco Webex Meetings Scheduler. The meeting start time, topic, and invitees can still be edited. As a workaround, we recommend scheduling meetings with the Cisco Webex Meetings Scheduler until this issue is resolved in a future update.


If a user scheduled a meeting on a host’s behalf using Productivity Tools, the meeting will be migrated into the host’s calendar, even if they do not install or sign in to Cisco Webex Meetings Scheduler. The scheduler or host will only be able to edit the meeting time, topic, and invitees using the Cisco Webex Meetings Scheduler or Productivity Tools.

Mac

Microsoft Outlook interface updates

In Microsoft Outlook for Mac, version 16.32, there are two UI interfaces. Users can enable or disable the new interface in the top right corner of the app window.

When New Outlook is enabled, Productivity Tools doesn't work as the Webex icon doesn't appear in the toolbar. The Microsoft Office 365 add-in also doesn’t work with this setting enabled. We recommend either not upgrading to the latest version of Microsoft Outlook for Mac, or keeping New Outlook disabled.

Windows and Mac

The issues noted here affect all Webex services unless indicated otherwise.

Known interoperability issues between Windows and Mac

If a meeting series has exceptions that were scheduled or updated with the Windows version of the desktop app, Mac desktop app users can't update the meeting series.

Any meeting that is scheduled or updated with the Windows version of the desktop app can’t be canceled with the Mac version of the desktop app.

Lockdown

The desktop app doesn’t support to lockdown to a specific version once automatic upgrading is enabled.

Some customers may stay on a specific desktop app version by disabling the automatic upgrade option. However, Cisco may ask all desktop app users to upgrade to a minimum version if security compliance is necessary. This is an option that can be enabled by Cisco administrators.

Missing meeting links

The meeting link doesn't appear when opening an ICS invitation in a Windows text editor if the meeting was scheduled using the desktop app for Mac. This is a known issue acknowledged by Microsoft.

Windows

The issues noted here affect all Webex services unless indicated otherwise.

Address button on the desktop app panel

On the desktop app panel, the address button that allows you to select email addresses from your Microsoft Outlook address book isn't supported for the 64-bit version of Microsoft Outlook.

Cross-platform support

The desktop app available for the Microsoft Windows and Mac platforms only. Linux, Unix, and Solaris platforms aren't supported.

Customized email templates

A site administrator can customize Microsoft Lync links in the email templates Invitation to a Meeting in Progress_PR(Productivity Tools) and MC MeetingInfo For Attendee(Productivity Tools). The customized link is available for all users, so the link is invalid in invitations sent by users without Webex Video Conferencing. The site administrator should be aware of this and should add a reference when customizing the templates.

If a site administrator customizes host and attendee email templates to be the same, only attendee versions are sent to hosts and attendees.

%MeetingDate% isn't a supported parameter when scheduling Personal Room meetings from the desktop app.

Email invitation templates

  • Attendee version only (without host information)

  • Host and attendee email versions both sent out

If a site has video device-enabled meetings enabled, only one email invitation template is available. Attendee versions don't contain host information like the host key and access code.

The Mac version of the desktop app still uses a single email template. If a Mac user edits meetings that were created on the Webex Productivity Tools version WBS29.13 or later for Windows, a new template is generated. The content's based on the unified email template for hosts and attendees.

Sometimes, if a host forwards a Webex meeting invitation, an attendee email is sent instead.

Hosts can cancel an individual meeting that's an exception to a series and then edit that meeting series. Sometimes, the cancellation notice to attendees would actually contain updated information for the updated meeting series.

If a host creates a video device-enabled meeting series, changes an occurrence, and then updates the series to Webex meetings, the exception email changes to plain text.

The desktop app doesn't support the %MeetingDate% parameter in the invitation email body. The meeting date and time is handled by the calendar system.

IBM Lotus Notes integration

If a user has IBM Lotus Notes as the default email application opens the desktop app, enters an email address of an invitee, and then selects Meet Now, the meeting invitation that's sent to that invitee is empty and doesn't include any meeting information.

Adding HTML content in the Webex calendar invitation results in an error in IBM Lotus Notes version 8.5.

Lotus Notes can only display plain text content of iCalendar mail. Formatting that's done in HTML isn't supported.

The IBM Lotus Notes integration supports only limited rich text format features, such as hyperlinks and images.

It isn't possible to specify TSP telephony while scheduling a Webex meeting using the IBM Lotus Notes integration.

The IBM Lotus Notes integration requires a script to be inserted on the Domino database for each user. As a result, a user with editor privileges can't install the IBM Lotus Notes integration by just running an MSI available from the Support page. For an IBM Lotus Notes user with editor privileges, a Domino administrator must insert a Webex script into the IBM Lotus Notes database using the administrator tool.

Using the IBM Lotus Notes integration MSI file, only an IBM Lotus Notes user with manager or designer privileges can install the Integration.

If a single occurrence of a recurring Webex meeting is deleted or rescheduled, the meeting information isn't updated on the Webex site. The host's and attendees' IBM Lotus Notes calendars, however, display the meeting correctly.

When a recurring Webex meeting is scheduled to recur on alternate weeks in an IBM Lotus Notes calendar, the recurring meeting appears to be scheduled on the Webex service site as occurring weekly instead. The host's and attendees' IBM Lotus Notes calendars, however, display the meeting correctly.

Attendee registration can't be enabled for recurring Webex meetings scheduled using the IBM Lotus Notes integration.

If an email template has the Mute on Entry option enabled, users still hear a sound as attendees join the meeting.

If IBM Lotus Notes is using a different time zone compared to the one on the Webex site, a meeting that's scheduled with the IBM Lotus Notes integration don't appear correctly on the Webex site. On the host's and attendees' IBM Lotus Notes calendars, the time zones for the meeting still appears correctly.

Since Lotus Notes Integration doesn't use an email template, it isn't possible to configure the content of the host's and attendees' email invitations for Webex meetings that are scheduled using the IBM Lotus Notes integration.

Webex events that are scheduled with the IBM Lotus Notes integration has the following limitations:

  • Hosts can't assign a program.

  • Hosts can't assign multiple time zones to an event.

  • Hosts can't add event options like uploading a host or presenter's image, uploading event material, or UCF auto play options.

  • Hosts can't add presenters and panelists.

  • Hosts can't edit email template options for an event.

  • The option to join a meeting before the host isn’t available for recurring events.

Webex training sessions that are scheduled with the IBM Lotus Notes integration has the following limitations:

  • Hosts can't specify Listed for authorized users only.

  • Hosts can't reserve Hands-on Lab computers.

  • Hosts can't specify a registration close date or maximum number of registrations.

  • Hosts can't invite attendees as presenters into the training session.

  • Hosts can't assign attendee privileges.

  • Hosts can't edit the type of email messages to want to send when different training sessions happen.

  • Hosts can't tests and course material.

  • The option to join a meeting before the host isn't available for recurring training sessions.

If a user schedules a meeting using IBM Lotus Notes and then changes the meeting on their Webex site, the changes don't appear in IBM Lotus Notes.

If a user selects multiple meetings in IBM Lotus Notes and then deletes or moves them at the same time, those changes don't appear on their Webex site.

If a user schedules a new meeting in IBM Lotus Notes by copying an existing meeting, a new meeting isn't created on their Webex site. Instead, the same Webex meeting link is shown on the original and is copied with the meeting.

The attendee access code isn't displayed for conferences scheduled with the IBM Lotus Notes integration.

If a host edits an already-scheduled meeting and adds an attendee, the attendee information isn't posted to the Webex site site. As a result, for such attendees, this meeting doesn't appear in the My Meetings list.

Installation privilege errors

If a user manually installs the desktop app using an MSI package, the user must have Windows administration privileges to complete the installation.

If an IT user mass deploys the desktop app using MSI packages, the IT user must have Windows administration privileges to complete the installation.

Windows administration privileges are mandatory for automatically upgrading the desktop app.

Microsoft Outlook integration

The desktop app doesn't support having more than one version of Microsoft Outlook installed on the same device.

Attendee registration can't be enabled for recurring Webex meetings scheduled using the Microsoft Outlook integration.

If an email template has the Mute on Entry option enabled, users still hear a sound as attendees join the meeting.

If Microsoft Outlook is using a different time zone compared to the one on the Webex site, a meeting that's scheduled with the Microsoft Outlook integration don't appear correctly on the Webex site. On the host's and attendees' Microsoft Outlook calendars, the time zones for the meeting still appears correctly.

If a host schedules a meeting using Microsoft Outlook and then changes the meeting information on the Webex site, the changes don't appear in Microsoft Outlook.

If a user selects multiple meetings in Microsoft Outlook and deletes or moves them at the same time, the changes don't appear on the Webex site.

If a host schedules a new meeting in Microsoft Outlook by copying an existing meeting, a new meeting isn't created on the Webex site. Instead, the same link is shown on both the original and copied meeting.

The attendee access code isn't displayed for audio conferences scheduled using the Microsoft Outlook integration.

Importing a company address book into the Webex contacts isn't supported with the 64-bit version of Microsoft Outlook 2010.

You can't edit a meeting that's in progress.

The settings in the Scheduled Meetings tab aren't used- the default settings from the Webex site meeting template are used instead. Users can still leverage the settings that are set while scheduling the meeting in Microsoft Outlook.

Webex events that are scheduled with the Microsoft Outlook integration has the following limitations:

  • Hosts can't assign a program.

  • Hosts can't assign multiple time zones to an event.

  • Hosts can't add event options like uploading a host or presenter's image, uploading event material, or UCF auto play options.

  • Hosts can't add presenters and panelists.

  • Hosts can't edit email template options for an event.

  • The option to join a meeting before the host isn’t available for recurring events.

Webex training sessions that are scheduled with the Microsoft Outlook integration has the following limitations:

  • Hosts can't specify Listed for authorized users only.

  • Hosts can't reserve Hands-on Lab computers.

  • Hosts can't specify a registration close date or maximum number of registrations.

  • Hosts can't invite attendees as presenters into the training session.

  • Hosts can't assign attendee privileges.

  • Hosts can't edit the type of email messages to want to send when different training sessions happen.

  • Hosts can't tests and course material.

  • The option to join a meeting before the host isn't available for recurring training sessions.

Sometimes scheduled meeting information isn't included in the body of the email. This may be due to Microsoft Word settings that prevent web pages from being displayed in Microsoft Outlook for Windows. As a workaround, users on Microsoft Word can go to File > Options > Trust Center > Trust Center Setting > File Block Settings. Then, in the Open column, disable Web Pages.

Links generated by the desktop app and recording services

As part of our updates to improve security, Cisco is making changes to improve the management of cryptographic keys used to generate URLs used across Webex services. As a result, existing links have been updated. Some users may need to request new links.

Mass uninstallation

Mass deploying the desktop app requires the mass uninstallation of the previously installed version. For users who have multiple versions of the desktop app installed, please see the IT Administrator Guide for Mass Deployment of Webex Productivity Tools.

Microsoft Lync 2013

Microsoft Lync 2013 doesn't allow the desktop app to change a user's status.

Embedding the Webex menu item into the right-click menu also isn't supported.

Microsoft Outlook support

Although the Webex Meetings desktop app supports Microsoft Outlook 2016 as of version WBS29.13.70, the desktop app supports only one email invitation template for meetings. The email template that's supported is the attendee version that doesn't contain the host key and access code. Similar to the Mac experience, hosts can view their host key or access code by signing in to their Webex site when joining their meeting.

The desktop app for Microsoft Outlook 2013 and earlier supports two email invitation templates. One template is for attendees, and the other which includes the host key and access codes for hosts. The Mac version of the desktop app has always supported only one email template for all supported versions of Microsoft Outlook.


Users with Webex Productivity Tools with Microsoft Outlook 2016 should install the latest version of the desktop application. Changes in Microsoft Outlook 2016 cause the older version of Productivity Tools to send the host email invitation template to attendees.

Hosts can use Microsoft Outlook to edit meetings created with supported versions of Microsoft Outlook in Webex Productivity Tools. A new email template is generated based on the unified email template for hosts and attendees.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2013. However, the email invitation shows Webex information for the original meeting and edited meetings.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2013. The user editing the meeting receives a message that Webex Meetings can't locate the meeting because it's being edited. Selecting OK or Cancel updates the meeting with incorrect information.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2007. The user editing the meeting receives a message that they don't have the appropriate permissions to edit and save the meeting.

Hosts can create recurring Webex meetings in Microsoft Outlook 2016 for Mac, change one occurrence, and then cancel the Webex portion of the meeting. However, the appointment can't be canceled in Microsoft Outlook 2016 for Windows if the calendars are in different time zones. Even if the email body is updated, the appointment can't be canceled.

Recurring meetings

If a user cancels a Webex recurring meeting in Microsoft Outlook that has an exception, and the user is using the Microsoft Exchange server version 2013 or later, the Webex information isn't completely removed from the cancelation email notification.

In Microsoft Outlook 2013 (15.0.4823.1000), updating a meeting series overwrites the email message of exception meetings.

Meeting times aren't displayed correctly in email invitations for a meeting series. This is because the %MeetingDate% parameter isn't supported. We recommend that you don't add this parameter to display the meeting date when customizing email templates.

Silent installation or mass deployment of the desktop app

If an administrator performs a silent installation or mass deployment of the desktop app, users can't edit any of the settings on the Tools panel. Performing a silent installation may cause some settings on the desktop app page of Webex Site Administration to be ignored.

For administrators who mass installed the desktop app and are trying to upgrade to a new version, we recommend that you perform a silent uninstallation first.

In some silent upgrade cases, the version of the desktop app on the control panel is reflected incorrectly. This problem doesn't impact features and should be fixed in a future update.

For more information about deploying the desktop app, see the IT Administrator Guide for Mass Deployment of Webex Productivity Tools.

Video call-in port setting for video device-enabled meetings

If a site administrator reduces the default video call-in number from ten to five, all scheduled video device-enabled meetings can still be updated.

Video device-enabled (Webex-enabled TelePresence) integration issues

For video device-enabled meetings, email templates are only supported in English only on Windows and Mac devices.

  • Scheduling video device-enabled meetings

    If an administrator turned on the TelePresence integration for a Webex site, users can schedule video device-enabled (Webex-enabled TelePresence) meetings with Microsoft Outlook for Windows. This option is only available for sites with TelePresence integration turned on. Once this option has been turned on, users may have to upgrade their desktop apps and restart Microsoft Outlook. The Allow people to join using Webex option in the Meeting Options dialog for video device-enabled meetings doesn't stay enabled if it was for a previous meeting. To allow users to join using Webex, this option must be enabled every meeting.

    Hosts who have video device-enabled meetings enabled but don't have the Webex setting in their Cisco TelePresence Management Suite (Cisco TMS) can't schedule TelePresence-only meetings with the desktop app.

  • Adding resources

    When users schedule a Webex meeting with Microsoft Outlook, if they add TelePresence rooms or extra video call-in participants, a Webex-enabled TelePresence meeting is automatically scheduled. If they don't include these resources, the meeting is a Webex-only meeting. Status indicators show that a TelePresence meeting was booked if these resources were added.

  • Email invitation templates for CMR Hybrid meetings

    CMR Hybrid meetings still only support one email invitation template, which is the attendee version that doesn't contain the host key and access codes. To view the host key and host access code, video device-enabled meeting hosts must sign in to their Webex site to see the Meeting Details Page. They can also sign in to their site on through the desktop app to view the information in their Advanced Webex Settings dialog.

    The desktop app for video device-enabled meetings doesn't support sending HTML email invitations. The email invitations are only available in plain text format.

    The desktop app email templates for video device-enabled meetings don't contain the %ConfCallParticipant% variable, so audio-only callers can join the audio conference from a mobile device. Instead, mobile device users can select the Join Webex meeting link or URL in their invitation, and join the meeting using the Webex Meetings mobile app. Users can also pick up or manually dial the call-in number and meeting ID number or access code in the invitation from their mobile device.

  • Time zone and Daylight Savings Time

    The time zone for a Webex site must match the time zone for the Cisco TMS; otherwise the meeting time isn't synchronized. When Daylight Savings Time changes are made between a Webex site and the Cisco TMS, it's possible that meetings might be an hour off schedule. If this happens, rescheduling is required. If this problem occurs with a meeting series where some instances occur before Daylight Savings Times begins and some occur after, we recommended that hosts create two meeting series: one meeting series that ends before the Daylight Savings Time begins and a second meeting series that starts after Daylight Savings Time begins.

  • Cisco Unified MeetingPlace Audio

    The desktop app that supports the Webex integration with Cisco TelePresence doesn't support Cisco Unified MeetingPlace Audio. Users with Cisco Unified MeetingPlace and the desktop app installed who want to schedule a combined Webex and TelePresence meeting with Webex or TSP audio, must use the Smart Scheduler in the Cisco TMS. A user can't have two versions of the desktop app installed at the same time.

  • Telephony service provider (TSP) audio

    For some TSP audio accounts, if a host with a TSP account schedules two adjacent video device-enabled or Webex video conferencing meetings, with the second one scheduled to start immediately after the first one ends, and if the TelePresence scheduling system automatically extends the first meeting past the scheduled end, the second meeting will end automatically because the host because the same TSP audio account can’t be used for both meetings at the same time. To work around this problem, hosts can set up two different TSP audio accounts with different host access codes, and use one account for the first meeting and the other account for the second meeting. Another option is the administrator to turn off the option for the TelePresence systems to automatically extend the meeting.

  • Support for Microsoft Office 365, Microsoft Outlook 2010, and Windows 8 and 8.1

    Webex sites that have the video device-enabled meetings enabled may require the latest versions of the Cisco TMS and Cisco TMSXE to support Microsoft Office 365, Microsoft Outlook 2010, or Windows 8 and 8.1. For more information, go to Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide > Cisco Webex Features and Important Notes > Prerequisites on the Cisco TelePresence Management Suite (TMS) Configuration Guides page.

  • Instant Meetings and Personal Room meetings

    Users can't start instant video device-enabled meetings; only schedule them. When users start instant meetings, they are Webex-only meetings and don't include TelePresence integration.

    Instant meetings that started with the Meet Now command are held in Personal Rooms by default. This option can be changed in a user's Preferences. In order to have a Personal Room meeting that users can join from a video conferencing system or app, the Webex site and host account must be enabled for it.

    A workaround for an instant meeting that uses both Webex and TelePresence is to start a meeting from a TelePresence system and then the named host has selects Instant Webex Meeting on the meeting detail page to generate a URL that allows external participants to join the TelePresence meeting from a desktop or mobile app.

  • Scheduling Webex-only or TelePresence-only meetings

    Webex sites that have video device-enabled meetings enabled require Cisco TMSXE in order for users to schedule Webex-only or TelePresence-only meetings with the desktop app.

  • Maximum of two simultaneous meetings per host

    Webex sites that have video device-enabled meetings enabled can't have a host have more than two meetings started at the same time.

  • Personal and audio conferences

    Although a video device-enabled meeting user can schedule a Personal Conference meeting for sites that have Webex Audio or an audio conference for sites that have TSP audio, it's a Webex-only meeting type and doesn't include video device-enabled meetings.

  • No branding or customizing of video device-enabled meeting features

    Site administrators can't change the branding for the video device-enabled meeting Options panel, hide info, and can't limit the number of video call-in participants that users can enter.

Webex One-Click, instant messenger, and Microsoft Office integrations

If users use personalized join links to automatically populate attendee names and email addresses on the Join Meeting page, some email gateways may truncate the links. Attendees can still click the links, but the links don't automatically allow them to join the meeting. Instead, they must enter their name and email address before joining the meeting. There’s no current known workarounds.

If the instant messenger integration was installed using a silent installer, users must restart their instant messenger to see the desktop app integration features.

Webex site URL change

If a user signs in to the desktop app with a new Webex site URL after the site was renamed, they can't edit the meetings that were scheduled with the previous URL.

Mac

The issues noted here affect all Webex services unless indicated otherwise.

Installation privilege errors

Users manually installing the desktop app using a DMG package must have iOS administration privileges.

iOS administration privileges are mandatory to automatically upgrade the desktop app.

Mass deployment of the desktop app isn't supported on the Mac.

Microsoft Outlook support

The desktop app for Mac doesn't support Microsoft Insider preview versions.

Hosts can create recurring Webex meetings in Microsoft Outlook 2016 for Mac, change one occurrence, and then cancel the Webex portion of the meeting. However, the appointment can't be canceled in Microsoft Outlook 2016 for Windows if the calendars are in different time zones. Even if the email body is updated, the appointment can't be canceled.

The desktop app support having more than one version of Microsoft Outlook installed on the same computer.

Meetings from Webex Meetings server aren't supported.

Some known issues may occur with the desktop app using Microsoft Exchange Server 2007 and Microsoft Outlook for Mac.

If a user is updating the Webex meeting on the Outlook calendar view instead of the editing window of the occurrence, some issues occur because some Microsoft Outlook behaviors aren't under the desktop app's control in the calendar view.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2013. However, the email invitation shows Webex information for the original meeting and edited meetings.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2013. The user editing the meeting receives a message that Webex Meetings can't locate the meeting because it's being edited. Selecting OK or Cancel updates the meeting with incorrect information.

If a user schedules a meeting in Microsoft Outlook 2016, someone can still edit that meeting using Microsoft Outlook 2007. The user editing the meeting receives a message that they don't have the appropriate permissions to edit and save the meeting.

Meeting times aren't displayed correctly in email invitations for a meeting series. This is because the %MeetingDate% parameter isn't supported. We recommend that hosts don't add this parameter to display the meeting date when customizing email templates.

In Microsoft Outlook 2016, an exception meeting opens when a user right-clicks an exception and selects Open > Open Series.

Cisco TelePresence Management Suite (TMS) sign in window

If the TMS sign in window doesn't appear after upgrading to the latest version of the desktop app, restart the device.

Default meeting templates

If the First attendee to join will be presenter option is enabled in Webex Site Administration, this option is enabled by default in a Webex site's meeting scheduler. The setting is also be enabled in the default meeting template that's used by the desktop app for scheduling Webex meetings. Custom meeting templates that have been created by users aren't be impacted. If a host schedules meetings with custom templates and wants the first attendee to become the presenter, the host must manually enable the setting.

IBM Lotus Notes integration

IBM Lotus Notes isn't supported in the desktop app.

Sign in and sign out processes

Sometimes, the desktop app might redirect a user to their Webex site to sign in again and change their password.

The desktop app supports enterprise single sign-on users; however, because there’s no single sign-out service from the enterprise site, users can only switch their account when the single sign-on token has expired.

Before single sign-on users first sign in to the desktop app, they must go to the Webex site to accept the site certification manually with Safari.

Video device-enabled meeting issues

For video device-enabled meetings, email templates are supported in English only.

The same issues that exist for the Webex-enabled TelePresence integration (CMR Hybrid) for the Windows version of the Desktop Application also apply to the Mac version.

If a host using the desktop app schedules a video device-enabled meeting and schedules a TelePresence room, and then the host drags the meeting to a new start time on the calendar or add a new Telepresence room, there may be a problem if the TelePresence room is already booked. As a result, the Cisco TelePresence Management Suite server can't update the meeting because of the conflict. In addition, the Webex meeting can’t be moved back to the original start time.

Webex Site Administration options from the desktop app

In the Site Administration, on the desktop app, the options under Installation Options and Integrations apply only to the Windows version of the desktop app, not the Mac version. In addition, the only integration that's available for the Mac version of the desktop app is the integration to Microsoft Outlook.

Water Mark

Known Issues and Limitations for Webex Video

view(s) people thought this was helpful

Cisco Webex Video Platform Version 2 Known Issues


This section applies only to Webex Meetings sites that have the Media Resource Type list available in the Cloud Collaboration Meeting Room site options. Contact your administrator for more information.

H.264 video codec required for content sharing

Content sharing is only supported using H.264 video codec. Older video systems that do not support H.264 codec will not be able to do content sharing.


Environments newly implementing Cloud-based services, or reviewing integration with Cloud-based services, should ensure that their Telepresence endpoints are sending High Definition Content. This typically includes setting endpoint’s Content Input Sources to Optimal Definition "High", along with ensuring the appropriate bandwidth is set to accommodate simultaneous HD-Level H264 main video and content. Please review the relevant TC or CE endpoint Administration Guide for Optimal Definition and Resolution-Bandwidth settings.

In-meeting video thumbnail experience

Any cascades in Webex Meetings are limited to up to six streams at a time in either direction. For example, Webex Meetings participants only see up to six video streams of Webex Video Platform users connected through TelePresence, Webex Cisco Webex Teams, Webex Room and Desk Devices, Skype for Business, and other SIP or H.323 devices connected to the meeting. Likewise, Webex Video Platform users only see up to six participants using Webex Meetings apps including apps for desktop, mobile, and web. Also, any participants that are connected through Webex Video Mesh nodes have the same limitation between their specific Webex Video Mesh node and devices or apps that are connected directly to the Webex cloud or other Webex Video Mesh nodes.

Cisco Webex Video Platform Version 1 Known Issues

Call My Video System

The option to Call My Video System may fail if attendees are required to press '1' and no RMS or Traversal Licenses are installed on the Customer Expressway-C and Expressway-E pair.

Display names

Display names for video conferencing system users are not visible in the Webex meeting video window. This issue will be addressed in a future update.

Leaving and reentering a Personal Room

Sometimes, when hosts end a Webex video platform version 1 meeting by leaving their Personal Room and then reentering their Personal Room within a few seconds, they may hear an audio prompt about an invalid meeting. If this happens, the host should hang up and wait a few seconds before redialing the Personal Room.

12-hour limit

A scheduled Webex video platform version 1 meeting can't last for more than 12 hours. Hosts and participants can reenter the meeting, or can schedule a new one.

Telephony service provider (TSP) audio

For users on Webex Meetings sites that utilize TSP audio conference bridges, video systems will not be able to join meetings until the meeting host has configured the toll phone number for their TSP audio service provider. To avoid this problem in a meeting, we recommend that hosts specify the toll number of the TSP audio service in their account preferences.

Due to some dial-out sequences having multiple steps and longer prompt durations that cannot be interrupted, it may take a while before audio from Webex Meetings users joining through phones can be heard by video systems and video systems can be heard by phones. During this time, users who have joined from video systems have no indication that their audio is not being heard by users who have joined using Webex Meetings. To avoid this problem, all participants should wait until the TSP audio dial-out sequence is complete, which is indicated by phone handset icons appearing next to participants' names in the participants list.

Truncated display names on video systems

If there is network bandwidth degradation on a user's video system, its video resolution may be reduced to a size that better accommodates the current network conditions. In that scenario, the display names of participants may appear truncated in the video endpoint active presence view. This is due to the lower resolution video for the video stream, which has a limited number of pixels to display the participant name.

In-meeting video experience

Starting in WBS33, Webex Meetings apps default to a filmstrip layout which requires that each participant be able to send thumbnail-quality video streams. Since Video Platform Version 1 only supports sending the active speaker video toWebex Meetings, Video Platform users will not have their video displayed in the filmstrip.

Video systems joining without encryption

If attendees join a meeting using video systems that do not setup encrypted signaling links or use encrypted media links, the meeting cannot be considered fully secured, since there are other devices whose connections cannot be secured.

Call leg security

The encrypted meeting status icon on video systems utilizing Telepresence Interoperability Protocol (TIP) or Call-Info security attributes does not reliably indicate the encryption status in meetings. Even when all call legs are encrypted, this icon may still indicate an unencrypted meeting.

Support for Microsoft Lync or Microsoft Skype for Business Applications

  • Content that is shared in a Webex video platform version 1 meeting is transcoded into the main video channel for users on Lync and Skype for Business clients

  • Clients using RTV video codec is not supported, including Lync 2011 on Mac OS.

  • For users registered to a Lync or Skype for Business server, Polycom video devices aren't supported.

  • To ensure 2-way video in a meeting, users must select Video and then select Start Video on the application before joining the meeting.

  • After joining the meeting, users may need to select Start Video one more time.

Join meetings by dialing an IP address

For latest interoperability compatibility test results, please refer to the IP dialing section of the compatibility document:. https://collaborationhelp.cisco.com/article/ipxxr2

Known Issues for Using Webex Meetings video platform version 1 with Cisco Teams

  • Cisco Webex Teams and Mozilla Firefox

    When Cisco Webex Teams users in Mozilla Firefox share their screen, Webex users see a black screen, instead of the shared content. When Webex users share their screen, Webex Teams users in Firefox can see the shared content.

  • Video Call-Back to Cisco IP Phone 8800 Series Video Phones Registered to the Cisco Teams Calling Service

    When you initiate a video call-back from the meeting to Cisco IP Phone 8800 Series Video Phones registered to the Webex Teams Calling service, where the site is configured to require DTMF key 1 to connect to the meeting, this connection fails. The workaround for these devices is to disable the requirement to enter DTMF key 1 to connect to meetings.

  • Sending video from Webex applications to video conferencing systems or applications

    A Webex Meetings video or CMR Hybrid meeting always starts at the best video resolution between video systems and the Webex Meetings application. If high-definition video is available, it is available to all participants. If any participant on the Webex Meetings side experiences poor network conditions, the resolution between video systems and the Webex Meetings application downgrades to accommodate that participant. As a result, video resolution will also be poor for all other participants. The minimum bit rate a Webex Meetings application must process from the Webex Cloud to be able to receive both video and application or screen sharing (formerly called "desktop sharing") content is 1.2 Mbps. Less than that results in the Webex Meetings application showing only the shared application or screen.

    For information about recommended bandwidth configuration settings for Webex video platform version 1 meeting, see the Cisco Webex Network Bandwidth White Paper.

    For information about recommended bandwidth configuration settings for CMR Hybrid meetings, see "Prerequisites" in the "Cisco Webex Features and Important Notes" chapter and "Tips for Troubleshooting Low Bandwidth with the Webex Meetings application on Windows or Mac" in the "Troubleshooting" chapter of the CMR Hybrid Configuration Guide on the Cisco TelePresence Management Suite (TMS) Configuration Guides page. For additional information, refer to the Cisco Webex Network Bandwidth White Paper.

  • Presentation and data sharing quality

    If you do not have adequate bandwidth, your presentation and data sharing in Webex Meetings video and CMR Hybrid meetings can degrade to XGA (1024 x 768 resolution) and 5 frames per second (FPS). On TelePresence systems, users see a "letterbox" format.

    Assuming all Webex Meetings applications have at least 2Mbps bandwidth, users in the meeting can enjoy 720p content sharing at up to 5 FPS.

    If Webex Meetings applications have at least 3-Mbps bandwidth, the content share quality is 1080p at 3 FPS.

  • Full-screen video view

    When presenters switch to full-screen video view while sharing their screen, application, or document, sharing is paused on the attendee side (the last-shared screen freezes). When the presenter exits full-screen video view, sharing automatically resumes.

    Attendees stay in full-screen video view when the presenter stops sharing and automatically exit full-screen video view when the presenter starts sharing again.

    If the Webex Meetings desktop application has two monitors, users can display a full-screen view on one monitor and full-screen or application sharing on the other monitor by dragging the video window to the other monitor and selecting the "View all participants in full-screen view" icon.

  • Presenter may unintentionally disable video for all participants

    If a Webex Meetings user who is the presenter in the meeting unchecks the Video option in the Meeting Options dialog box, video is disabled for all meeting participants, whether they joined from a Webex meeting application or from a video conferencing system. To restore video for all participants, the meeting host or current presenter should check the Video option in the Meeting Options dialog box.

  • Other teleconference audio

    The audio connection option Other teleconference audio is not supported for CMR Hybrid and Webex Meetings video conference meetings.

  • Telephony service provider (TSP) audio accounts

    For some telephony service provider (TSP) audio accounts, if a host with a TSP account schedules two adjacent CMR Hybrid or Webex Meetings video conference meetings, with the second one scheduled to start immediately after the first one ends, and if the TelePresence scheduling system automatically extends the first meeting past the scheduled end, the second meeting will end automatically because the same TSP audio account and host access code cannot be used for both meetings at the same time.

    To work around this problem, hosts can set up two different TSP audio accounts with different host access codes, and use one account for the first meeting and the other account for the second meeting. Another option is for the administrator to turn off the option for the TelePresence system that automatically extends the meeting.

  • Webex Meetings features

    If you are hosting a meeting that includes video systems, the following in-meeting features are unavailable:

    • Whiteboard

    • Document sharing

    • Polling

    • File Transfer

    • Chat (with TelePresence room participants)

For a list of compatible video systems and applications see Webex Meetings Video Compatibility and Support.

CMR Hybrid Integration Known Issues

The following issues apply to joint meetings with Webex Meetings and TelePresence in the CMR Hybrid solution:

  • Participant list

    • The Webex Meetings host in a joint CMR Hybrid meeting with Webex Meetings and TelePresence is not able to see a complete list of all Webex Meetings and TelePresence participants.

    • TelePresence participants are listed as "TelePresence Systems" in the Webex Meetings Participants list of a CMR Hybrid meeting.

  • Exceptions to a recurring meeting series using Webex Meetings Productivity Tools

    Although recurring meeting exceptions for CMR Hybrid meetings are now supported in Webex Meetings Productivity Tools. "Orphan" meetings are not yet supported. For example, you cannot add a Webex meeting and TelePresence rooms to a single occurrence of an Outlook-only meeting series. If you want to make these features available for a single occurrence, make the whole series a Webex Meetings and TelePresence meeting.

    Edits to a meeting series with exceptions that were changed before version WBS30 follow Microsoft Outlook's rules, where possible, regarding treatment of the exceptions' properties.

    If a host edits the subject or changes the meeting time of a single occurrence of a recurring CMR Hybrid meeting series by editing it directly in the Microsoft Outlook calendar, and then removes Webex Meetings from the entire series, the Webex meeting information still appears in the exception meeting.

    If the host scheduled a recurring CMR Hybrid meeting series, and the date of the first occurrence has passed without that meeting being started, the host cannot update the date of that individual occurrence. However, the host can change the date for the entire meeting series.

    If you remove the Webex meeting from an individual occurrence of a CMR Hybrid meeting series, you change it to a TelePresence-only meeting. However, the Cisco TelePresence Management Suite (Cisco TMS) still shows Webex Meetings information for that exception meeting.

    If you change all the individual meeting occurrences within a meeting series into exceptions, and you then attempt to add a TelePresence meeting to the entire series, Cisco TelePresence Management Suite for Microsoft Exchange (Cisco TMSXE) assumes the series in the past and does not give adequate warning messages to the meeting scheduler or host. Users can work around this issue by deleting the current series and creating a new series that has TelePresence added, and then editing the exceptions to that series individually, as exceptions, or deleting all the exceptions and creating individual meetings.

  • Making someone presenter

    A TelePresence system becomes the presenter when a VGA cable is connected to the laptop. In a standard Webex meeting, a user has to ask the host to make him or her the presenter. By default, the ability for anyone in the meeting to "grab the ball" or request to be the presenter is enabled for CMR Hybrid users. Starting in WBS29.11, the Anyone Can Share feature allows anyone to share without requesting to be the presenter. This option is also enabled by default for CMR Hybrid users. If you are connected to both Cisco Jabber and Webex Meetings on the same computer and try to share content from Jabber, you get repeating share windows. We recommend that you always share from Webex Meetings if you have both Jabber and Webex Meetings on your computer.

  • Time zone

    The time zone for the Webex Meetings site must match the time zone for the Cisco TelePresence Management Suite; otherwise the meeting time is not synchronized.

  • Leaving a meeting

    Unlike Webex Meetings-only meetings, which have an option to automatically extend if attended by audio-only callers, when all TelePresence endpoints leave a CMR Hybrid meeting, if there are no users of Webex Meetings applications to pass the host role to (or if audio-only endpoints are the only other attendees of a CMR Hybrid meeting), and capacity constraints on the TelePresence Management Suite do not allow the TelePresence side of the meeting to automatically extend beyond the scheduled end time of the meeting, the meeting ends.

  • File sharing and whiteboard sharing

    File sharing and whiteboard sharing are not supported in CMR Hybrid meetings. We recommend that you use screen sharing or application sharing instead.

  • Audio codec

    Cisco recommends the G.722 audio codec on the CMR Hybrid link for the best user experience. The G.711 codec is also supported as an alternative. We do not recommend or support use of the G.729 codec on the CMR Hybrid link.

  • Sending video from Webex Meetings applications to video conferencing systems or applications

    A Webex Meetings video or CMR Hybrid meeting always starts at the best video resolution between video systems and the Webex Meetings application. If high-definition video is available, it is available to all participants. If any participant on the Webex Meetings side experiences poor network conditions, the resolution between video systems and the Webex Meetings application downgrades to accommodate that participant. As a result, video resolution will also be poor for all other participants. The minimum bit rate a Webex Meetings application must process from the Webex Meetings Cloud to be able to receive both video and application or screen sharing (formerly called "desktop sharing") content is 1.2 Mbps. Less than that results in the Webex Meetings application showing only the shared application or screen.

    For information about recommended bandwidth configuration settings for Webex Meetings video conferencing meetings, see the Cisco Webex Network Bandwidth White Paper.

    For information about recommended bandwidth configuration settings for CMR Hybrid meetings, see "Prerequisites" in the " Cisco Webex Features and Important Notes" chapter and "Tips for Troubleshooting Low Bandwidth with the Webex Meetings application on Windows or Mac" in the "Troubleshooting" chapter of the CMR Hybrid Configuration Guide on the Cisco TelePresence Management Suite (TMS) Configuration Guides page. For additional information, refer to the Cisco Webex Network Bandwidth White Paper.

  • Presentation and data sharing quality

    If you do not have adequate bandwidth, your presentation and data sharing in Webex Meetings video and CMR Hybrid meetings can degrade to XGA (1024 x 768 resolution) and 5 frames per second (FPS). On TelePresence systems, users see a "letterbox" format.

    Assuming all Webex Meetings clients have at least 2Mbps bandwidth, users in the meeting can enjoy 720p content sharing at up to 5 FPS.

    If Webex Meetings applications have at least 3 Mbps bandwidth, the content share quality is 1080p at 3 FPS.

  • Full-screen video view

    When presenters switch to full-screen video view while sharing their screen, application, or document, sharing is paused on the attendee side (the last-shared screen freezes). When the presenter exits full-screen video view, sharing automatically resumes.

    Attendees stay in full-screen video view when the presenter stops sharing and automatically exit full-screen video view when the presenter starts sharing again.

    If the Mac or PC Webex Meetings application has two monitors, users can display a full-screen view on one monitor and full-screen or application sharing on the other monitor by dragging the video window to the other monitor and selecting the "View all participants in full-screen view" icon.

  • Presenter may unintentionally disable video for all participants

    If a Webex Meetings user who is the presenter in the meeting unchecks the Video option in the Meeting Options dialog box, video is disabled for all meeting participants, whether they joined from a Webex meeting application or from a video conferencing system. To restore video for all participants, the meeting host or current presenter should check the Video option in the Meeting Options dialog box.

  • Other teleconference audio

    The audio connection option Other teleconference audio is not supported for CMR Hybrid and Webex Meetings video conference meetings.

  • Telephony service provider (TSP) audio accounts

    For some telephony service provider (TSP) audio accounts, if a host with a TSP account schedules two adjacent CMR Hybrid or Webex Meetings video conference meetings, with the second one scheduled to start immediately after the first one ends, and if the TelePresence scheduling system automatically extends the first meeting past the scheduled end, the second meeting will end automatically because the same TSP audio account and host access code cannot be used for both meetings at the same time.

    To work around this problem, hosts can set up two different TSP audio accounts with different host access codes, and use one account for the first meeting and the other account for the second meeting. Another option is for the administrator to turn off the option for the TelePresence system that automatically extends the meeting.

  • Webex meeting features

    If you are hosting a meeting that includes video systems, the following in-meeting features are unavailable:

    • Whiteboard

    • Document sharing

    • Polling

    • File Transfer

    • Chat (with TelePresence room participants)

For a list of compatible video systems and applications see Webex Meetings Video Compatibility and Support.

Water Mark

Known Issues and Limitations for Cisco Webex Meetings

view(s) people thought this was helpful

Automatic Installation of Desktop App on Locked Down Sites

On Webex sites locked down to WBS39.5.x and WBS33.6.x, users without Webex Productivity Tools (WBS33.0.x) or the Webex Meetings desktop app (WBS33.x—WBS39.x) will have the pre-meeting desktop app automatically installed when they join a meeting on a WBS39.8 Webex site as a guest.

To avoid this automatic installation, users can install a Webex Meetings desktop app version earlier than WBS39.8 before joining a meeting on a WBS39.8 or later site.

Prompted to Install Webex Meetings Multiple Times

If you clear your cookies in Google Chrome, Mozilla Firefox, or Safari, you may see the install screen again next time you join a meeting from your web browser, even if you already have the desktop app installed. If you click the install file, you launch the desktop app.

Cannot Automatically Connect Using TSP Hybrid VoIP

You cannot automatically connect to audio when joining a meeting using TSP hybrid VoIP, even if you have enabled the setting "Automatically connect to audio using computer"

Recording Playback on Mobile Devices

You cannot play back a network-based recording on a mobile device.

Default Meeting Templates

If the First attendee to join will be presenter option is enabled in Site Administration, this option is enabled by default in the meeting scheduler on your Webex Meetings site. It is also enabled in the default meeting template that you use in Webex Meetings Productivity Tools for scheduling Webex meetings with Microsoft Outlook. Custom meeting templates that have been created by users are not impacted. If a host schedules meetings using custom templates and wants to have the first attendee to join the meetings automatically become the presenter, the host must manually enable the setting in the custom templates.

For video device-enabled meetings, the First attendee to join will be presenter option isn't shown on the scheduler page in Classic View, and is enabled by default.

Network-Based Recordings

Network-based recordings require a minimum bandwidth of 2.0 Mbps to play smoothly; otherwise, pausing might occur.

MP4 Playback in non-Webex Meetings Video Meetings Not Supported for the Webex Meetings Desktop App for Linux

Linux users on the Webex Meetings desktop app can't start or join a non-Webex video meeting that has enabled MP4 playback. They receive a warning message indicating their operating system is not supported for this meeting, because Linux only supports ARF recording format.


We recommend that Linux users use the Webex Meetings Web App for MP4 playback support in non-Webex video meetings.

Active Audio-Only Meetings Recycled

Audio-only meetings are recycled according to the 90-day meetings recycle period, or 180-day recurring meetings recycle period, even if the meetings were hosted or joined within that time.

Personal Rooms

BlackBerry 10 devices, Windows 8 phones, and the Webex Meetings Desktop App for Linux—You cannot start or host a meeting in your Personal Room using a BlackBerry 10 device, a Windows Phone 8 device, or the Webex Meetings desktop app for Linux.


We recommend that Linux users use the Webex Meetings Web App to start or host meetings from their Personal Rooms.

Personal Room lobby—Users of the following devices or applications cannot wait in the lobby while a Personal Room is locked: Webex Meetings desktop app for Linux, TelePresence devices, Windows Phone 8 device, and BlackBerry 10 devices. In addition users who join only the audio portion of the meeting cannot wait in the lobby while a Personal Room is locked. These users will receive a message that the room is locked, and will not be able to join until the room is unlocked.


We recommend that Linux users use the Webex Meetings Web App to wait in a lobby while a Personal Room is locked.

For more issues that affect Personal Rooms and Webex Meetings video, see Cross-platform Features and Known Issues.

Cisco Webex Web App

Video Limitation

VoIP is not supported when the host account has Webex Meetings video conferencing disabled.

Slow Join Times After a Major Upgrade

After a major Webex Meetings Suite upgrade containing more new features than a regular service pack release, you may encounter a long load time, as more files have to be downloaded and installed. Loading times depend on your network's bandwidth and the amount of traffic at the time of the download. In general, load times can range from 20 seconds to 3 minutes or more.

One Meeting at a Time

Mac users can join only one meeting at the same time.

In-meeting experience

  • Keyboard navigation and screen reader support:
    • Video thumbnail items in the Participant panel do not support navigation using the Tab key.

    • Some items in file sharing and in the Polling panel don't support navigation using the Tab key.

    • Items within the video full-screen view don't support navigation using the Tab key.

    • Elements inside the video user interface don't support screen readers.

    • Video thumbnail items don't support screen readers.

    • The participant list within the Participant panel doesn't support screen readers.

    • Some elements for file sharing and in the Polling panel don't support screen readers.

  • The Pan tool is not available when viewing a file that is shared using file sharing.

  • The new interface is not available for Linux users.

  • On Mac, when the presenter annotates during application sharing or screen sharing (formerly called desktop sharing) and takes notes or creates a poll, the Notes and Poll information cannot be saved.

  • On Mac, when using annotation during sharing, if user moves from tab view to full-screen view, the annotation option that as last used is not remembered.

  • On some Windows machines as well as on Linux machines, if attendee screen saver comes on and then the presenter starts file sharing, the screen saver automatically quits.

  • Some custom Quick Start templates, created using older releases of Webex Meetings, may not work after upgrading to this release.

  • In a few cases, uploading a very large Microsoft PowerPoint file to share in the meeting may cause the meeting to get disconnected for the presenter.

Initials in Avatars

The first letter of a user's first name and the first letter of the user's last name are used in avatars when there is no image available. Users with second names comprised of more than one word will not be displayed correctly as three letters, for example, "Mary Van Buren" and "Robert Smith Jr." will display as "MB" and "RJ" respectively.

Anyone Can Share Feature

  • The Anyone Can Share feature is not available for Linux users on the Webex Meetings desktop app. It is also not available for mobile users who are using earlier versions of the Cisco Webex Meetings mobile app. This feature will be supported in the Cisco Webex Meetings app version 6.6 or later for iPhone and iPad, version 3.6 or later for BlackBerry 10 devices, and version 6.5 or later for Android devices. Mobile users who have earlier versions of the application can still be made presenters by passing the presenter role to them only if the mobile app has presenter capabilities.


    We recommend that Linux users use the Webex Meetings Web App to access the Anyone Can Share feature.

  • If a host starts a meeting on a desktop and then disables the Anyone Can Share feature while in a meeting, participants in that meeting who are using earlier versions of the Cisco Webex Meetings app for iPhone, iPad, BlackBerry 10 devices, and Android devices will still be able to share.

  • Users of the Cisco Webex Meetings mobile app will not be able to disable the Anyone Can Share feature within a meeting, but will follow the site administration settings for that feature.

Host Role Taken Over by a Joining Alternate Host

In some circumstances, the host role may be taken over by an alternate host when joining a meeting or session, even if the host has already joined. If this occurs, we recommend the alternate host assigns the host role back to the host.

Leave Meeting Command

The Leave Meeting command is disabled for sites that use third-party telephony service provider (TSP) audio.

Links Generated by Webex Meetings and Webex Recording Services

As part of our continuing updates to improve security, Cisco is making changes to improve the management of cryptographic keys that are used to generate URLs used in the Webex Meetings Suite and Webex recording services. As a result, existing links that were generated by those services have been updated, and sometimes, users may need to request new links. More information can be found here: https://collaborationhelp.cisco.com/article/WBX78957.

Multi-monitor Support in Windows 10

Shared content may get cut off or display partially when sharing from a secondary screen that has a higher resolution than your primary screen. To remedy this, we recommend that you set your largest display to be your main display in your Windows display settings.

Shared Documents Display Quality

Webex Meetings uses a printer driver interface to import documents that are not natively supported. The presentation quality of documents shared in Print Driver mode, such as Microsoft Word, Excel, and Adobe PDF documents, cannot be better than a hard-copy printout of the same document printed by a physical printer. This issue is pronounced when these documents contain images of text.

Cropped, Cut Off, or Misplaced Drawing Objects

Drawing objects partially or wholly outside the 15-bit twips (32768 x 32768 twips = 22.75 x 22.75 inches) coordinate range are not displayed, cut off or misplaced. This includes regular PD drawing objects, images, UCF objects, and annotations. The actual size on pixels depends on the screen resolution and screen size.

To avoid this issue, we recommend you resize large documents to fit within the above coordinate range.

Microsoft Office 2013 and later Support

  • If you have Microsoft Office 2013 or later installed, the following features are not supported when sharing PowerPoint files:
    • Animations and transitions
    • Embedded video or audio files
    • UCF Toolkit
  • If you have customized your Info Tab, some custom elements may not be supported. We recommend that you validate it to make sure it continues to display properly in a Webex meeting.
  • In a few cases, the following problems may occur:
    • Text and fill colors may be slightly different from the actual colors in a slide.
    • Some graphic elements may be missing from a slide.
    • Fonts may appear blurry on a slide or may be different from the original.
    • The size of shapes may be different from the original.
  • If an object in a PowerPoint presentation does not display correctly in edit mode, it is automatically removed in Slide Show view; however, the object may continue to display when the file is shared in a Webex meeting.
  • You cannot share password-protected PowerPoint 2013 files using the file sharing feature. Use the application sharing or desktop sharing features instead.
  • You cannot share Excel 2013 files on Windows 8 using the file sharing feature. Use the application sharing or screen sharing (formerly called "desktop sharing") features instead.
  • You cannot share Word 2013 (64-bit) documents on Windows 8 (64-bit) using the file sharing feature. Use the application sharing or screen sharing features instead.

Tagging Internal Participants

Tags for internal participants do not appear in the following cases:

  • When the participant joins from mobile device

  • When a participant using One-Touch TelePresence Plus is not using SAML single sign-on

  • In Personal Conference meetings

File Sharing

If you are a host using Windows and do not have a universal printer driver that is installed on your system, you will not be able to share any file types except Microsoft PowerPoint files during file sharing. In this case, the system will provide an option to move to application sharing instead of file sharing or to install a universal printer driver before you proceed. (Windows 7 systems come pre-installed with a universal printer driver.)

File sharing is not supported for CMR Hybrid (Webex-enabled TelePresence) meetings.

Streaming Media Sharing

Attendee video resolution is optimized to 480p. Video files with higher resolution are resized to fit (640 X 480) resolution. The following media file formats are currently supported: WMV, WMA, WAV, MP3, ASF, AVI, MPG, MPEG, FLV, F4V, and MP4.

Recommended System requirements for video file sharing on Presenter side:

  • Core2-Duo E6750 @ 2.66GHz for VGA file is required

  • AMD 9650 2.3GHz (4 core) 8GB is preferred

  • Intel® Core™ 2 Duo -E7400 2.8GHz 2.79GHz is preferred

File sharing is not supported for CMR Hybrid (Webex-enabled TelePresence) meetings.

Audio Switching to Internal Speakers When File Sharing

If you are using an external audio device such as headphone or external speakers, sharing a file with sound, such as a WRF file, forces the Webex Meetings application to switch to the internal speakers, even if you select an external source in the Webex Meetings sound settings. The application returns to the external device once you stop sharing the file.

Unable to Join Meeting

Linux/Unix users might not able to join the meeting if NTLM authentication is enabled with ISA proxy. We recommend that Linux users use the Webex Meetings Web App as a workaround.

Viewing Office 2007 and Later Documents

Attendees who join a meeting from the Webex Meetings desktop app for Linux/Unix may have display issues when the presenter shares a Microsoft Office 2007 and later document. For example, some animations and pictures may not be displayed or become distorted. As a workaround, we recommend that attendees use the Webex Meetings Web App.

Microsoft Office PowerPoint

In Microsoft PowerPoint 2007 and later, text that is copied from a web page and pasted into the notes panel may not render properly. A workaround is to copy the text into Microsoft Word or Microsoft Notepad, then copy the text again from that editor in the notes panel.

Importing Contacts into Microsoft Outlook 2010

Importing your company address book into your Webex Meetings contacts is not supported with Microsoft Outlook 2010 64-bit.

Closing a Meeting

In Internet Explorer 7, if there are multiple tabs open in the browser, and the Webex Meetings "Meeting in Progress" page is not the tab in the foreground, the meeting manager cannot be closed. The reason is that the "Close meeting" confirmation dialog box becomes hidden if another tab is on top of the Webex Meetings page.

Full-Screen Video View

When the presenter switches to full-screen video view while sharing his or her screen (formerly called "desktop sharing"), an application, or a document, sharing is paused on the attendee side (the last-shared screen freezes) if he or she has only one monitor. When the presenter exits full-screen video view, sharing automatically resumes.

Attendees stay in full-screen video view when the presenter stops sharing and automatically exits full-screen video view when the presenter starts sharing again.

If the presenter has two or more monitors, he or she can easily share content on one monitor and switch to full-screen video view on another monitor.

Small Webex Meetings Window in Microsoft Surface

The Webex Meetings window in WBS versions earlier than 31.8 open small on a Microsoft Surface device. Text is difficult to read and controls are difficult to use. We recommend upgrading to the latest version of Webex Meetings.

Automatically Restarting a Meeting on a Backup Site

There is no automatic shared state recovery when a site becomes unavailable and automatically redirects to your backup site that was backed up with the Webex Global Site Backup (GSB) system. After the Meeting window reconnects to the meeting on a backup site, the shared state is lost and the presenter must start sharing content.

End-to-End Encryption Using PKI

End-to-end encryption of in-meeting data using a public and private key pair that is provided by the site administrator is no longer supported. End-to-end encryption in a live meeting continues to be available using an automatically generated session key only.

Denied Access on iOS Device After Upgrade

You may be prevented from joining a meeting from your iOS device with the error message "The version of your Webex Meetings application is not compatible with the current Webex service. Upgrade the application now." This is because of a security option to enforce secure access after all mobile app upgrades.

Overlapping Meetings Prematurely Ending

Overlapping meetings may end at the first meeting's end time sometimes.

For example, if a host schedules a daily repeat meeting with 24 hours duration with a starting time of 8:00 a.m. and the meeting supports joining before host 15 minutes before the meeting start, and if the host is not present, the meeting ends at 8:00 a.m. and host and participants must join the meeting again.

Water Mark

Known Issues and Limitations for Cisco Webex Events

view(s) people thought this was helpful

Recording playback on mobile devices

You cannot play back a network-based recording on a mobile device.

Slow Join Times After a Major Upgrade

After a major Webex Meetings Suite upgrade containing more new features than a regular service pack release, you may encounter a long load time, as more files have to be downloaded and installed. Loading times depend on your network's bandwidth and the amount of traffic at the time of the download. In general, load times can range from 20 seconds to 3 minutes or more.

In-meeting experience

  • Keyboard navigation and screen reader support:
    • Video thumbnail items in the Participant panel do not support navigation using the Tab key.

    • Some items in file sharing and in the Polling panel don't support navigation using the Tab key.

    • Items within the video full-screen view don't support navigation using the Tab key.

    • Elements inside the video user interface don't support screen readers.

    • Video thumbnail items don't support screen readers.

    • The participant list within the Participant panel doesn't support screen readers.

    • Some elements for file sharing and in the Polling panel don't support screen readers.

  • The Pan tool is not available when viewing a file that is shared using file sharing.

  • The new interface is not available for Linux users.

  • On Mac, when the presenter annotates during application sharing or screen sharing (formerly called desktop sharing) and takes notes or creates a poll, the Notes and Poll information cannot be saved.

  • On Mac, when using annotation during sharing, if user moves from tab view to full-screen view, the annotation option that as last used is not remembered.

  • On some Windows machines as well as on Linux machines, if attendee screen saver comes on and then the presenter starts file sharing, the screen saver automatically quits.

  • Some custom Quick Start templates, created using older releases of Webex Meetings, may not work after upgrading to this release.

  • In a few cases, uploading a very large Microsoft PowerPoint file to share in the meeting may cause the meeting to get disconnected for the presenter.

Initials in Avatars

The first letter of a user's first name and the first letter of the user's last name are used in avatars when there is no image available. Users with second names comprised of more than one word will not be displayed correctly as three letters, for example, "Mary Van Buren" and "Robert Smith Jr." will display as "MB" and "RJ" respectively.

Shared documents display quality

Webex Meetings uses a printer driver interface to import documents that are not natively supported. The presentation quality of documents shared in Print Driver mode, such as Microsoft Word, Excel, and Adobe PDF documents, cannot be better than a hard-copy printout of the same document printed by a physical printer. This issue is particularly pronounced when these documents contain images of text.

Attendee invitations

If a host removes any attendees for an event, the link to the event from the invitation will no longer be valid for those removed attendees. If you are planning to invite people for a mass-mailing list, we recommend that you use a third-party mailing service, and then link to the event address for attendees.

Host Role Taken Over by a Joining Alternate Host

In some circumstances, the host role may be taken over by an alternate host when joining a meeting or session, even if the host has already joined. If this occurs, we recommend the alternate host assigns the host role back to the host.

Links generated by Webex Meetings and Webex recording services

As part of our continuing updates to improve security, Cisco is making changes to improve the management of cryptographic keys used to generate URLs used in the Webex Meetings Suite and Webex recording services. As a result, existing links that were generated by those services have been updated, and in some cases, users may need to request new links.

Joining a Webex meeting on Chrome and Firefox

Because of Google and Mozilla policy changes, users must manually enable the Webex plug-in when using Chrome and Firefox.

One event at a time

Mac users can join only one event at the same time.

Multi-monitor Support in Windows 10

Shared content may get cut off or display partially when sharing from a secondary screen that has a higher resolution than your primary screen. To remedy this, we recommend that you set your largest display to be your main display in your Windows display settings.

Microsoft Office 2013 and later Support

  • If you have Microsoft Office 2013 or later installed, the following features are not supported when sharing PowerPoint files:
    • Animations and transitions
    • Embedded video or audio files
    • UCF Toolkit
  • If you have customized your Info Tab, some custom elements may not be supported. We recommend that you validate it to make sure it continues to display properly in a Webex meeting.
  • In a few cases, the following problems may occur:
    • Text and fill colors may be slightly different from the actual colors in a slide.
    • Some graphic elements may be missing from a slide.
    • Fonts may appear blurry on a slide or may be different from the original.
    • The size of shapes may be different from the original.
  • If an object in a PowerPoint presentation does not display correctly in edit mode, it is automatically removed in Slide Show view; however, the object may continue to display when the file is shared in a Webex meeting.
  • You cannot share password-protected PowerPoint 2013 files using the file sharing feature. Use the application sharing or desktop sharing features instead.
  • You cannot share Excel 2013 files on Windows 8 using the file sharing feature. Use the application sharing or screen sharing (formerly called "desktop sharing") features instead.
  • You cannot share Word 2013 (64-bit) documents on Windows 8 (64-bit) using the file sharing feature. Use the application sharing or screen sharing features instead.

Shared documents display quality

Webex Meetings uses a printer driver interface to import documents that are not natively supported. The presentation quality of documents shared in Print Driver mode, such as Microsoft Word, Excel, and Adobe PDF documents, cannot be better than a hard-copy printout of the same document printed by a physical printer. This issue is particularly pronounced when these documents contain images of text.

Streaming media sharing

Attendee video resolution is optimized to 480p. Video files with higher resolution are resized to fit (640 X 480) resolution. The following media file formats are currently supported: WMV, WMA, WAV, MP3, ASF, AVI, MPG, MPEG, FLV, F4V, and MP4.

Recommended System requirements for video file sharing on Presenter side:

  • Core2-Duo E6750 @ 2.66GHz for VGA file is required

  • AMD 9650 2.3GHz (4 core) 8GB is preferred

  • Intel® Core™ 2 Duo -E7400 2.8GHz 2.79GHz is preferred

HTML email content

The content of the default HTML email and its corresponding iCalendar (.ics) template are not the same [295149]

Description in iCalendar attachment

Due to an Outlook calendar limitation, the event description will not display in the iCalendar attachment if description exceeds a certain length. The description does not display if the field length exceeds these limits:

  • In Microsoft Outlook 2000 the field length limit is 8KB.

  • In Microsoft Outlook 2003 the field length limit is 4KB.

  • In Microsoft Outlook 2007 there is no limit for field length. [271477]

Play button in Flash files

When a presenter is sharing a Flash (.swf) file, clicking the Play button will "pause" the file instead of playing it. The Presenter needs to press the Play button twice in order to play the file. [289318]

Deleting meetings from My Meetings list

When the Delete from My Meetings when completed option is selected, an event still appears on the My Webex -> My Meetings list if the host completes the event before the end time of event. The event is deleted from the My Meetings list after the schedule end time has elapsed. For example, if an event is scheduled for 10:00 to 11:00 a.m. and the host ends the event at 10.45 a.m., the event is still displayed under My Meetings and the Webex Event Calendar until 11.01 a.m., after the scheduled end of the meeting. The event always displays when you turn on Show past events.

Participants Panel on Solaris

Some non-English characters do not display correctly in the Participants Panel on Solaris machines. [276651]

Switching poll coordinator role

During polling, if you switch the polling coordinator role, the Save Polling Result window will display.

Adding attendees to address book

From the event scheduler, if you select the option to add an attendee to your address book, an error message displays when you click Add Attendee

iCalendar attachment

When Webex Meetings sends the first and second event reminder to attendees, the iCalendar attachment that attendees use to automatically add the event to their calendar application is missing.

Email messages with iCalendar content

Due to an .ics limitation (iCalendar attachment), HTML email messages can not display content of .ics calendars properly. As a result, for HTML email messages, we will pull in the content from plain text email messages. This means if a user has customized an HTML email message, the customization can not be reflected in the iCalendar attachment.

Importing a CSV file when Creating an invitation list

When creating an invitation list, the option to import a CSV file is not supported for MAC. As a result, the Import CSV files button is unavailable for MAC and Safari.

Past events

The past event identification criteria is not consistent between the Webex Events page and Welcome pages. According to Webex Events logic, an event belongs to past events after the scheduled start time is passed. However, if the scheduled start time has passed, the event is still listed on the Welcome page, even when Show past meetings is not selected. [244342]

Past events status shows on the Webex Events calendar for attendee's view. When an attendee looks the Webex Events calendar and selects Show past events, all past events are displayed with Register and/or Not started status; however, no status should appear for past events on an attendee's view. [244153]

Event templates

When a host saves the event as a template, the list of attendees and panelists is not saved; however, the panelist information and the panelist password are saved. [180534]

Money symbol

The money symbol is missing for the budget field on the program information page. [183019]

Panelist information as search criteria

Panelist information can not be used as a search criteria on the Webex Events search page. However, the search can be done from the Welcome page [177716]

Saving user information when using Firefox

If a user is using Firefox, user information always is saved, regardless of whether Remember me on this computer is selected. [228112]

Calendar display of daily audio-only events

Since Webex Events does not have a concept of a recurring event, if a daily audio-only event is scheduled, the Webex Events calendar can not display it properly [161351]

Water Mark

Known Issues and Limitations for Cisco Webex Training

view(s) people thought this was helpful

Links generated by Webex Meetings and Webex recording services

As part of our continuing updates to improve security, Cisco is making changes to improve the management of cryptographic keys used to generate URLs used in the Webex Meetings Suite, and Webex recording services. As a result, existing links that were generated by those services have been updated, and in some cases, users may need to request new links.

Slow Join Times After a Major Upgrade

After a major Webex Meetings Suite upgrade containing more new features than a regular service pack release, you may encounter a long load time, as more files have to be downloaded and installed. Loading times depend on your network's bandwidth and the amount of traffic at the time of the download. In general, load times can range from 20 seconds to 3 minutes or more.

Host Role Taken Over by a Joining Alternate Host

In some circumstances, the host role may be taken over by an alternate host when joining a meeting or session, even if the host has already joined. If this occurs, we recommend the alternate host assigns the host role back to the host.

Multi-monitor Support in Windows 10

Shared content may get cut off or display partially when sharing from a secondary screen that has a higher resolution than your primary screen. To remedy this, we recommend that you set your largest display to be your main display in your Windows display settings.

Microsoft Office 2013 and later Support

  • If you have Microsoft Office 2013 or later installed, the following features are not supported when sharing PowerPoint files:
    • Animations and transitions
    • Embedded video or audio files
    • UCF Toolkit
  • If you have customized your Info Tab, some custom elements may not be supported. We recommend that you validate it to make sure it continues to display properly in a Webex meeting.
  • In a few cases, the following problems may occur:
    • Text and fill colors may be slightly different from the actual colors in a slide.
    • Some graphic elements may be missing from a slide.
    • Fonts may appear blurry on a slide or may be different from the original.
    • The size of shapes may be different from the original.
  • If an object in a PowerPoint presentation does not display correctly in edit mode, it is automatically removed in Slide Show view; however, the object may continue to display when the file is shared in a Webex meeting.
  • You cannot share password-protected PowerPoint 2013 files using the file sharing feature. Use the application sharing or desktop sharing features instead.
  • You cannot share Excel 2013 files on Windows 8 using the file sharing feature. Use the application sharing or screen sharing (formerly called "desktop sharing") features instead.
  • You cannot share Word 2013 (64-bit) documents on Windows 8 (64-bit) using the file sharing feature. Use the application sharing or screen sharing features instead.

Microsoft Office PowerPoint

In Microsoft PowerPoint 2007 and later, text copied from a web page and pasted into Notes panel may not render properly. The workaround is to copy the text into Microsoft Word or Microsoft Notepad, then copy the text again from that editor in the Note panel.

Shared documents display quality

Webex Meetings uses a printer driver interface to import documents that are not natively supported. The presentation quality of documents shared in Print Driver mode, such as Microsoft Word, Excel, and Adobe PDF documents, cannot be better than a hard-copy printout of the same document printed by a physical printer. This issue is particularly pronounced when these documents contain images of text.

Streaming media sharing

Attendee video resolution is optimized to 480p. Video files with higher resolution are resized to fit (640 X 480) resolution. The following media file formats are currently supported: WMV, WMA, WAV, MP3, ASF, AVI, MPG, MPEG, FLV, F4V, and MP4.

Recommended System requirements for video file sharing on Presenter side:

  • Core2-Duo E6750 @ 2.66GHz for VGA file is required

  • AMD 9650 2.3GHz (4 core) 8GB is preferred

  • Intel® Core™ 2 Duo -E7400 2.8GHz 2.79GHz is preferred

High-definition video

High-definition video is available for the main session only. There is no support for breakout sessions at this time.

High-quality video

High-quality video is available for the main session only. There is no support for breakout sessions at this time.

Operating system limitations

If you use Solaris or Linux you cannot:

  • Display UCF PowerPoint animations and transitions

  • Cache course material before the session starts

  • See the attendee-ready indicator

  • Use Webex Meetings integrated video

  • Record sessions with the Webex Meetings Recorder or edit them with the Webex Recording Editor

  • Play a training session recording file (WRF format) on Solaris or Linux

  • Use PCNow

  • Install the Integration to Microsoft Outlook

  • Conduct Hands-on Labs

The Linux platform does not support the new interface, Training Control panel, streaming video sharing, computer audio enhancements, new participant panel, and high-quality video behavior, including full-screen video behavior.

On Linux, presenters cannot share Microsoft Office, Open Office, or Star Office files. Only UCF file sharing is supported

If you use the Mac platform you cannot:

  • Install integration to Microsoft Outlook

  • View PowerPoint Notes in a panel

  • Use Quick Start

  • Invite or Remind attendees from Session Option tray during full screen document sharing, application and desktop sharing

  • Set Hands-On Lab options

  • Record sessions to a local computer with the local Webex Meetings Recorder or edit them with the Webex Recording Editor (.WRF format only).

Other Mac limitations

  • Mac users can join only one session at a time.

  • If a host on a Mac assigns the Presenter role to an attendee on a Mac, and at the same time has polling list, invite options, or Q&A tab options open, these options do not automatically close for the new presenter if she does full-screen or Application/Desktop sharing

  • A host cannot start a session on a Mac simultaneously while viewing a Webex Meetings Network Based Recording.

  • Chat and Q&A text box does not have a scroll bar when entering large amounts of text in the message

  • If an attendee switched to a presenter role while taking a test, they still can take the test.

  • Attendees can see the Presenter's Sharing menu during desktop share, if the latter is on an Intel Mac.

  • When doing desktop share, if Presenter tries to simultaneously assign attendees to breakout sessions from the Session Options tray, the panel overlaps the Assignment dialog and this dialog disappears if the presenter clicks anywhere on the desktop.

  • Scroll bar space for polls always appears, even if there is no scroll bar

Session options always appears on top of other windows if opened during desktop share and using other functions from the session options tray.

Attention tracking

If an attendee is on Solaris or Unix and they take a test within the session, they are assumed to be always paying attention in the session for as long as they are in the session during and after completing the test.

Registering for recurring sessions

In the case of single recurring sessions, if a registered attendee from a later session is manually invited by the presenter into the current ongoing session, they will lose their registration from the session they originally registered for and show up as an attendee of the current session in the usage reports.

Meta data name

The meta data name when entering data for SCORM 2004 cannot include certain special characters, even if the original session included these characters in the title.

Registering through email link

If an attendee is invited to register for a session and clicks on the email link to do so, their name is not pre-filled in the registration form.

Host account files

If your host user account is deleted, your files are still included in the site storage space allocation.

Network-based recording

  • The network-based Recorder does not record:

    • Private chat sessions with hosts

    • Polling results (unless the results are shared with attendees)

    • Test and breakout sessions

  • Webex Meetings Advanced Recording Format (.ARF) files are supported in the UCF Viewer.

Disabling Quick Start

If your site administrator disables the Quick Start page in the session type and you save a scheduling template for this session type, Quick Start still appears in the template's options. However, the Quick Start page does not appear in the session.

Closing dialog windows in the Firefox browser

When using Firefox, some dialog windows may not close when clicking the Close or OK button due to a technical limitation with Firefox.

Feature enhancements for Macintosh

Feature enhancements in this release are available for Windows, Solaris, and Linux. Enhancements and more feature support on Macintosh will be available shortly after this release.

Water Mark

Known Issues and Limitations for Webex Support

view(s) people thought this was helpful

Known Issues and Limitations for Webex Support

Windows 8.1, and 10

  • For file sharing, you must have Adobe Acrobat Reader to share PDFs.

  • When sharing Microsoft PowerPoint files in Print Driver mode, some content may not appear. We recommend that you use our standard Universal Communications Format (UCF) mode or use application sharing screen sharing instead.

  • When connecting to a remote computer with Windows 10, the local screen will not be able to be blacked out.

  • Webex Meetings attendees are able to save Universal Communications Format Files (UCF) to their computers, even when the host has canceled the save privilege for them.

  • Windows apps do not appear in the Access Anywhere or Remote Access Add Application dialog box.

  • When a Mac participant of a Webex meeting is sharing and annotating the whiteboard, the annotation color is incorrect when the square or oval shape is selected.

Microsoft Office 2013 and later Support

  • If you have Microsoft Office 2013 or later installed, the following features are not supported when sharing PowerPoint files:
    • Animations and transitions
    • Embedded video or audio files
    • UCF Toolkit
  • If you have customized your Info Tab, some custom elements may not be supported. We recommend that you validate it to make sure it continues to display properly in a Webex meeting.
  • In a few cases, the following problems may occur:
    • Text and fill colors may be slightly different from the actual colors in a slide.
    • Some graphic elements may be missing from a slide.
    • Fonts may appear blurry on a slide or may be different from the original.
    • The size of shapes may be different from the original.
  • If an object in a PowerPoint presentation does not display correctly in edit mode, it is automatically removed in Slide Show view; however, the object may continue to display when the file is shared in a Webex meeting.
  • You cannot share password-protected PowerPoint 2013 files using the file sharing feature. Use the application sharing or desktop sharing features instead.
  • You cannot share Excel 2013 files on Windows 8 using the file sharing feature. Use the application sharing or screen sharing (formerly called "desktop sharing") features instead.
  • You cannot share Word 2013 (64-bit) documents on Windows 8 (64-bit) using the file sharing feature. Use the application sharing or screen sharing features instead.

Shared documents display quality

Webex uses a printer driver interface to import documents that are not natively supported. The presentation quality of documents shared in Print Driver mode, such as Microsoft Word, Excel, and Adobe PDF documents, cannot be better than a hard-copy printout of the same document printed by a physical printer. This issue is particularly pronounced when these documents contain images of text.

Operating system support

To run Webex Support:

  • For Customer Support Representatives (CSRs) using Linux, Solaris, or Macintosh, some product features may not be supported. For more information, please refer to Cross-platform Features and Known Issues.

  • Customers can use Linux, Solaris, or Macintosh, but they will not be able to connect to a remote session from behind a Microsoft ISA proxy server with user authentication enabled. This is a known Java issue document by Sun at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4636657.

For more information about the computers, operating systems, and browsers supported by Webex Support, see Webex System Requirements and Feature Support Release Notes.

Crashing while logged in to customer computers

If you log in to a customer computer as a different user and the Webex Support browser crashes, you will remain logged in on customer's computer. When this happens, ask your customer to log off and then log back in again.

Applications show while recording session

When you record a Webex Support session while showing an application to a customer, all other browser windows that are open on you computer will be visible to your customer.

Disk space during file transfers

During file transfers, if the receiving party runs out of disk space, the session will end.

Moving file transfer window during desktop sharing

If you start a file transfer while sharing desktops, you cannot move the transfer window.

Disable system information

Site administrators cannot disable the System Information feature in custom session types.

Lotus Notes email invitation limitation

If you use the Lotus Notes email application, the "send email invitation using local mail client" feature may not work. This happens because Lotus Notes limits the size of email messages that you initiate from Web pages. To resolve this, change your invitation email template to reduce the message size.

Basic file transfer doesn't show up on event log

Files transferred using the basic file transfer method do not show in the event log.

Joining an inbound support session on slow network connection

When client download method is set to TFS (Temporary Folder Solution) for the site, and a customer attempts to join an inbound support session using a slow network connection, a customer may receive the error message "Join Conference confirmation failed" after the customer fills out the entry form and clicks Submit

Scrolling while using Webex Support web chat

When using the Webex Support web chat, after the scrollbars have appeared, quickly scrolling up and down may cause the chat window to flash in quick succession.

Blocked Webex Support functionality

In order to perform certain functions in Webex Support, Webex requires administration privileges in Windows. Without these credentials, some Webex Support functionality is blocked due to insufficient privileges, such as the ability to remotely control the Windows User Account Control (UAC) window, or other applications that require administrator privileges. There are two ways to allow the system to perform these actions:

  • On a system that has never had Webex Support installed, sign into Windows as an administrator to start Webex Support for the first time. After that, user can login with standard user account.

  • A local user with administrative privileges can allow Webex actions that require UAC permission.

Known Issues and Limitations for Remote Access

Joining a WebEx meeting on Chrome and Firefox

Because of Google and Mozilla policy changes, users will need to manually enable the Webex plug-in when using Chrome and Firefox.

Remote Access agents limitation

The Make Screen Blank command is disabled in Windows Safe mode.

Known Issues and Limitations for WebACD

Links generated by Webex applications and Webex recording services

As part of our continuing updates to improve security, Cisco is making changes to improve the management of cryptographic keys used to generate URLs used in Cisco Webex Meetings, Webex Training,Webex Support, Webex Events, and Webex recording services. As a result, existing links that were generated by those services have been updated, and in some cases, users may need to request new links.

Windows 8.1, and 10

  • For file sharing, you must have Adobe Acrobat Reader to share PDFs.

  • When sharing Microsoft PowerPoint files in Print Driver mode, some content may not appear. We recommend that you use our standard Universal Communications Format (UCF) mode or use application sharing screen sharing instead.

  • When connecting to a remote computer with Windows 10, the local screen will not be able to be blacked out.

  • Webex Meetings attendees are able to save Universal Communications Format Files (UCF) to their computers, even when the host has canceled the save privilege for them.

  • Windows apps do not appear in the Access Anywhere or Remote Access Add Application dialog box.

  • When a Mac participant of a Webex meeting is sharing and annotating the whiteboard, the annotation color is incorrect when the square or oval shape is selected.

Water Mark

Known Issues and Limitations for Site Administration

view(s) people thought this was helpful

Branding and customization

  • The new Webex header does not allow branded headers to be less than 75 px. If a branded site has a header height that is less then 75 px and does not have customized header HTML code, the system automatically increases header height to 75 px.

  • The Log in and Log out links for the Site Administration tool are not visible if the header navigation color is blue or a dark color.

If you want to make branding changes, you should contact your customer support manager (CSM).

Safari browser support

The Safari browser is not supported for Site Administration on the Mac.

CMR Hybrid (Webex-enabled TelePresence) meetings

The following issues apply for CMR Hybrid (Webex-enabled TelePresence) meetings:

  • To reduce the possibility of bandwidth issues for video, site administrators should make sure the following site administration options are set for CMR Hybrid users:

    • Make sure that for Webex VoIP and video connection, the Automatically encrypted UDP/TCP SSL option is always selected.

    • Select Site Settings > Site Options and check the maximum video bandwidth option. This sets the maximum video frame rate for in-meeting video. The default setting is 15 fps.

    • Under "OneTouch TelePresence Options," make sure Enable TelePresence bandwidth control is checked unless Webex Support recommends altering it.

    • Under "Meeting Options," make sure that Turn on high-definition video is turned on so that resolutions higher than 360 p can be sent.

    For additional information about recommended bandwidth configuration settings for CMR Hybrid meetings, see "Prerequisites" in the Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide on the Cisco TelePresence Management Suite (TMS) Configuration Guides page.

  • Site administrators should also make sure that Webex Meetings PRO TelePresence session type is enabled for your site:

    • Webex Meetings PRO TelePresence session type will give users a different user interface in the Webex Productivity Tools integration to Microsoft Outlook than the standard Webex integration with Outlook.

    • If you want existing users on your site to use CMR Hybrid, you need to batch-enable them for Webex Meetings Pro TelePresence session type-it is not enabled for them automatically.

    • When your site is enabled for CMR Hybrid, the Default for New Users checkbox is automatically checked next to Webex Meetings PRO TelePresence session type site administration option. If you do not want new users to be enabled for CMR Hybrid automatically, you should uncheck the Default for New Users checkbox.

    • You can also create additional custom session types based on Webex Meetings TelePresence session type.

  • Site administrators cannot make any changes to CMR Hybrid user interface for Webex Productivity Tools. For example, administrators cannot change the branding for the CMR Hybrid Meeting Options panel within the Outlook integration, cannot hide information in the Meeting Options panel or in the TelePresence or Webex Advanced Settings dialog boxes, and cannot limit the number of video call-in participants the user can enter.

  • Although screen sharing (formerly called "desktop sharing" and application sharing are supported in CMR Hybrid meetings, some standard sharing features, such as file sharing, annotation, and whiteboard sharing, are not supported in CMR Hybrid meetings.

  • Recording is supported for CMR Hybrid meetings; however, it has the following known issues and limitations:

    • CMR Hybrid meeting recordings will be in MP4 format. Video will be recorded at 360 p.

    • When users play back the recording, they can see screen sharing, application sharing, active speaker video camera feeds, the participant, list, chat, and polling. However, if users download the recordings, the screen sharing, application sharing, and audio portion is in one MP4 file, and does not contain active speaker video camera feeds, the participant list, chat, and polling.

    For more information about recording CMR Hybrid meetings, see Recording and Playback FAQs in the Webex Meetings Frequently Asked Questions.
  • If you do not have adequate bandwidth, your presentation and data sharing in Webex video conferencing and CMR Hybrid meetings can degrade to XGA (1024 x 768 resolution) and 5 fps. On TelePresence systems, users see a "letterbox" format. Up to 720 p resolution is supported as long as all Webex participants have at least 2 Mbps, and the data sharing can cover the whole TelePresence system screen on both 4:3 and 16:9 TelePresence systems without cropping. With TelePresence Server 4.1 and Conductor XC 3.0, 1080 p resolution is supported as long as all Webex participants have at least 3 Mbps. If any participants in the meeting do not have the minimum bandwidth, all participants will drop to the next lowest data sharing resolution level. For example, if 720 p resolution was used, but one participant has bandwidth that is below the threshold, the meeting resolution drops to 720 p for all participants. Or, if TelePresence Server 4.1 and Conductor XC 3.0 are used, 1080 p would normally be supported, but if one participant does not have least 3 Mbps, the data sharing resolution drops to 720 p for all participants. The presentation and data sharing quality from TelePresence system to TelePresence system does not change, and the resolution is based on TelePresence Server or Cisco TelePresence MCU series settings. The presentation and data sharing quality from Webex application to Webex application is good quality. These presentation and data sharing quality limitations do not apply to Webex-only meetings, which use a proprietary data rendering format.

    For a list of compatible video systems and applications see Webex Meetings Video Compatibility and Support

  • Screen sharing (formerly called "desktop sharing") and application sharing are supported in CMR Hybrid meetings, but some standard content sharing features, such as file sharing, annotation, and whiteboard sharing, are not supported.

  • Starting with Cisco TelePresence Management Suite (Cisco TMS) version 14.4, administrators can configure Cisco TMS to allow TelePresence participants to join a CMR Hybrid meeting up to 5 minutes before the scheduled start time. TelePresence doesn't join the meeting until the first TelePresence participant dials in to the meeting. Cisco TMS does not dial out to Webex until the scheduled start time of the meeting. For more information, see "Configuring Allow Early Join" in the "Configuring Conference Settings in Cisco TMS" section of the Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide on the Cisco TelePresence Management Suite (TMS) Configuration Guides page.

  • CMR Hybrid meetings do not support "VoIP Only" audio.

  • Scheduling large CMR Hybrid meetings requires that administrators set capacity limits. To mute everyone except the speaker, participants need to be muted in both Webex and TelePresence:

    • From the Webex application, the host can mute Webex participants.

    • On some TelePresence systems, the host can mute other TelePresence participants; otherwise, the administrator can mute TelePresence participants through TelePresence Server.

Water Mark

Known Limitations for Cisco Webex Meetings for Google

view(s) people thought this was helpful

  • If a user who has more than one Webex account signs in to one Webex account (such as companyA.webex.com) in the Chrome browser, and then signs in to the Cisco Webex Meetings for Google extension with the user’s Google account, and uses a different Webex account (companyb.webex.com) with different credentials, that user will not be able to sign in to Cisco Webex Meetings for Google. If this problem occurs, the user should sign out of the Chrome browser and clear cookies, and then try to sign in again to Cisco Webex Meetings for Google.

  • If a user signs in to Google calendar with one Google account, and then signs in to Cisco Webex Meetings for Google with a different Google account, when the user selects Schedule Meeting in the Cisco Webex Meetings for Google window, the calendar won’t open and won’t display the scheduled meeting, even though the meeting may have been scheduled successfully.

  • If a user’s Personal Room meeting settings change, those changes won’t be reflected in Cisco Webex Meetings for Google automatically. Personal Room meeting settings changes are synchronized when the user restarts the Chrome browser, or signs in to Cisco Webex Meetings for Google again, or signs in to his or her Webex through Cisco Webex Meetings for Google.

  • When the host adds Webex Personal Room meeting to a meeting in his or her Google Calendar, a confirmation appears that includes the video address, but invitees do not see this video address. However, invitees can see the video address and the meeting link in the invitation.

  • Sometimes the Cisco Webex Meetings for Google window doesn’t display completely. If this happens, the user can try double-clicking the Cisco Webex Meetings for Google icon in the Chrome browser.

Was this article helpful?

Related Articles

Recently Viewed

Didn’t find an answer to your question?

Didn’t find an answer to your question?

Contact us
Didn’t find an answer to your question?
Didn’t find an answer to your question?