Questions answered
Answered at the level asked, grouped by layer where that helps.
The layers
What they are and how they are taken.
No. Most organisations take one or two. The boundaries mean adding another later does not require unpicking the first, which is the usual reason estates end up with two suppliers.
Yes. Control can sit above a trunk you already own, and numbering can terminate into a phone system that is not ours. The failure boundary is then partly outside our control, and the design says so rather than implying otherwise.
Whichever one is failing. Blocked calls means connectivity, calls reaching the wrong place means control, a number unreachable means numbering, and something that broke after a change means operation.
Because in a mature estate change causes more incidents than component failure does. Treating it as an activity rather than as a bounded layer is how those incidents happen.
Technical
Capacity, quality, transport and interoperability.
If it speaks SIP, almost certainly. Legacy TDM platforms connect behind a gateway during transition. Unusual or heavily customised platforms are proven on a trial trunk before production traffic.
Roughly 100 kbps per concurrent call with common codecs and overheads. Bandwidth is rarely the binding constraint; queuing delay and jitter are, which is why prioritisation matters more than headline speed.
Jitter, packet loss, round-trip time and completion cause, per call, retained. That is the basis for both fault location and capacity review.
TLS signalling and SRTP media are the default where the endpoint supports them. Where one cannot, the exception is recorded and revisited rather than silently accepted.
Minutes after agreement. It is a configuration value; no site visit and nothing to install.
Security and evidence
Controls, defaults and what they produce.
Encrypted signalling and media where supported, address-based authorisation for fixed sites, destination policy denying by default, enforced concurrency ceilings, automatic spend containment, and role-based access with individual attribution.
Configuration records, policy records with change history, threshold configuration with an alert log, access logs with periodic review records, and per-change before and after state. Producible without additional collation.
This site makes no certification, accreditation, regulatory approval or carrier authorisation claim. Where a specific status bears on procurement, ask and the answer will be precise and in writing, including where it is no.
Where an endpoint genuinely cannot support something, yes — as a recorded exception attributable to a named person, revisited at the next review rather than becoming permanent by inattention.
Commercial
Figures, terms and their limits.
Because none of them could be checked by the person reading them. The layer boundaries, the protections and the failure behaviour can all be examined and disputed, so those carry the argument instead.
An access circuit we did not supply, a phone system we do not operate, or a network we cannot configure. A single-circuit site is bounded by that circuit regardless of the layer boundaries above it, and the design states that.
Because we would publish only what we had explicit permission to publish, and we do not manufacture social proof. If a reference matters, ask and we will say what can be arranged.
Against an agreed specification rather than a rate card. A figure produced before the measurement stage would be an estimate presented as a specification.
Term, notice period and early termination position are set out in writing before signature. Automatic renewal is not used as a retention mechanism.
Documented at length
Each layer page states its boundary, its protection and its failure behaviour in full.
Connectivity
The outermost layer. Whether a call can happen at all.
Open Layer twoControl
Where a call goes, and what happens when nobody answers.
Open Layer threeNumbering
What a caller dials, and whether it can ever be unreachable.
Open Layer fourOperation
Change, treated as a layer because it causes more incidents than failure does.
Open