IT consulting and training since 2006
We fix the problems that sit between your phones, your network and your firewall.
Skydome Consulting designs, repairs, migrates and teaches enterprise voice, network and security systems for government, healthcare and business.
You may recognize one of these
They are the situations we are called into most often.
Calls fail at random, and each vendor says the fault is somewhere else.
Find the causeThe move to cloud calling is approved, and nobody has a full list of what the old system does.
Plan the migrationThe new firewall is in, and call quality at the branches falls apart every afternoon.
Fix the pathA new platform goes live next quarter, and your engineers have only seen the sales demonstration.
Prepare the teamThe project is funded, and the people who would do it are already working nights.
Add engineers
You should not have to referee your vendors.
Most hard IT problems cross a boundary. The call fails because of a firewall rule. The migration stalls on a dial plan nobody documented. Each specialist checks one part, finds it healthy, and hands the problem back to you.
We work across those boundaries. Our engineers handle voice, networking and security together, so the problem stays with one team until it is solved. We have done this since 2006, and it is why we build our own troubleshooting and migration software and teach the courses we wish we had been given.
What we do
Four kinds of work, taken on separately or together.
Voice and collaboration
Design, troubleshooting and migration for phone systems and the platforms around them.
About voice and collaborationNetwork and security
Campus and wide-area networks, firewalls and segmentation, data center and cloud connectivity.
About network and securityTraining
Instructor-led training for engineering teams, built around how the technology is used in real networks.
About trainingProject engineering
Experienced engineers for projects your team does not have the people or the time to complete.
About project engineering
What the work looks like
All example scenariosA regional hospital
One call in twenty failed, and every vendor blamed another
Outbound calls from a hospital failed at random. The carrier pointed at the gateway, and the gateway vendor pointed at the carrier.
Read the scenarioA state agency
The cloud calling migration nobody could size
An agency had approval to move its phone system to the cloud and no complete record of what the old system did.
Read the scenarioA multi-site business
The new firewall that broke the phones every afternoon
After a firewall replacement, branch offices had choppy audio and dropped calls, but only at the busiest time of day.
Read the scenarioIllustrative scenarios. They show the kind of work we do and are not accounts of specific clients.
We build the tools we use.
After enough nights reading traces by hand and enough migrations that began with an incomplete spreadsheet, we wrote software for the parts of the job that should not depend on luck. It is called CollabPlane. We use it on our own engagements, and your team can license it.
CollabPlane Workbench
SIP and call troubleshooting
Read traces and captures as call ladders, compare a good call with a bad one, and capture from the device.
CollabPlane Vector
Phone system migration to cloud calling
Discover the existing system, map it to the new platform, then provision, verify and roll back in controlled steps.
CollabPlane Studio
Call flow design and configuration
Design call handling on a canvas, then generate the configuration for each platform that has to carry it.
How it works
Four steps, the same for a two-day problem and a six-month project.
Tell us the problem
A call or a message is enough. We ask about the environment and the result you need, and we say so if we are not the right fit.
Agree the scope
A short written scope: what will be done, by when, and how both sides will know it is finished.
We do the work with your team
In scheduled, reversible changes, with your engineers involved and written status as we go.
You own the result
Documentation, a walkthrough, and training where it helps. Your team runs it from there.
From our engineers
All articlesVoice
The call that fails one time in twenty
Intermittent call failures are the hardest voice problems to fix. A method for finding the cause when a second attempt usually works.
Migration
Before you move your phone system to the cloud, count the fax machines
Cloud calling migrations rarely fail on users and phones. They fail on the things nobody listed. What to look for before you set a date.
Network and security
Why voice breaks when you replace the firewall
A firewall replacement that passes every security test can still degrade phone calls. The four places to look, and how to prevent it.
Tell us what is going wrong, or what has to go right.
Describe the environment and the problem or the project. An engineer will read it and reply.
Or call 854-260-2732