1 / 28

Right Sizing Your IP PBX Determining the Approach that Fits Your Enterprise TMC University

Right Sizing Your IP PBX Determining the Approach that Fits Your Enterprise TMC University. Patrick W. Henkle Sphere Communications. Agenda. What we will not cover Specific Vendor Implementations Feature Details Protocol Wars. What we will cover Define “Right-Sizing”

billyowens
Download Presentation

Right Sizing Your IP PBX Determining the Approach that Fits Your Enterprise TMC University

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Right Sizing Your IP PBXDetermining the Approach that Fits Your EnterpriseTMC University Patrick W. Henkle Sphere Communications

  2. Agenda What we will not cover • Specific Vendor Implementations • Feature Details • Protocol Wars 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

  3. “In theory there is no difference between theory and practice. In practice there is.” Yogi Berra

  4. Right-Size Defined right·sizePronunciation: 'rIt-"sIzFunction: 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

  5. Legacy PBX IP PBX Communication Rules/Policy Database Media “Library” Feature Services Call & Media Control Presence Services Messaging Services Media Services Standards Based Interfaces Session Management Distributed Processing High Availability Right-Sizing Process

  6. 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”.

  7. +100 years of progress TelecommunicationsPast and Present Telecommunications has changed in many ways over the last century. However, one aspect remains essentially the same . . . . . . the plain old telephone.

  8. 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.

  9. 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.

  10. MIPS Time N2-N Applying Moore’s and Metcalf’s Laws to Enterprise Telecom Moore’s Law Metcalf’s Law Integrated Circuits will double in power every year! The value of a distributed communications network . . .

  11. WAN PSTN PSTN PSTN PSTN Telecom Today – Distributed IP Services IP Telephones Analog FXO Trunks Legacy PBX BranchHub COHub VoIP Manager VoIP Manager Analog Devices Facility 3 Facility 2 Mobile User IP Telephones Internet* Analog FXO Gateways MeetingHub COHub T1/E1/PRI VoIP Manager SOHO (IP Conference Hub) Voice Messaging PhoneHub (Vmail, Email Unified Messaging) IP Telephones Analog Devices (Desktop, Fax, Conference, Modem) Key: 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 IP Integrated Desktop Multi-media Communication Desktops IP WiFi Telephones Facility 1

  12. IP WAN PSTN IP WAN PSTN Enterprise VoIPTypical UnifiedCommunications Business IT Services Don’t Just “Change the Wire” • Multi-media communications • Presence enhanced apps. • Click to dial • Contact management

  13. IP Enabled Hybrid Client Server Extended Life TDM over IP Purpose Built IP IP WAN PSTN IP WAN PSTN IP WAN PSTN IP Trunks Legacy TDM PBX SIP PSTN TDM Trunks IP Trunks Media Gateway IP LAN Telecom Server IP LAN Telecom Servers IP Stations Analog Stations Media Gateway IP LAN IP PBX Architectural Approaches • 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

  14. 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 Evolving Enterprise VoIPAlternative Approaches (Generalized) Client / Server Hybrid TDM/IP

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

  16. Why VoIP? Why Should You Consider 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.

  17. Where VoIP? Where Should You Implement 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?

  18. When VoIP? When Should You Deploy 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.

  19. What VoIP? What Are Your Best Applications for 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 3rd party devices? • What choices do you have for: phones, call processing, voicemail, etc. from different providers?

  20. Who VoIP? Which Vendor(s) Can Best Meet Your Needs? • 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.

  21. Exploratory Cap and Grow Greenfield Technology Evaluation Proactive Introduction Full Scale Adoption IP PBX Deployment Scenarios • 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. • Deploy IP at all new locations. • Replace legacy systems. • Mandate use of enhanced services. • Actively pursue productivity advantages. • Balanced Approach • Manages obsolescence effectively • Does not realize full benefits • Expansion may be a challenge • Lowest Risk • Ensures readiness for the future • May represent throw away investment • Full benefits are realized • Best ROI • Greatest change • Greatest Risk

  22. 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.

  23. 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.

  24. Full Scale Adoption • Aggressively pursue the adoption of VoIP. • Replace legacy solutions as quickly as possible. • Utilize enhanced features and capabilities.

  25. Comprehensive Planning Adopt a Methodology for Planning Your Solution for Today, Tomorrow, and Next Year. Planning & Deployment(DDOSC) Review Review Discovery Design Order Review Review Stage Cutover

  26. 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!

  27. “The future ain’t what it used to be” Yogi Berra Patrick W. Henkle Director of Product Management Sphere Communications

More Related