"Should we use SIP or VoIP?" comes up in a lot of architecture discussions, and it's the wrong question. One is a category, the other is a protocol inside it. This post tears a single call apart layer by layer so you can see how little of it is SIP, then maps the real decision: which service you buy and who runs it.
VoIP is the broad category of carrying voice over IP networks. SIP is the signalling protocol most business VoIP uses to start, change, and end calls, and it carries no audio itself. So you never choose between them. You choose a VoIP service, and you decide who runs it.
This guide takes one call apart layer by layer, counts how little of it is really SIP, and maps each buying decision to a service. It then covers what changes when the call runs in India.
Note: Key takeaways
- SIP and VoIP sit at different levels. VoIP names the whole job, while SIP handles one layer of it. The two can't compete.
- A call is mostly not SIP. In our 3-minute example, SIP sends 10 messages and RTP sends 18,000 packets.
- The layer tells you where to debug. Calls that won't connect point at signalling, and bad audio points at media and the network.
- The buying decision is about ownership. Hosted PBX, SIP trunk, Voice API, and audio stream differ in who runs the phone system and the call logic.
- Indian rules follow the call. Number series, automated-call declarations, and toll bypass limits don't depend on what a vendor calls its product.
What is the difference between SIP and VoIP?
VoIP describes an outcome: your voice reaches someone over an IP network instead of a circuit. SIP describes one mechanism used along the way. Comparing them is like comparing "shipping" with "the booking system": one is the service, and the other is the part that arranges it.
The SIP standard, RFC 3261, defines SIP as an application-layer control protocol for creating, modifying, and terminating sessions. The same document says SIP is not a vertically integrated communications system. It relies on other protocols to do the rest, and the diagram shows where each one fits.
Each row does a different job, and each one fails in its own way:
| Layer | Job in the call | Common standards | When it fails, you see |
|---|---|---|---|
| Signalling | Finds the other party, then starts and ends the call | SIP, H.323 | Call rejected, or never rings |
| Description | States the codecs and the address that expects audio | SDP, with offer/answer | Connected, but one-way audio or none |
| Media | Moves timed audio packets | RTP, SRTP | Gaps, robotic sound, silence |
| Codec | Turns speech into bytes and back | G.711, Opus | Thin sound, or failed negotiation |
| Transport | Delivers packets across the network | UDP, TCP, TLS, WebSocket | Delay, loss, blocked connections |
The terms blur for a historical reason. TechTarget dates commercial VoIP to 1995. The IETF published SIP as RFC 2543 in March 1999 and revised it in 2002. SIP then became the usual signalling choice in business voice, so people started using the names for each other.
You may also read that VoIP is for voice while SIP is for multimedia, or that SIP suits enterprises and VoIP suits small firms. Both framings compare a category with a protocol. A small office on a hosted phone service can still be using SIP handsets, without anyone there knowing the term.
How much of a call is actually SIP?
Very little. Take a 3-minute call using G.711 with 20 ms packets, on a trunk that challenges each INVITE for credentials.
- SIP: 10 messages on that hop. Eight set the call up, including the challenge and retry, and two end it.
- RTP: 50 packets per second in each direction, which comes to 18,000 packets over 180 seconds.
- Data: TRAI puts a G.711 SIP call at about 87 kbps, so media is about 2 MB per direction.
This count has three practical consequences:
- Bandwidth planning is a media question. Size your links on the codec and the number of concurrent calls. SIP traffic barely registers next to RTP.
- "SIP quality" usually isn't SIP. Choppy audio comes from loss and jitter on the media path. A clean SIP trace can sit beside a terrible call.
- Two paths need two firewall rules. Signalling and media often use different ports and addresses. That's why a call can ring, connect, and bill while nobody hears anything. On Vobiz, the IP address allowlist lists SIP signalling and RTP media ranges as separate rules for exactly this reason.
Our SIP trunking guide follows this split through a full call ladder and a symptom table.
Can VoIP work without SIP?
Yes, and you may be using it that way already. SIP is common, but nothing in the definition of VoIP requires it.
| Approach | How signalling works | Where you meet it |
|---|---|---|
| SIP | Text-based requests and responses, defined by the IETF | PBXs, trunks, desk phones, carriers |
| H.323 | An ITU-T system for packet-based multimedia | Some video and voice deployments, especially older ones |
| WebRTC | JSEP specifies no signalling model, and sessions typically use application-specific protocols | Browser and in-app calling |
| SIP over WebSocket | RFC 7118 carries SIP over a WebSocket connection | Web softphones that register like a phone |
| Call-control API | Your server exchanges HTTP or WebSocket messages with the platform | Voice APIs and audio streaming |
Two points get lost in most comparisons.
WebRTC and SIP are not opposites. A browser client can run WebRTC media and use SIP over WebSocket for signalling. WebRTC endpoints must support Opus and G.711, and that standard names G.711 as the base for working with legacy phone systems. You can try this on Vobiz with the WebRTC Playground, which turns a browser tab into a softphone that answers calls to a real number. Our WebRTC explainer goes further.
SIP does more than voice. It has defined extensions for instant messaging and presence. So you can have VoIP without SIP, and SIP without a voice call.
Why do vendors compare SIP with VoIP?
Because the sales page is usually comparing two products while using protocol names. When a provider writes "SIP vs VoIP", it almost always means SIP trunking vs a hosted phone system. The real question behind that comparison is who owns and runs the phone system.
That framing fits an office phone replacement. It leaves out teams building calling into software, who have two more options. The matrix shows all four, and every one of them is VoIP.
Read each column as a list of what you'd own. A SIP trunk gives you the phone system and the SIP edge. A Voice API or audio stream gives you call logic instead, and the provider keeps the SIP edge. The carrier link stays with a provider in every column, because that's the part you can't easily run yourself.
These aren't exclusive either. A business can run a cloud PBX and SIP trunking together. A common pattern is a PBX for staff extensions, plus a separate voice application for automated calls.
SIP phones and VoIP phones
The same logic applies to hardware. A VoIP phone is any device that calls over IP, and a SIP phone is one that signals with SIP. Many of them are SIP phones too, so the label rarely changes a purchase.
The question to ask is narrower: can this handset register with any standard SIP registrar, or only with one vendor's cloud? That answer decides whether you can move it to another provider later. On Vobiz, a standard SIP client registers as a SIP endpoint using a username, password, and the registrar domain, with no vendor-specific firmware involved.
Which VoIP service should you buy?
Four questions settle it. None of them mentions SIP or VoIP.
Here's how that plays out in five hypothetical situations:
| Your situation | What to buy | The reason |
|---|---|---|
| A 40-seat office with no telecom staff, replacing old desk phones | Hosted PBX | Nobody on the team wants to patch or secure a phone system |
| A contact centre with an established PBX and an ageing E1 PRI | SIP trunk | The PBX keeps its call flows, and only the carrier connection changes |
| A SaaS product adding appointment reminders and a simple menu | Voice API | Your backend already holds the logic, so it can return call instructions |
| An AI agent built on a platform such as LiveKit or Vapi | SIP trunk to the platform | The platform handles speech and turn-taking, and needs a carrier path |
| An AI agent built with your own speech and LLM pipeline | Audio stream | Your code needs the raw audio in both directions |
Our comparison of SIP and WebSocket paths covers the last two rows in detail. On Vobiz, the two paths start differently:
- SIP trunk to a platform. Vobiz routes the call to the platform's SIP address, and the platform terminates SIP and runs speech, the model, and turn-taking. Audio moves as RTP over UDP, which never retransmits, so it stays real-time.
- Audio stream to your server. Vobiz fetches your Answer URL, your VobizXML returns a Stream element, and the caller's audio reaches your server over a wss:// socket. Your code sends replies back on the same connection and handles barge-in itself.
The two also combine. A call can arrive on a SIP trunk and still be piped to your socket, so SIP handles routing and the socket handles audio. The SIP vs WebSocket visualizer steps through both paths, inbound and outbound.
Moving off a PRI or landline
The order of work matters more than the technology:
- Decide where your numbers will live. You can stay with your current carrier, or take new numbers from the new provider. Settle this first, because it shapes the cutover. If the numbers stay put, Vobiz's Bring Your Own Carrier setup routes that carrier's traffic through Vobiz without porting.
- Count your channels. An E1 PRI gives you 30 channels on a 2 Mbps line. Size the replacement on your busiest hour, using the channel math in our trunking guide, or the Vobiz CPS and concurrency calculator, which counts ringing calls as occupied channels too.
- Test the data path. At 87 kbps, 30 G.711 calls need about 2.6 Mbps in each direction.
- Open two firewall paths. Allow signalling and media separately, then test audio in both directions.
- Run both systems in parallel. Move a small group first, and keep the old circuit until the new path has handled a real peak.
What changes when you run SIP or VoIP in India?
The rule that applies depends on what the call does, not on the product label. Indian telecom documents use the phrase "internet telephony", and commercial calling rules name PRI and SIP trunks directly. The diagram shows the four checks a business call meets.
These rules change often, so confirm the current text and take legal advice for your own case.
| Question | What the source says | Source and date |
|---|---|---|
| Who may connect VoIP to the phone network? | Access licensees could provide internet telephony and interconnect it with PSTN and mobile networks. DoT clarified that the service isn't tied to the customer's underlying access network | TRAI response to DoT, July 2018 |
| Which number series for promotions? | 140xx, for registered entities in any sector | TRAI press release 91/2026, July 2026 |
| Which series for service calls? | 1600xx, for entities regulated by RBI, SEBI, IRDAI, and PFRDA, and for government bodies | TRAI press release 91/2026, July 2026 |
| What happens after spam violations? | First instance: outgoing services barred for 15 days. Later instances: all resources, including PRI and SIP trunks, disconnected for one year across all access providers. If TRAI orders restoration, each DID on a trunk counts as a separate resource for the charge. The Third Amendment's revised text keeps these terms | TCCCPR Second Amendment, February 2025, and Third Amendment, September 2026 |
| Do automated calls need anything extra? | Once in force, senders must declare application-to-person calls and CLI ranges to the originating provider in advance. Undeclared calls count as unsolicited | TCCCPR Third Amendment, September 2026 |
| Can you carry PSTN calls on your own network? | For voice BPOs that meet the OSP definition, carrying public network calls between cities, or between India and abroad, over your own network is toll bypass. The same guidelines allow OSPs some carriage between their own centres over leased lines and MPLS VPNs | DoT OSP guidelines, June 2021 |
Three points need more care than a table allows.
The licensing framework is moving. The 2018 position above predates the Telecommunications Act, 2023. Khaitan & Co reports that DoT notified new authorisation rules on 24 June 2026, including a wireline access category for virtual network operators whose scope includes internet telephony. The firm also advises existing licensees to weigh migration against continuing under their licences. We read this law firm's summary and not the Gazette text. We also could not confirm whether the rules change the OSP position, so check with your provider and counsel.
An outbound voice agent appears to be an A2P call. The Third Amendment defines A2P as a call started by an application, software system, or automated platform without direct human dialling, including artificial voice. It also lets terminating operators charge originating operators up to ₹0.05 per minute on A2P calls, with 140xx, 1600xx, and 1601xx numbers exempt. The declaration and the charge start 60 days after Gazette publication. We could not confirm that publication date, so check whether they apply on your launch date.
Watch two recommendations on SIP numbering. TRAI's February 2025 recommendations ask DoT field units to monitor allocations above 15 numbers per Mbps on SIP and PRI connections, and they call for calling name presentation on SIP and PRI calls reaching mobile networks. These are recommendations, and we could not confirm their current status.
What should you ask a provider instead?
Once the label is gone, the useful questions map to the layers:
| Layer | Ask this | A good answer lets you |
|---|---|---|
| Signalling | Which transports are supported, and how do you authenticate? | Encrypt signalling, and match your network to IP or credential auth |
| Media | Is SRTP available, and where does media anchor? | Confirm encryption and data path against your own policy |
| Codec | Which codecs can be negotiated on my routes? | Predict bandwidth and audio quality |
| Capacity | How are concurrent calls and calls per second enforced? | Size for peaks and avoid surprise rejections |
| Visibility | What quality data appears on each call record? | Check quality per call instead of relying on complaints |
| Compliance | Who handles KYC and number series, and what do you need from me? | Launch without a late regulatory block |
Ask for documentation of each answer. A provider's public docs show you what you can verify before you sign. As one example of the signalling detail worth expecting, Vobiz publishes its hangup causes and what SIP 480 and 486 mean on a call record.
How Vobiz handles both sides
Vobiz offers the trunk, API, and streaming paths on one platform. Vobiz also connects to PBXs and voice AI platforms, so the choice above decides which resources you use.
- SIP trunks. Outbound and inbound trunks are separate resources. You authenticate with an IP Access Control List or a SIP credential.
- Encryption. On the trunk object, one setting picks UDP, TCP, or TLS for signalling and another turns on SRTP for media.
- Endpoints. SIP endpoints register softphones and desk phones, and custom WebRTC clients can register using SIP over WebSocket. These are separate from trunks.
- Call control. With VobizXML, Vobiz sends webhooks (callbacks) to your server as call events occur, and it executes the instructions you return. The Call API places and manages calls.
- Audio streaming. Audio Streams send live call audio to your WebSocket server. Inbound audio is L16 at 8 or 16 kHz, or μ-law at 8 kHz. Bidirectional playback accepts L16 at 8, 16, or 24 kHz, or μ-law at 8 kHz, and a clear-audio command supports barge-in.
- Existing systems. The 3CX guide covers that PBX. Bring Your Own Carrier lets you route traffic from your existing carrier or SBC through Vobiz while your numbers stay with that carrier.
- Voice AI platforms. Guides cover LiveKit, Vapi, and Retell AI over SIP, and Pipecat over WebSocket.
- Capacity. Concurrency and CPS limits apply at account level.
- Quality data. Each call record reports the codec, call-quality scores, jitter, and packet loss, so you can trace an audio complaint to the media layer.
- India. The calling regulations page covers eligibility, KYC, caller ID, and the media anchoring rule, which keeps both legs of an Indian call in India. See also UCC management and 140 and 160 series acquisition.
Current rates are on the Vobiz pricing page. Test calls are billed and reach real phones, so use your own Auth ID and Auth Token, and confirm each number first.
Frequently asked questions
FAQ
Is SIP the same as VoIP?
No. VoIP means carrying voice over IP networks, by any method. SIP is one protocol used inside many VoIP calls, and its job is to start, change, and end the session. SIP needs other protocols to move the audio, so it can't replace VoIP.
Can VoIP work without SIP?
Yes. H.323 can signal VoIP calls, some vendors use their own protocols, and WebRTC leaves signalling to the application. SIP is still the usual language at the boundary with carriers and business phone systems, so you often meet it somewhere on the path.
Does SIP carry the voice in a call?
No. SIP messages agree who is talking and how, using an SDP description of codecs and addresses. The audio then travels in separate RTP or SRTP packets. That split is why a call can connect correctly and still have no sound.
Is SIP trunking a type of VoIP?
Yes. A SIP trunk is a VoIP service that connects your PBX or application to a carrier and the public phone network. Hosted PBX services and Voice APIs are VoIP too. They differ in who runs the phone system and call logic.
Which is better for a business, SIP or VoIP?
Neither, because they aren't alternatives. Choose by who should run the phone system. Pick hosted PBX for a managed system, a SIP trunk if you run a PBX or voice AI platform, and a Voice API or audio stream if your software controls calls.
Are SIP and VoIP calls legal for businesses in India?
Yes, through an authorised provider and within the rules. Indian rules focus on how you use the service, including number series, automated calling, and toll bypass, rather than on the SIP or VoIP label. Check the current text and take legal advice for your case.
Further reading on Vobiz
- What is SIP? · Voice over IP explained · SIP trunking guide · WebRTC explained
- SIP trunking overview · SIP vs WebSockets · Voice streaming over WebSockets
- What is a Voice API? · How VobizXML works · India calling regulations
Sources
Standards
- IETF, RFC 2543: SIP: Session Initiation Protocol, March 1999.
- IETF, RFC 3261: SIP: Session Initiation Protocol, June 2002.
- IETF, RFC 3264: An Offer/Answer Model with SDP, June 2002.
- IETF, RFC 3428: SIP Extension for Instant Messaging, December 2002.
- IETF, RFC 3550: RTP: A Transport Protocol for Real-Time Applications, July 2003.
- IETF, RFC 3711: The Secure Real-time Transport Protocol, March 2004.
- IETF, RFC 3856: A Presence Event Package for SIP, August 2004.
- IETF, RFC 6716: Definition of the Opus Audio Codec, September 2012.
- IETF, RFC 7118: The WebSocket Protocol as a Transport for SIP, January 2014.
- IETF, RFC 7874: WebRTC Audio Codec and Processing Requirements, May 2016.
- IETF, RFC 8825: Overview: Real-Time Protocols for Browser-Based Applications, January 2021.
- IETF, RFC 8829: JavaScript Session Establishment Protocol, January 2021.
- IETF, RFC 8866: SDP: Session Description Protocol, January 2021.
- ITU-T, Recommendation H.323: Packet-based multimedia communications systems.
- ITU-T, Recommendation G.711: Pulse code modulation of voice frequencies.
Indian regulators and law firm analysis
- TRAI, Response to DoT's back-reference on Internet Telephony, 16 July 2018.
- TRAI, Telecom Commercial Communications Customer Preference (Second Amendment) Regulations, 2025, February 2025.
- TRAI, Recommendations on Revision of National Numbering Plan, 6 February 2025.
- TRAI, Press release 91/2026 on the 1600 and 140 series, 10 July 2026.
- TRAI, Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026, 18 September 2026.
- DoT, Revised Guidelines for Other Service Providers, 23 June 2021.
- Khaitan & Co, Update on the principal telecommunication services authorisation rules, 26 June 2026.
Industry pages that shaped this guide
- TechTarget, SIP trunking vs. VoIP: What's the difference?, June 2023.
If you're connecting a voice AI agent over SIP, Vobiz provides AI-native SIP trunking and phone numbers for it.
Top comments (0)