# What is UC? Why Does Your Business Need It? > Unified communications defined: what UC consolidates, how UCaaS differs from an on-premises deployment, and what gets harder when you bring an estate together. *Source: https://trybussolutions.com/what-is-uc-why-does-your-business-need-it/ · Trybus Solutions · Chattanooga, TN · 423-633-1817 · info@trybussolutions.com* - [Home](https://trybussolutions.com/) - Company[About us](https://trybussolutions.com/about-us/) - [Careers](https://trybussolutions.com/careers/) - Solutions[Collaboration](https://trybussolutions.com/collaboration-unified-communications/) - [Networking & Connectivity Solutions](https://trybussolutions.com/networking-connectivity/) - [Cybersecurity Solutions](https://trybussolutions.com/cybersecurity/) - [Cloud & Infrastructure](https://trybussolutions.com/cloud-and-infrastructure/) - [Governance, Risk & Compliance](https://trybussolutions.com/governance-risk-compliance/) - [Digital Workplace](https://trybussolutions.com/digital-workplace/) - Services[Implementation & Migration](https://trybussolutions.com/implementation-migration/) - [Managed Services & Support](https://trybussolutions.com/managed-services-and-support/) - [Trybus Connect](https://trybussolutions.com/trybus-connect/) - Industries[Enterprise](https://trybussolutions.com/enterprise/) - [Education](https://trybussolutions.com/education/) - [Healthcare](https://trybussolutions.com/healthcare/) - [Financial Services](https://trybussolutions.com/financial-services/) - [Retail](https://trybussolutions.com/retail/) - [Public Sector](https://trybussolutions.com/public-sector/) - [Tribal Organization](https://trybussolutions.com/tribal-organization/) - [Resources](https://trybussolutions.com/resources/) - [Partners](https://trybussolutions.com/partners/) - [Home](https://trybussolutions.com/) - Company[About us](https://trybussolutions.com/about-us/) - [Careers](https://trybussolutions.com/careers/) - Solutions[Collaboration](https://trybussolutions.com/collaboration-unified-communications/) - [Networking & Connectivity Solutions](https://trybussolutions.com/networking-connectivity/) - [Cybersecurity Solutions](https://trybussolutions.com/cybersecurity/) - [Cloud & Infrastructure](https://trybussolutions.com/cloud-and-infrastructure/) - [Governance, Risk & Compliance](https://trybussolutions.com/governance-risk-compliance/) - [Digital Workplace](https://trybussolutions.com/digital-workplace/) - Services[Implementation & Migration](https://trybussolutions.com/implementation-migration/) - [Managed Services & Support](https://trybussolutions.com/managed-services-and-support/) - [Trybus Connect](https://trybussolutions.com/trybus-connect/) - Industries[Enterprise](https://trybussolutions.com/enterprise/) - [Education](https://trybussolutions.com/education/) - [Healthcare](https://trybussolutions.com/healthcare/) - [Financial Services](https://trybussolutions.com/financial-services/) - [Retail](https://trybussolutions.com/retail/) - [Public Sector](https://trybussolutions.com/public-sector/) - [Tribal Organization](https://trybussolutions.com/tribal-organization/) - [Resources](https://trybussolutions.com/resources/) - [Partners](https://trybussolutions.com/partners/) - [Home](https://trybussolutions.com/) - [Company](https://trybussolutions.com/about-us/)[About us](https://trybussolutions.com/about-us/) - [Careers](https://trybussolutions.com/careers/) - Solutions[Collaboration & Unified Communications](https://trybussolutions.com/collaboration-unified-communications/) - [Networking & Connectivity Solutions](https://trybussolutions.com/networking-connectivity/) - [Cybersecurity Solutions](https://trybussolutions.com/cybersecurity/) - [Managed Services & Support](https://trybussolutions.com/managed-services-and-support/) - [Governance, Risk & Compliance Solutions](https://trybussolutions.com/governance-risk-compliance/) - [Cloud & Infrastructure](https://trybussolutions.com/cloud-and-infrastructure/) - [Digital Workplace](https://trybussolutions.com/digital-workplace/) - Services[Implementation & Migration](https://trybussolutions.com/implementation-migration/) - [Architecture & Solution Design](https://trybussolutions.com/architecture-solution-design/) - [Trybus Connect](https://trybussolutions.com/trybus-connect/) - [Trybus Hub](https://trybussolutions.com/trybus-hub/) - Industries[Enterprise](https://trybussolutions.com/enterprise/) - [Education](https://trybussolutions.com/education/) - [Healthcare](https://trybussolutions.com/healthcare/) - [Financial Services](https://trybussolutions.com/financial-services/) - [Retail](https://trybussolutions.com/retail/) - [Public Sector](https://trybussolutions.com/public-sector/) - [Tribal Organization](https://trybussolutions.com/tribal-organization/) - [Partners](https://trybussolutions.com/partners/) - [Resources](https://trybussolutions.com/resources/) - [Shop](https://shop.trybussolutions.com/) - [Contact Us](https://trybussolutions.com/contact-us/) - [Customer Portal](https://trybussolutions.myportallogin.com) - [Home](https://trybussolutions.com/) - [Resources](https://trybussolutions.com/resources/) - What is UC? Why Does Your Business Need It? # What is UC? Why Does Your Business Need It? October 23, 20248 min readUnified Communications Unified communications is the practice of running calling, meetings, video, messaging and presence as one system, with one directory, one set of policies and one place to administer them. The term describes an architecture, and the products that implement it differ widely. Organizations arrive at the question because something forced it: a phone system approaching the end of its support, sites that grew up on different platforms, or people working from places the phone system was never designed to reach. This page is a definition rather than a proposal. It covers what UC consolidates, how an on-premises deployment differs from [the same capability bought as a service](https://trybussolutions.com/ucaas-transformation-journey/), and which parts of a consolidation get harder rather than easier. Trybus Solutions delivers these systems as part of our [collaboration and unified communications](https://trybussolutions.com/collaboration-unified-communications/) practice, mostly for organizations that already have an IT team. ## What Is Unified Communications? Unified communications consolidates the channels people use to reach each other, and underneath them the systems that define who those people are. Separate applications for calling, meetings, chat and voicemail can be made to coexist. What they cannot easily share is a directory, a dial plan, a set of user identities, a retention policy and an administrative model. UC is the decision to hold those in one place, so that a user, a number and a permission are defined once. What a UC platform consolidates: - **Calling** Dial plan, extension ranges, hunt groups, call routing, voicemail, and the connection to the public telephone network. - **Meetings and video** Scheduled and ad hoc meetings, screen sharing and recording, with room systems and personal devices registered to the same platform. - **Messaging and presence** Persistent chat and file sharing, plus the availability status that tells one person whether another is already on a call. Presence only works when every channel reports to one system. - **Directory and identity** One user record driving the phone, the meeting invitation and the chat client, synchronized from the corporate directory and governed by the same access policy. - **Administration and reporting** One place to add a user, change a number, apply a policy and see what happened. This is where the operational saving comes from, and it is the part least often quantified before a purchase. ## Why Does Your Business Need Unified Communications? The question usually arrives attached to a specific problem. Four come up repeatedly, and which one applies shapes the scope more than the choice of platform does. - **A phone system going out of support** The equipment keeps working. Software fixes stop, spare parts get harder to source, and the next security assessment has a finding to write up. That date is what releases the budget. - **Sites that grew up separately** An acquisition, or fifteen years of local decisions. Two dial plans, overlapping extension ranges, two voicemail systems and two directories. - **People working where the system was never designed to reach** Home offices, clinics, vehicles, temporary sites. Forwarding rules and personal mobile numbers fill the gap, and none of that appears in a directory or a call record. - **Carrier and circuit changes** Copper facilities are being retired, and the analog lines supporting elevator phones, alarm dialers and fax machines get more expensive and harder to order every year. What consolidation delivers is narrower than most descriptions of it. One directory means an internal call reaches a person wherever that person is working. One console means adding a user is a single task, and removing a leaver is a task that actually completes, which matters more to security than to productivity. One numbering plan means the organization knows which numbers it owns, and that is frequently untrue at the start. Growth is the easiest of these to over-promise. Adding users to a subscription platform is genuinely quick. Adding a site is a different exercise, because a site brings a physical address, emergency calling records, local numbers to port and a network that has to carry voice. The user count scales. The site count is a project each time. Weighing a UC platform? Trybus Solutions designs and runs unified communications for organizations that cannot afford a bad cutover. A short scoping call establishes what your current estate can support before anyone proposes a platform. Cost is where the case is usually made and least often examined. Consolidation does remove duplicated subscriptions, maintenance contracts and circuits. Set against that are the migration itself, licensing that becomes recurring, analog lines that have to be retained, and whatever network work the platform turns out to require. The comparison only means something once the current estate has been inventoried, and the inventory is the step most often skipped. ## UC On Premises and UCaaS Are Different Operating Models Unified communications describes the capability. UCaaS describes one way of buying it: the platform runs as a subscription service operated by a provider. On premises means the call control, and usually the media path, run on servers your organization owns or hosts under licenses it holds. Hybrid arrangements are common, and for many organizations they are the end state rather than a transitional stage, because a contact center, a recording obligation or a set of analog circuits keeps part of the estate local. - **Where the call control runs** On premises, on servers patched and upgraded on a schedule you set. As a service, in the provider’s platform on the provider’s schedule, which is convenient until an upgrade changes something you had built a process around. - **How the public telephone network is reached** On premises, through your own SIP trunks and session border controllers, with the carrier contract in your name. As a service, either through calling bundled with the subscription or through a gateway kept on site so existing carrier contracts stay where they are. That choice is usually settled on contractual and porting grounds before technical ones. - **Who is accountable when it breaks** As a service, the provider owns platform availability and your team owns everything up to the handoff: the network, the identity provider and the endpoints. Most user-reported voice faults originate there either way. - **How the cost is shaped** A capital purchase with maintenance renewals, against a recurring per-user subscription. The subscription is easier to budget and harder to leave, and the licensing tier is the least reversible decision in the project. Neither model removes the need to design. A dial plan, a numbering scheme, a class of service policy, an emergency calling plan and a decision about what happens when a link fails all have to exist either way. A subscription does not write them. ## What Gets Harder When You Consolidate The platform work is rarely the difficult part. Four things reliably take longer than the build, and all four sit outside the control of whoever sold the platform. - **Number porting** Moving numbers between carriers runs to carrier timescales, and nobody on the project can compress them. A port needs every number listed correctly and the billing account details to match the losing carrier’s records exactly, which means finding the numbers nobody remembers ordering first. Porting is the critical path on most migrations, and a rejected port moves a cutover date rather than a task. - **Emergency calling and address records** Each location, and in larger buildings each floor or zone, needs a civic address held against the numbers and devices that sit there, so a call for help arrives at the right dispatch point with the right address. Those records have to be correct on cutover day and maintained afterwards as people and devices move. What is required varies by jurisdiction and by building, so the rules for your sites are worth confirming during design. - **Analog devices nobody has inventoried** Elevator phones, fire panels, alarm dialers, overhead paging, gate intercoms, and the fax line some regulator still expects. None appear in a user count, several are tied to life safety, and each needs its own decision about an adapter, a gateway or a retained line. Finding them is a walk of the building, and [it is the most common reason a calling migration stops short of finished](https://trybussolutions.com/analog-endpoints-cloud-calling-migration/). - **Whether the network can carry voice** Voice tolerates loss, delay and jitter far less well than the traffic already on the network. Switch power for the phones, quality of service marking that survives every hop, wireless coverage where calls are actually made, and internet paths without a single congested link. Consolidating concentrates every conversation onto that path, which is why [the network assessment belongs before the platform decision](https://trybussolutions.com/networking-connectivity/). Our engineers work these four out during discovery, before any platform is proposed, because each of them can change the sequence and two of them can change the budget. The [implementation and migration](https://trybussolutions.com/implementation-migration/) work is comparatively straightforward once they are known. They are almost never known at the start. ## Do You Actually Need Unified Communications? Sometimes the answer is no, and it is worth saying so plainly. If the current system is supported, the sites already share a dial plan and a directory, and nobody is trying to work from a place the system cannot reach, then consolidation is a project without a problem attached to it. It will still cost money and still put a working phone system through a cutover. We will say so when that is the case. The answer is usually yes when a support date is approaching, when an acquisition has left two of everything, or when the workarounds people invented for themselves have become the way the organization communicates. In that case the first useful step is not a platform shortlist. It is an inventory of numbers, sites, endpoints and carrier contracts, because the platform decision is easier than it looks once that document exists. ## Decide whether unified communications is right for your organization Our engineers assess your current calling, meeting and messaging estate, identify what carries forward and what does not, and give you a written recommendation you can take to your leadership. Or call [423-633-1817](tel:+14236331817) · [info@trybussolutions.com](mailto:info@trybussolutions.com) ## Related article What still works at a site when it loses its connection to cloud call control, what does not, and how survivability is decided site by site. Three ways to reach the PSTN from a cloud calling platform, and what each changes about support, number ownership, contracts and the porting schedule. What a UCaaS migration involves in order: the inventory taken first, what the decision turns on, why porting sets the schedule, and the first month after cutover.