Voice over IP
Enable an agent to recognise a Voice over IP implementation, assess whether it can deliver usable voice communication, and identify justified configuration, troubleshooting or service actions.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
recalled by Codex without web access - no source was read
Researched by: Codex
Purpose and description
Enable an agent to recognise a Voice over IP implementation, assess whether it can deliver usable voice communication, and identify justified configuration, troubleshooting or service actions.
Voice over IP (VoIP) is a family of technologies for carrying digitized speech in packets over Internet Protocol networks to support voice communication, usually with associated call signalling.
It can be Trace a failed or degraded call across signalling, media, endpoint and interconnection boundaries.; Compare negotiated voice capabilities and identify a compatible configuration.; Assess measured voice quality against an explicitly chosen service target.; Identify exposed trust boundaries and propose authorised changes to voice access and protection controls.; Evaluate whether routing, capacity or failover changes preserve required calling capabilities.; Record unresolved service limitations before recommending adoption or operational changes..
Distinguishing features
The voice media itself traverses an IP network; IP-based call control alone does not establish that the bearer is VoIP.
The implementation supports voice session delivery, rather than merely transferring stored audio files.
Use of a private IP network still qualifies; public Internet carriage is not a defining requirement.
A telephone number, a physical desk phone or a particular signalling protocol is not required for recognition.
Where a gateway connects IP voice to circuit-switched telephony, the model distinguishes the IP segment from the converted segment.
Scope
+ Voice capture, encoding, packet transport, reception and playout across IP networks
+ Call signalling, session negotiation and the relationship between signalling and media paths
+ Voice quality, network impairments and service continuity
+ Endpoint, provider and telephone-network interoperability
+ Voice-specific security, operational controls and service capabilities
- General IP network design except where it constrains voice delivery
- Physical telephone and headset construction
- Circuit-switched telephony beyond its interworking boundary with VoIP
- Video conferencing, messaging and collaboration features beyond shared voice dependencies
- Speech recognition, speech synthesis and interpretation of conversation content
- The telecommunications profession or its literature as separate registered things
Characteristics
- Implementation boundary
- endpoint pair, enterprise deployment, provider service, interconnection or other explicitly bounded implementation Determines which components, observations and actions the assessment covers.
- Signalling and session negotiation
- protocols, profiles, extensions and versions actually supported and negotiated Explains whether participants can establish, modify and terminate compatible voice sessions.
- Negotiated audio encoding
- codec, clock rate, channel count, packetisation interval and relevant negotiated parameters Connects endpoint compatibility, bandwidth demand and audio processing requirements.
- Media route
- endpoints linked through direct paths, relays, media anchors, transcoders or gateways Locates dependencies and explains why media can fail even when call signalling succeeds.
- One-way voice delay
- milliseconds, with direction, measurement boundaries, method and observation window Supports assessment of conversational responsiveness without confusing network transit time with full mouth-to-ear delay.
- Packet delivery impairment
- loss percentage, burst-loss pattern, delay variation in milliseconds and late-discard rate, with definitions and time window Helps distinguish transport impairment from endpoint or codec problems.
- Observed speech quality
- named listening or estimation method, score scale, direction and test conditions Prevents an unexplained quality score from being treated as universally comparable.
- Voice session outcome
- unavailable, setup failed, established without audio, one-way audio, degraded, usable or unexpectedly terminated Separates successful call establishment from successful voice communication.
- Protection coverage
- authentication and signalling/media protection recorded separately for each hop and termination point Makes trust boundaries visible and avoids mistaking hop protection for end-to-end confidentiality.
- Calling reachability
- supported identities, destinations, inbound routes and telephone-network interconnections Defines whom the service can actually reach and which provider or gateway dependencies apply.
Also called
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 6 bundles · 11 layers · 19 findings · 29 questions.
Voice service boundary Establishes which IP voice implementation is being modelled and the calling capabilities it actually offers.
VoIP names a technical approach spanning multiple deployment types, so an agent must establish the concrete service boundary before judging it.
IP voice identity
Identifies where voice media uses IP and separates that from adjacent communication technologies.
Voice bearer boundary
Record the IP-carried voice segments and any transitions to other bearer technologies.
- Which part of the voice media path is transported over IP, and what evidence establishes that? definition
- Where does responsibility pass to a circuit-switched network, another provider or an independently modelled service? boundary
Calling capabilities
Describes reachable parties and supported voice behaviours without assuming public telephone service.
Reachability and feature contract
Record supported destinations and features, distinguishing advertised support from verified operation.
- Which internal identities, external voice services and public telephone destinations can users call or receive calls from? boundary
- Which capabilities, such as transfer, hold, conferencing or emergency calling, have been verified, and against which service documentation? provenance
Session control and interworking Captures how calls are addressed, established, negotiated and connected across technical boundaries.
Voice failures frequently arise from differences between endpoint capabilities, signalling expectations and gateway behaviour.
Call establishment
Records identity resolution, signalling routes and session lifecycle behaviour.
Signalling contract
Record the actual signalling mechanisms, participating control services and negotiated session parameters.
- How is a called identity resolved to a destination, and which signalling components participate in setup and termination? definition
- Which call trace or provider specification establishes the protocols, extensions and session parameters in use? provenance
Endpoint and gateway compatibility
Examines voice negotiation and feature translation between unlike participants.
Negotiation and conversion
Record common audio capabilities and any translation needed for codecs, dialled identities or telephone event signalling.
- Which codecs and telephone event mechanisms can both sides use, and where are transcoding or other conversions required? boundary
- Which interoperability tests are needed before changing an endpoint, trunk, gateway or negotiated media profile? action
Media delivery and speech quality Follows voice from audio input through packet delivery to audible output and evaluates conversational usability.
A connected call can still deliver poor, missing or one-way audio, so voice delivery requires evidence independent of signalling success.
Audio processing path
Captures encoding, packetisation, buffering and audio processing along each direction of the call.
Audio processing budget
Record where encoding, buffering, transcoding and endpoint audio behaviour affect delay and intelligibility.
- What codec, packetisation interval, playout buffering and transcoding steps apply in each direction? definition
- How are endpoint processing delay, echo and clipping distinguished from packet-network impairments? measurement
Transport and listening evidence
Relates directional packet observations to measured or reported voice quality.
Conversational quality assessment
Record loss, delay variation, late packets and voice quality with their methods and operating conditions.
- What are the measured delay, packet loss, burst patterns and late-discard rates for each direction during representative calls? measurement
- Which listening test or quality estimation method supports the usability judgment, and what acceptance target applies? measurement
Network dependencies and continuity Records the infrastructure conditions needed for voice paths to remain reachable and adequately provisioned.
VoIP usability depends on media traversal, concurrent traffic and supporting services that may fail independently of the application.
Media reachability
Makes actual media paths and address-boundary traversal explicit.
Bidirectional media path
Record the route in each direction, including address translation, firewall rules, relays and media anchors.
- Which addresses, ports, transports and traversal mechanisms produce a working media path in each direction? definition
- What authorised diagnostic observation would distinguish blocked media, incorrect destination information and an endpoint audio fault? action
Capacity and failure behaviour
Examines expected call load, competing traffic and dependency failures.
Voice continuity envelope
Record the operating load and failure conditions under which required calling remains available.
- How many concurrent calls meet the chosen quality target under representative traffic, including packet overhead and any traffic prioritisation? measurement
- What happens to active calls and new calls when power, access connectivity, name resolution, call control or a media relay fails? measurement
Voice security and operational control Defines the trust boundaries, misuse controls and evidence needed to operate a voice service responsibly.
Call routing, voice confidentiality and diagnostic access expose different risks and require separately recorded controls.
Identity and media protection
Separates authentication, caller identity assertions and protection of signalling and speech.
Voice trust boundaries
Record who authenticates each participant, who asserts displayed identity and where protected traffic can be decrypted.
- How are endpoints and providers authenticated, and what evidence supports trusting a displayed caller identity? provenance
- Where do signalling and media protection terminate, and which intermediaries can access call metadata or intelligible speech? boundary
Abuse controls and diagnostics
Records controls over calling privileges and the handling of voice-related operational evidence.
Authorised voice operations
Record controls against unauthorised calling and service disruption, together with permissions for diagnostic data collection.
- Which destination restrictions, call-rate controls and alerts constrain unauthorised or excessive calling, and how can their effectiveness be tested? action
- Which call records, packet captures or recordings may an agent collect, and what access, consent and retention constraints apply? boundary
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- This describes VoIP as a technology family, rather than as an academic discipline; the registry records no narrower sense.
- The kinds overlap because they distinguish signalling, deployment and service arrangements.
- Standards are named from recall; jurisdiction-specific obligations and performance targets require verification for a particular deployment.
- Which of these check these first hold for the sense of Voice over IP this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- SIP-based telephony
- H.323-based telephony
- Hosted IP telephony
- On-premises IP PBX telephony
- Application-to-application voice calling
- IP trunking between telephone systems
- Which of these kinds and varieties hold for the sense of Voice over IP this model covers, and on what evidence? provenance
Identifiers and schemes
Recalled without web access and unsourced; every item is a lead to verify.
- SIP URI - sip:user@domain - Identifies a SIP communication resource; it need not correspond to a telephone number.
- ITU-T E.164 - International telephone number containing at most 15 digits - Used for telephone-number addressing where VoIP services interconnect with public telephone networks; not required for every VoIP endpoint.
- Which of these identifiers and schemes hold for the sense of Voice over IP this model covers, and on what evidence? provenance
Standards and regulation
Recalled without web access and unsourced; every item is a lead to verify.
- IETF RFC 3261: Session Initiation Protocol (SIP), used for session signalling.
- IETF RFC 3550: Real-time Transport Protocol (RTP), with RTCP for reporting and control.
- IETF RFC 3711: Secure Real-time Transport Protocol (SRTP), providing protection for real-time media.
- ITU-T Recommendation G.711: Pulse code modulation of voice frequencies.
- ITU-T Recommendation H.323: Packet-based multimedia communications systems.
- Which of these standards and regulation hold for the sense of Voice over IP this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Business telephone systems and contact centres
- Residential telephone service delivered over broadband
- Voice calling within messaging and collaboration applications
- Interconnection of PBXs and telephone service providers
- Remote extensions for employees working away from an office
- Which of these real-world use hold for the sense of Voice over IP this model covers, and on what evidence? provenance
Typical measurements
Recalled without web access and unsourced; every item is a lead to verify.
- G.711 encoded audio bit rate - 64 - kbit/s per direction, excluding transport overhead
- Voice packetization interval - 10-30, depending on codec and configuration - ms
- One-way mouth-to-ear delay - Below approximately 150 is a common conversational design target, not a guaranteed operating range - ms
- Which of these typical measurements hold for the sense of Voice over IP this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Packet loss, delay variation and excessive latency cause missing speech, distorted audio or difficult conversational turn-taking.
- NAT, firewall or signalling configuration problems can prevent calls or produce one-way audio.
- Loss of local power or network connectivity can interrupt service.
- Inadequate authentication or media protection can enable toll fraud, impersonation or eavesdropping.
- Emergency calls may fail or convey incorrect location information when endpoint location and emergency routing are not maintained.
- Which of these failure modes and hazards hold for the sense of Voice over IP this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Emergency calling, location reporting and service availability obligations vary by jurisdiction and service classification.
- Number allocation, number portability and interconnection requirements vary among national telephone systems.
- Some jurisdictions restrict particular VoIP services or require providers to hold telecommunications licences.
- Which of these regional variation hold for the sense of Voice over IP this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- IP telephony - Often used synonymously with VoIP; where distinguished, IP telephony includes the complete telephone service and its features, while VoIP describes voice transport technology.
- Circuit-switched telephony - Carries calls through allocated circuit resources rather than transporting speech as IP packets.
- SIP - A session signalling protocol; it does not itself encode or transport the voice media.
- RTP - A real-time media transport protocol used for voice and other media; it is one component of many VoIP systems.
- WebRTC - A framework for real-time audio, video and data communication that can implement VoIP but also supports non-voice communication.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of Voice over IP this model covers, and on what evidence? provenance
What the second pass must settle
- Does the registry intend Voice over IP to denote a technical approach, a service class or a field of knowledge, and does an existing Vercy model already own that concept?
- Which authoritative specifications and implementation documents should anchor the model's signalling, media, traversal and interworking terminology?
- Which deployment contexts and call scenarios should define representative quality targets and capacity tests?
- For any concrete service, which emergency-calling capabilities and jurisdiction-specific obligations apply, and what evidence verifies them?
- Which provider claims about interoperability, failover, caller identity and encryption can be independently verified, and which must remain explicitly unconfirmed?