> ## Documentation Index > Fetch the complete documentation index at: https://www.vobiz.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # PBX Full Form: What a PBX Does and When You Need One > PBX full form is Private Branch Exchange. Learn how a PBX routes calls, EPABX vs IP vs cloud PBX, channel sizing math, India's 2026 rules, and when to buy one. *November 3, 2026 · By [Piyush Sahoo](https://www.linkedin.com/in/piyush-s713/)* PBX stands for Private Branch Exchange, a private telephone switch that connects an organisation's internal extensions to each other and shares a smaller pool of outside lines among them. In India it is often called an EPABX. It can run as on-site hardware, as software on a server, or as a hosted cloud service. This guide decodes the acronyms, follows a call through the switch, sizes the outside channels with real math, and helps you decide whether you need a PBX at all. It also covers the June 2026 Indian rules that now name cloud EPABX services, each linked to the Gazette or regulator text. > [!NOTE] > > **Key takeaways** > > * **PBX, PABX, and EPABX mean nearly the same thing today.** Indian vendors and DoT rules favour EPABX. > * **A PBX does three jobs:** it shares outside lines, connects internal calls, and applies your call-handling rules. > * **Size outside channels on traffic, not headcount.** In our illustrative case, 50 extensions need 11 to 21 channels at 1% blocking. > * **PBX types differ mainly in who runs each layer.** That choice affects cost, patching, and what still works when the internet drops. > * **India now has a named authorisation for cloud EPABX services.** The DoT's June 2026 rules set partitioning and record-keeping duties for providers. ## What is the full form of PBX? The three letters expand to **Private Branch Exchange**. In Hindi script, the term is written प्राइवेट ब्रांच एक्सचेंज. Each word carries meaning: * **Private.** The organisation uses the switch for its own people, instead of the public network serving everyone. * **Branch.** The system hangs off the public telephone network like a branch, with its own smaller set of phones. * **Exchange.** It switches calls, the same job a telephone exchange does for a city. The surrounding acronyms record how the technology changed. [Operators with cord circuits ran the first company switchboards](https://en.wikipedia.org/wiki/Business_telephone_system), and "automatic" and "manual" variants were named once machines took over. [TechTarget notes](https://www.techtarget.com/news/private-branch-exchange-PBX/850458/) that the distinction has faded, so PBX and PABX now describe the same system. | Term | Full form | What it signals today | | - | - | - | | **PBX** | Private Branch Exchange | The general term for the whole category | | **PMBX** | Private Manual Branch Exchange | Historic, an operator connected every call | | **PABX** | Private Automatic Branch Exchange | Same as PBX in current use | | **EPABX** | Electronic Private Automatic Branch Exchange | The usual Indian term, often meaning a hardware box | | **IP PBX** | Internet Protocol PBX | A PBX that carries calls over IP | | **Soft PBX** | Software PBX | An [IP PBX that runs as software](https://en.wikipedia.org/wiki/Business_telephone_system) instead of dedicated hardware | | **Hosted or cloud PBX** | No separate expansion | A third party runs the PBX and you use it as a service | Don't read too much into a label on a quote. [RFC 7092](https://www.rfc-editor.org/info/rfc7092/) says plainly that "SIP PBX" is a market category rather than something a standard specifies. Ask what the product connects to and who operates it. ## What does a PBX actually do? A PBX does three jobs. Most feature lists are variations on the third one. ![Diagram of a PBX. On the left, an IP desk phone, a softphone, and an analog phone connect as extensions. In the centre, the PBX holds a registrar, dial plan, switch, and features. On the right, a SIP trunk, an E1 PRI, and an analog line connect outwards. An internal call uses no outside channel, and an outside call holds one channel until it ends.](https://mintcdn.com/vobizai/zgiAJLirDTpgnhEe/images/blog/what-is-a-pbx/pbx-anatomy-light.svg?fit=max\&auto=format\&n=zgiAJLirDTpgnhEe\&q=85\&s=83fb6738ab1347fd036ec92b797a49f5) **It shares outside lines.** Not everyone is on an outside call at once, so a pool can serve many people. [Sharing also cuts the lines you need](https://en.wikipedia.org/wiki/Business_telephone_system) from the public network. **It connects internal calls.** Two extensions can talk without touching the public network. That was the original cost saving, and it still means an internal call takes no outside channel. **It applies your rules.** The dial plan decides what each dialled digit means, which trunk an outside call uses, and who may call where. Call-handling features sit on top of it: | Feature | What it does for you | | - | - | | **Extension dialling** | Staff reach each other with short numbers | | **Auto attendant or [IVR](https://www.vobiz.ai/docs/blogs/what-is-an-ivr.md)** | A menu sends callers to the right team | | **Ring groups and hunting** | Several phones ring together, or one after another | | **Queues** | Callers wait for the next free person | | **Voicemail** | Callers leave a message when nobody answers | | **Transfer and conference** | Staff move a live call or add people to it | | **Call recording and call logs** | You keep records for quality and audits | ## How does a call move through a PBX? Follow one inbound call on an IP PBX connected by a SIP trunk: 1. **The carrier delivers the call.** A caller dials your [DID number](https://www.vobiz.ai/docs/blogs/what-is-a-did-number.md), and the carrier sends a SIP `INVITE` down the trunk. 2. **The dial plan matches the number.** The PBX maps that number to a destination, such as a menu, a queue, or one extension. 3. **A channel is now held.** The call occupies one trunk channel from this moment, even while it waits in a menu or queue. 4. **The registrar finds the phone.** Each phone earlier sent a `REGISTER`, and [the registrar stored that binding](https://www.rfc-editor.org/info/rfc3261/), so the PBX knows the phone's current address. 5. **The PBX starts a second call leg.** It rings the phone and joins the two legs when someone answers. 6. **Audio flows.** Audio follows either a path through the PBX or a direct path between endpoints, depending on the design. 7. **The channel frees up.** A hang-up from either side releases the channel to the pool. ### Why a PBX is usually two calls joined together A SIP PBX commonly behaves as a back-to-back user agent, which ends one SIP call and originates another. That is why it can change headers, numbers, and codecs between the two sides. [RFC 7092](https://www.rfc-editor.org/info/rfc7092/) explains that a SIP PBX can take on any of the roles it lists, so one product can relay media while another handles only signalling. This affects your design in two ways: * **Media through the PBX** lets it record calls and convert codecs, but it consumes server capacity and bandwidth at that site. * **Direct media** removes that load, but both ends must reach each other through any firewalls between them. ### Registration runs in both directions Phones register with the PBX, and a PBX can also register with its carrier. [RFC 6140](https://www.rfc-editor.org/info/rfc6140/) defines how a PBX registers with a SIP provider to receive calls for many numbers at once. Some carriers instead send calls to a fixed address, so check which model your [SIP trunk](https://www.vobiz.ai/docs/blogs/what-is-sip-trunking.md) uses. ### What physically connects to a PBX | Connection | Side | What to know | | - | - | - | | **IP phone or softphone** | Extension | Uses your LAN or the internet, and registers over SIP | | **Analog phone** | Extension | Plugs into an [FXS port, which supplies dial tone and ringing](https://en.wikipedia.org/wiki/Foreign_exchange_service_\(telecommunications\)) | | **Analog exchange line** | Trunk | Plugs into an FXO port, and carries one call at a time | | **E1 PRI** | Trunk | [TRAI describes each PRI as 30 channels on a 2 Mbps line](https://www.trai.gov.in/sites/default/files/2025-02/Recommendation_06022025.pdf) | | **SIP trunk** | Trunk | Carries as many channels as your plan and bandwidth allow | | **Session border controller** | Edge | [Hides topology and handles NAT traversal and protocol repair](https://www.rfc-editor.org/info/rfc5853/) between networks | ## Which type of PBX fits you: EPABX, IP PBX, or cloud? Vendors compare feature lists, but the more useful comparison is who owns each layer of work. ![Grid of four PBX models against six layers. With an on-site EPABX or IP PBX, you handle hardware, software, patching, and lines. With an IP PBX on a rented server, the host handles hardware and you handle the rest. With a hosted PBX, the provider handles hardware, software, and patching, and lines are often bundled. When the internet drops, an EPABX on PRI keeps working, an on-site IP PBX on a SIP trunk keeps internal calls only, and the other two lose calls.](https://mintcdn.com/vobizai/zgiAJLirDTpgnhEe/images/blog/what-is-a-pbx/who-runs-what-light.svg?fit=max\&auto=format\&n=zgiAJLirDTpgnhEe\&q=85\&s=80fc3f82953f76c4c7b02f1acfd2d78f) Three practical consequences follow: * **Failure modes differ.** A box on site still needs power and a UPS. A hosted PBX depends on your internet path, so ask whether calls can fail over to a mobile number. * **Remote work favours server-based models.** A phone on an app reaches a hosted or rented-server PBX over the internet. An on-site PBX needs a VPN or a border controller first. * **Hybrid systems exist for migration.** A [hybrid PBX handles PRI and SIP together](https://telecomssupermarket.in/blog/epabx-system-india-buyers-guide), so you can move lines in stages. ### What does a PBX cost over five years? Prices vary widely, so use the chart as a template for your own quotes. It takes the midpoints of the 2026 ranges published by one Indian telecom comparison site, for 25 users. | Input | Published range | Midpoint used | | - | - | - | | [EPABX for 25 users](https://telecomssupermarket.in/blog/cloud-pbx-vs-epabx-india-2026) | ₹80,000 to ₹2,50,000 | ₹1,65,000 | | [Installation](https://telecomssupermarket.in/blog/epabx-system-india-buyers-guide) | ₹5,000 to ₹30,000 | ₹17,500 | | [IP handsets](https://telecomssupermarket.in/blog/epabx-system-india-buyers-guide) | ₹3,000 to ₹15,000 each | ₹2,25,000 for 25 | | [Annual maintenance](https://telecomssupermarket.in/blog/epabx-system-india-buyers-guide) | 10% to 15% of hardware cost | ₹20,625 a year | | [Cloud PBX](https://telecomssupermarket.in/blog/cloud-pbx-vs-epabx-india-2026) | ₹400 to ₹900 per user per month | ₹1,95,000 a year | ![Illustrative line chart of cumulative cost for 25 users. An on-site EPABX starts at 4.08 lakh rupees and reaches 5.11 lakh by year five. A hosted PBX starts at zero and reaches 9.75 lakh by year five. The lines cross at about 2.3 years.](https://mintcdn.com/vobizai/zgiAJLirDTpgnhEe/images/blog/what-is-a-pbx/five-year-cost-light.svg?fit=max\&auto=format\&n=zgiAJLirDTpgnhEe\&q=85\&s=ee2a4bfd50825582e47f565700ed0456) The crossing point depends heavily on the seat price. It moves to about 1.6 years at ₹900 per seat and about 4.1 years at ₹400 per seat. Our arithmetic is deliberately narrow. It leaves out call charges, lines, staff time, a UPS, and hardware replacement, and all of those shift the answer. It also counts IP handsets on the on-site side only, assuming hosted users work from an app. Count handsets on both sides, or on neither, and the starting gap falls to ₹1,82,500 and the lines cross at about one year. The same site [concludes that cloud usually costs less over three years below about 150 users](https://telecomssupermarket.in/blog/cloud-pbx-vs-epabx-india-2026), so add your real staff and line costs before you trust either view. ## How many outside channels does a PBX need? Size channels from traffic, because headcount alone tells you little. Traffic is measured in [erlangs](https://en.wikipedia.org/wiki/Erlang_\(unit\)), and one erlang is one channel busy for a full hour. Start with what each extension does in your busiest hour: * **A quiet office line** might spend 6 minutes on outside calls, or 0.1 erlang. * **A busy sales or support line** might spend 15 minutes, or 0.25 erlang. Both figures are illustrative. Replace them with your own call logs if you have any. Then multiply by your extensions and apply the Erlang B formula, which gives the channels needed for a target share of blocked calls. ![Line chart of outside channels against extensions at 1 percent blocking. At 0.1 erlang per extension, 50 extensions need 11 channels, 200 need 30, and 500 need 64. At 0.25 erlang per extension, 50 extensions need 21 channels, 200 need 64, and 500 need 144. A dashed line marks the 30 channels of one E1 PRI.](https://mintcdn.com/vobizai/zgiAJLirDTpgnhEe/images/blog/what-is-a-pbx/channels-vs-extensions-light.svg?fit=max\&auto=format\&n=zgiAJLirDTpgnhEe\&q=85\&s=3839d5548d3670e88de63a85d2d0bacd) | Extensions | Channels at 0.1 erlang each | Channels at 0.25 erlang each | | - | - | - | | 25 | 7 | 13 | | 50 | 11 | 21 | | 100 | 18 | 36 | | 200 | 30 | 64 | | 500 | 64 | 144 | We calculated these with the Erlang B recursion at 1% blocking. A few points affect how you use them: * **One E1 goes a long way.** Thirty channels carry about 20 erlangs at 1% blocking. That covers roughly 200 quiet extensions or 80 busy ones. * **Bandwidth follows channels.** TRAI puts a [SIP call at about 87 kbps with G.711 and 32 kbps with G.729](https://www.trai.gov.in/sites/default/files/2025-02/Recommendation_06022025.pdf). So 21 G.711 channels need about 1.8 Mbps in each direction. * **Small pools are approximate.** Erlang B assumes a large calling population, so it can overstate the need for a small office. Treat its result as a safe upper estimate there. * **Bursts break the model.** An outage or a campaign makes callers arrive together and redial, so add headroom when that can happen. Our [SIP trunking guide](https://www.vobiz.ai/docs/blogs/what-is-sip-trunking.md) works a larger example and covers outbound diallers, which need different math. ## Do you need a PBX at all? Not every phone setup needs one. Work through these four questions in order. ![Decision map with four questions. If only software answers calls, skip the PBX and use a voice API or agent. If several people do not share business numbers, forward the number to a phone. If you already run a working PBX or EPABX, keep it and move lines to a SIP trunk. If you can run a server or need on-site calls during an internet cut, run an IP PBX with a SIP trunk. Otherwise, use a hosted PBX.](https://mintcdn.com/vobizai/zgiAJLirDTpgnhEe/images/blog/what-is-a-pbx/pbx-decision-map-light.svg?fit=max\&auto=format\&n=zgiAJLirDTpgnhEe\&q=85\&s=196a3f7277b4a5c6323e6e4305cfc9a6) **You probably need a PBX when:** * Several people share business numbers and transfer calls between them. * Staff use desk phones and dial each other by extension. * You run reception, department lines, or a small support queue with people answering. **You probably don't need one when:** * One or two people can answer a forwarded number. * Software handles the call, as with OTP calls, reminders, or an AI voice agent. A [voice API](https://www.vobiz.ai/docs/blogs/what-is-a-voice-api.md) fits this better. * Your product places calls from code. Compare [SIP with WebSocket streaming](https://www.vobiz.ai/docs/concepts/sip-vs-websockets.md) instead. **A migration is worth planning when:** * The vendor has stopped issuing security updates or spare parts. * Remote staff can't get extensions without awkward workarounds. * A line contract is ending, which gives you a natural moment to compare options. ## How is a PBX different from similar systems? These terms get mixed up on quotes and in meetings. | Compared with | The real difference | | - | - | | **SIP trunk** | The PBX routes calls. The trunk connects the PBX to the public network. | | **VoIP** | [VoIP](https://www.vobiz.ai/docs/blogs/what-is-voip.md) is how voice travels over IP. A PBX may or may not use it. | | **IVR** | An IVR is a menu. It can be one feature of a PBX, or run without one. | | **Contact centre platform** | It adds agent routing and reporting for teams whose main job is calls. | | **Key telephone system** | [Users pick outside lines by hand on a key system](https://en.wikipedia.org/wiki/Business_telephone_system), while a PBX selects one automatically. | | **Centrex** | [The carrier provides PBX-style features from its own exchange](https://en.wikipedia.org/wiki/Business_telephone_system), a model dating from the 1960s. | | **Voice API** | Your application controls each call, so routing lives in your code. | ## What Indian rules apply to a PBX? India's rules depend on what you do with the PBX. They are also moving, because [DoT now issues authorisations under the Telecommunications Act, 2023, and existing licences can migrate](https://eservices.dot.gov.in/autho/about-authorisation-portal). Confirm the current text and take legal advice for your own case. | Your situation | What the text says | Source | | - | - | - | | **You sell a cloud EPABX service** | Commercial supply falls under the enterprise communication service authorisation. The definition covers EPABX-as-a-service and communications platform-as-a-service. | [Miscellaneous Services Rules, G.S.R. 512(E)](https://eservices.dot.gov.in/sites/default/files/circular-notifications/misc-telecom-services-rules-2026.pdf), rule 50, 23 June 2026 | | **Same provider's duties** | Keep customers logically partitioned, keep partition logs for two years and user records for one year, and don't allow illegal passing of long-distance traffic. | Same rules, rules 55 and 56 | | **You run a voice BPO** | No OSP registration is needed. EPABX sharing for office use, foreign EPABX, third-party data centres in India, and EPABX services from telecom providers are all addressed. | [DoT OSP guidelines](https://www.dot.gov.in/static/uploads/2025/08/4e6e21029dc45f42b4e1e57e6300fa72.pdf), 23 June 2021 | | **BPO records** | Keep CDRs and system logs for one year, with a copy at an OSP centre in India. Show the agent against each call. | Same guidelines, chapter 5 | | **You run an ordinary office PBX** | Businesses without voice BPO services aren't regulated under the OSP guidelines. | Same guidelines, chapter 2 | | **You call for marketing** | Use the 140xx series, after registering with your telecom provider. | [TRAI press release 91/2026](https://www.trai.gov.in/sites/default/files/2026-07/PR_No91of2026.pdf), 10 July 2026 | | **You are a BFSI or government sender** | Use the 1600xx series for service and transaction calls. | Same press release | | **You break spam rules** | First instance: outgoing services barred for 15 days. Repeat: all resources, including PRI and SIP trunks, disconnected for one year. | [TCCCPR Second Amendment](https://www.trai.gov.in/sites/default/files/2025-02/Regulation_12022025.pdf), February 2025. The [Third Amendment text](https://www.medianama.com/wp-content/uploads/2026/09/trai-amendments-unsolicited-communications.pdf), September 2026, repeats these terms | Four points need more care. **Ask a hosted provider about its authorisation.** Before the 2026 rules, [Khaitan & Co read the 2021 guidelines](https://khaitanco.com/sites/default/files/2021-06/Ergo_25062021_0.pdf) as silent on hosted contact-centre services from non-telecom companies. The Gazette text now names the service, and [DoT's portal says migrations are open](https://eservices.dot.gov.in/autho/about-authorisation-portal). Ask which authorisation or licence your provider holds. **Toll bypass is the classic PBX trap.** Linking offices tempts you to save money by carrying public calls across your own network. The OSP guidelines define [toll bypass](https://www.dot.gov.in/static/uploads/2025/08/4e6e21029dc45f42b4e1e57e6300fa72.pdf) as illegal carriage of calls between the public network in two Indian cities, or between India and abroad, over your own network. Internal calls within a closed user group are treated separately. Those definitions apply to OSPs, so get advice before you link sites on any other basis. **Running your own PBX looks different from selling one.** Part B of the Miscellaneous Rules covers services provided "on commercial basis". We found no mention of EPABX in the [Captive Services Rules](https://eservices.dot.gov.in/sites/default/files/circular-notifications/captive-telecom-services-rules-2026.pdf), and no mention of OSPs or EPABX in the [Principal Services Rules](https://eservices.dot.gov.in/sites/default/files/circular-notifications/principal-telecom-services-rule-2026.pdf). We could not confirm whether the 2021 OSP text is being replaced, so check it before you design a BPO network. **Every DID counts.** Under the TCCCPR amendment, [each DID on a PRI or SIP trunk is a separate resource](https://www.trai.gov.in/sites/default/files/2025-02/Regulation_12022025.pdf) when restoration charges apply. Those charges are ₹5,000 per resource, capped at ₹5 lakh. The [September 2026 Third Amendment text](https://www.medianama.com/wp-content/uploads/2026/09/trai-amendments-unsolicited-communications.pdf) repeats both points. It takes effect a set number of days after Gazette publication, and we could not confirm that date. TRAI has also [recommended monitoring enterprise allocations above 15 numbers per Mbps](https://www.trai.gov.in/sites/default/files/2025-02/Recommendation_06022025.pdf). That is a February 2025 recommendation, and we could not confirm its current status. Our SIP trunking guide tracks the [September 2026 change on automated calls](https://www.vobiz.ai/docs/blogs/what-is-sip-trunking.md#what-rules-apply-to-sip-trunks-in-india), which matters if a dialler sits behind your PBX. ## How do you secure a PBX? Attackers want your outside lines, because calls placed through your PBX land on your bill. NIST's 2001 PBX report called [toll fraud probably the most common motive](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-24.pdf) and warned about remote maintenance access. [NIST withdrew it in 2018](https://csrc.nist.gov/pubs/sp/800/24/final) because it predates VoIP, so read it as history, but the motive is still easy to recognise. 1. **Never expose the admin console.** Reach it through a VPN, and remove default accounts. 2. **Use strong extension passwords.** A guessed SIP password turns any extension into a paid outside line. 3. **Limit dialling by role.** Block international and premium destinations for extensions that don't need them. 4. **Put a controlled edge in front.** Use an [SBC](https://www.rfc-editor.org/info/rfc5853/) or a narrow firewall policy, and encrypt signalling and media where both sides support it. 5. **Lock down voicemail.** Change default PINs, and disable any feature that dials out from voicemail. 6. **Watch the call logs.** Alert on night-time spikes and destinations you never call. 7. **Keep it patched.** Assign a named owner for updates. ## How Vobiz fits with a PBX You can connect Vobiz to your own PBX, or build PBX-style call flows on Vobiz directly. **Connect your existing or new PBX over a SIP trunk:** * **Compatible systems.** Vobiz supports [FreeSWITCH, Asterisk, 3CX, Cisco CallManager, and legacy PBXs](https://www.vobiz.ai/docs/faq/integrations.md) over standard SIP trunking. * **Outbound.** An [outbound trunk](https://www.vobiz.ai/docs/platform/sip/outbound-trunks.md) gives your PBX its own SIP domain to send calls to. * **Authentication.** Attach an [IP Access Control List](https://www.vobiz.ai/docs/platform/sip/ip-access-control-list.md) for a fixed address, or a [SIP credential](https://www.vobiz.ai/docs/platform/sip/credentials.md) if your address changes. * **Inbound.** An [inbound trunk](https://www.vobiz.ai/docs/platform/sip/inbound-trunks.md) forwards calls for its linked numbers to an [origination URI](https://www.vobiz.ai/docs/platform/sip/origination-uri.md) that points at your PBX. * **A worked setup.** The [3CX guide](https://www.vobiz.ai/docs/integrations/3cx.md) walks through the trunk, DIDs, and tests. * **Firewalls.** Use the [IP whitelisting page](https://www.vobiz.ai/docs/concepts/ip-whitelisting.md) for the current signalling and media ranges. * **Keeping your carrier.** [Bring Your Own Carrier](https://www.vobiz.ai/docs/concepts/bring-your-own-carrier.md) lets your numbers and on-premise PBX stay where they are. * **Transfers.** [SIP REFER is supported on verified trunks](https://www.vobiz.ai/docs/faq/call-transfer.md), so a PBX can trigger transfers at the network layer. **Or build the behaviour you need with VobizXML and endpoints:** | PBX feature | Vobiz building block | | - | - | | Extensions | [SIP endpoints](https://www.vobiz.ai/docs/platform/voice/endpoints.md) for softphones, browsers, and WebRTC clients | | Ring group | [Simultaneous dialling](https://www.vobiz.ai/docs/xml/dial/simultaneous-dialing.md) with `` | | Hunting | [Sequential dialling](https://www.vobiz.ai/docs/xml/dial/sequential-dialing.md) through the Dial `action` URL | | Auto attendant | [``](https://www.vobiz.ai/docs/xml/gather) for DTMF or speech input, as in the [IVR example](https://www.vobiz.ai/docs/examples/vobiz-ivr-xml-python.md) | | Queue | The [call queue example](https://www.vobiz.ai/docs/examples/vobiz-call-queue-xml-python.md), with hold music and round-robin dispatch | | Voicemail | [`` as a voicemail](https://www.vobiz.ai/docs/xml/record/record-a-voicemail) | | Conference | [``](https://www.vobiz.ai/docs/xml/conference) | **Capacity and India details for either path:** * **Channels.** [Concurrency](https://www.vobiz.ai/docs/platform/capacity/concurrency.md) caps live calls per account, and each inbound or outbound call takes one channel. Use your sizing above with the [CPS and concurrency calculator](https://www.vobiz.ai/docs/resources/calculator.md). * **Compliance.** [India calling regulations](https://www.vobiz.ai/docs/compliance/india/calling-regulations.md) cover eligibility, KYC, caller ID, and media anchoring, under which both legs of an Indian call stay in India. * **Pricing.** Current rates are on the [Vobiz pricing page](https://www.vobiz.ai/pricing/). Test calls and capacity purchases are billed to your account. Run them with your own Auth ID and Auth Token, and confirm numbers and quantities first. ## Frequently asked questions > [accordion] What is the full form of PBX? > > The full form is Private Branch Exchange. This telephone switch serves one organisation and its staff. It connects internal extensions to each other and shares a pool of outside lines among them. > [accordion] What is the difference between PBX, PABX, and EPABX? > > PABX adds Automatic, and EPABX adds Electronic, to the same idea. PABX once separated automatic switches from manual ones. Today all three usually describe the same kind of system. EPABX is the common term in India and appears in DoT rules. > [accordion] What is the difference between a PBX and a SIP trunk? > > A PBX decides where calls go inside your organisation. A SIP trunk connects that PBX to the public phone network over IP. You usually need both, unless a hosted PBX provider bundles the connection or your application handles calls without a PBX. > [accordion] What is a PBX number? > > People use the phrase for two things. One is the main public number that reaches the PBX. The other is a short internal extension, such as 201. A DID is a public number that the PBX can route straight to one extension. > [accordion] Does a small business need a PBX? > > Only if several people share business numbers and need transfers, extensions, or queues. One or two people can forward a number to their phones. Small teams that do need those features usually start with a hosted PBX, because nobody has to run a server. > [accordion] Is a PBX obsolete? > > The function is not obsolete, because staff still need to share numbers and transfer calls. The form keeps changing, from cord switchboards to electronic exchanges, IP PBX software, and hosted services. Replace an old box when spares, security updates, or line contracts force the question. ## Further reading on Vobiz * [What is SIP trunking?](https://www.vobiz.ai/docs/blogs/what-is-sip-trunking.md) * [What is a DID number?](https://www.vobiz.ai/docs/blogs/what-is-a-did-number.md) * [What is call routing?](https://www.vobiz.ai/docs/blogs/what-is-call-routing.md) * [SIP vs VoIP](https://www.vobiz.ai/docs/blogs/sip-vs-voip.md) * [SIP trunking overview](https://www.vobiz.ai/docs/platform/sip/overview.md) * [Connect 3CX to Vobiz](https://www.vobiz.ai/docs/integrations/3cx.md) ## Sources **Indian regulators** * DoT, [Telecommunications (Authorisation for Provision of Miscellaneous Telecommunication Services) Rules, 2026, G.S.R. 512(E)](https://eservices.dot.gov.in/sites/default/files/circular-notifications/misc-telecom-services-rules-2026.pdf), 23 June 2026. * DoT, [Telecommunications (Authorisation for Provision of Captive Telecommunication Services) Rules, 2026](https://eservices.dot.gov.in/sites/default/files/circular-notifications/captive-telecom-services-rules-2026.pdf), 2026. * DoT, [Telecommunications (Authorisation for Provision of Principal Telecommunication Services) Rules, 2026](https://eservices.dot.gov.in/sites/default/files/circular-notifications/principal-telecom-services-rule-2026.pdf), 2026. * DoT, [Authorisation Portal](https://eservices.dot.gov.in/autho/about-authorisation-portal), read November 3, 2026. * DoT, [Revised Guidelines for Other Service Providers](https://www.dot.gov.in/static/uploads/2025/08/4e6e21029dc45f42b4e1e57e6300fa72.pdf), 23 June 2021. * TRAI, [Telecom Commercial Communications Customer Preference (Second Amendment) Regulations, 2025](https://www.trai.gov.in/sites/default/files/2025-02/Regulation_12022025.pdf), February 2025. * TRAI, [Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026, copy hosted by MediaNama](https://www.medianama.com/wp-content/uploads/2026/09/trai-amendments-unsolicited-communications.pdf), 18 September 2026. * TRAI, [Press release 119/2026 on the Third Amendment](https://www.trai.gov.in/sites/default/files/2026-09/PR_No119of2026.pdf), 18 September 2026. * TRAI, [Recommendations on Revision of National Numbering Plan](https://www.trai.gov.in/sites/default/files/2025-02/Recommendation_06022025.pdf), 6 February 2025. * TRAI, [Press release 91/2026 on the 1600 and 140 series](https://www.trai.gov.in/sites/default/files/2026-07/PR_No91of2026.pdf), 10 July 2026. * Khaitan & Co, [DoT's re-vision to the OSP framework](https://khaitanco.com/sites/default/files/2021-06/Ergo_25062021_0.pdf), June 2021. **Standards and government references** * IETF, [RFC 3261: SIP: Session Initiation Protocol](https://www.rfc-editor.org/info/rfc3261/), June 2002. * IETF, [RFC 5853: Requirements from SIP Session Border Control Deployments](https://www.rfc-editor.org/info/rfc5853/), April 2010. * IETF, [RFC 6140: Registration for Multiple Phone Numbers in SIP](https://www.rfc-editor.org/info/rfc6140/), March 2011. * IETF, [RFC 7092: A Taxonomy of SIP Back-to-Back User Agents](https://www.rfc-editor.org/info/rfc7092/), December 2013. * NIST, [SP 800-24: PBX Vulnerability Analysis](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-24.pdf), April 2001, [withdrawn in 2018](https://csrc.nist.gov/pubs/sp/800/24/final). **Industry and reference** * TechTarget, [What is a private branch exchange?](https://www.techtarget.com/news/private-branch-exchange-PBX/850458/). * Telecoms Supermarket India, [Cloud PBX vs EPABX](https://telecomssupermarket.in/blog/cloud-pbx-vs-epabx-india-2026), updated September 2026. * Telecoms Supermarket India, [EPABX system buyer's guide](https://telecomssupermarket.in/blog/epabx-system-india-buyers-guide), updated September 2026. * Wikipedia, ["Business telephone system"](https://en.wikipedia.org/wiki/Business_telephone_system). * Wikipedia, ["Erlang (unit)"](https://en.wikipedia.org/wiki/Erlang_\(unit\)). * Wikipedia, ["FXO and FXS"](https://en.wikipedia.org/wiki/Foreign_exchange_service_\(telecommunications\)). > [card] [Connect your PBX to Vobiz](https://www.vobiz.ai/docs/quick-start.md) > > Set up a SIP trunk and place your first call. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.