# Business Phone Systems and Cloud Calling in Alaska

> Cloud, on-premises and hybrid business phone systems for Alaska organizations: dial plan, carrier connections, 911 location and site survivability.

*Source: https://trybussolutions.com/alaska/business-phone-systems/ · Trybus Solutions · Chattanooga, TN · 423-633-1817 · info@trybussolutions.com*

## What We Do

Trybus Solutions designs, installs and supports business phone systems for organizations in Alaska. That covers cloud calling, on-premises call control and the mix of the two that many multi-site organizations end up running, along with the connections to the telephone network, emergency calling, and the desk phones, softphones and analog devices at the end of it.

Most of our work starts for one of a few reasons. A system is coming up on end of support. A carrier contract is up for renewal. An organization has grown into more sites than its phone system was designed for. Or a move to cloud calling has been decided, and nobody has yet worked out what happens at a site when its link goes down.

Dates are driving some of it. Cisco's version 14 on-premises calling applications, for example, reach their last date of support on April 30, 2027. Whatever platform comes next, getting off the current one starts with an inventory, and our guide to the [version 14 end-of-life dates](https://trybussolutions.com/cucm-14-end-of-life-dates/) sets out what each milestone means.

We work nationwide from Chattanooga, Tennessee. Our clients usually have their own IT team, and we are there for the parts that need people who have done this before. The wider scope of our [collaboration, unified communications and contact center work](https://trybussolutions.com/collaboration-unified-communications/) is set out on its own page.

## Why Alaska Organizations Bring Us In

- **We are not tied to one platform.** Cloud calling suits some organizations and some sites, and not others. We carry a range of technology partners, so what we recommend is decided by your sites and your links. If the system you have still fits, we will say so.
- **We design for the link each site has.** Voice is sensitive to delay. The ITU-T G.114 recommendation treats one-way delay under 150 milliseconds as close to transparent for conversation, and a single hop through a geostationary satellite adds more than that on distance alone. We measure each site link before deciding where call control lives.
- **We decide what each site keeps when its link fails.** Calls inside the building, calls to the public network, 911 and call queues each behave differently when a site loses its connection to cloud call control. We rank them with you and design survivability site by site.
- **We treat 911 as a design requirement.** FCC rules under Kari's Law and RAY BAUM'S Act require multi-line telephone systems installed after February 16, 2020 to allow direct 911 dialing, to notify a designated person or location when 911 is dialed, and to send a dispatchable location with the call. For sites spread across a borough, and for staff who work from home or travel, getting the location right is most of the work.
- **We look at the parts that usually get missed.** Analog lines, fax, elevator and gate phones, overhead paging, and numbers spread across several carriers. These are what tend to hold up a cutover, so we go through them during discovery.
- **We are still there after go-live.** Support is available as a separate agreement, with coverage hours agreed in Alaska time. Plenty of clients keep their own team and use us only for the project.

[Start a conversation](https://trybussolutions.com/contact-us/?service_solution=collaboration-unified-communications)

## What You Get

Scope varies. A phone replacement at one office does not need the same documentation as a migration across twenty sites with a contact center attached. Below is what we produce on a typical mid-size project, and we agree which of it you need during scoping.

Everything we produce is yours. If you take the design elsewhere to be built, it will be complete enough for somebody else to build it.

- **Site and link assessment:** Each site, how it connects, and measured delay, jitter and loss on the path voice will use.
- **Number and device inventory:** Every number by carrier, and every device that is not a desk phone, from fax lines to elevator phones.
- **Recommendation and options:** Cloud, on-premises or hybrid, what else was considered, and the reasoning. Written so it can be taken to a board without an engineer to translate it.
- **Dial plan and numbering:** Numbering, routing, class of service and the porting plan, worked against carrier lead times.
- **Emergency calling design:** How each site and each remote worker presents a dispatchable location, and who is notified, on site or elsewhere, when someone dials 911.
- **Survivability plan:** What each site keeps when it loses its link, and the local hardware or circuits that requires.
- **Project plan, test plan and acceptance criteria:** Stages, cutover windows and site visits, and what has to work before each stage is signed off.
- **As-built documentation and handover pack:** What was built, how it is configured, and what your team needs to run it.

## The Systems We Work On

Six areas. Most phone system projects touch more than one of them.

### Cloud Calling

Call control delivered from a provider's data centers, sometimes sold as hosted VoIP, with phones and softphones registering over the internet or a private link. It takes servers out of your buildings and makes every site depend on its path out. Whether that suits a site depends on what that path is.

### On-Premises and Hybrid Call Control

Call control kept in your own data center, or split so that larger sites run locally while smaller ones register to the cloud. Organizations with remote sites often run a mix like this for years, and it needs planning so both halves can still reach each other.

### Carrier Connections and Numbers

SIP trunks, local circuits at sites that need their own path to the telephone network, and number porting. Porting runs on carrier dates rather than project dates, so the plan is built around the dates we are given.

### Emergency Calling

Direct 911 dialing, notification to a designated person or location when someone dials 911, and a dispatchable location for every device, including softphones on laptops that move between a clinic, a home and a hotel. This is the part of a phone project with legal obligations attached.

### Analog and Legacy Endpoints

Fax, elevator and fire panel lines, gate phones, overhead paging and alarm circuits. They outlive every platform around them, and they are the most common reason a cloud calling project stops short of finished.

### Phones, Softphones and Mobile

Desk phones for shared spaces, softphones and mobile apps for people who travel between sites, and headsets for people on the phone all day. The right mix comes from how each group works, which discovery establishes.

## How a Project Runs in Alaska

Broadly the same shape whether it is one office or forty sites. Timescales depend on carrier lead times, freight to the sites, and how much of your team is available.

- **Scoping and kickoff:** Agree what is in scope, the deliverables, who is involved on both sides and how decisions get made, including any procurement rules or funding deadlines that set the calendar.
- **Discovery:** Sessions with the people who run the system now, configuration pulled from the live environment, and link measurements at each site. When discovery changes the scope, we price it and you decide before we carry on.
- **Design and review:** Dial plan, survivability, emergency calling and the porting plan documented, then walked through with your team. Better to argue about it on paper than during a cutover.
- **Procurement and staging:** Phones and gateways configured and tested before they ship, so a site visit is spent installing and testing rather than configuring.
- **Pilot:** On larger projects one site or group goes first, with a way back if it does not go well. For a single office this stage often is not worth the time, and we will say so.
- **Migration:** Site by site, with number porting scheduled around carrier dates. Old and new systems run side by side, with calling between them, until the last site moves.
- **Punch list and handover:** Closer support after cutover while the snags come out, then documentation, training for your team, and a decision about the old system.

## What Is Quoted Separately

Most of what is below is work we do. It is not part of a phone system project by default, because each piece carries its own scope, its own schedule and its own cost. If you want any of it included, say so at scoping and we will quote it in. The last one is different: it is work we do not do at all.

- [Structured cabling and pathways. We do not pull cable ourselves. We survey the building, write the specification and coordinate the cabling partners who install against it, then check the results before the switching goes on top.](https://trybussolutions.com/networking-connectivity/)
- [Network readiness. If a site link or the local network cannot carry voice, that is a network project with its own scope. We will tell you during discovery and quote it on its own.](https://trybussolutions.com/alaska/network-wifi-sd-wan/)
- [Contact center. Queues, agents, recording and reporting are scoped and priced as their own project, because they carry their own requirements.](https://trybussolutions.com/alaska/contact-center/)
- [Ongoing operation and support. Managed services is a separate agreement with its own service levels, and a decision worth making on its own.](https://trybussolutions.com/alaska/managed-it-services/)
- **Carrier service and calling plans.** We design and configure the connection to the telephone network, but we do not become your carrier. Numbers, minutes and the bill for them stay with your provider.

## Who We Work With in Alaska

Phone systems look much the same from sector to sector. What has to keep working when a link fails is what changes.

### [Tribal Health and Tribal Government →](https://trybussolutions.com/tribal-organization/)

Clinics, government offices and enterprises on one phone system, with 911 location for sites spread across a region.

### [Alaska Native Corporations →](https://trybussolutions.com/enterprise/)

Subsidiaries in several states, often with one phone system per acquisition, brought onto one dial plan.

### [Hospitals and Clinics →](https://trybussolutions.com/healthcare/)

Nurse call and paging integration, clinical teams on mobile devices, and sites that cannot lose 911 when the link to the cloud goes down.

### [Boroughs, Cities and State Agencies →](https://trybussolutions.com/public-sector/)

Public procurement rules, emergency calling obligations, and retention rules for recorded calls.

## Technology We Work With

We hold partner relationships across the communications industry, and our engineers also work in platforms we do not sell. A migration starts on whatever you are running now, whoever supplied it.

We do not publish comparisons between manufacturers. Which platform suits an organization is something an assessment works out, not something a website should decide.

[See all technology partners →](https://trybussolutions.com/partners/)

## Talk to Us About a Phone System in Alaska

Tell us what phone system you run, how many sites are on it, and what date is driving the change. We will tell you what we think needs doing and what does not, and put a scope and a number against it.

[Start a conversation](https://trybussolutions.com/contact-us/?service_solution=collaboration-unified-communications)

[Insights and guides](https://trybussolutions.com/resources/)

## Related guides

- [Cisco version 14 end-of-life dates](https://trybussolutions.com/cucm-14-end-of-life-dates/)
- [Moving from on-premises call control to cloud calling](https://trybussolutions.com/cucm-to-webex-calling-migration/)
- [What a site keeps when it loses its link to cloud calling](https://trybussolutions.com/reliable-communication-with-webex-calling/)
- [Analog endpoints and cloud calling](https://trybussolutions.com/analog-endpoints-cloud-calling-migration/)