SIP Trunking Basics: How Business Phone Calls Travel Online
What a SIP trunk is, how it differs from traditional phone lines, what to check on codecs, channels and failover, and how to choose a provider.
If you have ever heard a vendor say "we just need a SIP trunk" and nodded along, this guide is for you. SIP trunking is one of those pieces of telephony plumbing that is simple in principle and easy to get wrong in practice. We will cover what it is, how it compares with older lines, the technical points worth checking, and how to choose and test a provider.

What a SIP trunk actually is
SIP stands for Session Initiation Protocol, the signalling language that sets up, changes and ends voice calls over an IP network. A trunk is a bundle of call capacity between two systems. Put together, a SIP trunk is a virtual connection between your phone system and a provider that can reach the public telephone network.
In the old model, a business bought physical lines from a telephone company and a box on the wall turned them into calls for the office. With a SIP trunk, your phone system, whether it sits in your office or in the cloud, talks to a provider over the internet. The provider hands your outbound calls to the wider phone network and brings incoming calls back to you.
Following one outbound call
- Agent dialsSomeone on your team places a call from a softphone, desk phone or browser.
- Your phone system signalsIt sends a SIP request to the trunk provider asking to set up a call to the dialled number.
- Provider connectsThe provider routes the call across the public phone network to the person being called.
- Audio flowsOnce answered, voice travels as small packets of data in both directions, usually using RTP.
- Call endsEither side hangs up and the session closes; the provider keeps the call details for billing and reports.
SIP trunks compared with traditional lines
Most businesses that move to SIP trunking do it for flexibility. The comparison below sets out the practical differences.
Traditional lines vs SIP trunking
| Traditional lines | SIP trunking | |
|---|---|---|
| Capacity | Fixed by the number of physical lines or channels installed | Set by the number of channels you subscribe to, often changed with a request |
| Installation | Engineer visit and dedicated cabling | Configuration on your phone system and a working internet connection |
| Location | Tied to a site | Calls can be delivered to any site or cloud system that can reach the provider |
| Numbers | Tied to the local exchange | Often held by the provider and routed wherever you choose, within local rules |
| Failure planning | Depends on the carrier and the building | Depends on your internet connection, the provider's routes and the backup you design |
The terms you will meet
A provider's proposal will use shorthand. These are the terms that matter most when comparing offers.
- Channels (concurrent calls): how many calls can be active at once. A team that expects ten calls at the same time needs at least ten channels, and some headroom.
- DID (direct inward dialling) numbers: public numbers that ring into your system. Ask which countries and number types the provider can actually supply, and whether you can bring your own through porting.
- Codec: the method used to compress voice. G.711 gives familiar landline quality and uses more bandwidth; G.729 uses less bandwidth but loses some clarity; Opus is common in browser calling. Both ends must agree on at least one codec.
- Registration or IP authentication: how the provider recognises your system. Either the system logs in with credentials, or the provider only accepts traffic from IP addresses you have listed.
- SBC (session border controller): a device or service at the edge of your network that manages and tidies call traffic. Some providers include one; some systems need their own.
- Failover: what happens when the primary route is down. Good providers offer a secondary route or an automatic diversion to another destination.
Call quality starts with your network
SIP trunking sends voice over the same connection as everything else your office does. That means poor audio is more often a network problem than a provider problem. Three measurements are worth knowing.
Why voice is sensitive
- LatencyThe delay between speaking and being heard. Long delays make people talk over each other.
- JitterVariation in the delay between packets. High jitter makes audio choppy or robotic.
- Packet lossPackets that never arrive. Even small losses can leave gaps in words.
A few habits help. Give voice traffic priority on your router where it supports quality-of-service settings, keep wired connections for important desks, and test during your busiest hour, not at seven in the morning. For a closer look at audio itself, read Telephony Audio Quality.
Protecting the trunk from misuse
A trunk that can place calls is a target. If someone gets hold of your credentials or finds an open system, they can place expensive calls to premium destinations at your expense. Sensible habits reduce that risk:
- Restrict which IP addresses may use the trunk wherever the provider allows it.
- Use long, unique credentials and rotate them when staff or contractors leave.
- Block destinations your business never calls, and set a spending alert or limit with the provider.
- Review call logs regularly for unusual late-night or international patterns.
How to choose a provider
Features look similar on paper, so ask practical questions and get the answers in writing.
Questions to ask before you sign
- Which countries and number types can you supply, and can I port my existing numbers?
- How many channels are included and how quickly can capacity change?
- Which codecs do you support, and how do you handle codec mismatches?
- What redundancy do you have between your own carriers and data centres?
- How do I get a call-detail record, and for how long is it kept?
- What are the notice period and exit terms if I move away?
- What support hours do you offer, and who answers during an outage?
Planning for outages
Any internet-based service can fail. The question is what your callers experience when it does. A realistic plan has three parts: a secondary route or provider for incoming calls, a diversion destination such as a mobile phone or another site, and a written procedure that says who switches it on. Practise the procedure once a quarter so it is not the first time during a real incident. For the caller-facing side, see Emergency and Outage Messages in Your IVR and Contact Center Crisis Readiness.
Moving to a SIP trunk without dropping calls
The riskiest moment is the changeover. Most problems come from rushing it, so plan the move in stages rather than switching everything on a Monday morning.
A cautious migration
- Audit what you haveList every number, line, fax or alarm line, and which team or device uses each one. Forgotten lines are the usual casualties.
- Choose and testOpen a trunk with a small number of channels and a spare number. Make calls in both directions from several devices.
- Port numbersAsk the provider to explain the porting timeline and the exact date and time of the cut-over. Keep the old service until the new one is confirmed.
- Cut over in a quiet windowMove numbers during your lowest-traffic period and have the old route ready as a fallback.
- Review after a weekCheck call logs, complaints and audio quality, then retire the old lines.
What to test before and after launch
Treat the trunk like any other system change and write down what you tested. Beyond simple calls, check the situations that tend to fail quietly.
- Caller identification: the number your callers see should be one you are entitled to present. See Caller ID Honesty for the principles.
- Transfers and conferencing: transfers to outside numbers often use features that vary by provider.
- Key-press tones (DTMF): make sure menu choices register, because some codec and network combinations garble them.
- Emergency calling: confirm how calls to emergency services are handled, including what location information is sent. Rules vary by country and by whether numbers are fixed or mobile.
- Peak load: place enough simultaneous calls to see whether channel limits and bandwidth hold.
Keep a record of the results. When something breaks months later, a dated test log tells you quickly whether it ever worked.
SIP trunking and Call
In Call, your phone lines connect through the telephony provider that your account is set up with. Setting up that connection is an administrator task: the provider is chosen, and the addresses it needs to send call events back are configured, in the telephony settings. A SIP trunk can be recorded as information about a number, but it is not yet a provider that places calls, so check with your account administrator before planning around one.
Once lines are connected, the day-to-day work happens elsewhere: lines are managed under phone lines, calls are distributed through queues, and a diversion can send every inbound queue to an outside destination during an outage. The overview in Getting Started with Call and the comparison in Cloud PBX vs On-Premise are good next reads.
Frequently asked questions
Is SIP trunking the same as VoIP?
Not exactly. VoIP is the general idea of carrying voice over IP networks. A SIP trunk is one specific way of connecting a phone system to the public phone network using that idea.
How many channels do I need?
Start from the highest number of calls you expect at the same time, not the number of staff. Add some headroom for peaks and for calls that wait in a queue, then review after a month of real traffic.
Do I need a special phone for SIP?
No. Softphones, browser calling and many desk phones all work. What matters is that your phone system speaks SIP to the provider and your network can carry the audio.
Can I keep my existing phone numbers?
Often yes, through number porting, though the rules and timescales depend on the country and the current carrier. Ask the new provider to explain the process before you cancel anything.
What happens if my internet goes down?
Calls over the trunk stop unless you have a second connection or a diversion. Arrange a backup route or a destination such as a mobile phone, and test it.
Is SIP trunking cheaper than traditional lines?
It often costs less to run and to change, but the answer depends on your call volume, destinations and the channels you need. Compare quotes on the same assumptions rather than relying on a general claim.