SIP is the protocol that makes modern business phone systems work. Every call placed through a VoIP phone system, every SIP trunk connecting a PBX to a carrier, every STIR/SHAKEN attestation — all of it runs on SIP. But most explanations of SIP are written for network engineers and read like IETF specifications. This guide explains SIP in plain language for operators who need to understand what it does without becoming protocol experts.
SIPNEX is an FCC-licensed carrier. SIP is how your phone system talks to ours. Understanding the basics helps you configure your trunk correctly, troubleshoot problems faster, and have productive conversations with your carrier when something breaks.
What SIP does in one paragraph
SIP (Session Initiation Protocol) is the signaling protocol that sets up, manages, and tears down phone calls over IP networks. When your PBX or VICIdial places a call, it sends a SIP message to the carrier saying “I want to call this number from this number using this audio format.” The carrier responds saying “OK, send the audio here.” The audio flows. When someone hangs up, SIP sends a message saying “call is over.” That is SIP — the conversation about having a conversation.
SIP does NOT carry the actual voice audio. That is handled by RTP (Real-time Transport Protocol). SIP is the control plane. RTP is the media plane. SIP decides who talks to whom and how. RTP carries what they say.
The SIP message types you need to know
SIP communication happens through messages — requests from your system and responses from the carrier (or vice versa). You do not need to memorize all of them, but knowing the six most common ones helps you read SIP logs when troubleshooting.
INVITE — “I want to start a call.” Your system sends an INVITE to the carrier with the called number, your caller ID, and your codec preferences. This is the most important SIP message — it initiates everything.
200 OK — “Yes, the call is connected.” The carrier (or the called party’s system) sends this back when the call is answered. After 200 OK, audio starts flowing via RTP.
ACK — “I confirm the connection.” Your system sends this to acknowledge the 200 OK. The three-way handshake (INVITE → 200 OK → ACK) completes the call setup.
BYE — “I’m ending this call.” Either side sends BYE to hang up. The other side responds with 200 OK to confirm.
REGISTER — “Here I am, I’m online.” Your PBX sends REGISTER to the carrier periodically to maintain its presence. This tells the carrier where to send incoming calls. Used with digest authentication — IP-authenticated trunks do not need REGISTER.
OPTIONS — “Are you still there?” A keepalive message. Your system or the carrier sends OPTIONS periodically to verify the other end is responsive. If OPTIONS goes unanswered, the trunk is marked as down.
SIP response codes: what the numbers mean
When your SIP INVITE fails, the carrier returns a response code that tells you why. These are the codes you will see most often in your logs:
1xx — Provisional (the call is in progress): 100 Trying (carrier received the INVITE), 180 Ringing (the called phone is ringing), 183 Session Progress (early media — you might hear ringback tone through RTP before the call is answered).
2xx — Success: 200 OK (call answered or action completed).
4xx — Client error (something is wrong with your request): 401/407 (authentication required — your credentials are wrong or missing), 403 Forbidden (your account is blocked or the number is not authorized), 404 Not Found (the called number does not exist), 486 Busy Here (the called party is busy), 480 Temporarily Unavailable (called party did not answer).
5xx — Server error (something is wrong on the carrier side): 500 Internal Server Error (carrier system problem), 503 Service Unavailable (carrier is overloaded or you hit a channel cap — if you see 503s during high-volume dialing, your carrier may be throttling you).
6xx — Global failure: 603 Decline (the call was actively rejected by the called party or their carrier — increasingly common when spam filters block calls).
If you see a pattern of specific error codes, it narrows the problem. Lots of 403s = authentication or authorization issue. Lots of 503s = carrier capacity problem. Lots of 603s = your calls are being blocked, likely a caller ID reputation or attestation issue.
How SIP relates to SIP trunking
SIP trunking is the specific application of SIP to connect your phone system to a carrier’s network for PSTN access. The “trunk” is the logical connection — your PBX registers to (or is IP-authenticated with) the carrier’s SIP proxy, and all calls between your system and the telephone network flow through that connection using SIP signaling.
Your PBX sends SIP INVITEs to the carrier for outbound calls. The carrier sends SIP INVITEs to your PBX for inbound calls to your DIDs. The carrier handles the conversion between SIP (your IP network) and the PSTN (the traditional telephone network) — or routes directly to the terminating carrier via SIP-to-SIP peering.
How SIP relates to STIR/SHAKEN
STIR/SHAKEN is implemented as an extension to SIP. When the carrier signs an outbound call, it adds an Identity header to the SIP INVITE. This header contains a cryptographic token (JWT) that includes the attestation level and the carrier’s digital signature. The Identity header travels with the SIP INVITE through the call path. The terminating carrier extracts the header, verifies the signature, and applies the attestation level to its call treatment decisions.
This is why A-level attestation only works with a carrier that signs SIP directly. The Identity header must be inserted by the originating carrier into the SIP INVITE before it leaves the carrier’s network. A reseller that passes your SIP traffic upstream cannot insert this header — only the carrier holding the SP-KI certificate can sign it.
SIP configuration basics
When configuring a SIP trunk on your PBX (VICIdial setup guide), you need to provide:
Carrier proxy address: The IP address or hostname of the carrier’s SIP proxy — where your system sends SIP messages. SIPNEX provides this during provisioning.
Authentication: IP-based (carrier whitelists your IP, no credentials needed) or digest (username + password sent in response to 401/407 challenges).
Codec preferences: Listed in your sip.conf allow= statements. G.711u recommended for call centers.
DTMF mode: RFC 2833 is the standard. Configurable in sip.conf as dtmfmode=rfc2833.
NAT settings: If behind NAT (most servers are), configure nat=force_rport,comedia to ensure RTP media flows correctly.
Number format: E.164 (+1XXXXXXXXXX) for both outbound dialing and caller ID.
Frequently asked questions
What is SIP in simple terms?
SIP (Session Initiation Protocol) is the signaling protocol that manages phone calls over IP networks. It handles setting up calls (who is calling whom, which audio format to use), managing calls (hold, transfer, conference), and ending calls (hangup). SIP does not carry the actual voice audio — that is handled by RTP. Think of SIP as the phone ringing and someone answering. RTP is the conversation that follows. SIP is the standard protocol used by virtually all business VoIP phone systems, SIP trunks, and carrier interconnections.
Is SIP the same as VoIP?
No. VoIP (Voice over Internet Protocol) is the broad category of transmitting voice over IP networks. SIP is a specific protocol within VoIP that handles call signaling. All SIP communication is VoIP, but not all VoIP uses SIP — other protocols like H.323, MGCP, and proprietary systems also qualify as VoIP. In practice, SIP dominates the business VoIP market to such a degree that the terms are often used interchangeably. See our detailed SIP vs VoIP comparison for more.
Do I need to understand SIP to use a SIP trunk?
Not deeply. For basic SIP trunk setup and operation, you need to understand the configuration parameters (proxy address, authentication, codecs, DTMF mode) and the most common SIP response codes (so you can interpret error messages in your logs). You do not need to understand the protocol at the packet level for daily operation. However, basic SIP knowledge significantly speeds up troubleshooting — when support tells you “you’re getting 403 Forbidden on outbound INVITEs,” understanding that 403 means authorization failure narrows the problem to credentials or CID configuration immediately.
SIPNEX speaks SIP at the carrier level. When you configure your trunk with our SIP proxy credentials, your system connects to a carrier-grade SIP infrastructure built for high-volume dialing. Get trunk credentials or see our rates.
Keep Reading
SIPNEX
FCC-licensed carrier with its own STIR/SHAKEN SP certificate. Operator-owned. SIP trunks built for operators who dial at volume.