Cisco Cisco MeetingPlace Gateway SIM Anleitung Für Quick Setup

Customer Premise Equipment (CPE) customers who implement SSO software integrations on their 
Cisco Unified MeetingPlace Web Servers do so at their own risk and are responsible for understanding 
the technical implementations and feasibility of SSO integrations on their systems. 

By allowing SSO software integrations, we do not claim support for any SSO software packages or 
vendors. 

Using SSO software integrations requires proper configuration of Cisco Unified MeetingPlace Web 
Conferencing systems through the Admin pages. If your SSO software integration requires a change in 
the Web Conferencing product source code, your SSO integration becomes an SSO customization, and 
we do not support customizations by either customers or any other parties. 

Any CPE customers who want to integrate SSO packages can contact Cisco Managed Services to obtain 
a Service Request to implement SSO. This service is offered as a convenience and does not change the 
scope of the SSO integration: this service is an integration and configuration of the Web Conferencing 
product, not a customization of the product code. 

Customers must first implement SSO software integrations on test or lab servers and verify that the 
integrated systems work, including Web Conferencing features and operations. 

Customers are responsible for ensuring stability of integrated Web Conferencing-SSO systems, 
including communicating with SSO software vendors for the following reasons: 

To obtain necessary fixes and support 

To troubleshoot functional problems and technical problems, including crashes triggered by the SSO 
package 

Many SSO software products include a web-server extension, called the IIS ISAPI extension or filter. 
Web Conferencing installs and uses four IIS extensions. Any incompatibility between an SSO software 
extension and the Web Conferencing extensions can make IIS non-functional or unstable. Any crash of 
the SSO IIS extension can cause IIS to crash and can generate a full Web Conferencing outage, resulting 
in a full system restart, ending of in-progress meetings, and disconnecting of Web Conferencing users. 
Any memory leak in the SSO package or module can make IIS or the whole server unstable, as well. 

When you restart the web server, all manual changes made to the registry are lost.

Although SSO software integration is productized for the Web Conferencing system, any changes in 
overall configuration, including Web Conferencing upgrades and SSO package upgrades, can potentially 
break integrated Web Conferencing-SSO systems.