From the business's point of view, inbound is simple: the phone rings because someone else placed the call. From the network's point of view, that call had to be routed through numbering plans, interconnects, and a last-hop delivery onto a SIP trunk, a PRI, or a WebRTC client. The published target is almost always a DID (Direct Inward Dialing) in E.164 form, which may be a local number or a toll-free number.
Contact centers, reception desks, and after-hours services are inbound-heavy. The quality of that experience depends on more than audio: time to answer, how ANI / Caller ID is presented, whether DTMF reaches the IVR, and what happens when every agent is busy.
What counts as inbound
A call is inbound to a business when the destination number is one the business owns or rents, regardless of who pays for the minutes. The caller may be on a mobile, a landline, or another VoIP system. The media may stay IP end to end or cross a TDM gateway. Direction is defined by numbering and routing, not by which side is using IP.
- Customer support and sales lines that appear on a website or invoice.
- Toll-free numbers, where the business pays for the inbound leg.
- Personal DIDs on a hunt group so a department can be reached without a private branch number.
- Failover targets: an inbound number that forwards to a mobile when the office is closed.
Origination versus termination
Carriers name these directions from their own perspective, which is the opposite of how a contact center describes them. Origination is the service of accepting a call from the public network and delivering it to a VoIP customer (inbound to the business). Termination is the service of accepting a call from a VoIP customer and completing it on the public network (outbound from the business). Invoices, rate decks, and capacity contracts follow that split, not the words agents use.
A single conversation can be origination on one interconnect and termination on another. If Alice, calling from the PSTN, dials Bob's company DID, her carrier hands the call to the DID's carrier, which originates it toward Bob's PBX. If Bob then conferences an outside party, that second leg is termination.
How inbound calls are routed after they land
Delivery to the trunk is only the first hop inside the company. A typical inbound treatment is a sequence of applications:
- Number identification: which DID was dialed (the DNIS, Dialed Number Identification Service). One trunk can host thousands of DIDs with different treatments.
- Schedule and flags: open hours, holidays, emergency close.
- IVR: play a prompt, collect DTMF or speech, branch.
- ACD-style distribution: hunt groups (simultaneous or sequential ring) or call queues with hold treatment.
- Overflow: forward to another number, voicemail, or a callback.
Automatic Call Distribution (ACD) is the contact-center name for the last steps: skills, longest-idle, and service-level timers. A small office may only need a simultaneous ring. Either way, the network did the same job: it delivered an inbound call.
Identity on inbound calls
The calling party is presented as Caller ID (often the calling number in E.164 or national format) and optionally a name. Two related identifiers appear in carrier systems: ANI (Automatic Number Identification), historically the billing number, and the signaling calling-party number, which may differ after forwarding or a PBX rewrite. CNAM is a name lookup keyed off that number, not a cryptographically proven identity.
Inbound STIR/SHAKEN attestation, when present, tells the terminating network how much the originating provider stands behind the calling number. It is a tool against Caller ID spoofing and robocalls. It does not by itself prove that the human on the line is who the name says.
Inbound versus outbound
| Inbound traffic | Outbound traffic | |
|---|---|---|
| Business direction | Calls toward a number you publish | Calls you place toward someone else's number |
| Carrier term (typical) | Origination onto your trunk | Termination off your trunk |
| You control | DIDs, hours, IVR, queues, recording policy | Dial list, CLI, pacing, consent records |
| Identity that matters | Calling ANI / Caller ID of the visitor | Your CLI, CNAM, and STIR/SHAKEN attestation |
| Common bottlenecks | Simultaneous inbound channels, queue time, IVR depth | CPS limits, carrier tracebacks, TCPA rules |
| Failure the caller sees | Busy, endless ring, wrong menu, dropped queue | Failed call setup, spam labeling, blocked CLI |
Capacity, concurrency, and overflow
Inbound capacity is measured in simultaneous calls (and sometimes in calls per second at the edge). A trunk sized for average load will reject or delay bursts: a TV spot, an outage, a storm. Overflow policies (forwarding, extra queue slots, a recorded apology) are part of inbound design, not an afterthought.
Audio quality on inbound is the same physics as any other VoIP path (see call quality), with one extra constraint: you do not choose the caller's last-mile network. G.711 at the PSTN border is common. HD Voice appears only when the inbound hop is IP end to end and both sides negotiate a wideband codec.
- DNIS
- The number the caller dialed, used to select a tenant, language, or campaign on a shared trunk.
- ACD
- Automatic Call Distribution: rules that pick an agent from a queue or hunt group.
- Concurrent inbound
- How many inbound sessions the trunk, licenses, and agents can hold at once.