Communications
Multiple Offices. One Phone System.
An organization with four buildings should not be paying for four phone systems, four support arrangements and four bills. One communications platform gives every site a shared extension plan, transfers between buildings, shared reception coverage and centralized administration, while each location keeps its own published numbers, call flow and registered emergency address.
Multiple offices
One phone system across every location
An organization with four buildings should not be running four phone systems. Consolidating locations onto one communications platform is usually the single change that makes the phones feel like one company again.
What multi-site organizations accumulate
- A separate phone system in every building
- Different carriers and different support arrangements
- Extensions that mean different things at different sites
- A separate auto attendant nobody maintains
- Several bills, several renewal dates
What one system gives them
- Extension-to-extension calling between offices
- Centralized call routing
- One shared company directory
- Common auto attendants with per-site behavior
- Centralized administration and changes
- One consistent experience for every employee
- One support relationship
- Reporting across the whole organization
What consolidation looks like
- Main office
- Second location
- Branch or annex
- Remote and field staff
One communications platform
Shared extension plan and directory
- Cross-site transfers
- Centralized routing and administration
- Location-specific numbers and call flow where needed
- Per-building registered emergency address
Who this fits
- Counties and municipalities with courthouses, annexes and outlying departments
- Clinics and practices with several sites
- Manufacturers with a plant and a separate office
- Firms with branch offices and remote staff
What breaks first on old phone systems
- A separate phone system, vendor and bill at every building
- Staff dialing outside numbers to reach the office across town
- Calls that cannot be transferred between locations
- Changes that require a technician visit to each site
What is included
- One extension plan spanning every location
- Extension-to-extension calling and transfers between buildings
- Centralized call routing with location-specific call flows
- Shared or centralized reception, with coverage between sites
- Per-location caller ID and per-location emergency address registration
- One administrative interface for all sites
- Remote employees included in the same system as office staff
- Consistent voicemail, presence and directory across the organization
How a phone cutover runs
Step 1
Inventory every site
Numbers, handsets, analog circuits, internet connection and network equipment are documented per building, because sites are rarely as similar as the org chart suggests.
Step 2
Design the numbering plan
Extension ranges, site prefixes and directory structure are decided once, up front, so the plan still works when a location is added.
Step 3
Prepare each network
Every site gets its own readiness review: circuit, switching, PoE, firewall. A single weak site produces complaints attributed to the whole system.
Step 4
Cut over in a planned sequence
Sites are ported and cut over in an order that fits the organization's operations rather than all at once by default.
Making the change
Keep your numbers. Change everything behind them.
Replacing a phone system does not mean starting over. Your published numbers are normally ported from the existing carrier, so customers keep dialing what they have always dialed. What changes is everything behind those numbers: how calls are answered, where they go, who can reach whom and from where.
We run the transition, including the parts most organizations do not think about until cutover day, like overhead paging, door phones and fax lines.
- Existing phone-number porting
- Call-flow planning with the staff who answer
- Auto-attendant and greeting design
- Phone provisioning and staging
- User and extension setup
- Desktop and mobile application rollout
- Training close to cutover
- Testing of every routing path
- Cutover planning with a fallback position
- Support through the first weeks
Why organizations here trust us with the phones
- Serving Southern Illinois organizations since 2006
- Local engineers, remote and onsite support
- Phones and network managed by one team
- Business and government deployments
- Multiple platforms supported, selected by fit
- Number porting and carrier coordination handled for you
- Multi-location and remote-staff experience
- 24/7 monitoring of managed environments
Where multi-site deployments actually get difficult
The phone platform is the easy part. The difficulty is that buildings differ: one has a managed switch with PoE headroom and one has an unmanaged switch under a counter, one is on fiber and one is on fixed wireless, one has an overhead paging amplifier from 1994 that still has to work. Multi-site projects fail on the site nobody surveyed, so every location gets its own assessment rather than an assumption inherited from headquarters.
The second difficulty is governance. In a county, offices are separately elected and administer themselves; in a healthcare group, one clinic's front desk works nothing like another's. A shared system does not mean an identical configuration. Each location keeps the call flow that fits how it works, while the directory, extension plan and administration stay common.
- Per-site survey: circuit, switching, PoE budget, cabling, analog circuits, paging
- Numbering plan designed to accommodate the location you will add in three years
- Cutovers sequenced site by site so a problem is contained to one building
- Emergency addresses registered per building and re-verified when departments relocate
Why Mayer Networks
- One system, one administrative interface, one team accountable for all of it
- Each site's network is assessed by the same people supporting the phone system
- Location-specific requirements are respected instead of flattened into one template
- One organization accountable for support, engineering, security, infrastructure and communications.
Security considerations
- Per-building emergency address registration rather than one address for the organization
- Site-to-site voice traffic handled deliberately across whatever connectivity exists
- Voice separated from data networks at each location
- Administrative access scoped by role where departments are separately governed
How much bandwidth does a phone system need?
Roughly 100 Kbps per concurrent call with overhead, so capacity is rarely the issue. Consistency is: jitter, packet loss and latency cause the audio problems people describe, which is why we measure the circuit and configure QoS on the switching and firewall rather than relying on a speed test.
How long does it take to port our numbers?
Straightforward ports commonly complete in one to two weeks after the losing carrier accepts the request. Ports involving several carriers, mismatched account details or small local carriers take longer, so we schedule the cutover around the confirmed date rather than an estimate.
Can each location keep its own phone number?
Yes. Each site keeps its published numbers and its own outbound caller ID while sharing one system and one extension plan.
Do all sites need the same internet connection?
No, and they rarely do. Each site is designed around the connection available at that address, which in this region can mean fiber at one building and something considerably less predictable at another.
Can the receptionist at one building answer for another?
Yes. Coverage between sites is a routing decision, which is why organizations with a thin front desk at a satellite office often consolidate reception.
How does 911 work across multiple buildings?
Each building gets its own registered dispatchable location, verified during deployment and reviewed when departments move. Sharing one address across sites is the most consequential mistake in a multi-site deployment.
Does every site need on-premises equipment?
Not necessarily. Depending on the platform and design, sites may need little more than network equipment and handsets. What each location needs is determined during the assessment.
Let's talk about your technology
Tell us what you are running and what is not working. We will tell you plainly what we would do about it.