January 23-26, 2007 Ft. Lauderdale, Florida Right Sizing Your IP PBX Determining the Approach that Fits Your Enterprise TMC University Patrick W. Henkle Sphere Communications

January 23-26, 2007 Ft. Lauderdale, Florida 3 Agenda What we will cover Define “Right-Sizing” Telephony Past and Present Key Considerations –System Architectures –5 - W’s of VoIP –Deployment Scenarios –Sample Planning Methodology What we will not cover Specific Vendor Implementations Feature Details Protocol Wars

January 23-26, 2007 Ft. Lauderdale, Florida 4 “In theory there is no difference between theory and practice. In practice there is.” Yogi Berra

January 23-26, 2007 Ft. Lauderdale, Florida 5 Right-Size Defined right·size Pronunciation: 'rIt-"sIz Function: transitive senses: to reduce (as in a workforce) to an optimal size intransitive senses : to undergo a reduction to an optimal size Source: Websters On-line dictionary

January 23-26, 2007 Ft. Lauderdale, Florida 6 R i g h t - S i z i n g P r o c e s s Legacy PBX IP PBX Media “Library” Communication Rules/Policy Database Feature Services Call & Media Control Presence Services Messaging Services Media Services Standards Based Interfaces Session Management Distributed Processing High Availability

January 23-26, 2007 Ft. Lauderdale, Florida 7 Right-Sizing an IP PBX Does not mean “make it smaller” – although that is usually an attractive outcome! It means selecting a solution that is the right size for you today, but that can also grow with you in the future. –This should not mean “grow into” in the future. –This should not mean replace with a new one in the future. It also means selecting a solution that will continue to “add value” in the future, in addition to “capacity”.

January 23-26, 2007 Ft. Lauderdale, Florida 8 Telecommunications Past and Present +100 years of progress Telecommunications has changed in many ways over the last century. However, one aspect remains essentially the same the plain old telephone.

January 23-26, 2007 Ft. Lauderdale, Florida 9 Enterprise Telecom Past Each phone plugged directly into the legacy switch. When the card was full, you had to add another card; when the switch was filled to capacity, you bought a new phone system, or multiple phone systems.

January 23-26, 2007 Ft. Lauderdale, Florida 10 Why is this a concern? Legacy PBX solutions have fixed capacities based on hardware limited technology. In other words, you can’t add more than 16 stations to a 16-port card. IP-PBX solutions do not have to be limited by the same constraints! The right platform can grow with you over time.

January 23-26, 2007 Ft. Lauderdale, Florida 11 Applying Moore’s and Metcalf’s Laws to Enterprise Telecom Integrated Circuits will double in power every year! Time MIPS N 2 -N The value of a distributed communications network... Moore’s Law Metcalf’s Law

January 23-26, 2007 Ft. Lauderdale, Florida 12 Telecom Today – Distributed IP Services VoIP Manager BranchHub PSTN AnalogDevices (Desktop, Fax, Conference,Modem) Facility 1 VoIP Manager AnalogDevices Facility 2 PSTN Facility 3 SOHO Legacy PBX Multi-mediaCommunicationDesktops T1/E1/PRI Analog FXO Trunks IPTelephones (Vmail, Unified Messaging) WAN IPTelephones IP Telephones IP Integrated Desktop VoiceMessaging MeetingHub COHub Mobile User VoIP Manager COHub PhoneHub IP Connectivity (Ethernet or WAN) Digital Trunks (T1, E1, ISDN PRI) Analog Lines (PSTN or Stations) * requires private network connectivity via, typically via a VPN connection Key: PSTN Analog FXO Gateways (IP Conference Hub) Internet* IP WiFi Telephones

January 23-26, 2007 Ft. Lauderdale, Florida 13 IP WAN PSTN Don’tJust“Change the Wire” IP WAN PSTN Unified Communications Enterprise VoIP Typical Business IT Services Multi-media communications Presence enhanced apps. Click to dial Contact management

January 23-26, 2007 Ft. Lauderdale, Florida 14 IP PBX Architectural Approaches Extended Life TDM over IP Purpose Built IP IP Enabled Hybrid Client Server Ideal for extending the life of a Legacy PBX Often used for tie line migration to IP Lowers TDM Trunk costs Ideal for small scale systems (<100 stations) Dependant on embedded call processing modules Redundancy is a challenge Most scalable approach Most flexible approach – can also be used as a legacy PBX migration strategy Greatest amount of change PSTN IP WAN IP LAN Legacy TDM PBX IP Trunks Media Gateway PSTN IP WAN IP LAN Media Gateway Telecom Servers PSTN IP WAN IP Trunks IP Stations TDM Trunks Telecom Server Analog Stations IP LAN SIP PSTN

January 23-26, 2007 Ft. Lauderdale, Florida 15 Evolving Enterprise VoIP Alternative Approaches (Generalized) Software Centric Network Agnostic Open Standards Oriented System Flat / Distributed Architecture N + 1 Redundancy Simplified Configuration Software Enabled / Bundled Features Add-on Upgrades for Expansion Multi-Vendor Devices and Apps. Best of Breed Options Costs Less Internet Model Hardware Centric Network Dependant Closed / Proprietary Systems Hierarchical / Centralized Architecture N times 2 Redundancy – if any Complex Configuration Costly Add-on Features Forklift Upgrades for Expansion Vendor Specific Devices & Apps. Single Vendor Solution Costs More Legacy Model Hybrid TDM/IP Client / Server

January 23-26, 2007 Ft. Lauderdale, Florida 16 5-W’s: Key Questions to Answer Why VoIP? What is driving this decision? Economics, Applications, Productivity, Obsolescence, etc. Where VoIP? Where do you require VoIP? All offices, some offices, all employees, some employees, etc. When VoIP? What is the best timing? How can the deployment be phased in? How can the timing match budgetary requirements? What VoIP? What applications or services would be best delivered via VoIP? All Telecom services, niche functions or applications, etc. Who VoIP? Which solutions best fit your needs? Can you start small and grow economically? How can you leverage best-of-breed components?

January 23-26, 2007 Ft. Lauderdale, Florida 17 Why Should You Consider VoIP? Why VoIP? Your Legacy PBX is obsolete, too costly to service, or out of capacity. Continued investment results in a stranded asset that is not fully depreciable. You have a high population of “knowledge” workers that can realize the increased productivity of “enhanced services”. Integrated voice, video, text and unified messaging. Personalized call management. Integration with other business applications (CRM, ERP, Workflow). You are rapidly expanding and a converged solution is easier to deploy, maintain and grow. New office locations, mergers / acquisitions, mobile workforce, etc.

January 23-26, 2007 Ft. Lauderdale, Florida 18 Where Should You Implement VoIP? Where VoIP? Which employees would benefit the most? Knowledge workers, executives, call center agents, mobile sales force, etc. What locations are the best fit? Remote offices, HQ, new offices? Which networks are capable today? Which ones will require upgrades? All LAN’s, most LAN’s, WAN connected remote offices, mobile workers?

January 23-26, 2007 Ft. Lauderdale, Florida 19 When Should You Deploy VoIP? When VoIP? What is the appropriate sense of urgency? Is there an immediate problem that can be solved? Obsolete TDM system. New office locations. Should you start by “extending the life” of your current system? How can you leverage this opportunity to begin positioning for your future needs? If possible, develop a phased approach over 6, 12, 18 months.

January 23-26, 2007 Ft. Lauderdale, Florida 20 What Are Your Best Applications for VoIP? What VoIP? Should you replace all legacy systems with VoIP? Can you continue to leverage VoIP to extend the life of your existing system? If so, how will that solution allow you to expand easily and cost effectively. Can the VoIP platform start small and easily grow to meet my longer term needs? If so how and at what cost? How can you utilize a “best-of-breed” approach to the solution including 3 rd party devices? What choices do you have for: phones, call processing, voic , etc. from different providers?

January 23-26, 2007 Ft. Lauderdale, Florida 21 Which Vendor(s) Can Best Meet Your Needs? Who VoIP? What is their core business / competency? Experienced with Voice or Data Applications? Experienced with Legacy voice, or VoIP? Open solutions vs Closed solutions? Implications on longer term Total Cost of Ownership! Multi-Vendor Components vs Single Vendor Components? Avoid being locked into a single source solution! Software Application focused vs Hardware / Network focused? Leverage the IT services deployment model. Separation of applications from the underlying connectivity.

January 23-26, 2007 Ft. Lauderdale, Florida 22 IP PBX Deployment Scenarios Technology Evaluation Proactive Introduction Full Scale Adoption Exploratory Cap and Grow Greenfield Proactive evaluation of the technology and capabilities. Limited reach within the organization initially. Controlled roll out. Minimize capital expenditures. Cap investments in legacy solutions. Selective introduce capabilities to targeted users. Solve practical business needs. Understand the larger picture and potential. Lowest Risk Ensures readiness for the future May represent throw away investment Balanced Approach Manages obsolescence effectively Does not realize full benefits Expansion may be a challenge Full benefits are realized Best ROI Greatest change Greatest Risk Deploy IP at all new locations. Replace legacy systems. Mandate use of enhanced services. Actively pursue productivity advantages.

January 23-26, 2007 Ft. Lauderdale, Florida 23 Exploratory Roll Out Tie in legacy voice systems. Gain experience with both analog and IP devices Limit exposure to a small user base Position for a controlled roll out.

January 23-26, 2007 Ft. Lauderdale, Florida 24 Cap and Grow Tie in legacy voice systems. Cap investment in legacy systems. All expansion based on VoIP. Selectively migrate users from the legacy system to VoIP. Increasingly adopt enhanced IP features.

January 23-26, 2007 Ft. Lauderdale, Florida 25 Full Scale Adoption Aggressively pursue the adoption of VoIP. Replace legacy solutions as quickly as possible. Utilize enhanced features and capabilities.

January 23-26, 2007 Ft. Lauderdale, Florida 26 Planning & Deployment (DDOSC) Discovery Review DesignOrder Review Adopt a Methodology for Planning Your Solution for Today, Tomorrow, and Next Year. Comprehensive Planning Review StageCutover Review

January 23-26, 2007 Ft. Lauderdale, Florida 27 Summary Start NOW, even if modestly. The sooner you gain exposure and experience the better. Do not let your organization be caught by surprise. Try to anticipate the future. Make sure the solution fits your needs not only today, but tomorrow as well. –How can advanced communications options be leveraged? –How does your chosen platform get you there? Hardware Upgrades vs Software Upgrades. Understand your migration path. Avoid forklift upgrades when you expand. –How does your chosen platform carry your forward? –Not all solutions from a single vendor (small, medium, large), have feature transparency. (Phone features, management features, etc.) Don’t Just Change the Wire, Change the Game!

January 23-26, 2007 Ft. Lauderdale, Florida 28 “The future ain’t what it used to be” Yogi Berra Patrick W. Henkle Director of Product Management Sphere Communications