The following is a set of frequently asked questions we've collected from early developer discussions. CCP is designed to search the Internet for customer postings which are referred to in CCP as "Social Contacts". CCP will use standard search interfaces to query and standard results formats to capture results. For example, many social media sites support OpenSearch and RSS or ATOM to return results. CCP is packaged as a virtual machine applicance. The operating system (Linux), the application software, and the database are all bundled together in a VMWare virtual machine. Larger deployments may have a cluster of CCP virtual machines. The specific hardware requirements for CCP will depend on deployment size. Not at this time. It is a stand-alone component, although the UI can be optionally configured to run in Quad. The released version of the product will likely be integrated with Cisco Unified Intelligence Center for advanced reporting capability. A future version (2011) will include universal queue integration with Cisco Unified Contact Center Enterprise. All of the CCP user interface elements are implemented as OpenSocial Gadgets. The CCP system will install with a built-in OpenSocial gadget container to control layout and look-and-feel for the gadgets. The combination of the gadgets plus container provides a complete thin-client user interface for CCP. Note: the default container that ships with CCP will share source code with Cisco Quad, providing consistent look and feel to the complete Quad solution. It should also be possible to run the CCP gadgets in any standard OpenSocial gadget container. The gadget source code will be open-source, so customizations will be possible. CCP will have several ways to distribute social postings or work. Note: in some cases interested parties may want to just look/see the postings. In other cases, there may be staff (or systems) assigned to handle/respond to the postings. It is not clear at this point what options will be available in what timeframe but the following list provides the choices in likely order of availability: 100% of CCP functionalty is accessible through REST API's. This includes all setup/configuration as well as user capability. The API's will all be documented in the CCP API documentation. All shipping UI/Gadgets will be implemented using the published APIs. All technical documentation for CCP will be available on this technology center. Note: the API documentation for CCP is being written in parallel to the development of the software therefore you will not find documentation on features that have not been implemented even if they are anticipated for the first release of the product. As of May 2010, CCP is available via a hosted pilot on an invite only basis. If you have an interested in developing to CVP you can contact Product Management via the forum here:Getting Started With CCP
How does CCP find postings?
What is the CCP packaging?
Does CCP require depend on any other Cisco components?
What is the CCP user interface?
How does CCP Queue/Assign Postings?
What API's are supported by CCP?
What documentation is available for CCP developers?
How can I get CCP?
Where do I go for help?
All questions about CCP should be posted on the Forums area of this Tech Center?
Is there a Service Level for the forums?
Sorry, at this time we can't committ to a service level for replies but we will be monitoring the forums closely and we'll reply as quickly as possible.