© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Unity Connection 2.0 Architecture TOI Part I – System Level Overview June 2007

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 2 Business Goals  Increased attach rate with CuCM  Co-residency with other VTG Products  Address mid-market product offering  Address customer requests for non-Microsoft solution  Facilitate architecture, design, code sharing and collaboration within VTG

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 3 Architecture Plans  Provide co-resident solution with IPCBU CuCM Move to UCOS/CuCM Platform Move to Linux Move to Informix Move to Appliance Model  Provide standalone solution on same code-base  Support mid-market scale and feature set  Make strategic steps towards interoperability

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 4 Architectural Activities  Porting Linux, UCOS, Informix, OpenSpeech, Mixer, Utf-8  Collaboration Co resident Architecture, Administration/Serviceability Model, Installation/Upgrades/Rollback/Backup/Restore framework, build, and hardware platforms  Interoperability VM Interop (VPIM), External services (Exchange 2Kx, MPE), and Phone Apps  Phase Containment/Verification Code review procedures, daily unit test, On-demand/weekly static analysis, and early/continual load testing

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 5 Key Concepts  Appliance Model: Abstraction of underlying operating system, platform etc. No direct external access to db or file system (blocked by ip tables)  Single-sign-on: In co-residency the ability to access either products web applications with a single logon. This is facilitated by the Identity Management System (IMS), which also allows a single set of credentials for pin and password used by user facing applications.  Sleeping seadragon: Use of CuCM/UCOS as an appliance platform. Allows platform and serviceability subsystems to be leveraged, though the entire CuCM application is installed (unused subsystems are disabled or “sleeping”)

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 6 Architecture Diagram

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 7 Architecture Changes  Services removed from Connection 1.x: Server Roles Manager SRM – deferred till Connection goes multi-box Stream Server – deferred till Connection goes multi-box Voice Processing Gateway – Windows/COM artifact. No longer needed Media Admin - Incorporated into CUCA Media Service Watcher – Speechworks replaced by OpenSpeech

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 8 Architecture Changes  Services added to Connection 2.0: Connection DB (unityoninit) – Connection Informix dbms instance Connection Mixer (CuMixer) – Provides media processing. Replaces processing done by TSP/AvWav. Connection SMTP Server (CuSmtpSvr) – SMTP server replacing IIS SMTP in Connection 1.x. Used to support VPIM. Connection CM Database Listener (CuCmDbEventListener) – Synchronizes changes between Call Manager’s Database and Connections. Connection Reports Data Harvestor (CuScavenger) – Reports data collection service Connection Voice Recognizer – Nuance OpenSpeech ASR engine

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 9 Architecture Changes  Web Applications added to Connection 2.0: Connection Serviceability (CuService) – Serviceability web application Connection RSS (CuRss) – Connection RSS voice mail feed (first look)  Web Services added to Connection 2.0: Connection Realtime Monitoring APIs

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 10 Architecture Changes  UCOS/CuCM subsystems leveraged: AlarmInterface – For Event log replacement CLI – For troubleshooting DRS – For backup/restore IMS – For authentication and single sign-on support Option Installer – For installing language packs Performance Interface – For perf counters RTMT – For trace/alarm gathering and Port Status Monitoring SDITrace – For diagnostic logging ServM – For Windows Service Control Manager replacement Setup – For install, partition switch upgrade/rollback, ES

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 11 Limitations Not delivered in Connection 2.0  No multi-box support (no failover, digital networking, or clustering)  No FAX integration  Mid-market scalability (3k users)  No SMS/SMPP support  No direct access to file system or database  No corporate directory integration  Limited MCS Configurations (fixed drive and partition configurations)

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 12 Summary  The Connection 2.0 release represents a significant architectural change to the product to provide a non-Windows mid-market solution  Connection 2.0 leverages the CuCM/UCOS platform to provide both the CuCMBE coresidency solution and Unity Connection 2.0 standalone version  Connection 2.0 completes a key milestone in the roadmap for the Unity Connection Product

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 13 References  EDCS – Lucas PRD  EDCS – Lucas SFS  EDCS – Lucas SAP

© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 14 Q and A