On-prem to SBC to ITSP: the full call path

A single outbound office call actually crosses three separate systems, each trusting the next just enough and no more. Here is the whole chain, end to end.

The full chain, end to end

A single outbound call from an office phone crosses at least three systems that each have to trust the next one just enough, and no more. Seeing the whole chain at once makes it obvious why enterprise telephony problems are so often about the seams between systems, not the systems themselves.

Stage 1: your PBX decides where the call should go

The call starts at your PBX, which applies your dial plan, checks permissions, and decides this call needs to leave the building. It hands the call to a trunk pointing at your SBC, not directly to the outside world.

Stage 2: your SBC becomes the trusted edge

The SBC receives it, rewrites the signaling to hide your internal topology, applies your security policy, and re-originates the call outward as a request your carrier is actually willing to accept from an unknown internal network.

Stage 3: your ITSP puts it on the real phone network

The call now leaves your organisation entirely and reaches your ITSP over the SIP trunk you provisioned with them. From here it is their job to route it across the wider phone network, whether that means the PSTN, another carrier, or straight to a mobile network.

Why this chain matters when something breaks

A call failing somewhere in this chain can look identical from the phone that placed it, no matter which of the three stages actually failed. Reading a SIP trace and knowing which device generated which message is what turns "the phone system is broken" into an actual, fixable diagnosis.